Three bound documents leave an integrator's shop on a typical job, and they get mixed up constantly: the submittal package, the O&M manual, and the turnover package. They look similar. They share content. Mixing them up costs real money, because each one is due at a different moment and answers to a different reader.
The fastest way to keep them straight is to notice that each answers a different question.
The submittal package: "here is what we intend to supply"
Due: before you build or buy. Reader: the reviewing engineer.
The submittal is a proposal in document form. It goes out early, before fabrication, so the engineer can catch a wrong component while it is still a paperwork problem instead of a mounted-in-the-panel problem. It gets reviewed, stamped, maybe revised, and eventually approved. What that approval lets you do depends on the stamp and the project documents. Either way, the returned copy is the record of what the engineer reviewed.
Contents in brief: equipment schedule, shop drawings, datasheets with the supplied catalog number marked, certifications. The full breakdown is in what goes in a control system submittal package.
The O&M manual: "here is how to run and fix it"
Due: at or near substantial completion, often as a precondition of it. Reader: the operator and the maintenance tech, for the next twenty years.
The Operations and Maintenance manual is written for the people who inherit the system. The engineer may review it, but its real audience is the operator at 2 a.m. with an alarm on the screen and the maintenance tech looking for a replacement part number.
That changes what belongs in it:
- Overview and safety information for the installed system
- The station or panel bill of materials: what is actually in each enclosure
- Panel drawings, corrected to as-built where things changed
- Component datasheets, so the tech can find the replacement part
- Manufacturer O&M literature for the supplied hardware
- Test records, calibration sheets, and commissioning results where the spec requires them
The datasheets overlap with the submittal, which tempts people to reuse the submittal wholesale. Resist it. The submittal was organized for a reviewer verifying compliance. The O&M manual should be organized for someone standing in front of a specific panel, which usually means per-panel chapters rather than per-spec-section ones.
The turnover package: "here is the record of what you own now"
Due: at closeout, before whatever acceptance or payment milestone the project documents name. Reader: the owner's records, and whoever touches the system in ten years.
The turnover package (some specs say closeout package) is the full record set handed over at the end: as-built drawings with every field redline incorporated, as-left program and configuration files, the O&M manuals, test and commissioning records, warranty documents, license information, and spare parts documentation.
The O&M manual is inside the turnover package; it's one named item on the list. The turnover package is the container for everything, and its contents are defined by the contract's closeout section, so read that section at the start of the job, not the end. Items like training videos or spare parts have long lead times, and discovering them the week before final payment is how closeout drags on for months.
The one-glance table
| Submittal package | O&M manual | Turnover package | |
|---|---|---|---|
| Question it answers | What will you supply? | How do I run and fix it? | What is the complete record? |
| When | Before build/buy | At substantial completion | At closeout |
| Reader | Reviewing engineer | Operator, maintenance tech | Owner's records |
| Gets stamped? | Yes, reviewed and returned | Sometimes reviewed | Accepted, not stamped |
| Organized by | Spec section | Site and panel | The contract's closeout list |
Where jobs go wrong
Two failure patterns account for most of the pain.
Building the O&M manual from scratch in the last week. Everything the manual needs existed months earlier, in the submittal and in the field records. The structure and the process that avoids the last-week scramble are in how to build a control panel O&M manual, and the rest of the closeout set is in the closeout checklist.
Treating the record casually. Every one of these documents becomes evidence eventually. Which revision of the submittal did the engineer approve? Which drawings went in the turnover package? When the question comes up years later, "the folder on the server" is not an answer, because the folder kept changing. Whatever your tooling, keep the issued copy of each document frozen exactly as it went out, with the date and the response. A numbering scheme that holds up is part of that; see submittal numbering and revision schemes.
How Submittal Kit handles this
These three documents share content, and retyping it between them is where they drift apart. In Submittal Kit, submittal packages and O&M manuals both read from the project's Equipment Register, and a manual created from an issued submittal shares its equipment list live, so the manual is assembled from what the engineer already approved. The turnover package itself is your contract's list, but its pieces can go out as closeout packages typed O&M Manual, Warranty, or Record Documents. Every package you issue, manual included, becomes a numbered revision on the Submittal Log whose files never change afterward, which answers "which revision did the engineer approve" years later. See O&M manuals and Issue a revision.
Disclosure: I build Submittal Kit, and these distinctions hold no matter what assembles the documents.