Mechanical Complete, Commissioning Ready, or Accepted? Three Evidence Gates for Modular Booth Handoff

Direct answer: three labels, three different decisions

Mechanical complete, commissioning ready, and accepted must not be used as three ways of saying that a modular booth is finished. Each label needs a stable Gate ID, an identified physical scope, a named state, a controlled evidence index, an open-item rule, and the project-appointed authority for that exact decision.

Mechanical complete answers a physical-definition question: is the named booth, module, zone, interface, or mechanical work package assembled to the controlled mechanical basis in the recorded configuration, with excluded work, temporary conditions, protection, deviations, and open items visible? It does not say that utilities are available, controls are ready, functional behavior has been demonstrated, or the work has been contractually accepted.

Commissioning ready answers a prerequisite question: are the approved inputs for one identified commissioning activity available in the required state? The record must name the system or subsystem boundary, location, procedure, site interfaces, responsible participants, instruments or test equipment where applicable, restrictions, and unresolved items. Readiness is not evidence that the activity has been executed or passed.

Accepted answers an authority question: has the person or organization appointed by the controlling project documents made the defined decision for a named scope, state, criteria set, evidence package, and residual-open-item list? An acceptance record cannot silently expand from one module, interface, test, or deliverable to the complete booth.

There is no universal order or one-time sequence supplied here. The actual project may phase by module, zone, subsystem, location, delivery package, or commissioning activity. It may repeat a gate after change, use conditional release, or place different scopes at different gates on the same date. The title separates three decision types; it does not prescribe a schedule.

The non-transfer rule is simple: evidence closes only the question it actually answers. Installed hardware does not prove commissioning readiness. Readiness does not prove a test result. A test result does not automatically prove contractual acceptance. None of these records by itself proves leakage, ventilation, exposure, fire, electrical, controls, structural, acoustic, environmental, safety, code, or regulatory performance. Those subjects retain their own design, test, compliance, and decision authorities.

Do not reuse one gate outcome across unlike scopes. A mechanical-complete module can be adjacent to an incomplete site seam. A subsystem can be ready for one approved check while another interface is held. One delivery package can have a recorded acceptance decision while later work remains outside that decision. The matrix must preserve those boundaries with separate Gate IDs and explicit relationships; a project dashboard may summarize them only without erasing the underlying scope, state, evidence, conditions, and authority.

Lock one Gate ID, scope, state, and document basis

Do not issue a gate against the word booth alone. Define the project, booth ID, module or zone, system or subsystem where relevant, physical location, configuration, drawing/model/register revision, and date or event state. Name the included work and interfaces. Identify excluded work, customer- or third-party-supplied items, temporary supports, shipping braces, protection, access restrictions, damage, substitutions, field changes, and incomplete connections that remain present.

Create a controlled Gate Evidence Index. For every drawing, model, schedule, procedure, supplier record, installation record, check sheet, deviation, nonconformance, punch item, photograph when required, test record, manual, or decision record, list the identifier, revision, status, issuer, purpose, and applicable Gate ID. State which representation controls if files conflict. An as-built markup may record installed condition without becoming the design authority for an unapproved change.

ISO 16792:2021 is publicly titled around digital product-definition data practices.^[1] That subject supports controlled identity and status when the framework is invoked, but the official record does not prescribe this evidence index, decide file precedence, approve an as-built condition, define any of the three gates, assign authority, or establish conformity.

The module shipping and local-assembly guide is useful for identifying separated modules, connection kits, packing states, and local assembly boundaries. This article begins after those boundaries are named and asks what evidence closes a particular handoff decision. The linked guide does not establish completion, readiness, acceptance, or performance for the current scope.

Gate scope must also name the physical state. Installed can mean temporarily held, partially connected, mechanically fixed, protected for later work, or complete only within one supplier's package. Replace the loose word with the actual condition. If access panels, guards, filters, doors, ducts, fan equipment, lights, controls, services, or finishes are outside the gate, list them rather than allowing readers to assume that a photographed enclosure includes them.

Gate 1: record mechanical completion without extending its meaning

A mechanical-complete record starts with the controlled physical definition. Depending on the written scope, that may include identified modules, panel joints, doors, frames, supports, penetrations, fasteners, gaskets or sealant interfaces, equipment mounting provisions, guards, access components, and mechanical connections. This list is not a default booth checklist. The project selects what belongs in the Gate ID and which characteristics must be checked.

For every included item or interface, record identity, location, revision, installed state, required characteristic, check source, result, deviation, and disposition. Distinguish presence from condition: a component count can show that named items were found; it cannot prove alignment, fastening state, clearance, hidden continuity, structural adequacy, or functional behavior. Likewise, a photograph can document visible configuration without establishing an unobserved or unmeasured characteristic.

ISO 10012:2003 is publicly titled for measurement-management systems, measurement processes, and measuring equipment.^[2] Its subject supports keeping a result tied to the object or measurand, physical state, method and equipment identity, criterion, and responsible decision. The public record supplies no booth measurement method, sampling, calibration result, uncertainty, tolerance, pass value, acceptance decision, certification, or StelBooth capability.

The mechanical record needs an explicit temporary-state section. List clamps, braces, covers, blanks, caps, transport aids, protective films, temporary power or service connections, and unfinished site interfaces that affect condition or access. Name who owns removal or conversion, the due event, and what evidence must follow. Mechanical completion for a defined shop package can coexist with an open site connection only if the gate definition and appointed authority explicitly permit that condition.

Open items cannot be hidden behind minor punch list. Give each item an ID, location, description, affected requirement and gate, current condition, owner, due event, evidence needed for closure, and the authority deciding whether it blocks this Gate ID. This article supplies no universal rule about which defect, missing item, or incomplete interface may remain open.

Use the coordinated equipment-package guide to distinguish who supplies each module, component, accessory, or adjacent system. Supply allocation does not itself prove mechanical completion. The gate must still show what arrived, what was installed, what remains outside scope, and who can disposition a mismatch.

Mechanical complete therefore means only: the identified mechanical scope has a reconstructable state and decision under the project definition. It does not mean commissioned, ready to energize or operate, safe for every activity, leak-tested, balanced, exposure-controlled, fire-approved, electrically complete, structurally certified, regulator-approved, accepted, or delivered without conditions.

Gate 2: define readiness for one commissioning activity

Commissioning readiness begins with an Activity ID, not a general statement that the booth can be commissioned. Identify the exact system or subsystem, physical and functional boundary, location, configuration, intended activity, procedure revision, prerequisites, participants, witness/review roles, result record, and decision authority. If several activities have different prerequisites, give them separate readiness rows.

Mills describes building commissioning as a systems-level, team process that goes beyond the presence of equipment and can include installation, testing, problem correction, performance intent, information, and operational participants.^[3] That paper focuses on building energy commissioning and its own evidence. It does not define a modular spray-booth gate, activity list, test value, ventilation or exposure result, fire or electrical criterion, regulatory decision, or StelBooth service.

For B1, the bounded lesson is that commissioning readiness must point forward to a defined process and evidence route. It cannot be inferred from a clean-looking installation. Record the current commissioning plan or procedure, the system configuration it assumes, prerequisites, approved design and supplier inputs, method and equipment records where applicable, personnel roles, site access, temporary controls, restrictions, and the result/disposition path.

Site interfaces require their own precondition status. Depending on the named activity, relevant interfaces may include physical connection, service availability, isolation, controls communication, exhaust or duct interfaces, drainage, access, temporary provisions, or another project-selected condition. This list selects no utility, sequence, test, or value. Use the site utilities and interface-responsibility guide to define each boundary and owner before a readiness decision. That guide does not prove that an interface is available or authorized for use.

Do not write FAT passed, SAT complete, site tested, or integrated without the test object and boundary. The public title and scope of BS EN IEC 62381:2024 distinguish factory acceptance, factory integration, site acceptance, and site integration tests for process-industry automation systems.^[4] That source supports explicit Test ID, location, object, requirement set, and result boundary. Its automation scope supplies no booth-wide gate sequence, commissioning procedure, value, pass result, electrical or controls compliance, contractual acceptance, or capability.

A readiness review should separate five states:

• required and verified prerequisite: evidence is identified, current, and accepted by the authority assigned to that prerequisite;
• required but open: the activity cannot proceed under the current gate definition unless an authorized conditional route exists;
• not applicable to this Activity ID: the appointed authority records why;
• restriction during the activity: the condition, owner, monitoring or control source, and stop/disposition route are named by the project; and
• future requirement: relevant to another activity or gate but not evidence for the present decision.

These are editorial record labels, not a universal permit-to-work or safety scheme. The project risk, electrical, controls, ventilation, fire, exposure, site, and regulatory authorities define their own prerequisites and authorizations. A commissioning ready entry cannot create one.

The Gate 2 decision is ready, conditional, or held only for the named Activity ID and boundary. It does not say that the activity passed, that the complete booth can operate, or that downstream acceptance criteria are satisfied.

Gate 3: record acceptance as an appointed decision

Acceptance must point to the contract or controlled project document that defines the accepted object, required state, criteria, evidence, decision authority, and effect of the decision. Do not assume that the customer is one universal signatory. A customer's project manager, owner representative, designer, commissioning authority, quality reviewer, site operator, regulator, or specialist may have different appointments, and this article cannot combine or assign them.

Build the acceptance package from the exact requirements for that scope. It may reference controlled drawings and as-built records, completed check or test results, deviations and nonconformances, manuals, training records, spares, warranties, certificates, open-item dispositions, or other deliverables only when the project requires them. A missing document should remain visible; it must not be replaced by a generic completion certificate invented for this article.

The public purpose of BS EN ISO/IEC 17050-1:2004 describes a supplier's declaration of conformity as referring to an identified object and specified requirements while making the declaring responsibility visible.^[5] That supports keeping the declaration object, claim, issuer, and basis explicit. It does not turn a supplier declaration into customer acceptance, third-party certification, regulatory approval, a test record outside its scope, or proof of an unclaimed booth performance.

The acceptance decision record should include Gate ID, accepted scope and state, criteria source, evidence-index revision, excluded decisions, residual open-item list, conditions, appointed authority, decision, date, and retained record. If acceptance is partial, conditional, sectional, provisional, or subject to later work, use only the term and effect defined by the controlling contract. This article assigns none of those effects.

Acceptance also has a firewall. Contractual acceptance of a delivery package does not automatically establish regulatory approval, occupational exposure control, fire safety, ventilation performance, electrical conformity, structural adequacy, or operational authorization. Each required decision must remain traceable to its own authority and evidence.

Use the Three-Gate Handoff Evidence Matrix

Create one matrix row per Gate ID and physical or activity scope. Do not use a single project-wide row if modules, zones, interfaces, systems, procedures, or authorities differ.

For each row, complete the following control fields:

BS ISO 21502:2020 publicly provides project-management guidance applicable across organizations and project types, regardless of delivery approach or life-cycle model.^[6] That broad scope supports tying the matrix to the actual project basis. It does not prescribe these three gates, their order, a punch-list rule, a booth contract, customer signatory authority, completion criteria, regulatory approval, or outcome.

Read the matrix left to right before issuing a gate: is the scope defined, is the physical state reconstructable, is every prerequisite or check attached to a controlled source, and are open items dispositioned by the right authority? Read it right to left during audit: does the decision trace to evidence for the same object, configuration, location, date, and state? A break in either path holds that Gate ID; it does not necessarily decide another gate.

Hold, reopen, and prepare the handoff package

Hold the affected gate when scope, state, revision, source precedence, site interface, procedure, criterion, method/equipment record, result, open-item effect, or appointed authority is missing or conflicting. Hold when a record for one module or subsystem is presented as evidence for the complete booth, or when a readiness statement is being used as a pass result.

Reopen after a scope, configuration, location, drawing/model, procedure, test boundary, site-interface, supplier item, installation, damage, repair, substitution, nonconformance, result, evidence-validity, contract, or authority change. Record which evidence is invalidated and which decision must be made again. Reopen does not automatically reject, retest, rework, accept, or withdraw another gate.

The drawing-handoff discipline used for fabricated tanks is an adjacent example of keeping revisions, owners, and open inputs visible. It supplies no booth completion definition, commissioning procedure, acceptance criterion, authority, or performance result.

For review, send the gate definitions, scope and interface registers, controlled drawing/model index, supplier and installation records, site-interface status, commissioning plan/procedures where applicable, check/test index, deviations, nonconformances, open-item register, required deliverables, and authority matrix through the StelBooth project inquiry. Sending the package does not prove readiness, acceptance, regulatory approval, or StelBooth capability.

The final stop line is exact: if the team cannot identify which decision is being made, for which physical object and state, from which controlled evidence, with which open items, and by which appointed authority, the label is not ready to issue.

References

1. International Organization for Standardization, ISO 16792:2021, Technical product documentation - Digital product definition data practices. Official ISO catalogue record. Public title and subject only; no B1 gate, file hierarchy, approval, authority, applicability, conformity, or retention is supplied. Back to citation
2. International Organization for Standardization, ISO 10012:2003, Measurement management systems - Requirements for measurement processes and measuring equipment. Official ISO catalogue record. Public title and subject only; no booth method, calibration result, uncertainty, sampling, value, acceptance, certification, or capability is supplied. Back to citation
3. Evan Mills, Building commissioning: a golden opportunity for reducing energy costs and greenhouse gas emissions in the United States, Energy Efficiency 4(2), 145-173 (2011). Publisher DOI record. Introduction and Commissioning defined section only for the bounded systems/process distinction; no booth gate, value, performance, compliance, acceptance, or capability is supplied. Back to citation
4. BSI, BS EN IEC 62381:2024 - TC, Automation systems in the process industry - Factory acceptance test (FAT), site acceptance test (SAT), and site integration test (SIT). DOI standards record. Public title and scope only; process-industry automation does not provide a booth-wide sequence, test, value, pass result, compliance decision, acceptance, or capability. Back to citation
5. BSI, BS EN ISO/IEC 17050-1:2004, Conformity assessment - Supplier's declaration of conformity - Part 1: General requirements. DOI standards record. Public abstract and purpose only; a scoped supplier declaration is not automatically customer acceptance, certification, regulatory approval, or proof beyond its stated object and requirements. Back to citation
6. BSI, BS ISO 21502:2020, Project, programme and portfolio management - Guidance on project management. DOI standards record. Public title and scope only; no B1 gate, order, punch-list rule, contract, signatory, completion criterion, approval, or outcome is supplied. Back to citation