For county, city, and school district finance and property teams
Property records that hold up when someone asks.
The Documentation Center turns fragmented property documentation into a standardized, retrievable record — built from patterns found in real government audit findings, not guesswork.
Built for finance, asset management, facilities, schools, and grant/program teams.
Discuss a Documentation Pilot →Where property documentation actually breaks down
- An asset exists, but the record doesn't — or doesn't match what's actually on the shelf.
- Custody and location aren't clearly assigned, so no one's sure who's responsible.
- An asset is surplused or transferred with no closing paperwork, and inventory never catches up.
- Condition and maintenance history lives in someone's memory, not on paper.
- When an audit, grant review, or loss event happens, staff reconstruct records after the fact instead of producing them.
What a completed record looks like
Two views of the same asset — the record itself, and an honest read on how complete it is. Sample data, shown to make the structure concrete.
Sample record — illustrative
HVAC Unit #04
Municipal Operations Building
- Facility
- Municipal Operations Building
- Asset name / ID
- HVAC Unit #04
- Location
- Building A, Mechanical Room
- Last verified
- 08/12/2026
- Condition
- Good
- Photos
- 14
- Service records
- 6
- Responsible department
- Facilities
- Documentation status
- Complete
Documentation Health
The same record, scored by category. Not everything is green — that is the point.
- OwnershipVerified
- LocationVerified
- ConditionVerified
- PhotosVerified
- MaintenanceNeeds update
- CustodianVerified
- Supporting recordsMissing
Documentation completeness: 71%
5 of 7 categories verified. Maintenance history is stale; supporting records were never filed.
What changes
Before
- Spreadsheets
- Photos on phones
- Email attachments
- Paper files
- Staff memory
- Disconnected records
After
One structured property record
- What exists
- Where it is
- What condition it's in
- What happened
- Who documented it
- When it was documented
- Supporting evidence
Who it's for
Finance / CFO
"Can we prove what we own, what it costs, and why the next investment is necessary?"
A property record that answers the question with documents rather than estimates — before a board, an auditor, or a budget cycle asks it.
Property / Asset Manager
"Can we produce the record when someone asks for it?"
Not reconstruct it, not go looking for it — produce it. Indexed, consistent, and the same shape across every department.
Facilities Director
"Can the person taking over this facility understand its history without calling three people?"
Condition, maintenance, incidents and custody in one place, so institutional knowledge survives the person who held it.
This isn't another CMMS
- Not work-order management.
- Not an ERP replacement.
- Not procurement software.
- Not facilities scheduling.
It's the documentation layer — the record those systems assume you already have.
Built around documented government problems
Each item below is a published finding from a metro-Atlanta county's internal audit function, reviewed as part of an ongoing research program. They are quoted because they are real, not because they are representative.
The sample, stated plainly: 27 audit documents reviewed across 5 Georgia counties. 19 findings recorded; 9 contained asset, inventory or custody content. Those 9 come from 4 independent sources inside a single county's internal audit office, spanning 2015–2026. That is the entire evidence base. It is not a survey, and it is not large enough to claim these patterns are typical of government generally.
Audit finding Roughly 250 surplus water meters were stolen from a storage facility the audit found lacked surveillance and required only a key for entry. The same review found the required annual physical inventory count had not been performed that year.
Documentation gap With no current count, the loss was not detectable from the records themselves.
Evidence requirement A periodic verification that produces a dated, retrievable result.
What the kit structures A scheduled verification log attached to each asset record, so a missing count is visible before a loss is.
Audit finding At a county-funded institution, available records and labeling did not clearly distinguish pieces owned by the county from those owned by the organization housing them.
Documentation gap Ownership was not determinable from the record or the item.
Evidence requirement Ownership attributable per item, on the record and on the object.
What the kit structures Identification fields that tie item to owner to supporting evidence, rather than assuming custody implies ownership.
Audit finding A county airport had fifteen tenants; only twelve leases could be produced.
Documentation gap The document set was incomplete, and nothing made the incompleteness visible.
Evidence requirement Completeness legible against the set that should exist.
What the kit structures An index showing what should be on file beside what is, so gaps surface without an audit to find them.
What makes these worth acting on isn't how many there are. It's that four unrelated departments — a water utility, an airport, a museum, and a juvenile court — produced the same shape of failure across eleven years, inside one organization. That points at a documentation practice, not four unlucky departments.
What this research does not establish
An audit finding does not automatically mean a documentation kit addresses it. Some findings point to policy, training, staffing, or governance changes instead — and a kit would not fix those. Part of what this research tries to do is tell those apart: distinguishing an actual documentation problem from a problem that merely produces documentation symptoms.
The evidence base above is one county's internal audit function. We have not established that these patterns hold across other jurisdictions, and we don't claim it. The research is expanding; we will say so plainly when that changes.
Start with a documentation pilot
Pick one department, one property class, or one documentation gap. We build the structure, your team uses it against real records, and you decide whether it's worth expanding.
Discuss a Documentation Pilot →More detail on the research behind this, the kit structure, and what it does and doesn't do: see the overview or the kits.