When Is an SSHO Required on a Project?

A project can be fully staffed, on schedule, and technically sound - then lose time fast because the safety requirement was misunderstood from day one. That is usually how the question shows up in real life: when is an SSHO required, and does this job actually need one on site full time?

For federal construction, the answer is rarely based on preference. It is driven by contract language, agency standards, project risk, and the specific safety obligations written into the work. If you are bidding or mobilizing on a USACE, NAVFAC, DoD, or other high-compliance project, guessing is expensive. The right answer protects the workforce, keeps the contract moving, and avoids the kind of documentation rejection or field correction that turns into delay claims.

When is an SSHO required?

An SSHO is required when the contract, governing safety standard, or owner requirement calls for a dedicated Site Safety and Health Officer to oversee project safety compliance. On federal and military construction projects, that often means the requirement is written directly into the contract and tied to EM 385-1-1 expectations, jobsite hazard exposure, and the need for continuous competent safety oversight.

That sounds straightforward, but the real issue is that not every project is structured the same way. Some contracts clearly state that a full-time SSHO must be present whenever work is being performed. Others define the role through safety submittal requirements, personnel qualifications, and oversight obligations that effectively create the same requirement. In both cases, the practical result is identical: you need a qualified person approved and active before work gets underway.

For many contractors, the safest assumption is this: if the project is federal, military, USACE, NAVFAC, or otherwise governed by EM 385-1-1, you should expect serious SSHO scrutiny and verify the requirement before mobilization.

The contract decides first

The first place to look is not a general internet answer. It is the contract itself. If the statement of work, safety specification, or administrative section names an SSHO, sets minimum credentials, or requires a designated site safety professional with authority to enforce compliance, that requirement controls.

This is where contractors get into trouble. They may assume a superintendent can cover safety informally, or they may plan to use a part-time safety consultant. On many private projects, that may be enough. On federal work, it often is not. If the contract requires an SSHO, the owner is not asking for occasional safety support. The owner is requiring a specific role with defined authority, qualifications, and accountability.

That role usually includes daily inspections, hazard identification, compliance monitoring, incident response, activity review, and coordination around Accident Prevention Plans and Activity Hazard Analyses. If the contract expects those tasks to be handled in the field by a named and qualified individual, then the SSHO is not optional.

EM 385-1-1 changes the standard

On USACE and many military-related projects, EM 385-1-1 is the standard that raises the bar. OSHA still matters, but EM 385 is often the controlling project requirement for federal construction safety administration. That is a critical distinction.

OSHA establishes baseline legal obligations. EM 385 frequently adds project-specific structure, stricter documentation demands, more defined training expectations, and a clearer requirement for dedicated on-site safety oversight. If your project falls under that framework, the question is not simply whether someone knows OSHA. The question is whether the assigned safety lead can operate within EM 385, satisfy the agency reviewer, and keep field execution aligned with approved plans.

That is why an SSHO on a federal project is not just a title. It is a compliance function. The person in that role must be able to support approvals, monitor work against accepted safety controls, and respond immediately when conditions change.

Projects where an SSHO is commonly required

In practice, SSHO requirements appear most often on federal and military construction projects, especially those involving USACE, NAVFAC, DoD installations, VA facilities, airfields, utilities, civil works, renovation in occupied government buildings, and projects with elevated hazard profiles.

The likelihood goes up when the work includes confined space entry, critical lifts, excavation, energized systems, demolition, environmental exposure, waterfront operations, heavy equipment coordination, or complex multi-employer activity. It also increases when the owner expects extensive pre-task planning, daily documentation, and formal submittal acceptance.

Overseas government-linked projects often carry the same expectation, sometimes with even less tolerance for staffing gaps because replacement timelines, badging, and mobilization logistics are harder to manage.

None of this means every small federal task order automatically requires a full-time SSHO. Some lower-risk scopes may allow a different staffing structure. But if the contract is written around EM 385 controls and substantial field oversight, a dedicated SSHO is usually the correct operational answer.

Full-time versus part-time depends on the project

This is where nuance matters. Contractors often ask whether an SSHO must be on site full time, or whether one person can split time across multiple jobs. The answer depends on what the contract says, how the work is phased, and whether the risk profile allows anything less than dedicated coverage.

On many federal projects, the expectation is full-time on-site presence whenever work is in progress. That is especially true when the contract language is explicit, when the project has multiple crews, or when the hazards change daily. A remote reviewer or occasional visitor cannot manage those conditions effectively.

There are projects where an owner may permit a less intensive model, particularly for limited scope or low-risk work. But contractors should be careful here. A staffing plan that looks economical on paper can fail in practice if inspections are missed, AHAs are not kept current, corrective actions lag, or agency representatives see that safety authority is diluted.

If the project requires real-time control of field hazards, the SSHO should be present with the authority and credentials to act immediately.

Qualifications matter as much as the requirement itself

A common mistake is treating the SSHO requirement like a box to check. Federal owners do not usually see it that way. If the contract requires an SSHO, they are also likely to evaluate whether that person actually meets the stated qualifications.

That can include EM 385 training, OSHA training, first aid and CPR credentials, relevant construction safety experience, hazard-specific knowledge, and the ability to prepare or support key project documents. Some agencies or contracting teams may also review resume history, project type experience, and whether the proposed SSHO has enough authority within the contractor's organization.

If the submitted SSHO is weak, the practical result is the same as having no SSHO at all - delayed approvals, rejected submittals, field friction, and pressure on the schedule before meaningful work even begins.

This is one reason experienced contractors secure safety leadership early. They know the real risk is not just whether an SSHO is required. It is whether the proposed SSHO will be accepted and effective.

What happens if you get it wrong

When contractors misjudge the SSHO requirement, the damage is rarely limited to one correction notice. Work can be delayed during mobilization. Safety plans may be rejected. Preconstruction approvals can stall. Field activities may be restricted until compliant oversight is in place.

If an incident occurs while the project is under-supported from a safety leadership standpoint, the exposure becomes much more serious. Investigations will quickly focus on whether the contractor met the contract's staffing and oversight obligations. That affects more than safety performance. It can affect client confidence, payment flow, claims posture, and future eligibility for similar work.

The cost of a qualified SSHO is visible in the budget. The cost of not having one usually shows up later, and it is almost always higher.

How to determine the requirement before mobilization

The cleanest approach is to review the contract early and read the safety sections as an operational requirement, not just a submittal requirement. Look for direct references to an SSHO, Site Safety and Health Officer qualifications, EM 385-1-1 applicability, staffing language, daily inspection duties, and approval requirements tied to the Accident Prevention Plan.

Then evaluate the actual work. Even if the language seems broad, ask what the job demands in the field. Will crews be performing higher-risk activities? Will the owner expect constant coordination? Will changing site conditions require immediate hazard analysis and enforcement authority? Those answers often make the staffing decision clearer.

If there is any ambiguity, get clarification before award or before notice to proceed. Waiting until the government reviewer rejects your proposed setup is the slowest and most expensive way to answer a simple question.

For contractors operating in this environment regularly, this is where a specialized partner adds value. A firm such as SSHOSafety© does more than provide a resume. It aligns staffing, documentation, and field execution so the SSHO function works the way the contract expects it to work.

The strongest projects do not treat safety staffing as a late administrative task. They treat it as part of how the job gets built correctly from the start. If your contract points toward dedicated safety oversight, the smart move is to solve that requirement before it becomes a problem in the field.

The job will tell you what it needs if you read the contract carefully enough - and on federal work, the contract is usually telling you sooner than you think.