Government Cloud in Princeton, NJ

The obligations do not scale down with the staff: a three-person office holds records under the same retention and production duties, answers to the same audit standard and serves residents with the same entitlement as a department of three hundred. What scales is the build — this programme sizes the estate to the office (the governed ground, the named access, the producible archive, the plain monthly report) without the enterprise apparatus around it. The genuinely unaffordable option is the accidental estate at the moment of examination: the three-week records request, the unexplainable bill, the departed vendor’s live account. Small offices are exactly where public-grade discipline pays fastest, because there is no depth of staff to absorb its absence.

Respectfully, and in the open: the strategy phase produces documents a board can act on — scope in plain language, phases costed against the budget process, the obligations each control answers named — so the procurement file shows its reasoning rather than merely its winner. Phasing follows the budget cycle rather than fighting it, and the monthly operating report is written for the same audience that approved the purchase, in language that survives being read aloud in session. A public body should never have to defend a technology purchase it cannot explain; this programme’s paperwork is designed so that it always can.

That is a design requirement, not a hope: the archive is structured by the body’s retention schedules, productions are retrievals from indexed ground rather than excavations through inboxes, and the production itself is logged — what was produced, what was withheld under which provision, by whom — so the answer is defensible as well as fast. During the build, a sample request is run against the new estate as an acceptance test, timed. If your last request took weeks, bring its details to the first conversation; it becomes the benchmark the design is measured against, in writing.

Documents written for them: the obligations inventory (what the body owes, in law and in policy), the strategy (what will be built, in which phases, at what cost, answering which obligation), and thereafter a monthly state report in plain language — posture, incidents, costs, waste named, access changes listed — that can be minuted without translation. Hard questions in public session are this programme’s home ground, because every claim in those documents traces to a control, a log or a test the board can ask to see. The estates that fear the meeting are the ones whose answers live in somebody’s memory.

That is determined in the obligations inventory, from your body’s actual situation — the records and privacy duties in your governing law and funding terms, the payment rules if you take cards, the state and sector requirements your auditors already cite — rather than from a vendor’s generic list. Controls are then engineered to those frameworks and evidenced as they operate, so the audit is answered from standing records. This programme will also tell you, in writing, where a fashionable framework does NOT apply to a body of your kind; public money spent answering imaginary obligations is still public money spent.

The exit is contractual and architectural from the start: records held in exportable forms, the estate’s documentation (configurations, access register, retention structures) maintained as the body’s own records, and departure assistance specified rather than improvised. A public body’s records must outlive any vendor, including this one — administrations change, contracts lapse, and the archive’s continuity is the body’s obligation, not the provider’s favour. Ask every bidder the same question and compare the paperwork; it is the fastest diligence in this field.

The obligations inventory and strategy are a defined engagement, producing the phased, costed documents for your budget process. Build phases are priced against the obligations they discharge, and operations are a standing rhythm sized to a small estate — with the monthly report naming waste as it is removed, so the operating line defends itself in session. The honest comparison includes the accidental estate’s hidden ledger: staff weeks lost to records excavations, audit findings and their remediation under deadline, the incident whose cost arrives all at once. Public-grade ground, phased to a public budget, is priced against that ledger — and usually wins it.