How to coordinate contractors without becoming a full-time project manager

Most people managing a commercial building don't describe their role as contractor management, but that's what a significant portion of their week amounts to. Scheduling access, chasing confirmation, dealing with the gap between what was agreed and what was delivered, fielding calls from contractors who have questions they should have asked before they arrived.

The frustrating part is that this overhead is mostly structural. It comes from a few predictable failure points that repeat across every building and every trade, and which can be reduced with some deliberate process rather than more time.

The briefing problem

Most contractor problems start before the job begins. The contractor arrives without knowing what access they have, who to call if they need something, what the building's rules are for working hours or noise, or exactly what the scope of the job is. So they improvise, or they call you.

A one-page site briefing document eliminates a surprising proportion of this. It doesn't need to be elaborate: building address, entry procedure, on-site contact, parking, noise and working hours restrictions, what to do if they find additional scope, and where to leave keys or cards on the way out. Write it once, update it occasionally, send it with every job instruction.

The scope ambiguity problem

Contractors operate on the assumption that the person placing the job knows what they want. When the scope is vague, they make a reasonable guess, complete what they think was asked for, and invoice accordingly. Then you review it and find they've done the wrong thing, or half the thing, or something adjacent to the thing.

Getting into the habit of writing the job instruction in a specific format helps: what the symptom is, what you want investigated or repaired, and what the output should be (verbal report, written report, fixed and signed off). That last part matters. "Fix the leak" leaves too much room. "Fix the leak and send a brief email confirming what was done and what part was replaced" does not.

The confirmation call

A confirmation call the day before a scheduled job sounds unnecessary until you've had a contractor not show up without warning for the third time and had to rearrange building access, reschedule the tenant who was going to clear the affected area, and explain to the building owner why the maintenance schedule has slipped again.

One call, the day before, confirming time of arrival and flagging any issues. This is a coordination habit that takes two minutes and saves considerably more.

Post-job sign-off

The job is done when you've confirmed it is, not when the contractor says it is. That doesn't require a lengthy inspection — it means checking that the specific item from the job instruction was addressed, that the site was left clean, and that you have something in writing that says what was done. That record matters when the same problem recurs six months later and you need to know whether it's a new failure or a repair that didn't hold.

None of this is complicated. The difficulty is consistency — maintaining these habits across every contractor, every job, while also managing everything else that's on the plate. That's usually when it makes sense to look at whether the coordination function should be someone's actual job rather than an overhead everyone's absorbing.