Why Mountain Owl
FM handover is not a new problem. Buildings have always been handed over with incomplete operating programs. What is new is a practice built specifically to close that gap, with 25 years of FM experience on every side of the handover table and a methodology that already matched the funder's standard before we set out to meet it.
The Gap
Most FM handover work falls into one of two failure modes. Mountain Owl was built specifically because both of them are predictable and both are avoidable.
Failure Mode 1
A structurally correct framework is produced using generic industry templates. PM schedules reference equipment that may or may not be installed. Compliance calendars list obligations as TBC. The document looks complete. It is not usable.
Failure Mode 2
The GC's O&M manuals are forwarded as the handover package. The documentation is technically complete. It is organized by trade, written for tradespeople, and contains no integrated maintenance schedule, no capital plan, and no compliance calendar. The operator cannot use it without FM expertise they do not have.
Mountain Owl
Every data point drawn from the actual project documents. Maintenance obligations documented precisely, with consequences stated clearly. Compliance obligations tracked with due dates. The program the operator needs, built from the building they are actually managing.
The Difference in Practice
This is not a theoretical distinction. AI tools are widely available now, and we use them in our own work. But a closeout package is not something an owner can simply hand to a general tool and get a usable program back. We tested exactly that: the same building's information, run through general AI tools against the program we had already built by hand. The tools fell short, and the test was generous to them, because we fed them information we had already extracted and organized. A real owner starts with raw files and no map. The hard part was never generating the document. It is knowing what to feed in, what to ask for, and what is wrong in the output. That judgment is the work, and it sits upstream of any tool.
| Program element | Template / AI output | Mountain Owl |
|---|---|---|
| PM schedule tasks | 1 placeholder row | 68 tasks, sourced and verified |
| Warranty void conditions | Refer to manufacturer documentation | Documented precisely, full consequence stated |
| Compliance obligations | All listed as TBC | 63 obligations with dates and consequences |
| Asset register | Empty framework | 85 assets documented with full data |
| Warranties tracked | Refer to warranty documents | 53 warranties, colour-coded by expiry urgency |
| Capital plan | Structural framework only | 30-year plan with inflated cost estimates |
| Contact directory | Generic placeholder contacts | 76 verified contacts in 7 categories |
| Usable from day one | No | Yes |
The Approach
Every data point in a Mountain Owl program is traceable to a specific project document. We work through the shop drawings and submittals, the site instructions, and the change orders, and reconcile them against each other so the record matches what was actually installed. Maintenance obligations are documented precisely. The operator reads what is required and what the consequence of missing it is, not a paraphrase. When documents conflict, the conflict is resolved using a consistent hierarchy of authority and the discrepancy is flagged for the owner. Gaps are tracked. They are not quietly filled with plausible-sounding content.
The deliverables are written for the person running the building on Monday morning. Plain language. Actionable format. The difference between "consider reviewing the service contract" and "call the elevator contractor before January 8 or the warranty is void." The same standard on every engagement regardless of building type, size, or owner. The volume of documentation changes. The standard does not.
Experience
The FM Handover Program was built from 25 years of practice across sectors where the consequences of getting handover wrong are concrete: warranties expiring unclaimed, life safety systems missing scheduled inspections, capital reserves underfunded because nobody ran the numbers at possession.
Daniel Morris has been the contractor, the construction administrator, and the operations lead. He has managed capital budgets across sectors and taken new buildings from construction into operation across commercial, government, Indigenous, and residential projects throughout BC and Alberta. Mountain Owl was built on that experience.
SNC Lavalin O&M — where the approach began
The original concept was one Daniel developed here: preload building portfolios to support operations-and-maintenance takeover bids. It was never carried forward or put into use at the time. He has continued to develop and improve on that work ever since, and the FM Handover Program is what it has become.
FM Handover Program — seniors residence, BC Interior
37 suites, 4 storeys, BC Housing-funded. 85 assets, 68 PM tasks, 53 warranties, 63 compliance obligations, 30-year capital plan. Client anonymized; full sample on request.
Strathcona County Community Centre — Centre in the Park
A municipal community centre taken from construction into operations, including bringing the county library and family and community services into the building. That transition, from a finished building to a running one, is the core of what Mountain Owl now does at handover.
First Nations community facilities — BC Interior
Facilities and public works programs delivered for First Nations communities, including the Splatsin Community Centre and the Okanagan Indian Band, built to match each community's in-house maintenance capacity and resources.
If you want to see what a properly built handover program looks like, start with a 20-minute conversation and we will walk you through the sample. No commitment. The program either makes sense for your project or it does not.
Get in Touch