By Maria Mothibedi, Head of Operations at SPM
Site work does not begin when the team arrives. That is one of the first lessons you learn in operations, often through experience rather than theory.
By the time people get to site, many of the conditions that will shape the day have already been set. These vary, some are technical, some are procedural, and some are practical. They can include access, permits, isolation, the availability of the right contact person, the accuracy of the scope, the condition of the equipment and the amount of time actually available for the work.
This is where site readiness becomes more than preparation. It becomes part of delivery.
In industrial environments, readiness is sometimes treated as a step that must be completed before the real work starts. From an operations point of view, that separation is risky. The work on site depends heavily on what has been confirmed, clarified and resolved before the team enters the gate. When those details are handled properly, execution has room to move. When they are not, the site team starts the day working around avoidable problems.
Many readiness issues are only noticed when people are already on site. A permit has not been signed off. A shutdown window has changed. Equipment is not accessible. A drawing no longer reflects the current installation. Another contractor is working in the same area. A decision-maker is not available when a call needs to be made.
None of these issues are unusual in industrial work. Sites are active environments, conditions change, priorities shift, and production demands continue. The point is not that every uncertainty can be removed. The point is that operations must reduce as many avoidable uncertainties as possible before they reach the site team.
That is why site readiness should be seen as an operational discipline, not an administrative exercise. It is not only about having documents in place. It is about understanding whether the site is practically ready for work to proceed safely and efficiently.
In operations, a job is not viewed only as a date on a schedule. It has people attached to it. It has tools, vehicles, spares, safety requirements, site rules, client expectations and operating conditions. Each of those details can either support the work or complicate it.
That is why the questions asked before mobilisation matter. What exactly must be done? Has the scope changed since the first discussion? Is the site contact available? Are access requirements clear? Has the equipment been isolated? Are there lifting requirements? Will other contractors be working nearby? Are the correct spares and tools available? Is the shutdown window realistic for the work required?
These questions are not asked to slow the process down. They are asked because the fastest route to completion is often the one that begins with proper clarity.
Good operations teams know the cost of assumptions. Assuming that access has been arranged, permits are ready, the equipment condition is as described, the client’s internal teams are aligned, or the team will be able to resolve everything once they arrive can seem harmless during planning. On site, those assumptions become time, pressure and risk.
Site readiness also requires honest communication between the client and the contractor. There are times when a site is not fully ready, when internal approvals are still outstanding, when conditions have changed or when the scope needs to be revisited. Raising those issues early gives everyone a better chance of managing them properly.
This is where operational maturity becomes visible. It is not only seen in how quickly a team responds to a problem. It is also seen in how clearly people communicate before the problem reaches site. A mature operating environment allows necessary conversations to happen early: the site is not ready, the timeline needs to be reviewed, the scope is unclear, the safety requirement has changed, or the work cannot proceed until a specific condition is met.
Those conversations are not always comfortable, but they protect the work.
There is also a human side to this. When a team arrives on site with clear information, the day starts differently. People know where they are expected to be. Supervisors can focus on leading the work. Technicians can concentrate on the task. Safety discussions are linked to the actual conditions on site. The client knows who is responsible for what. Small decisions do not become unnecessary delays.
When readiness is weak, the opposite happens. The team may still find a way to proceed, but too much energy is spent solving problems that should have been cleared earlier. That affects morale, pace and focus. It can also create frustration between teams that are all trying to achieve the same outcome.
In industrial work, the quality of execution is often shaped before execution starts. This is why operations cannot be treated as a back-office function that only allocates resources after decisions have been made. Operations must be part of the conversation early enough to test whether the plan can work in practice.
The strongest projects are often those where both sides understand this. The client prepares the environment. The contractor prepares the team. Information moves early. Risks are discussed before they become delays. The site team arrives with enough clarity to begin well.
That is the work before the work. It may not always be visible, but it is felt in the way a project unfolds. It shows in fewer interruptions, better coordination, clearer communication and safer execution.
Site readiness is not paperwork sitting on the side of a project. It is part of the project. When it is treated with the seriousness it deserves, it gives technical work a stronger foundation. It helps protect the client’s time, the team’s safety and the quality of the final outcome. In operations, that is where delivery begins.