The breakdown
Commissioning scopes are usually sold as a capability and settled later as an argument. This page is the opposite: the documents that land, the order the work happens in, what is needed from your side, and what deliberately sits outside the fee.
A Level 3 and Level 4 package for one building typically arrives as a single reviewed set, in your platform's format.
Installation, termination, labelling, torque and settings verification written against that asset's submittal rather than a generic template. Every device on the list gets its own sheet.
Step-by-step sequences with expected values, acceptance criteria and a sign-off line for each. Written so a competent technician who has never seen the building can run them and a witness can follow along.
One narrative that the switchgear, generator, UPS and controls procedures all agree with — including the timing windows that only matter when a transfer is happening and nobody has time to look anything up.
Every contradiction found between submittals, drawings and vendor procedures, written down with a recommendation. In practice this is the part clients quote back to their vendors, and often the part that pays for the package.
Where a Level 5 framework is in scope: step loading, rejection, paralleling and failure scenarios sequenced so the integrated test proves something rather than merely finishing.
A single-building package runs about two working weeks. Larger and phased scopes stretch the middle, not the shape.
Submittal set, one-lines, the sequence of operation, and the asset list. A short call to establish what the owner actually cares about proving, which is not always what the specification says.
Vendor procedures read side by side against the submittals. This is where the contradictions surface, and where the issues log gets written. Anything that looks like a genuine design question is raised immediately rather than saved for the report.
Checklists and functional procedures written into your platform, in your numbering, so they drop into the program without anybody rekeying them.
A working session over the draft, revisions inside the same window, and the issues log walked through line by line. Revisions arising from that review are included.
Short list, and the package cannot start without the first three.
The sequence of operation does not need to be finished. Half the value of the reconciliation is finding out where it stops matching the equipment that actually got bought — so send the version that exists, not the version you wish existed.
Named here rather than discovered at invoice.
Every engagement runs under a written scope of work, priced on deliverables and dates rather than hours. Professional and general liability are placed at engagement. No client's confidential methods or materials ever carry between projects — what travels is pattern and standard, and nothing else.
That is enough to put a band, a fee and a date against the work — usually within a day, and before anybody commits to anything.