No. 30

One database across the building life cycle

Context
Point of view
Year
2026
Type
Approach
Tools
Layer

Every phase of a building's life re-creates the same information in a different tool. I think a project should be one structured database that every role reads in its own way, and that this is what will make AI useful to a firm.

Today an assessment lives in a spreadsheet and a folder of photographs, the design in Revit and a drawing set, construction in submittal and field apps, and operations in a work-order system. Each handover retypes what the last phase already knew, and each role keeps its own copy.

If every room, element and document is a record with an id that never changes, that stops. The owner, the architect, the engineer, the contractor and the facility manager read the same records in their own views, and the reports each of them issues are printed from the data instead of assembled by hand.

This matters more with AI, not less. An AI agent can only answer a question across projects if the data is structured and the ids hold. With that in place a firm could ask which rooms depart from its standard, or pull every casework specification it has used, and an owner, architect and contractor could exchange by id instead of retyping.

Two pieces of my own work test parts of this. Room Data Sheets carries one database from room standards to issued sheets. From model and site data to a place you can walk carries one id from a Revit element to a playable model and its record.

I have not run a building this way from start to finish. I believe in it, I build it in Layer, and I am curious to try it on a live project.

01

Every role, every phase, one set of records

01

Every role, every phase, one set of records Three bands across a building's life: Assess, Build and Maintain, holding six phases: Assessments (condition assessments, facility audits, building surveys; tools today: spreadsheets, PDF reports), Planning (programming, room data sheets, equipment planning; tools today: programming tools), Design (team coordination, drawing markups, FF&E; tools today: Revit, drawing sets), Construction (RFIs, project closeout, field reports; tools today: submittal and field apps), Operations (asset tracking, space management, property inspections; tools today: CMMS), Maintenance (compliance inspections, work requests, warranty tracking; tools today: work-order systems). Seven roles and the workflows each touches. Owner: condition assessments, facility audits, programming, project closeout, asset tracking, space management, property inspections and warranty tracking; Architect: condition assessments, building surveys, programming, room data sheets, team coordination, drawing markups, RFIs, project closeout and field reports; Interior designer: room data sheets, equipment planning, drawing markups, FF&E and field reports; Engineer: building surveys, equipment planning, team coordination, RFIs and compliance inspections; Contractor: RFIs, project closeout, field reports and work requests; Facility manager: facility audits, asset tracking, space management, property inspections, compliance inspections, work requests and warranty tracking; Preservation architect: condition assessments, building surveys and drawing markups. Beneath every phase, one continuous line: One structured project database: every room, element and document a record with a stable id. From it, reports and documents printed from the data, and AI agents and APIs reaching any data in any phase. A return arrow runs from the end back to the start: Reassess: the next cycle starts with the whole project history. ASSESS BUILD MAINTAIN Assessments Planning Design Construction Operations Maintenance Condition assessments Facility audits Building surveys Programming Room data sheets Equipment planning Team coordination Drawing markups FF&E RFIs Project closeout Field reports Asset tracking Space management Property inspections Compliance inspections Work requests Warranty tracking Owner Architect Interior designer Engineer Contractor Facility manager Preservation architect TOOLS TODAY Spreadsheets, PDF reports Programming tools Revit, drawing sets Submittal and field apps CMMS Work-order systems One structured project database: every room, element and document a record with a stable id Reports and documents printed from the data AI agents and APIs: any data, any phase Reassess: the next cycle starts with the whole project history
Every role, every phase, one set of records Stacked version. Three bands across a building's life: Assess, Build and Maintain, holding six phases: Assessments (condition assessments, facility audits, building surveys; tools today: spreadsheets, PDF reports), Planning (programming, room data sheets, equipment planning; tools today: programming tools), Design (team coordination, drawing markups, FF&E; tools today: Revit, drawing sets), Construction (RFIs, project closeout, field reports; tools today: submittal and field apps), Operations (asset tracking, space management, property inspections; tools today: CMMS), Maintenance (compliance inspections, work requests, warranty tracking; tools today: work-order systems). Seven roles and the workflows each touches. Owner: condition assessments, facility audits, programming, project closeout, asset tracking, space management, property inspections and warranty tracking; Architect: condition assessments, building surveys, programming, room data sheets, team coordination, drawing markups, RFIs, project closeout and field reports; Interior designer: room data sheets, equipment planning, drawing markups, FF&E and field reports; Engineer: building surveys, equipment planning, team coordination, RFIs and compliance inspections; Contractor: RFIs, project closeout, field reports and work requests; Facility manager: facility audits, asset tracking, space management, property inspections, compliance inspections, work requests and warranty tracking; Preservation architect: condition assessments, building surveys and drawing markups. Beneath every phase, one continuous line: One structured project database: every room, element and document a record with a stable id. From it, reports and documents printed from the data, and AI agents and APIs reaching any data in any phase. A return arrow runs from the end back to the start: Reassess: the next cycle starts with the whole project history. ROLES O Owner A Architect I Interior designer E Engineer C Contractor F Facility manager P Preservation architect ASSESS Assessments O A I E C F P Condition assessments Facility audits Building surveys Tools today: spreadsheets, PDF reports BUILD Planning O A I E C F P Programming Room data sheets Equipment planning Tools today: programming tools Design O A I E C F P Team coordination Drawing markups FF&E Tools today: Revit, drawing sets Construction O A I E C F P RFIs Project closeout Field reports Tools today: submittal and field apps MAINTAIN Operations O A I E C F P Asset tracking Space management Property inspections Tools today: CMMS Maintenance O A I E C F P Compliance inspections Work requests Warranty tracking Tools today: work-order systems One structured project database: every room, element and document a record with a stable id Reports and documents printed from the data AI agents and APIs: any data, any phase Reassess: the next cycle starts with the whole project history
Who touches which workflow across a building's life, and the one database beneath them. Adapted from a diagram I made for Layer's website.