Commissioning certificates are the formal sign-offs that close each stage of completion for a system or subsystem, from mechanical completion through commissioning to handover. A typical sequence is Mechanical Completion Certificate (MCC), Ready for Commissioning (RFC), Ready for Start-Up (RFSU) and Take-Over or handover Certificate (TOC). Each certificate records that defined evidence exists and that the system can safely move to the next stage.
Certificate names, the number of stages and even the order vary between owners, contractors and industries. Treat the sequence below as a typical example and check your project's completions procedure for the exact chain you are working to.
Why certificates exist at all
A large project may have tens of thousands of tags and ITRs. Nobody at a stage-gate meeting can review that detail system by system. Certificates compress it: a signed MCC says "every mechanical completion record for this subsystem is complete and accepted, and the open punch items are only of a category that is allowed at this stage".
Certificates also mark changes in responsibility and risk. When a system moves from construction to commissioning, control of the work, the permit regime and the risk profile all change. When it is handed over, care, custody and control pass to the owner. A certificate is the point at which people put their names to that change.
The typical certificate sequence
| Stage | Certificate | What it certifies | Typical prerequisites | Punch allowed open |
|---|---|---|---|---|
| Construction complete | Mechanical Completion Certificate (MCC) | System or subsystem installed to drawings and specifications | All A ITRs complete and accepted; test packs closed; walkdown done | B and C only |
| Pre-commissioning complete | Ready for Commissioning (RFC or RFCC) | System tested and fit to be energised or receive media | MCC issued; all B ITRs complete; flushing and cleaning closed; procedures approved | B and C only, reviewed |
| Commissioning complete | Ready for Start-Up (RFSU) | System ready for introduction of process fluids and operation | RFC issued; commissioning procedures executed; safety systems proven; pre-start-up safety review closed | Items agreed as non-safety-critical |
| Handover | Take-Over / Transfer of Care, Custody and Control (TOC) | Owner or operator accepts the system | RFSU issued or start-up achieved; handover dossier accepted; exceptions agreed | Agreed exceptions list |
| Contract close | Final or provisional acceptance (names vary) | Contractual acceptance of the works | Performance or reliability tests met; punch closed; documentation complete | None, or as contract allows |
Punch categories follow the same caveat. A common convention is that Category A items must be cleared before mechanical completion and Category B before start-up or handover, with C items allowed to run on. Your project may use different letters, a Category D, or different rules. Our guide to punch list categories A, B and C covers this in more detail.
Mechanical Completion Certificate (MCC)
The MCC confirms that a system or subsystem has been installed in accordance with the design and is ready for pre-commissioning. It is normally issued per subsystem so that commissioning can start on the first subsystems while construction carries on elsewhere.
Prerequisites usually include completed and accepted A ITRs for every tag, closed pressure test packs, a joint walkdown with the commissioning team and owner, and a punch list with no open Category A items. Some projects add intermediate records before the MCC, such as a mechanical completion check record summarising discipline status, or discipline acceptance certificates. For the detail, see mechanical completion explained.
Ready for Commissioning (RFC) certificate
The RFC certificate confirms that pre-commissioning is finished and the system can be energised or receive utilities and media. It sits between the static world of construction and the live world of commissioning, so it is the gate that most directly protects people.
Typical prerequisites:
- MCC issued for the subsystem
- All B ITRs complete, with witnessed tests signed by the required parties
- Flushing, cleaning, drying and reinstatement complete; temporary strainers and blinds logged
- Loop checks and electrical tests complete
- System boundaries and isolation points defined and marked
- Commissioning procedures approved
- Permit-to-work and isolation arrangements in place for the live system
The difference between the work before and after this certificate is set out in pre-commissioning vs commissioning.
Ready for Start-Up (RFSU) certificate
The RFSU certificate confirms that a system has been commissioned and is ready for introduction of hydrocarbons, process chemicals or its normal operating duty. On many projects it is the point at which operations becomes the dominant voice in the sign-off.
Prerequisites typically include the RFC, executed commissioning procedures with results accepted, proven safety systems (shutdown, fire and gas, relief), a pre-start-up safety review or equivalent, operating procedures issued, operators trained, and the remaining punch list agreed as not affecting safe start-up. Some owners issue RFSU per system; others issue it per unit or facility once all contributing systems are ready.
Take-Over Certificate (TOC) and handover
The TOC, sometimes called a handover certificate or transfer of care, custody and control, records that the owner or operator has accepted responsibility for the system. From this point, the owner's permit system usually governs work, and any remaining contractor work is done under the owner's control.
The TOC normally depends on an accepted handover dossier: certificates, ITRs, test records, punch status, vendor data, as-built drawings, operating and maintenance manuals, and spares information. Exceptions are recorded on the certificate or an attached list, with owners and target dates.
Some frameworks split this further. OPERCOM-style approaches, for example, use stage gates such as ready for commissioning, acceptance for operation and transfer to maintenance or operations. Final or provisional acceptance certificates may then close the contract after performance testing.
Other certificates you may meet
Depending on the owner and the industry, your chain may also include:
- Discipline acceptance certificates – each discipline confirms its scope is complete before the system-level MCC.
- System handover certificates – construction hands a system to the commissioning team, separate from the MCC.
- Energisation certificates – specifically for electrical systems before first energisation.
- Ready for operation or acceptance for operation – after start-up, confirming stable operation.
- Final acceptance certificates – at the end of the defects or warranty period.
None of these is universal. What matters is that the chain is written down in the completions procedure, including prerequisites, signatories and allowed punch categories for each certificate.
Why the chain has to be enforced
Most certificate problems are not about missing certificates. They are about certificates issued out of order or ahead of the evidence:
- An RFC signed for a subsystem whose MCC is still waiting on two A ITRs, "because they'll be done this week".
- An MCC issued with Category A punch items re-graded to B the night before the stage-gate meeting.
- A TOC signed with half the handover dossier missing, on the promise that documents will follow.
- A certificate issued against an old system boundary after a late systemisation change.
Each is understandable under schedule pressure, and each moves risk to people who did not agree to carry it. The commissioning team inherits construction defects; operations inherit undocumented equipment.
An enforced dependency chain removes the grey area. If the system will not generate an RFC while any prerequisite record is open, the conversation changes from "can we sign this?" to "what exactly is outstanding and who is closing it?". Where an exception is genuinely justified, it becomes a documented deviation with an approver, rather than a quiet signature.
Checklist for each certificate
- The certificate is issued against a defined system or subsystem boundary
- Every prerequisite certificate for that boundary is issued
- All required ITRs for every tag within the boundary are complete and accepted
- Open punch items are only of categories permitted at this stage
- Signatories match the completions procedure
- Any exceptions are listed with owner, action and target date
- The certificate and its supporting records are retrievable for the handover dossier
Managing this in Accord
Accord enforces its certificate chain — MCCR → DAC → MCC → SHC → RFCC → AOC → RFSU → TOC/TOM → PTC — as a directed acyclic graph, so a certificate cannot be issued until its prerequisites are in place. Certificates sit on a project, system, subsystem and tag hierarchy, with A and B ITRs, witnessing and Category A/B/C punch items that can block stage gates. Terminology, stage gates and certificate types are configurable to your sector, and certificate change requests go through an approval workflow. Per-system handover dossiers track required documents and compile locked archives. To see it against your own chain, contact us.
Frequently asked questions
What is the difference between RFC and RFSU?
RFC (Ready for Commissioning) confirms pre-commissioning is complete and a system can be energised or receive utilities. RFSU (Ready for Start-Up) comes later and confirms commissioning is complete and the system is ready for process fluids and normal operation. RFSU normally requires the RFC and additional safety and operational readiness checks.
What does a TOC certificate mean?
A TOC, or take-over certificate, records that the owner or operator accepts care, custody and control of a system or facility. It is usually supported by a handover dossier and a list of agreed exceptions. Some projects call it a handover certificate or transfer of care, custody and control.
What is the handover certificate sequence?
A typical sequence is MCC, RFC, RFSU, TOC and then a contractual final or provisional acceptance. Many owners add intermediate certificates such as discipline acceptance or system handover certificates. The exact sequence is set by the project's completions procedure and contract.
Are commissioning certificates issued per system or per facility?
MCC and RFC are usually issued per subsystem so work can progress in parallel. RFSU and TOC may be issued per system, per unit or per facility, depending on how the owner wants to start up and take over the plant.
Can a certificate be issued with open punch items?
Yes, provided the open items are of a category the procedure allows at that stage and are listed on the certificate. Category A items typically block mechanical completion; allowing them through requires a formal, approved deviation.