What if the most consequential control-systems decisions are made before anyone draws a schematic? At RIBA Stage 1, project ambitions need to become clear operational requirements. Stakeholder priorities can differ, and key interfaces may still be unexplored. RIBA stage 1 control systems consultancy brings these considerations into the brief while there is still scope to make informed choices.
Control systems can be difficult to define during early project planning, when operational needs and the technical approach are still taking shape. A consultant helps clarify what the systems must support, identify constraints and risks, and give the project team a sound basis for decisions that will guide later design. This is especially relevant in complex operational environments such as airports, as well as other projects with demanding control requirements.
This guide explains the purpose and scope of Stage 1 consultancy, the questions it can help resolve, and how it brings operational stakeholders and technical disciplines into alignment. It also shows how early decisions can inform the next design stages in the RIBA Plan of Work 2020 and its Smart Building Overlay.
Key Takeaways
- RIBA stage 1 control systems consultancy turns operational ambitions into decisions that can guide later design.
- Review project objectives, existing systems, constraints and interfaces to bring important considerations into view early.
- Compare strategic approaches against agreed outcomes before committing to detailed hardware or software.
- Use stakeholder discussions and available project information to identify evidence gaps, assumptions and decisions that need direction.
- AAC LTD | All About Control provides control-systems design across RIBA Stages 1 to 5, with experience in airport environments and SCADA integration.
Why RIBA Stage 1 control systems consultancy matters at project inception
What does Strategic Definition mean for control systems?
The distinction between RIBA stages matters. In the RIBA Plan of Work 2020, Stage 0 is Strategic Definition, while Stage 1 is Preparation and Brief. Stage 1 develops the Project Brief, giving the team an opportunity to define how the building needs to operate before detailed design begins. Control systems belong in this discussion because they support operational outcomes, rather than being a separate technical decision to leave until later.
RIBA stage 1 control systems consultancy translates operational objectives and constraints into considered requirements and decisions for the design stages ahead. It helps establish what the systems must enable, what information is needed, and which questions require client direction. It does not mean selecting every controller, software platform or equipment specification before the wider design is developed.
Consider an airport project. The team may need to understand how building-services monitoring relates to operational technology, or where interfaces with other operational functions need further definition. The specific interfaces depend on the project, but identifying them early lets stakeholders consider ownership, information flows and dependencies while the brief is still taking shape. This is strategic coordination, not a premature system design.
Why involve a specialist before the design is fixed?
Control systems cross technical and operational boundaries. Decisions about plant, communications, monitoring and day-to-day responsibilities can affect one another. An assumption in one discipline may create a constraint elsewhere. Early specialist input helps the team surface these dependencies, separate known requirements from unresolved questions, and identify where further information or client direction is needed.
Operational stakeholders are central to this process. They can explain how the building must function, what needs to be monitored and which disruptions or limitations matter in practice. Bringing those perspectives into brief development helps avoid a technically coherent proposal that overlooks the people and processes relying on it. It also gives the team a basis for comparing approaches against project needs, rather than treating a preferred technology as the starting point.
A useful early discussion can record:
- the operational outcomes the control systems need to support;
- existing systems, project constraints and interfaces that may shape the approach;
- assumptions that need validation and decisions awaiting client direction.
Make the record useful for the next decision: note what is known, where the information came from, what remains uncertain and who needs to resolve it. The scope and format should suit the project and appointment, rather than follow a one-size-fits-all list of deliverables. AAC LTD | All About Control provides consultancy and design across RIBA Stages 1 to 5, linking early considerations with later engineering development. For a broader view of how those stages fit together, explore the control systems design consultancy guide.
What a control systems consultant examines during RIBA Stage 1
Stage 1 discovery gives the team a structured way to understand what the control systems must support and what could affect their future design. A consultant reviews operational objectives, existing assets, constraints and interfaces, then distinguishes established information from assumptions that need testing or questions that remain open. This makes it easier to see which decisions can be made now and which require more evidence.
At Stage 1, control-systems consultancy connects operational needs with system boundaries so the brief can guide later design without treating unknowns as settled decisions. The work is tailored to the project, rather than being a prescribed set of outputs. The RIBA Plan of Work 2020 Overview sets out the wider stage framework; project-specific advice should sit within the agreed brief and appointment.
Operational needs, stakeholders and system boundaries
Start with the people who define, deliver and rely on building operations. Client representatives can clarify priorities and decision-making responsibilities. Operational teams can describe processes and the information they need. Engineering disciplines can identify technical dependencies. Together, these perspectives help separate essential functions from preferences and show where the brief needs more definition.
Existing assets and proposed systems also shape the initial boundaries. A project might need to consider whether a new control system will monitor existing plant, interact with building services or connect to a wider operational technology environment. SCADA may be relevant in some contexts, but it should not be assumed as a requirement. In an airport, for example, operational technology interfaces may affect how systems exchange information and how responsibilities are divided, making them useful topics for early investigation.
Interfaces, constraints and existing-system considerations
Interface mapping helps the team see where control systems meet other disciplines, such as mechanical and electrical services, communications infrastructure, facilities operations or an existing supervisory system. At Stage 1, the aim is to identify the relationship and the questions it raises, not to specify a final technical solution. Legacy equipment, incomplete records and limited access to system information can all affect what the team can conclude.
Operational continuity deserves attention where existing systems support live activities. The project team may need to understand which functions must remain available during future changes, who holds relevant system knowledge and what information is required to assess potential constraints. Keep a clear record of confirmed facts, assumptions and outstanding questions, with an owner for each follow-up. For airport-specific context, airport SCADA integration illustrates why operational technology relationships merit careful consideration.
AAC LTD | All About Control provides RIBA Stage 1 to 5 control-systems consultancy, connecting early engineering considerations with the wider design process.
Which Stage 1 control systems decisions should the project team compare?
Stage 1 option appraisal should help the client choose a credible direction, not commit the project to detail before the necessary information exists. Compare approaches against agreed operational outcomes, known constraints and available evidence. Depending on the project, options might include retaining and integrating existing systems, extending them, or developing a new control-system approach. These are options to assess, not default recommendations.
How to appraise control-system approaches without over-designing
Use consistent criteria to compare the alternatives fairly. Ask whether each approach supports the required operations, how it fits with existing assets and other disciplines, and what it could mean for maintenance and day-to-day use. Also consider the dependencies each option creates, the information needed to develop it and whether it leaves unresolved interface responsibilities. The Building Controls Industry Association (BCIA) provides wider context on the role of building controls, alongside project-specific requirements.
Some decisions should remain open until surveys, stakeholder input or coordination with other disciplines provides better evidence. That is a useful outcome if the reason is recorded and the next information or decision point is clear. A concise option record can distinguish:
- the agreed objectives and constraints used to assess each approach;
- assumptions, evidence gaps and dependencies that could change the comparison;
- the operational, integration and lifecycle considerations still to be explored.
This record makes the reasoning transparent and revisitable as the brief develops. It also prevents a provisional preference from being mistaken for a final specification. RIBA stage 1 control systems consultancy helps the client make informed strategic choices while preserving flexibility for later design.
Why postponing every systems decision can create risk
Deferring all control-system discussion until the design is established may leave interfaces unresolved while other disciplines develop their proposals. The team may not have agreed what information needs to pass between systems, where responsibilities sit, or how an existing asset relates to a proposed solution. These uncertainties can complicate coordination and narrow the available choices as the project progresses.
Recognise legacy-system dependencies early wherever operations rely on established control infrastructure. In an airport environment, the team may need to understand how existing operational technology relates to proposed systems and what information is required to assess continuity and integration. This does not dictate a particular architecture. It identifies a decision that needs evidence and appropriate ownership.
Where architectural principles are relevant to the project, the IEC 61499 architecture guide offers context for considering system architecture without treating a standard as an automatic solution. The Stage 1 task is to compare approaches against project needs, document why a direction is preferred and identify what must be resolved before detailed design.
What information and outputs help Stage 1 consultancy move the project forward?
Useful Stage 1 advice depends on the quality and limits of the information available, so make both visible. A practical sequence is to gather relevant project records, speak with the people responsible for defining and operating the building, assess the control-systems context, document findings and agree next steps. This gives the project team a traceable basis for decisions without presenting early assumptions as settled requirements.
Stage 1 outputs should be proportionate to the project: clear enough to guide decisions and preserve important reasoning, without creating detail the brief does not yet support. RIBA does not prescribe a single universal pack of control-systems documents for every appointment. Depending on the scope and context, advice might be recorded in a briefing note, an assumptions and constraints register, an interface schedule or a list of open actions. These are examples, not mandatory formats.
What the client team can prepare for a focused commission
Before discussions begin, bring together the project information already available, even if some records are incomplete. Useful inputs may include:
- project objectives, operational requirements and relevant brief material;
- available records of existing control systems, assets and connected infrastructure;
- stakeholder roles, known constraints and decisions that need client agreement.
Mark information gaps clearly. If a system drawing is unavailable or an operational requirement is still under discussion, record that status rather than filling it with an assumption. The consultant can then separate established facts from points requiring investigation, identify where stakeholder input is needed and focus the assessment on the information the project can reasonably provide.
How findings can inform the next design stage
Close the Stage 1 work with an agreed record of what the team knows, what it has decided and what remains open. This can help the next design stage develop the control-systems brief without treating early advice as completed technical design. Requirements can inform further development, while unresolved interfaces, information gaps and dependencies stay visible for follow-up.
Project governance gives those actions a route forward. Assign an owner to each open item, agree who has authority to make the relevant decision, and identify when further evidence or direction is needed. This supports continuity when responsibility passes between stakeholders or disciplines and helps prevent an unanswered question from silently becoming a design assumption.
RIBA stage 1 control systems consultancy is most useful when findings can be carried forward and revisited as the project develops. AAC LTD | All About Control provides control-systems design consultancy across RIBA Stages 1 to 5, linking early engineering advice with subsequent design development. Discuss your Stage 1 control-systems requirements with AAC to establish a project-specific basis for the next decisions.
How AAC supports RIBA Stage 1 control systems consultancy
AAC Ltd provides automation engineering consultancy and control-systems design from RIBA Stage 1 through Stage 5. This connects early discussions about operational intent with the engineering work that follows, so strategic advice can inform the brief and provide continuity as the design develops. The Stage 1 scope is shaped around the project, its objectives and the agreed appointment.
From strategic intent to coordinated control-systems design
AAC helps project teams consider how control systems relate to intended operations, existing assets and other technical disciplines. The purpose is to establish relevant requirements and questions, not to impose a standard solution or settle detailed design prematurely. As the project progresses, those early considerations can develop in step with the wider control-systems design process.
This work draws on AAC’s experience in mission-critical airport environments and SCADA integration. Airport infrastructure can involve operational technology and existing systems whose relationships need careful consideration, although each project has its own context and requirements. The aim is to bring relevant engineering questions into the conversation early, then carry agreed decisions and dependencies into subsequent design work.
AAC is a Schneider Electric EAE Master Partner. This experience is relevant where a project calls for specialist control-systems knowledge, while the project brief, operational requirements and technical context guide the advice. For a broader view of how control-systems design can develop across the project lifecycle, see the RIBA Stages 1 to 5 design consultancy guide.
Agreeing the right next step for the project
A productive first discussion centres on the project’s objectives, current RIBA stage, operational context and available information. It can also identify which stakeholders should contribute, what decisions are approaching and where further evidence may be needed. This gives the consultancy a clear starting point without assuming every project needs the same investigations or outputs.
From there, AAC shapes the scope around the brief and the decisions the client needs to make. This may involve clarifying system boundaries, examining an existing control environment or helping the team understand interfaces that could influence later design. The emphasis is on relevant, proportionate engineering input that supports the project rather than adding detail without purpose.
For RIBA stage 1 control systems consultancy tailored to your project, discuss your project objectives and Stage 1 control-systems requirements with AAC.
Set a clear direction for your next design decision
The value of RIBA stage 1 control systems consultancy is not measured by how much technical detail is produced at the outset. It is measured by whether the project can move forward with clearer priorities, better-defined questions and a sound basis for decisions. Consider which operational needs, interfaces or assumptions need attention before the brief advances.
AAC’s control-systems design consultancy spans RIBA Stages 1 to 5, supporting continuity as project requirements develop. Its specialist experience in mission-critical airport environments and SCADA integration informs work where operational technology is a central consideration. AAC is also a Schneider Electric EAE Master Partner and UAO member. These capabilities provide relevant engineering context, with advice shaped around each project’s requirements.
Bring your project objectives, current stage and key operational questions to AAC to establish what early-stage support will best serve the brief. Discuss your project’s control systems requirements with AAC and take a considered next step towards a coordinated design.
Frequently Asked Questions
What is RIBA Stage 1 in a control systems project?
Under the RIBA Plan of Work 2020, Stage 1 is Preparation and Brief; Stage 0 is Strategic Definition. For control systems, Stage 1 is where the project team develops its brief and considers how operational requirements could affect system scope and coordination. For example, the brief might clarify which functions require monitoring and who will use that information. The work remains strategic, rather than a completed technical design.
Is control systems consultancy needed at RIBA Stage 1?
It can be valuable if control systems influence how the building will operate or how disciplines need to coordinate. RIBA stage 1 control systems consultancy helps a client determine whether links to existing systems, operational monitoring or responsibility for system interfaces need attention in the brief. The case for early input depends on the project’s objectives, context and available information.
Can a control systems consultant be appointed before the design team is complete?
Yes. A client can appoint specialist control-systems advice while the wider design team is forming, particularly if operational requirements or existing infrastructure may shape the brief. Early input can identify information that other appointments will need to address, such as how a proposed system relates to existing assets. Set out the consultant’s responsibilities and boundaries clearly so the advice complements the developing team’s work and avoids duplicated tasks or gaps in accountability.
Does RIBA Stage 1 produce a control systems specification?
Not necessarily. Stage 1 focuses on preparing the brief, so a detailed technical specification may be premature. Depending on the appointment, a useful record could capture functional priorities, known constraints, assumptions, interface questions and decisions for client consideration. For instance, the brief may state that a system needs to provide operational information without yet defining the equipment or software that will deliver it. Detailed design develops as the project progresses.
How long does RIBA Stage 1 control systems consultancy take?
There is no single duration that applies across projects. The programme depends on the agreed scope, the complexity of the operational context, access to existing records and the availability of relevant stakeholders. The client team can help plan the work by identifying decision dates and aligning discussions with brief development. If key information is missing, agree whether to investigate it now or record it as an action for a later project stage.
What information should we provide to a Stage 1 control systems consultant?
Start with the current project brief, operational objectives, known system records and relevant constraints. It is also useful to identify who can speak for the client, building operations and technical disciplines, and who will approve decisions. If drawings or asset information are incomplete, label them as incomplete rather than treating them as definitive. This helps the consultant distinguish evidence from assumption and focus on gaps that could affect the brief.
What happens if control systems consultancy starts after RIBA Stage 1?
A consultant can still assess the project at a later stage. The initial task is to review the current brief, design information and existing decisions, then identify unresolved control-system requirements or interfaces. For example, a developing design may show a proposed connection to an existing system without explaining its operational purpose. The team can assess whether clarification is needed, record any consequences and identify proportionate next steps without reopening settled decisions without cause.
