Straight into the service manual page
WrenchQuarry
More

3 coordination duties when contractors share a site

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

When two contractors share one site, the risk sits in the gaps between their plans. Coordination duties are the agreements the two sides make before work starts: who does what, where, and when, and who acts when the plan changes. Each crew may know its own work well and still not know which task the other crew is doing, which hazard it is controlling, or who will act if something shifts partway through the day. A delay on one side can also move people into the other side's space without anyone deciding that it should happen.

Key takeaways

  • Talk with the other contractor before your crew arrives, and keep one shared plan with a date on it.
  • Name in advance who evaluates the work zone when a crane works near an overhead power line.
  • Agree in writing who reports an injury or dangerous occurrence, and keep a contact list both crews can reach fast.
  • Each duty here has an official source, but each source speaks only to the place it names.

Consider a simple case. One crew is setting up steel while the other runs deliveries through the same gate. Neither crew is careless, but each is working from its own plan, and the gate is where the plans meet. For dispatchers and owners, the job is to close those gaps before a crew goes on site.

This post covers three coordination duties. Each one is tied to an official source, and each source speaks only to the place it names. Some come from New Zealand, one from Oregon and one from the United Kingdom. Treat them as a starting point for talks with the contractors involved, not as a statement of what applies to your job. For that, read the rules that cover your site, and ask someone qualified to advise you.

Talk with the other contractor before your crew arrives

The first step comes from section 34 of New Zealand's HSWA, titled "PCBU must consult other PCBUs with same duty." The WorkSafe New Zealand working-at-height page links to that section, and the rule applies in New Zealand. Elsewhere, treat the conversation as a sound habit rather than a requirement these sources set.

Start the talk with the work itself. Ask what the other crew will be doing, on which days, in which parts of the site, and at what times of day. Ask which tasks overlap with yours. One crew working below the other is an overlap. So is both crews needing the same access route, lift point, or storage area. Ask what equipment and materials they will bring into shared space, and whether any of it will stay there overnight. Send the answers to the other contractor, so both supervisors work from the same notes instead of from memory.

A shared plan does not need to be long. One page can cover the tasks each crew will do and when, the access routes and gates, the lift points and storage areas, the names and phone numbers of the people in charge, and the date of the last update. Put a date on it every time it changes. Without one, nobody can tell whether the copy on the gate matches the plan the supervisors approved.

Ask whether the other crew's workers know what your crew will be doing and when. A supervisor may have the full picture while the people on the ground have only part of it. Brief your own crew leads on the other crew's plan, and ask them to report anything that does not match. Crews often see an overlap forming before anyone in an office does, so they should know who to call and feel free to call without waiting for a meeting.

When you talk with the other contractor, a few questions help. Who is the point of contact for each crew? What hours will each crew work? What happens if one crew runs late and the other is already scheduled into the shared area? Who decides when a shared area is clear for the next task? You will not get every answer in one meeting. Note the open questions, put a date beside each one, and pick them up at the next talk.

If the other contractor is slow to reply, say so in writing and name a date for the next talk. Silence is not agreement, and a plan one side never acknowledged is a weak plan on a busy day.

Owners can help here. An owner who sets up the first meeting and names one person to keep the shared notes current removes the guessing about who runs the schedule. That person does not need to be a dispatcher, but they do need the authority to call a pause when the plan stops matching the site.

Expect the first talk to surface disagreements. Two supervisors who have run their own jobs for years may see sequencing, cleanup, or barrier placement differently. Those differences are easier to settle at a planning meeting than in the middle of a lift. Bring them out early and capture the decision reached.

Dispatchers can add a short check at the start of each shift: has anything changed since the last talk? A plan made at the start of a week can shift by midweek when a delivery moves, a second crew arrives, or a task runs long. Agree in advance on what counts as a change worth a phone call, such as a new lift, a new crew member on site, a different access route, or a delay that moves one crew into the other's area.

The same page also points readers to section 46 of HSWA, "Duties of other persons at a workplace" and to section 2.6 of its guidelines, "Worker engagement, participation and representation." Review both with your crew leads before the first shift. The page gives only these section titles, so build the conversation around what your own crews need to know rather than around details the sources do not provide.

Who evaluates the work zone when cranes work near power lines?

The sources here do not name who does the evaluation. The Oregon construction page says it "provides contractors with a flow chart to help them evaluate a work zone when cranes will be operating within 20 feet of an overhead power line," so the shared plan should name who will use that flow chart before the crane runs. The Oregon Occupational Safety and Health construction page is the source for that point.

The 20-foot figure comes from the Oregon page. It is not a general safe distance, and it should not be used as one in other states or countries. The page describes the flow chart as a way to evaluate a work zone. It does not say the flow chart is mandatory, and it does not say the flow chart applies on every job in Oregon.

On a shared site, the crane may belong to one contractor while the overhead line affects both crews. That makes the crane plan a joint document. Before the crane is sent, settle a few questions. Where will the boom and the load swing? Which parts of the work zone sit close to the line? Who watches the line while the crane moves, and who can stop it if something looks wrong? Who tells the other crew when the plan changes? If the answers differ on each side, the crane waits until they match.

Ask the operator to walk the swing path with the ground crew before the first lift, and let anyone who will be in that path say so if they feel unsure. A short walk-through costs little compared with a lift that goes wrong.

Sequencing matters too. Before a crane crew is booked, find out whether the other contractor is setting up in the same area, and whether that setup appears in the shared plan. If a crane's work zone overlaps a ground crew's zone, the plan should say which crew stops first when a load is moving. Putting the crane and the ground crews in one conversation before either is booked prevents much of this confusion.

A booking note for a crane job can carry the work zone, the power line, who did the evaluation, the other crew working nearby, and the date the shared plan was last agreed. Those few fields give the operator and the ground crew a starting point before they meet on site. Nothing in these sources requires that exact list, so adapt it to your own dispatch habits.

Conditions change during a shift. A gust picks up, a load arrives early, or a ground crew drifts closer to the line than planned. The sensible response is to stop the affected work, compare the situation with the agreed plan, and tell the other crew before anyone restarts. A restart that happens only because one supervisor said so, with the other side unaware, is exactly the gap the shared plan exists to close.

Put the answers into the shared plan: the person who makes the call, the date the evaluation happened, and a stop signal everyone understands. Give the other crew's supervisor the same copy. A verbal agreement at the gate is not enough, because the people who made it may not be the ones on the crane when work starts.

If the site is outside Oregon, the flow chart does not apply there. The habit still does: agree in writing on how the work zone will be evaluated, and name who will carry out the evaluation.

Decide in advance who reports an injury or dangerous occurrence

Decide this before work starts. Under the UK's Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013, it is sufficient compliance with sub-paragraph (1) for a self-employed person to make arrangements for the report to be sent to the relevant enforcing authority by some other person. The legislation.gov.uk text of Schedule 1 says this. That is a UK rule, so it covers only work within those regulations. The quote does not say what sub-paragraph (1) requires, so read the schedule itself for that.

The same schedule says that sub-paragraph (1)(a) "does not apply to a self-employed person who is injured at premises owned or occupied by that self-employed person." Whether a shared site counts as premises owned or occupied by a particular contractor is a question for the people involved to work through. This post does not decide it.

The schedule also says that "where required to follow the reporting procedure by regulation 9 the responsible person must notify the relevant enforcing authority in an approved manner." For a dispatcher, two questions follow. Who on the shared site is the responsible person? Does that person know what the approved manner is? The quote does not explain how regulation 9 applies to a given case, so that point needs a closer reading.

Do not assume the other contractor will report an incident that affects your crew, or that your crew will report one on their side. Agree on one contact for each crew, who calls whom first, and where the incident details are kept. Keep that list somewhere a shift lead can reach it fast, such as a printed sheet at the site office or a saved contact on a phone, not an email thread someone must search while a person is hurt. The aim is for these answers to be known before anyone is hurt and before the crew is busy.

Contact lists go out of date quickly. When a foreman changes or a crew adds a member, update the list the same day and send the new copy to the other side. An old phone number is the kind of gap that surfaces only when someone needs it most.

Useful incident notes are simple. They can give the date and time, the place on site, the crews involved, what happened in plain words, who was told and when, and what was done next. Owners and dispatchers do not need to write these notes themselves, but they should agree on who starts them. Share the same notes with the other contractor so both sides describe the same event.

Owners can also ask, before the first shift, how each contractor will tell the other when an incident happens, and whether that arrangement is in writing. A short written answer from each side is far easier to rely on later than a memory of a phone call.

Before any incident, a dispatcher can walk both crews through a scenario: someone is hurt near the boundary between the two work areas. Who makes the first call? Who secures the area? Who tells the other contractor? If the group cannot answer those quickly, the answers are not yet clear enough.

Worked example: a gate, a crane and one contact list

A steel crew and a delivery crew share one gate. Before day one, the two supervisors agree on a one-page plan: the steel lift runs in the morning, deliveries pause during the lift, and the gate closes while the load moves. They name one contact for each crew, agree that a delivery running late gets a phone call rather than a guess, and note the date on the plan. The crane booking note lists the work zone, the overhead line, who evaluates it, and the other crew nearby. After three days, the delivery window moves, so the plan is updated the same day and a new copy goes to both sides.

Settle these points in writing before the first crew arrives: who talks with whom, who evaluates the work zone near overhead power lines, and who reports an incident. Then review the shared plan after the first few days on site. Ask both crews what has not matched the notes, and update the date on the plan when you change it. The table below lists each source and where it applies.

SourceApplies whereWhat the quote says
WorkSafe NZ guidance: HSWA section 34New ZealandSection 34 is titled "PCBU must consult other PCBUs with same duty."
WorkSafe NZ guidance: HSWA section 46New ZealandSection 46 is titled "Duties of other persons at a workplace."
WorkSafe NZ guidance: guidelines section 2.6New ZealandSection 2.6 is titled "Worker engagement, participation and representation."
Oregon construction pageOregonProvides contractors with a flow chart to help them evaluate a work zone when cranes will be operating within 20 feet of an overhead power line.
Schedule 1 textUnited KingdomIt is sufficient compliance with sub-paragraph (1) for a self-employed person to make arrangements for the report to be sent to the relevant enforcing authority by some other person.
Schedule 1 textUnited KingdomWhere required to follow the reporting procedure by regulation 9, the responsible person must notify the relevant enforcing authority in an approved manner.

Related guides: PPE duties on a job site: 3 checks for crews · Crew break rules away from the job site: 3 states · 3 eye protection rules for field techs on the job site.

Sources

More field guides