What if a control system is fully installed but still isn’t ready to operate? At RIBA Stage 5, equipment being in place is only part of the picture. RIBA stage 5 commissioning services establish whether controls, software and connected systems work together as intended, with test results and clear evidence to support handover.
Responsibilities can become blurred between installation, integration, commissioning and handover, particularly when control systems depend on inputs from several project disciplines. If teams leave interfaces and dependencies unresolved, defects may surface late, putting operational readiness under pressure.
This article explains what specialist control systems commissioning should deliver, how to define responsibilities and acceptance evidence, and why coordination with other disciplines matters. It also shows how carrying design knowledge into Stage 5 can link design intent with site testing and system integration. In complex environments such as airports, where control systems support demanding operations, a structured approach helps teams understand what has been tested and what remains unresolved.
Key Takeaways
- Distinguish Stage 5 construction activity from commissioning outcomes, so installation progress isn’t mistaken for proof of system performance.
- RIBA stage 5 commissioning services should connect design intent to coordinated testing of SCADA, PLCs, field devices and bespoke software.
- Map stakeholder responsibilities and system interfaces early, then link acceptance criteria and test evidence to project requirements.
- Use a sequenced commissioning plan that accounts for dependencies, readiness and site access conditions.
- Continuity from design into Stage 5 can help carry key control system decisions through integration and towards handover.
What RIBA Stage 5 commissioning services mean for control systems
RIBA Stage 5 covers manufacturing and construction, when the designed system is delivered and installed. Commissioning is a distinct outcome within this work: evidence that the installed controls perform their intended functions across components and interfaces. RIBA stage 5 commissioning services therefore go beyond confirming that equipment is present or powered. They verify how the configured system behaves against relevant design information and project requirements.
Stage 5 control systems commissioning is the planned verification of installed control equipment, software and interfaces against defined requirements. It records test results to inform acceptance and handover. This establishes how the system performs under the conditions tested, without guaranteeing defect-free operation in every future circumstance.
The RIBA Plan of Work organises project activity into stages, but it doesn’t prescribe one universal commissioning package for every control system. Scope, test methods and acceptance evidence need to reflect the design, system architecture and operational requirements. Commissioning is a structured way to verify performance, not simply another name for construction completion.
Where commissioning sits within RIBA Stage 5
Commissioning depends on both design information and installation progress. The team needs enough detail to identify intended sequences, interfaces and expected responses. Site work must also have progressed to the point where relevant equipment can be tested safely and meaningfully. If either is incomplete, testing may be limited or need repeating once outstanding work is resolved.
Construction completion records that work has reached a defined project milestone. It doesn’t, by itself, demonstrate that connected controls operate as intended. Stage 5 commissioning generates test evidence to support the transition to Stage 6, Handover. Later activities, such as observing system performance in use, are distinct from verifying the installed system during construction.
Why control systems need specialist attention
Individual devices can appear functional when checked in isolation, yet the overall control response may depend on correct signals, logic, communications and operator interfaces. For example, a sensor reading needs to be interpreted correctly by the controller and represented appropriately in the supervisory system. Commissioning examines these relationships rather than treating each installed item as a separate endpoint.
In an airport environment, SCADA may bring information from multiple control systems together for monitoring and response. Testing should consider how a change or alarm travels across relevant interfaces, not just whether a field device or screen works independently. The required sequence and checks depend on the project design and operational context.
That systems view starts with coordinated design decisions, including how controls are structured and how they relate to wider project requirements. AAC LTD | All About Control’s control systems design consultancy carries this engineering perspective across RIBA Stages 1 to 5, linking design intent with practical verification as systems are installed and integrated.
What RIBA Stage 5 control systems commissioning covers
Stage 5 control systems commissioning takes the approved design and checks, in a planned sequence, whether the installed and integrated system responds as intended. The work typically moves from design review and installation readiness to integration tests, functional tests and recorded outcomes. Activities depend on project requirements and system architecture, so RIBA stage 5 commissioning services should be defined for the project rather than treated as a standard, interchangeable package.
Clear boundaries matter. Installation teams carry out physical work such as fitting, wiring and connecting equipment within their agreed scope. Commissioning verifies that equipment and configured functions operate correctly within the wider system. Some activities may overlap, but the project team should agree who prepares equipment for testing, performs each test, resolves findings and accepts the evidence. A responsibility matrix makes these interfaces visible before testing begins.
From design intent to integrated system tests
Testing should trace back to approved control narratives, functional requirements and relevant design information. These define what the system is meant to do and provide a basis for choosing test scenarios. The aim isn’t to test every possible operating condition, but to establish that agreed functions and interfaces behave as required under the project’s specified conditions.
Depending on the system, checks may follow a signal from a field device through a PLC and into a SCADA display, or verify how an alarm is generated, presented and acknowledged. Sequence tests check that intended actions occur in the correct order. Interface tests examine information exchanged between connected systems, including whether a status or command is interpreted consistently at each boundary.
Interface testing matters because connected components can each pass individual checks whilst the information or commands exchanged between them still fail to produce the intended system response.
Changes made during construction need to be reflected in the test basis. If an approved design change alters a sequence, signal allocation or software configuration, update the relevant test scenario and records. Keeping the current design, configuration and test documentation aligned helps prevent teams accepting a system against superseded assumptions.
Commissioning evidence and defect resolution
Useful evidence records what was tested, under what conditions, what result was observed and whether it met the agreed acceptance criterion. An issue log can identify the finding, its priority, the responsible party and the action required. The evidence format should suit the project. No single certificate or document is appropriate to every control systems commissioning scope.
Findings need a controlled route to resolution. Assign corrective work, update relevant records where required, then repeat the affected test. If a change could affect connected functions, retesting may need to extend beyond the component directly altered. This keeps acceptance grounded in evidence and supports a clear handover record.
AAC LTD | All About Control provides control systems design and automation engineering expertise to help project teams align test scope and system interfaces with project requirements.
How commissioning coordinates stakeholders, interfaces and acceptance
Control system commissioning depends on coordinated contributions, not a test plan prepared in isolation. The client sets operational priorities and participates in acceptance decisions; the designer clarifies intended functions; the integrator coordinates system logic and interfaces; installers confirm that equipment and connections are ready for testing. Other disciplines contribute when their systems or activities affect a test. RIBA stage 5 commissioning services work best when responsibilities, dependencies and evidence requirements are agreed before testing begins.
The framework below is illustrative, not a fixed allocation of contractual duties. Project scope and appointments determine who undertakes each task.
Illustrative responsibility and evidence framework
| Participant | Typical contribution | Evidence or input |
|---|---|---|
| Client or operator | Defines operational priorities and reviews results against agreed acceptance criteria | Requirements, review comments and acceptance decisions |
| Designer | Explains design intent and clarifies functional requirements | Approved design information and responses to technical queries |
| Integrator | Coordinates control logic, system interfaces and test execution within its scope | Test procedures, results and records of configuration changes |
| Installer | Completes and confirms relevant installation work before testing | Readiness information and records relevant to its work |
| Other disciplines | Support tests involving connected systems or shared dependencies | Interface inputs, agreed access and test participation |
Managing control system interfaces across disciplines
Start by listing each interface within the project scope, naming the parties responsible for technical input and test coordination. On an airport project, this might include baggage handling or another operational system where the connection is part of the design. Record dependencies such as required signals, system availability, access arrangements and the sequence for testing connected functions. This makes potential clashes visible early enough to plan around them.
Live airport environments require careful coordination of test windows, permissions and operational constraints. Planning can reduce avoidable disruption, but can’t guarantee uninterrupted operation. The test approach must reflect site conditions and the operator’s arrangements. AAC LTD | All About Control’s strategic airport SCADA integration guide explores wider considerations for connecting operational technology.
Agreeing acceptance criteria before testing
Each test should point to an agreed functional requirement or documented project outcome, with a result that can be assessed consistently. The project should also establish who reviews evidence, who approves technical results and how outstanding issues are considered. If a test fails, assign an owner and define a route to resolution. Keep unresolved items visible in acceptance discussions rather than obscuring them with overall completion figures.
Technical test completion and operational acceptance are related but distinct. A system may have completed its defined tests whilst the client’s wider process still considers operational readiness, procedures or other handover matters. Clear governance connects these decisions without treating a passed test as automatic approval for every aspect of use.
A practical sequence for RIBA Stage 5 commissioning
A commissioning sequence turns project requirements into controlled checks, with clear decision points before the team moves from readiness review to testing and handover preparation. The order matters: an integrated function can’t be meaningfully tested until its prerequisites are in place, and access to connected systems may depend on construction progress or operational conditions. RIBA stage 5 commissioning services should be planned around project dependencies, not just a convenient calendar.
Prepare the system and commissioning plan
Align the commissioning scope with design intent, system boundaries and each party’s interface responsibilities. Review prerequisites, including relevant equipment, software configurations, current drawings and supporting records. With stakeholders, define test scenarios, recording methods, access arrangements and escalation routes. This preparation helps distinguish a genuine system issue from a test that couldn’t proceed because a dependency or readiness condition was missing.
Adapt a practical sequence to the project:
- Align scope and responsibilities. Confirm which systems and functions are included, who prepares them for testing and who coordinates each interface.
- Review readiness. Check that required installation work is complete, relevant equipment is available, software configurations are identified and test prerequisites are met.
- Set the test order. Arrange checks so dependent components and interfaces are available in a workable sequence. Agree access windows with relevant project and operational stakeholders.
- Run agreed tests. Follow planned scenarios, record results against acceptance criteria and note limitations or unexpected behaviour as they arise.
- Resolve and retest. Assign failed tests for corrective action, document relevant changes and repeat affected checks. Extend retesting where a change could influence connected functions.
- Prepare handover information. Assemble final test records and relevant configuration and operating information, with unresolved items clearly identified for review.
Test order should reflect actual dependencies, not an assumed universal progression. For example, a higher-level supervisory function may rely on verified signals or communications from lower-level equipment. If a test window is constrained, identify which prerequisites must be satisfied beforehand and what evidence can be captured during the available access period. Site conditions may require changes to the sequence. Record those changes so stakeholders understand what was tested and what remains outstanding.
Test, resolve and prepare for handover
Testing and operational transition are connected, but they aren’t the same activity. Technical commissioning produces evidence about defined system functions. The client’s operational transition may also involve internal procedures, staff preparation and wider project decisions. Coordinate these workstreams so technical results inform readiness discussions, without treating a completed test schedule as automatic approval for use.
Before handover, check that records identify the tested configuration and clearly document test outcomes, corrective actions and retests. This gives the receiving team a practical account of verified system functions and any open matters requiring attention.
AAC provides control systems design and automation engineering across RIBA Stages 1 to 5, helping teams connect design intent with commissioning and handover requirements.
How AAC supports RIBA Stage 5 commissioning services
AAC’s control systems design experience across RIBA Stages 1 to 5 provides continuity between early design decisions and the practical demands of Stage 5. That continuity helps project teams keep the purpose behind system functions in view as equipment is installed, interfaces are coordinated and commissioning is planned. RIBA stage 5 commissioning services benefit from understanding how a system was intended to operate, not just what has been assembled on site.
Design continuity for complex control systems
Earlier design information is a useful reference when commissioning questions arise: why a function was specified, which systems it depends on and which project requirements it supports. AAC’s control systems design and automation engineering consultancy carries this knowledge through the project stages, supporting technical coordination as the installed system is prepared for verification.
This perspective is particularly relevant to airport environments, where control systems may need to work across multiple operational interfaces. AAC delivers specialist engineering solutions for airport environments and works with mission-critical control systems and SCADA integration. This experience informs a considered approach to system boundaries and project dependencies; each system still needs to be tested against its project requirements and actual configuration.
Where bespoke software forms part of the agreed project scope, consider its role alongside the wider control system. Commissioning planning can account for how configured functions relate to field inputs, controller behaviour and supervisory interfaces, assessing software as part of the system rather than in isolation.
Discussing a project’s commissioning requirements
A productive technical discussion can start with three practical points: the project’s current RIBA stage, the control system boundaries and the systems or disciplines it must interface with. Stakeholders can then clarify design information, commissioning responsibilities, dependencies and the evidence needed to assess agreed requirements. The scope should reflect the project context, including constraints associated with an operational airport environment.
AAC brings together specialist consultancy and systems integration, focusing on control systems rather than hardware manufacture. This keeps the discussion centred on engineering scope: how design intent carries into Stage 5, what needs coordination across system interfaces and how testing can align with project requirements. It can also identify where further design clarification or configuration information is needed to plan meaningful commissioning activity.
For project stakeholders preparing for Stage 5, the system boundaries, project stage and integration context provide a practical starting point for defining commissioning scope and coordination needs.
Plan the next commissioning conversation
Bring commissioning into project planning while there’s still time to clarify system boundaries, responsibilities and the evidence needed for acceptance. This gives design, integration and site teams a shared basis for resolving questions as installation progresses, rather than leaving interface decisions until testing is under way. A considered RIBA stage 5 commissioning services scope reflects the project’s operational context and the control system’s specific dependencies.
AAC combines control systems design across RIBA Stages 1 to 5 with SCADA integration and automation engineering for demanding airport environments. This provides a practical basis for discussion around design intent, project stage and the systems involved, while recognising that each project has its own requirements.
Discuss your RIBA Stage 5 commissioning requirements with AAC to explore the engineering scope and coordination your project needs.
Frequently Asked Questions
Does RIBA Stage 5 include commissioning?
Yes. The RIBA Plan of Work 2020 includes commissioning within Stage 5, Manufacturing and Construction, before the project moves into Stage 6, Handover. This places commissioning alongside delivery activity, but doesn’t define one fixed package or acceptance threshold for every project. The project team needs to set out the control system scope, required tests and evidence in line with its design and contract arrangements.
Who is responsible for control system commissioning during RIBA Stage 5?
Responsibility is defined by the project’s appointments, scope and commissioning plan, rather than by one universal rule. The controls integrator may carry out specified system tests, whilst installers provide information about completed work and the designer clarifies intended functions. The client or operator’s role in reviewing results and making acceptance decisions should also be established. A responsibility schedule helps prevent tasks falling between organisations.
What commissioning records should a control systems project retain?
Keep records that allow someone reviewing the project later to understand what was checked, which system configuration was involved and how findings were resolved. Depending on scope, this may include approved test procedures, completed results, configuration references, issue logs, retest evidence and relevant design changes. Agree the record format and storage location with project stakeholders. Required documents depend on the project and its contractual arrangements.
Can control system commissioning begin before all construction work is complete?
Yes. Selected checks can start before the entire project is finished if the systems and prerequisites for those checks are ready. For example, a team might verify a completed control panel or test a defined subsystem whilst other areas remain under construction. Record the results and their limits. Test dependent end-to-end functions later, when connected equipment and interfaces are available.
How are commissioning defects managed before handover?
Record each failed test with enough detail to reproduce the issue, including the relevant function, observed result and test conditions. Assign an owner for investigation and corrective work, then track the change and arrange an appropriate retest. If the correction could affect related functions, assess whether those checks need repeating too. Keep unresolved findings visible for review rather than treating them as closed without supporting evidence.
What is the difference between testing and commissioning a control system?
Testing is an activity, such as checking whether a sensor input appears correctly at a controller or whether an alarm is presented as intended. Commissioning is the wider, organised process that defines why and when those tests are performed, relates results to project requirements and manages findings. A collection of successful individual checks may not, by itself, demonstrate that all required system functions have been assessed.
Can commissioning be phased across multiple system interfaces?
Yes. Phasing can suit projects where systems become available at different times or interface tests depend on construction sequencing and agreed access windows. Define the scope and acceptance basis for each phase, record remaining dependencies and plan later tests to verify connected functions together. A phase-specific pass shouldn’t be treated as final acceptance of an interface that hasn’t yet been tested end to end.
