Space and lease management systems: floor plans, occupancy, and GASB 87 data

Reference article · 5 min read

Facilities and real property offices usually run on two sets of records that were never designed to work together. Drawings and space inventories sit with the CAD group or the architect of record. Leases sit with real estate, legal, and finance, often as scanned PDFs in a shared folder with a tracking spreadsheet beside them. An integrated workplace management system (IWMS) or computer-aided facility management (CAFM) system is meant to hold both. Whether it earns trust depends far less on the feature list than on whether the data inside stays current enough that staff stop keeping private side copies.

The lease half of the system now carries accounting consequences. Under GASB Statement No. 87, most leases are reported as financings of a right to use an underlying asset, which means the system has to support numbers that end up in audited financial statements. That changes the standard a facilities system is held to. It has to be right, and it has to be able to show its work.

The space record: plans, rooms, and assignments

A trustworthy space inventory is built from a few linked pieces:

• A current base plan for every floor. The plan should carry closed polygons for each space, so area is calculated from geometry rather than typed in from a memo.
• A stable space identifier. Building, floor, and room numbering that survives renovations. Renumbering a floor breaks history, chargeback, and any link to work orders or asset records.
• A consistent classification and measurement basis. Office, workstation, conference, storage, mechanical, circulation, and a documented standard for usable versus rentable or gross area. Mixed standards across a portfolio quietly corrupt every rollup.
• Assignment. Department or cost center, program, and where relevant the funding source that pays for the space.
• Chargeback method. The rate basis and how common area is allocated. Write the method down in policy, not only in a configuration screen.

Occupancy and utilization, handled carefully

Utilization data usually comes from badge readers, room reservation systems, network association, or occupancy sensors. Each source measures something slightly different, and none of them measures headcount directly. Decide up front what question you are answering: peak demand, average daily presence, or whether a specific room is worth keeping.

Badge and network data are personnel data. Before wiring them into a facilities dashboard, confirm retention limits, aggregation thresholds that prevent identifying individuals, public records exposure, and any labor agreement obligations. Many agencies choose to store only aggregated counts in the facilities system and leave the raw records in the access control system under its own controls.

What a defensible lease record contains

For each lease, both as lessee and as lessor, the system should hold the executed document and the structured fields that come from it: premises and the space records they map to, commencement and expiration dates, termination rights, renewal and purchase options with their notice deadlines, the base payment schedule, escalation terms including index-based increases, and variable payments such as common area maintenance or utilities. It should also hold the judgments, not just the facts: whether the arrangement is a lease at all, whether it qualifies for the short-term exclusion, the lease term concluded including options reasonably certain of exercise, and the discount rate used with a note on its basis.

Why these systems lose credibility

Two failure modes account for most of it.

Drawings drift after every remodel. The fix is procedural. Require as-built drawings as a contract deliverable in construction and tenant improvement contracts, in a named file format and layer standard, and make acceptance of the project contingent on receiving them. Assign one person responsibility for updating the space polygons and reassigning departments at project closeout. Audit a sample of floors on a schedule by walking them.

Lease data stays in the spreadsheet. Usually because the spreadsheet is faster and nobody verified the migrated records. Migrate once, verify every field against the source document, run one reporting period in parallel, then retire the spreadsheet and restrict who can alter a payment schedule. Alerts on option notice deadlines are the feature that makes people prefer the system.

What GASB 87 asks the system to produce

Confirm specifics with the pronouncements themselves, your auditors, and your finance office, since implementation guidance continues to evolve. In general, the system should be able to generate:

• Initial measurement of the lease liability at the present value of expected payments over the lease term, and the corresponding right-to-use asset.
• Period amortization schedules splitting interest and principal, reproducible for any prior period.
• Remeasurement when the lease term changes, when the assessment of an option changes, or when payment estimates change, with the superseded schedule retained.
• Support for note disclosures, including lease assets by major class, accumulated amortization, variable payments not included in the liability, and future principal and interest requirements presented for coming years and in later increments.
• An audit trail linking every figure to a document and an approver.

Related standards cover public-private partnerships and subscription-based information technology arrangements, which use similar mechanics. Ask whether the same module handles them.

What to ask vendors and put in the contract

1. Demonstrate with our data: one complicated lease and one floor that was recently remodeled.
2. Show a mid-term remeasurement and the retained prior schedule.
3. Explain how space area is derived, and whether the drawing link survives replacing the CAD or BIM file.
4. Describe the journal entry output and how it reaches our financial system.

In the contract, specify migration scope and who verifies records against source documents, tie acceptance to a reconciled portfolio rather than a go-live date, and require full export of leases, schedules, and drawings in usable formats at no additional charge. Address hosting, security review expectations, and accessibility conformance documentation.

HQT is a technology and software company serving United States state and local government agencies, with work spanning software development, data integration, and technology advisory support for enterprise systems of this kind.

Frequently asked questions