Most owner-operators reach for a project coordinator when the real bottleneck is that job status lives in one person's head and a string of separate texts, not that there is too little labor to go around. A coordinator hire earns its cost once you are running enough concurrent jobs that no system can substitute for another set of hands; a better shared, current plan fixes the version where the jobs themselves are fine but nobody except you can answer where any of them stand. A 2018 industry study by FMI and PlanGrid found poor communication and bad project data account for 48% of all rework in construction — the exact tax either fix is supposed to remove.
Every owner-operator eventually hits the same wall: too many jobs, not enough of you to go around, and a client base that starts calling before you've called them. The instinct is to hire a project coordinator. Sometimes that's exactly right. Just as often, the jobs themselves are fine — the actual bottleneck is that job status lives in one person's head and a string of separate texts, and no new hire fixes that until they've spent a month extracting it from you first.
Two different problems get treated as the same hire
A capacity problem means there is genuinely too much physical and administrative work for one person: nobody is on-site to catch a sub who no-shows, nobody confirms deliveries, nobody is free to take the call while you're mid-walkthrough on another job. An information problem looks similar from the outside but is different underneath: the jobs are moving fine, subs know what to do, but you are the only person who can answer "where are we" on any given job, and every update is reactive instead of sent before the client has to ask. A coordinator solves the first. A shared, current plan solves the second — and costs a lot less.
What the group-text-and-spreadsheet system actually costs you
This isn't just a communication annoyance — it shows up as rework. A 2018 industry study by FMI and PlanGrid, surveying nearly 600 construction leaders, found that poor communication and bad project data together account for 48% of all rework in U.S. construction, with poor communication alone responsible for about a quarter of it. That's the tax a business pays for the plan living in someone's head instead of somewhere everyone can see it — and it's a tax neither more labor nor more hours fixes on its own.
The capacity test
Ask honestly: in the last month, did a job stall because there was literally no one available to be somewhere or make a call? Did a sub go unsupervised because you were on another site? Are you turning down work you'd otherwise take because you don't have the hands to run it? If yes, that's a real capacity gap, and a coordinator (or another PM, or simply hiring ahead of the workload) is the right tool — no system replaces a second set of eyes on a job site.
The information test
Ask the opposite question: are the jobs themselves actually fine — subs sequenced, materials arriving, inspections passing — but you're still the bottleneck because you're the only one who can say where things stand? Do clients call before you've told them anything, because nobody proactively sent an update? Do you spend evenings re-explaining the same job status to three different people? That's an information problem, and it is usually cheaper and faster to fix with a better shared plan and a standing update habit than with a new salary.
Fix the system first
Before committing to a coordinator's salary, try closing the information gap: one shared, current plan that anyone on the job can check, and a client-update cadence that goes out after every check-in instead of only when someone asks. Software built for this — Lilli, for instance — proposes the update draft for you to approve after a check-in, so the habit doesn't depend on you remembering to sit down and write it. If that alone clears the "where are we" calls and the after-hours re-explaining, you've solved the expensive problem for the price of a tool, not a hire.
If you still need the hire
If you've fixed the information gap and the wall is still there — jobs stalling for lack of a physical presence, work you're turning away because there's no one to run it — that's a genuine capacity problem, and it's worth paying for. Just make sure you're hiring to solve that problem specifically, not paying a salary to do a job a current, shared plan could have done for the cost of the discipline to keep it updated.
Questions, answered.
How do I know if I need a project coordinator or just a better system?
Separate the two problems. If jobs are stalling because there is no one physically available to catch a sub on-site, confirm a delivery, or make a call while you're on a roof, that is a capacity problem — a coordinator fixes it. If the jobs are actually fine and moving, but you are the only person who can answer "where are we" on any of them, that is an information problem — a shared, current plan fixes it for a fraction of the cost.
What does a construction project coordinator do day to day?
Typically: confirming sub and vendor schedules, chasing material and permit status, updating clients, and keeping whatever tracking system the business uses current. Most of that list is information work, not physical labor — which is exactly why it's worth checking whether a better system closes the gap before you commit to the hire.
How much rework does poor communication really cause on a job?
A 2018 study by FMI and PlanGrid, based on input from nearly 600 construction industry leaders, found that poor communication and bad project data together account for 48% of all rework in the U.S. construction industry — with poor communication alone responsible for roughly a quarter of it. That is the cost a coordinator or a better system is being asked to eliminate.
Can software replace a project coordinator?
Not for capacity — software cannot physically walk a site or catch a sub who no-shows. But a lot of what gets billed as coordinator work is actually keeping one shared plan current and drafting the client update after every check-in, and that part is exactly what a live, propose-then-approve plan is built to do. You still decide; the software removes the manual chasing.
What's the first sign a job is slipping from a communication problem, not a capacity one?
The client calls before you have news to give them. That is almost always an information failure, not a labor shortage — the job may be on track, but nobody proactively told the client, so they filled the silence with a phone call. Fix the update cadence before you assume you need to hire.