Temporary works coordination: establishing clear project responsibilities
Admin · 22 October 2026
Illustrative image. Photo by Frames For Your Heart on Unsplash. Unsplash License.
Temporary works can involve design, supply and site activities spread across several organisations. If the interfaces are unclear, each party may complete its own scope while nobody has coordinated the full sequence. The management task is to make the required responsibilities, decisions and evidence explicit from the start, using competent people and the arrangements appropriate to the project.
This is a coordination article, not a technical design or operating guide. The actual temporary works need competent assessment and the applicable requirements. HSE’s temporary works guidance provides relevant context, including the importance of planning and management. Project leaders should establish the specific system with appropriate advice before relying on a general checklist.
Identify the scope with competent input
Ask the relevant technical team to identify the temporary works and interfaces associated with the planned construction sequence. Do not assume that only conspicuous support structures require consideration. The competent team determines the actual scope and assessment needs. The management process records the items, owners and next decisions so they are visible in planning.
Review the scope when methods, equipment or sequence change. A register prepared at inception can become incomplete if packages introduce new arrangements without coordination. Give suppliers and package managers a clear route to raise proposals and obtain the relevant review. The fact that an item is temporary does not reduce the need to establish a suitable process.
Define coordination separately from design
Identify who coordinates the overall process and who performs the relevant design and checks. HSE’s temporary works FAQs explain that coordination is not automatically the designer’s role and that a specific coordinator job title is not universally required by law. The project still needs an appropriate management arrangement.
Make the actual allocation clear in appointments, scopes and procedures with appropriate technical and commercial review. A designer’s involvement should not be interpreted as acceptance of every site coordination responsibility. Equally, a coordinator’s appointment does not imply they personally perform all technical work. Each role needs a clear scope, competent resource and authority.
Keep interfaces with permanent works visible
Identify the information exchanged between temporary and permanent works designers through the actual scope and coordination arrangements. The relevant specialists should establish what each needs and how changes are reviewed. A permanent works detail may not answer every question about its temporary condition during construction. The coordinator should make that interface explicit and track the required decisions. If the sequence changes, refer the effect back to the responsible people rather than assume the original exchange remains adequate. Preserve the current references so the site can identify the basis being relied on.
Prepare a complete design brief
The responsible team should establish what information the designer needs, including the relevant conditions and interfaces. The project coordinator obtains inputs from the parties holding them and records limitations. A brief should not conceal uncertain information behind an apparently complete form. Missing inputs need owners and a route to resolution.
Connect the brief to the planned sequence and intended use. If the arrangement depends on a particular construction stage or another package’s work, make that dependency explicit. The designer and relevant checking parties need the current basis. A later operational change should not be assumed acceptable because the original design exists.
Plan checks and authorisations
The competent team determines the applicable checking, verification and authorisation arrangements under the project system. Record who performs each action and the evidence required. Avoid vague sign-off columns whose meaning is unclear. Participants should understand whether they are acknowledging receipt, reviewing a specific aspect or authorising a defined next step.
Include these events in the programme with realistic information and notice dependencies. A planned construction date does not establish that the relevant design or checks will be complete. The coordinator needs a current readiness position and a clear escalation route for missing evidence. Preserve uncertainty rather than report a convenient green status unsupported by the records.
Coordinate procurement interfaces
Identify what the provider supplies and what the project must provide separately. Standard equipment can still rely on conditions that need assessment for the actual site. The competent people should establish the relevant requirements and limits. Procurement needs to preserve those conditions in the review rather than assume availability equals suitability.
A hypothetical package proposes a proprietary arrangement used on another site. The project needs to establish whether its assumptions and conditions apply here through the appropriate process. A past successful use is useful context, but it does not replace the assessment of this operation. The coordination record should identify the required decision and responsible people.
Keep the site information current
Use controlled references for the relevant design and instructions, with their status and revisions clear. The people supervising the work need to know which information applies. A revised design held only in an email can leave the site using an earlier basis. The project’s information process should carry consequential updates to affected teams.
Record changes through the actual system and obtain the appropriate assessment before implementation. Informal adjustments can alter the conditions the design relies on. The coordinator should ensure questions reach the competent designer and other responsible parties. The role is to preserve the process and communication, not improvise a technical answer under programme pressure.
Make stage status visible
Distinguish proposed, designed, checked, installed and other relevant states using the project’s established definitions. The actual sequence and terminology should be determined for the arrangement. A single complete field may conceal important differences. Delivery managers need to understand what the current status permits and what remains outstanding.
Where another package depends on the outcome, communicate the relevant handover through the approved route. The next team should not infer readiness from physical appearance or an informal assurance. Link the decision to the actual item and stage so a record for one location cannot be mistaken for a general release elsewhere.
Plan continuing review and changes
The responsible competent team should establish the requirements during use and the response to changed conditions. Assign responsibility for obtaining and communicating relevant observations. The coordination arrangement must remain active after installation rather than treat the initial design as the end of the process.
Review interfaces when adjacent work or the construction sequence changes. Another package may affect the assumptions without directly modifying the temporary works. A clear reporting route helps the project identify that issue before relying on the old arrangement. The appropriate specialists determine the consequence and required action.
Include removal in the original plan
Identify the relevant decision process and competent input for removal or transition. The project should not assume that a construction milestone automatically authorises the next stage. Record the conditions and evidence established under the system, with clear ownership and communication. The programme needs a credible sequence through to close-out.
Retain the records required by the project and review the coordination experience. Repeated gaps may indicate unclear scope, late information or inadequate authority. Improve those conditions rather than simply add another form. The aim is a dependable management arrangement that connects competent technical work to the actual site sequence.
Clear temporary works responsibilities give the project a shared account of who coordinates, designs, checks and authorises within the applicable process. They preserve the distinction between those roles and keep changes connected to the relevant expertise. That discipline supports informed decisions throughout the arrangement’s lifecycle, without relying on assumptions about a title or a familiar piece of equipment.
During mobilisation, test one representative item through the proposed workflow. Confirm that required information, authority and communication routes are available before several packages depend on the system.
