A practical guide / Building services
O&M manuals: what goes in them and how AI speeds them up
An O&M manual (operation and maintenance manual) tells the client how to run, maintain and repair what was installed. Yes. Use AI to prepare an O&M pack index, match asset references to product manuals and draft a handover gap list. Begin with one building services system and its checked installed asset list.
O&M means operation and maintenance. Use the asset list as the route into the pack. Link each item to its manual and test records. The example below follows two fan units. It shows how to turn a bundle of files into a clear list of what to collect.
Use the handover promptUse the asset tag to find the right handover record.
Start with the assets actually installed
Prepare a schedule with system, asset tag, place, maker, model, serial number where relevant and site record ID. Use the site team’s confirmed record as the starting point. Put contract needs for the handover pack beside it.
More on this step
Ask the assistant to sort the files against that list. Use fields for file title, model covered, version, file path and match status. For a changed product, keep the site change record. If the asset list and product label differ, send a query to the installer with both sources.
Build an index that a facilities team can use
Try these pack headings: system overview, asset list, product guides, commissioning and test records, drawings, warranties, contacts and open items. Adapt them to the contract and the client’s handover needs.
More on this step
Keep the CDM health and safety file identified separately in the file index. HSE’s L153 guidance describes information needed for safe future construction work and distinguishes the file from general operating material. Use the index to direct readers to the right record, with a clear asset tag or system reference at each link.
Read the source: HSE: CDM guidance, including the health and safety file
Make each gap a clear request
Ask for a gap list with asset tag, missing record, files checked, query, supplier and due date. Flag whether a file is absent or covers the wrong model. Add the contract or agreed handover requirement behind each request.
More on this step
HSE’s construction guidance describes the health and safety file for projects with more than one contractor. Where needed, track that file with the project team as a distinct handover item. For the O&M pack, agree who accepts each record. Note acceptance in the file index.
Read the source: HSE: construction records and administration
Worked example
Two fan units and three document queries
Example with made-up details: the installed ventilation schedule lists V01 as model AX200 and V02 as AX250. The bundle contains an AX200 manual, a second copy of that manual and a commissioning sheet for V01.
The draft index matches the AX200 manual to V01 and flags the duplicate. It raises two file requests for V02: the AX250 manual and its commissioning record. A third query asks whether the duplicate was intended to refer to another file. The handover lead can send each query with an asset tag and the document names already checked. Keep the source files linked while the suppliers respond.
Illustrative example.
Installed schedule
Confirm the model and location.
Document index
Match assets to original files.
Gap requests
Name the missing record and supplier.
Try a practical task
Create an asset-led handover index
Use a sample asset list and file list to prepare your first index.
Try this in your AI app
ChatGPT
Claude
Gemini
CodexUsing Gemini? The button copies the prompt. Paste it into the new chat.
Act as the file manager for a building services handover. Match the installed asset list to the product manuals, drawings and commissioning records. Use exact asset tags and model numbers. Flag uncertain matches in a separate query field.
Draft an O&M contents list grouped by system, then an asset index with file title, revision, file path and reason for match. Prepare a supplier gap list for missing or conflicting records, identifying which files you examined.
Keep the CDM health and safety file listed separately where it forms part of the given handover needs. Keep original product instructions and test results. Refer questions about service intervals and conflicting technical limits to the engineer.
What a related public reporting example shows
Iain Davidson carries out health, safety and security audits for luxury hotels. He built an app that connects audit evidence and findings to a repeatable report structure. It helped him produce a 70-page first client report, and he refined it for other hotel sites.
For an O&M pack, the useful link is the route from source material to a structured document that the recipient can use.
Read the source: Public story: Iain Davidson, hotel audit records and reporting
Keep product instructions and approval with the project team
HSE’s maintenance guidance emphasises the use of maker’s instructions when planning equipment maintenance. Keep those instructions and have the relevant engineer resolve model conflicts, service limits and technical gaps. Use the project’s agreed acceptance process for the finished pack.
Use AI to sort the pack and draft its index. Keep test results, safe isolation steps and service needs with the right specialists and source files. Use approved tools for contract and contact details. Before issue, follow a sample of asset links to the files. Confirm that the client can open them at the delivered paths.
Read the source: HSE: maintenance of work equipment
Questions about this task
What should the first pack cover?
Choose one system with a confirmed asset list. Produce an index and supplier gap list, then ask the handover lead to resolve the matches.
How should we treat a summary of a product manual?
Keep it as a short guide linked to the source file. Ask the engineer to check technical wording and keep the maker’s instructions in the delivered pack.