The chiller on the south building has been making a noise since Tuesday morning. The vendor's tech showed up Thursday, said it was probably a bearing, ordered the part, and promised a return visit Monday. Your CMMS now has the work order, the vendor name, and the open status. What it doesn't show: that this is the third bearing on this unit in eighteen months, that the warranty conversation with the manufacturer is still open from the last replacement, and that your boss asked last quarter whether it was worth replacing the whole unit before next summer.
Most facilities operations have this shape. The CMMS handles work orders, preventive maintenance schedules, and asset records. The actual operational memory — the running threads with vendors, the warranty disputes, the institutional knowledge about why this building's HVAC is the way it is — usually lives in someone's email folder, a binder in a closet, and the senior tech's head.
This post is about turning that scattered operational memory into a workspace that holds the parts the CMMS doesn't.
What facilities management actually needs from a notes system
The shape is specific:
- Building-level continuity — the running thread for each property, the open issues, the deferred maintenance, the recent work, the warranty status of major equipment
- Vendor relationships that span work orders — the HVAC company you've used for eight years with three open issues, the new electrical contractor you're trying out, the manufacturer you're in a warranty dispute with
- Equipment biographies — every major asset with a history of work, the serial-number quirks, the recall notices, the actual service intervals (not the manufacturer's optimistic version)
- Cross-building pattern recognition — every rooftop unit of this model with the same failure mode, every elevator in the portfolio approaching the same modernization cycle
- Compliance and inspection memory — fire marshal visits, elevator certifications, environmental reporting, pressure-vessel inspections — what was flagged, what was resolved, what's coming up
- Capital planning context — the running list of we should replace this notes that need to feed next year's budget conversation
Plus: it has to be usable on a phone in a basement mechanical room. The senior tech who's actually opening up an air handler needs to be able to look up the last service date and the relevant SOP without leaving the work area. Adjacent shapes — fleet-of-physical-assets and SOP rot — are in How to Use AI Notes for Fleet Management and Standard Operating Procedures, Without the Wiki Maintenance Tax.
Page-per-building, with a vendor vault alongside
In Docapybara, every building gets a top-level markdown page. The title is the building identifier — South Tower, 1450 Oak Street. Page nesting holds the structure underneath: equipment, vendors, open issues, capital plan, compliance.
Separately, every vendor and major piece of equipment gets its own page. A common shape:
Buildings → South Tower → Equipment, Open Issues, Vendors, Compliance, Capital PlanBuildings → South Tower → Equipment → one page per major asset (chiller, AHU, boiler, elevator, fire panel, BMS)Vendors → by trade — HVAC, Electrical, Plumbing, Elevator, Fire/Life Safety, Roofing, Janitorial — one page per vendorManufacturers → one page per major equipment manufacturer (warranty status, parts contact, recall history)Compliance → by category — Fire, Elevator, Pressure Vessels, Environmental — with sub-pages for each cycleCapital Plan → by year, with running notes that feed the budget conversation
Plain markdown means the pages stay searchable, copyable, and exportable. If you transition the portfolio to a new property manager, the operational memory comes with it as text anyone can read.
A live database for open issues and equipment health
Embed a :::database::: directive on the building's Open Issues page. Six column types — text, number, date, select, checkbox, link — cover the work. A typical issues board:
| Asset |
Issue |
Reported |
Vendor |
Status |
Warranty |
Last Update |
| Chiller CH-2 |
Bearing noise (3rd in 18mo) |
2026-04-23 |
Carrier-DFW |
Part on order |
In dispute |
2026-04-25 |
| AHU-7 |
VFD intermittent fault |
2026-04-19 |
ABM |
Diagnostic scheduled |
N/A |
2026-04-22 |
| Elevator #3 |
Door safety edge |
2026-04-21 |
OTIS |
Tech onsite tomorrow |
N/A |
2026-04-25 |
Sort by reported date, you see the backlog. Filter by status, you see what's stalled. Filter by warranty, you see what needs a manufacturer push.
The same shape works for an Equipment Health board — one row per major asset, columns for last service, next due, condition rating, warranty end, replacement budget year. Sort by next-due-date, the preventive-maintenance picture is right there. The CMMS may already track this; the workspace version is the analytical layer where you can actually read across it and make decisions.
The agent reads across the whole portfolio
Capy, the assistant inside the workspace, reads across every building, vendor, and asset when you ask. The kinds of questions facilities operations actually have to answer fast:
- "Across the portfolio, how many rooftop units do I have on the same Trane platform that had the bearing issue last year?" — cross-building retrieval
- "What's the running warranty thread with Carrier on the South Tower chiller?" — pulls the vendor and equipment pages
- "List every elevator in the portfolio with a state inspection due in the next 90 days." — reads the compliance database
- "Draft an executive summary for tomorrow's portfolio review: top three open issues per building, three biggest vendor disputes, three capital items that should be in next year's plan."
The agent reads the relevant pages, drafts the summary, you adjust. The portfolio review prep that took a long Sunday becomes an hour of reviewing what the workspace already knows. The agent-acts-on-docs differentiator is described in Claude Code for Documents.
Recording the vendor conversations that need to survive
Most vendor calls don't need recording. Some do. The post-failure debrief with the chiller manufacturer when warranty is on the table. The walk-through with a new general contractor for a major capital project. The annual vendor review with your largest service provider. The owners-rep meeting where commitments are being made.
Audio with speaker labels keeps each speaker attributable on replay. Drop the recording on the vendor's page. The transcript drops in alongside. Tomorrow when you're drafting the warranty escalation letter and you need the exact words the manufacturer's rep used, the answer is searchable text rather than a half-remembered impression of a Tuesday call.
The recording question is a workflow choice — what's appropriate to record, what consent looks like, what gets retained. Once that's settled, the workspace just holds whatever you decide to capture.
Old O&M manuals, drawings, and warranty PDFs
Facilities accumulates paper by the building. O&M manuals, equipment cut sheets, warranty certificates, as-built drawings, inspection reports, manufacturer recall notices, the original commissioning report from when the building opened. They're useful when findable and a problem when not.
Drop the PDFs into the relevant equipment or building page. Each one converts to markdown automatically, which means the agent can read across them. When you ask "what does the chiller's O&M manual say about bearing replacement intervals?", the agent pulls the relevant section as text. When the warranty rep argues the failure is outside coverage, you can pull the original warranty terms in seconds.
For a long-tenured facilities team, this is often the single highest-leverage day of work. The institutional memory locked in binders nobody opens becomes searchable in an afternoon.
The compliance calendar nobody wants to forget
Compliance is the part of facilities work where forgetting hurts. Fire panel certification overdue. Elevator inspection lapsed. Boiler test missed. Backflow prevention not done. The dates are scattered across emails from inspectors, certificates in binders, and notices nobody filed.
A :::database::: on the Compliance page with columns for asset, certification type, issuer, last completed, next due, status, contact gives you the running picture. Sort by next due, you see the next 90 days. When the agent reads it, "what compliance items are due in the next 60 days, by building?" returns the list. You assign owners, schedule the work, file the certificates back to the workspace as PDFs when complete.
The workspace doesn't replace whatever official compliance system the jurisdiction or the carrier requires. It does mean the data isn't sitting in three different places when the inspector walks in. The audit-prep version of this shape is covered in AI Notes for Compliance and Audit Preparation.
The capital planning page that actually feeds the budget
Most facilities teams build the capital plan in October from a combination of email notes, sticky notes, and the senior tech's memory. The workspace alternative: a Capital Plan page per building that gets updated continuously as issues come up.
Every time a major piece of equipment shows a sign of approaching end-of-life, you add a one-line note to the capital page: Chiller CH-2 — third bearing failure in 18 months. Likely candidate for replacement before summer 2027. Current rough order $180–220K based on Carrier's prior quote on similar unit.
By October, the capital page is already the rough draft of the conversation. Ask the agent: "Draft next year's capital recommendations for South Tower based on the running notes in the capital plan page. Group by likelihood and rough cost." The draft comes back. You refine, get vendor quotes for the top items, and walk into the budget conversation with something defensible.
Try Docapybara free
The fastest test: pick the building where you have the most active operational issues right now. Open Docapybara, create the building page, drop in your last month of work-order notes and any relevant PDFs, and build an Open Issues database from what's currently outstanding. Try Docapybara free, bring one building's worth of operational mess and a stack of warranty PDFs nobody can find, and see whether the workspace can hold the parts of facilities work the CMMS leaves on the floor.