Subcontractor assurance reviews before mobilisation
Admin · 22 October 2026
Illustrative image. Photo by Etienne Girardet on Unsplash. Unsplash License.
Prequalification can establish useful background about a subcontractor without answering every question about a particular mobilisation. The actual work, personnel and interfaces may differ from those considered during the initial enquiry. A pre-mobilisation assurance review connects the appointment to current project conditions and identifies what must be resolved before the package begins.
For contractors, the review should be proportionate to the scope and relevant requirements. It is not an exercise in collecting every policy available from the supplier. The responsible technical, safety, quality and commercial teams need evidence that addresses the actual arrangement. The coordinator makes those questions and actions visible without claiming that an administrative checklist provides complete assurance by itself.
Start with the agreed package basis
Identify the scope, accepted clarifications and relevant requirements through the project’s controlled records. The mobilisation team should understand what was actually appointed, not rely only on the original tender invitation. Differences between procurement assumptions and delivery expectations need clarification through the appropriate process before they become work-front disputes.
Record any material conditions still outstanding from award. Name the owner, required evidence and decision date. A conditional appointment should not become unconditional by silence as the start approaches. The responsible managers need an accurate readiness view and a route to resolve or escalate the remaining matters.
Confirm the proposed people and organisation
Review the actual management and supervision arrangements for the package. Identify who holds each relevant responsibility and whether proposed personnel differ from the submission reviewed earlier. The organisation’s competence and appointment processes determine the required evidence. A familiar company name should not be treated as proof that every current role is suitably resourced.
HSE’s competence guidance provides context for considering relevant skills, knowledge, training and experience. The project should use competent assessment for the actual responsibilities and work. A certificate may be relevant evidence, but the review should not infer readiness for every task from its presence alone.
Check information and design interfaces
Establish what the subcontractor needs from others and what it must provide before work. Include specialist design, supplier information and coordination requirements where applicable. Link them to the information schedule and programme. A package can be commercially awarded while still lacking the inputs necessary for a credible mobilisation.
Identify the current status and permitted use of the information. The delivery team should know which documents form the applicable basis and which remain provisional. If the package proposes an alternative, route it through the relevant technical and change procedures. Mobilisation should not silently introduce a substitution that has not been assessed.
Review the planned work arrangement
The relevant competent people should assess the proposed methods and required controls under the project’s actual procedures. The assurance coordinator checks that the process and evidence are in place without improvising technical instructions. A submitted document is not automatically an accepted arrangement merely because the system records it as received.
Keep the relationship with the wider site clear. Access, shared resources and predecessor work can affect readiness. The subcontractor needs a realistic account of what the site will provide and when. Assurance is weakened if the buyer checks the supplier’s obligations while leaving its own consequential dependencies undefined.
Connect quality evidence to the sequence
Confirm the applicable inspection, test and acceptance arrangements with the responsible specialists. Identify required records and the parties involved in relevant stages. The programme should reflect those dependencies rather than expect quality evidence to be assembled after access has disappeared. Procurement and delivery need a common understanding of the information the package must produce.
A hypothetical subcontractor is ready to begin repetitive work, but the project has not agreed how the required evidence will identify locations. The review can resolve that format before many records are created. The benefit is not a more attractive form; it is a traceable account that the responsible reviewers and receiving teams can interpret.
Assess resources against actual timing
Reconfirm consequential availability and support arrangements, including changes since tender. The relevant team should understand whether personnel or equipment are confirmed, expected to transfer or dependent on further action. Preserve those distinctions in the readiness record. An intention to mobilise is different from a demonstrated arrangement to deliver the planned work.
Discuss overlaps and shared resources with the planner and package leads. A subcontractor may have sufficient capability overall while facing a specific timing conflict. The review should identify the consequence and available decisions, not simply record a headcount. Changes to the sequence need to be assessed and communicated through the appropriate project routes.
Make communication routes usable
Confirm how formal information, urgent concerns and ordinary coordination will be handled. Identify contacts and cover arrangements. The subcontractor’s supervisors should know where questions go and the limits of their authority. A mobilisation presentation should not assume that every participant already understands the main contractor’s particular processes.
Consider language and practical access needs under the organisation’s relevant arrangements. A system login may exist without the user being able to retrieve the correct package information. Test representative tasks and resolve gaps. The project needs functioning communication, not only evidence that invitations and passwords were sent.
Keep statuses specific
Use terms that distinguish received, reviewed, accepted and outstanding under the project’s definitions. Different disciplines may use different review procedures, so the coordinator should preserve their meaning. A single green status can conceal unresolved technical matters if it represents only document receipt. Decision makers need to understand what the readiness conclusion actually covers.
Assign each gap an owner and required outcome. Prioritise by consequence to mobilisation and the affected work. The appropriate responsible people determine whether an issue prevents the intended start or can be managed through another authorised arrangement. Do not make that judgement implicitly through a percentage-complete report.
Check assurance at further mobilisation stages
A subcontractor may introduce another team, activity or specialist supplier after the initial start. Establish how the relevant review requirements apply to that change through the project’s procedures. The original mobilisation decision should not be treated as permanent approval of every later resource or method. Give the package lead a clear route to identify the change and obtain the appropriate assessment.
Review the information inherited from earlier assurance as well. It may provide useful evidence but still require confirmation against the new arrangement. Keep the basis, current status and owner visible so the project can distinguish a legitimate reuse of evidence from an unsupported assumption that nothing material has changed.
Confirm the decision and follow through
Record the authorised mobilisation position, scope and conditions through the applicable process. Communicate it to the people controlling work release and the subcontractor’s relevant managers. A meeting agreement should not be assumed to replace a formal approval or instruction required elsewhere. The actual project arrangements establish the route.
Review early delivery against the assumptions. New evidence may reveal an information or support gap not apparent before the start. The process should provide a clear response rather than treat mobilisation approval as permanent assurance. Maintain the relevant records and update responsibilities as the package develops.
A useful pre-mobilisation review connects current scope, competent resources and traceable evidence to the first work. It makes both supplier and buyer dependencies visible and gives unresolved matters a responsible route. That supports a more credible start than a document collection whose completion status says little about the arrangement the site will actually use.
Retain lessons about missing inputs and unclear review meanings. Improve the next package’s procurement and mobilisation brief while the experience is fresh, rather than repeat the same late requests at every start.
