Before hiring another project manager, find out how your current project managers spend their week. If much of it goes to documentation - RFIs, submittals, change order paperwork, schedule updates, selections and client emails - moving that work to a project coordinator or assistant project manager can add capacity faster, and for less, than another PM. If the constraint is judgment - buyout, subcontractor performance, schedule risk and client relationships - you need another project manager.
Most general contractors and remodelers skip that check. Project managers are working late, jobs are slipping, and a new PM is the obvious move. Sometimes it is the right one. It is also the most expensive way to buy back project manager time.
Ask each project manager to log one normal week, then sort the hours into two columns.
| Judgment: needs a project manager | Production: needs someone competent |
|---|---|
| Buyout and subcontractor selection | RFI logs and follow-up |
| Schedule strategy and recovery | Submittal packages and tracking |
| Negotiating change orders with the owner | Change order documentation and backup |
| Client relationships and difficult conversations | Meeting minutes and action items |
| Subcontractor performance problems | Schedule updates from field reports |
| Cost-to-complete and risk decisions | Insurance certificates, lien waivers and compliance documents |
| Site walks and quality calls | Closeout documents, warranties and manuals |
If the second column is eating the week, you do not have a project manager shortage yet. You have a production problem sitting on project managers' desks. If the first column is still overloaded once the second is gone - too many clients, too many decisions waiting, not enough experienced people to make them - another project manager is the right hire.
Check one more thing while the log is open. If project managers are also estimating new work, the bottleneck may be preconstruction rather than delivery, and a remote estimator takes that off their desks without adding a PM.
Start with work that recurs every week, follows a clear format and has an obvious definition of done. For most firms the order looks something like this:
Our list of 25 tasks construction companies can delegate goes wider, across estimating, accounting and administration.
| Project coordinator | Assistant project manager | Project manager | |
|---|---|---|---|
| Carries | Information and documentation | Delegated responsibility, within limits the PM sets | The project: cost, schedule, quality and the client |
| Typical work | Submittals, RFIs, logs, minutes, schedule updates and closeout documents | Cost tracking, procurement follow-through, change order preparation and subcontractor coordination | Buyout, negotiation, risk, client relationships and final decisions |
| Decides | Nothing on the project's behalf | Routine matters inside agreed limits | Everything that matters |
| Hire when | PMs are buried in paperwork | PMs need a second in command, not only paperwork help | There are more decisions than experienced people to make them |
A remote project coordinator is the earlier hire for most firms. A remote assistant project manager makes sense once there is enough delegated responsibility to justify it, and the role is a common path to developing your next project manager rather than recruiting one. For company-wide paperwork that is not tied to a single project, a construction administrative assistant is often enough.
If the choice you are really weighing is between more estimating capacity and more delivery capacity, see estimator or project coordinator: which do you need first.
Yes. Commercial general contractors are buried in submittals, RFIs and pay applications. Remodelers and custom builders are buried in the client.
A residential project manager often spends the week answering homeowner questions, chasing selections, explaining change orders and repeating schedule updates across several smaller jobs at once, frequently while also being the owner. The delegation list shifts accordingly:
The principle is the same on both sides of the industry. The client relationship and the judgment calls stay with the project manager. The documentation that supports them does not have to.
The U.S. Bureau of Labor Statistics reports a median annual wage of $114,990 for construction managers in May 2025, from $98,390 in residential building construction to $126,690 in nonresidential building construction (BLS Occupational Outlook Handbook). That is before payroll taxes, benefits, a vehicle or allowance, software and recruiting, and before the months a new PM needs to learn how your company runs.
That cost is justified when the constraint is judgment. It is hard to justify when the constraint is paperwork, because you would be paying a project manager's wage for work that does not need one, and the new PM will soon be buried under the same documentation as everyone else.
If the handoff does not actually happen, no hire will fix the problem. A coordinator added while project managers keep doing the same tasks ends up underused, and the wrong conclusion gets drawn about the role.
A project manager is responsible for the project's outcome - cost, schedule, quality and the client relationship - and makes the decisions that affect it. A project coordinator supports the project manager by managing information and documentation, such as submittals, RFIs, logs, meeting minutes and schedule updates, without making decisions on the project's behalf.
There is no standard number. It depends on project size and complexity, how far apart the sites are, how demanding the clients are and how much documentation support the project manager has. The same person can usually carry more work with a coordinator handling the paperwork than without one.
Much of the role can. Cost tracking, procurement follow-through, change order preparation, documentation and subcontractor coordination happen in software and by phone. Site walks, inspections and in-person meetings stay with your local team.
The U.S. Bureau of Labor Statistics reports a median annual wage of $114,990 for construction managers in May 2025. Medians were lower in residential building construction and higher in nonresidential building and heavy and civil engineering construction, and pay varies widely by region and project type.
When the judgment work is still overloaded after documentation has moved: too many clients needing attention, too many decisions waiting, or not enough experienced people to run jobs without the owner stepping in. Support roles make project managers more productive. They do not replace the experience it takes to run a project.
Within a maximum of approximately two weeks we can normally present two to three pre-screened candidates who meet the requirements of the position and are ready to be interviewed. The final hiring time depends mainly on how quickly your own evaluation and decision process moves.
Construction is a physical industry, and the reasonable first reaction to remote staffing is scepticism. Buildings do not get built over video calls.
But a contracting company is two businesses stapled together. One of them happens on site and cannot move. The other happens in software - estimating, documentation, scheduling, accounting, procurement, correspondence - and has already been remote-capable for years without most contractors noticing, because the people doing it happened to sit in the office.
The useful question is not whether construction work can be done remotely. It is which parts of your office already run entirely through systems that a competent person can reach from anywhere.
One question sorts almost every role correctly.
Does the work require touching something, being somewhere, or being physically present to exercise authority?
If yes, it is a local role. Installing, inspecting, supervising, receiving material, signing for something in person, walking a site with a client.
If no - if the work is reading, calculating, coordinating, documenting, communicating and recording - then location is a habit rather than a requirement.
Apply that honestly and most contractors find that between a third and a half of their office workload falls on the remote side of the line.
Quantity takeoff, plan reading, bid solicitation, subcontractor follow-up, quote comparison and proposal assembly are all done from digital drawings inside estimating software. Nothing in that list improves by being in the building. What stays local is the site walk, the scope judgment on unusual conditions, and sitting in front of a client.
Submittal registers, transmittals, RFI logs, document control, schedule updates, meeting minutes and closeout assembly are information work performed in your project management platform. This is often the single largest pool of delegatable time in a contracting business, because it is currently spread across project managers who are paid for judgment.
Payables, receivables, job costing, reconciliation, lien waiver collection, subcontractor compliance records, certified payroll preparation and month-end reporting all run through accounting software and document storage. Cheque signing and any in-person banking stay with you.
Shop drawings, as-builts, markups, coordination drawings and permit sets are produced in CAD and BIM environments that are already collaborative and already remote by design. Field verification and anything requiring a professional seal stay with your licensed people.
For service-based contractors - mechanical, plumbing, electrical, roofing, restoration - the board, the phone and the customer record are all software. A dispatcher assigns and re-sequences the day remotely exactly as they would from a desk in your office. Parts, vehicles and keys stay local.
Job file maintenance, correspondence, compliance document tracking, permit portal work, insurance certificate chasing and record keeping are the definition of location-independent work.
It is worth being equally clear about the other side of the line, because vagueness here is what makes contractors suspicious of the whole idea.
Field labour of any trade. Site supervision and superintendence. Quality and safety inspection. Physical measurement and field verification. Receiving and inspecting material. Equipment operation. Anything requiring a licensed professional to be physically present or to seal work. Client-facing site walks where presence is the point.
Nobody credible places these remotely, and a staffing partner who blurs the boundary is not one to work with.
Some roles are genuinely partial, and the honest answer is that they split rather than move.
A project manager is a good example. The judgment, the client relationship and the site presence are local. The documentation, reporting, procurement follow-through and coordination underneath them are not - which is why an assistant project manager or coordinator working remotely is common while a fully remote project manager is not.
Procurement splits the same way. Sourcing, purchase orders, expediting and delivery tracking are remote. Physical receiving and inspection are not.
The mistake is treating these as all-or-nothing. Most of the available capacity is in the half that moves.
Three things, in order of how often they are the cause of failure.
Your systems have to be reachable. If your project documentation lives in a filing cabinet and your job costing lives in the owner's head, no remote role can function. Most contractors are further along than they think, because their software already runs in a browser.
The scope has to be written down. Remote roles fail most often because nobody defined what moves. Listing the specific recurring tasks that transfer, before the person starts, is the single highest-return hour in the whole process.
Working hours have to overlap. Coordination roles need to be reachable when your field team and your customers are active. This is a scheduling decision to make at the start of an engagement rather than a discovery to make in week three.
Take one week and log where your most expensive office person actually spent their time. Separate the entries into work that required their judgment and work that simply required somebody competent.
The second column is your first remote role. It is usually larger than expected, and it is usually documentation.
No. Every role we place is a professional office or back-office position performed remotely - estimating, project coordination, accounting and bookkeeping, drafting, dispatch, customer service and administration. Trade labour, site supervision and inspection stay with your own workforce.
Whichever is currently costing the most. For general contractors and builders that is usually estimating or project coordination. For service-based contractors it is usually dispatch or service coordination. For companies where job costing has stopped being reliable, it is bookkeeping, because everything else is measured against it.
Yes. The roles are defined by working inside your existing systems - your estimating package, project management platform, accounting software and document storage - rather than introducing anything new. Proficiency in your specific platforms is part of what we screen for.
Coverage of your working hours is agreed before an engagement starts. Availability varies by role and by the hours required, which is why it is worth raising early rather than assuming.
No. Smaller contractors often benefit earliest, because the gap between what the field can deliver and what the office can administer is proportionally widest before there is a dedicated office team at all.
Within a maximum of approximately two weeks we can normally present two to three pre-screened candidates who meet the requirements of the position and are ready to be interviewed. The final hiring time depends mainly on how quickly your own evaluation and decision process moves.
When a contractor asks whether to add an estimator or a project coordinator first, the real question is usually simpler than it sounds: which of my two bottlenecks is costing me more right now.
One of them stops you winning work. The other stops you keeping the margin on the work you already won. Both feel urgent from inside the business, and they feel urgent in the same way - a senior person is drowning and something is slipping. But they are different failures with different price tags, and the cheaper fix is rarely the one that gets chosen first.
This is a decision you can usually make with two numbers and an afternoon.
An estimator changes how much work you can price, which changes how much work you can win.
The mechanism is straightforward. Most contractors have a fixed weekly ceiling on bids, set by whoever prices the work. When invitations exceed that ceiling, the excess is declined - usually quietly, usually by the person already at capacity, usually without anyone recording that a decision was made. Adding estimating capacity lifts the ceiling.
What that looks like in practice: quantity takeoffs, plan reading, bid solicitation and subcontractor follow-up, comparison of received quotes, proposal assembly, and the administrative work of keeping a bid calendar honest.
What it does not change: your win rate on the bids you were already submitting, your pricing judgment, or your relationships. Capacity is not skill. If you are pricing forty jobs and winning two, an estimator gives you eighty losses instead of forty. The constraint there is something else.
A project coordinator changes how much of your project managers' time goes to managing projects rather than administering them.
Most project managers spend somewhere between a third and half their week on work that does not require their judgment: chasing submittals, logging RFIs, updating schedules, assembling documentation, following up with subcontractors on paperwork, and preparing the reports that tell everyone else what is happening. None of that needs a project manager. All of it needs somebody.
What that looks like in practice: submittal registers and transmittals, RFI logs, document control, schedule updates, subcontractor communication, meeting minutes, closeout package assembly, and progress reporting.
What it does not change: decisions about sequence, cost, risk or client relationships. A coordinator moves information; a project manager makes calls. Confusing the two produces a coordinator who is blocked constantly and a project manager who is still doing the work.
The diagnosis is usually visible in how the pain gets described.
"We are turning down bid invitations." Estimator. And the cost is measurable: count the invitations declined last quarter, apply your average win rate and average contract value, and you have the number.
"Our project managers are working nights and things are still slipping." Coordinator. The cost is harder to see but usually larger, because it shows up as change orders unclaimed, submittals late, closeout dragging, and retention held longer than it should be.
"We won a big job and it exposed everything." Coordinator, urgently. Growth in project size raises documentation load faster than it raises field complexity.
"Bids go out late and half-finished." Estimator, but check first whether the estimator is late because they are also coordinating live jobs. That is common in companies under about thirty people, and the fix is the coordinator.
The default instinct is to hire the estimator first, because winning work feels like the growth move and administration feels like overhead.
That instinct is right roughly half the time. The other half, it makes things worse in a specific way: you win more work, that work lands on project managers who were already at capacity, and the margin you gained on volume is given back in poor execution, missed change orders and slow closeout. The company gets busier and no more profitable.
The question worth asking before hiring an estimator is: if we won thirty percent more work next quarter, could we deliver it with the office we have? If the honest answer is no, the coordinator is the first hire, and the estimator is the second.
Your bid pipeline is constrained and your delivery side has headroom. You are declining invitations. Your win rate on submitted bids is healthy, so more submissions convert predictably. Preconstruction is one person deep and that person is a single point of failure.
Your project managers are the constraint. Documentation is late. Change orders are being identified after the window to claim them. Closeout takes months. You are about to start a project materially larger than your usual size. Or your estimator is being pulled into live job administration, in which case the coordinator fixes both problems at once.
Past roughly twenty to thirty office and field staff, most contractors need both, and the two roles reinforce each other: the estimator fills the pipeline, the coordinator makes the delivery of that pipeline survivable. Adding one without the other simply moves the bottleneck rather than removing it.
This is the part that determines whether either hire works.
A support role only creates capacity if work actually moves to it. The common failure is that a coordinator is added and project managers keep doing the same tasks, because delegating requires deciding what to delegate and then living with it being done differently. Six weeks later the coordinator is underused and the conclusion is that the role does not work.
Before either hire, write down the specific recurring tasks that will move, and who currently does them - the list in before you hire another project manager is a good place to start. If you cannot fill a page, the problem may not be capacity.
Two numbers. First: bid invitations declined in the last ninety days, multiplied by your win rate and average contract value. Second: hours your project managers spent last week on documentation, chasing and reporting, multiplied by their loaded cost, then annualised.
Whichever is larger is your first hire. If they are close, hire the coordinator, because it protects the value of everything you win afterwards.
Many small contractors run it that way, and it works until bid volume and live job volume peak at the same time - which they tend to do. The person then chooses, usually in favour of whatever is loudest, and the other side slips. If you are seeing bids go out late during busy delivery periods, that is the structure failing rather than the person.
Either works remotely, because both are systems and documentation roles. If you can only place one remotely, most contractors get more out of placing the one that carries the higher volume of routine production work - usually the coordinator early on, and the estimator once bid volume is the binding constraint.
Yes. The role involves submittals, RFIs, schedules and closeout documentation, and someone without construction context will not recognise when a submittal register is wrong or when an RFI response does not actually answer the question. General administrative experience is not a substitute.
An assistant project manager carries delegated decision-making - cost tracking, procurement follow-through, and judgment within limits set by the project manager. A coordinator carries information flow and documentation. The coordinator is the earlier hire for most companies; the assistant project manager makes sense once there is enough delegated authority to justify it.
That is common, and it is the usual reason contractors look at remote support rather than a local hire. The comparison between remote and in-house estimating is a separate decision with its own arithmetic, as is the choice between a per-bid estimating service and a dedicated estimator. Both are worth running properly before assuming a full-time local position is the only option.
Within a maximum of approximately two weeks we can normally present two to three pre-screened candidates who meet the requirements of the position and are ready to be interviewed. The final hiring time depends mainly on how quickly your own evaluation and decision process moves.
Ask ten contractors what a construction virtual assistant does and you will get ten answers. Someone who answers the phone. Someone who chases lien waivers. Someone in another country doing takeoffs for a fraction of what an estimator costs. All three are being sold under the same label, and the gap between them is the reason most first attempts go badly.
The term describes where a person sits. It says nothing about what they know.
That is a real problem when the work is construction. A general assistant can keep a calendar and clear an inbox for any business on earth. A submittal log is not any business on earth. Neither is a schedule of values, a certified payroll report, or a bid invitation that expires on Thursday. Handing that work to someone hired for their availability rather than their background produces exactly what you would expect, and the contractor concludes that remote support does not work.
It works. The label is just doing a lot of damage.
There are two distinct things being sold here, and it is worth being blunt about the difference.
General virtual assistance is capacity. You buy hours from a pool, and those hours can be pointed at inbox management, data entry, scheduling, basic customer service and general administration. It is genuinely useful, it is usually cheap, and it requires almost no onboarding because the work requires almost no context.
Remote construction staffing is a hire. You define a position, someone recruits against that definition, and a professional with relevant industry experience joins your team and owns a piece of your operation. It costs more, takes longer to set up, and produces something a pool of hours cannot: someone who knows what an RFI is for and why the answer matters.
Neither is wrong. But if you need the second and buy the first, you will spend three months proving to yourself that outsourcing does not work, when what actually happened is that you bought the wrong product.
When the role is defined properly, the work falls into four areas. Most contractors start in one of them and expand later.
Quantity takeoffs from drawings and specifications. Material and labor pricing. Subcontractor solicitation, follow-up and bid levelling. Proposal assembly. Plan reading and budget preparation.
This is the area contractors are most skeptical about and where the capacity gain is usually largest. The reason is arithmetic: an estimator's week is mostly measurement and data entry, and only a slice of it is scope judgment. Moving the first part off their desk does not dilute the second. It protects it.
RFIs, submittals, change order paperwork, schedule updates, document control, meeting minutes, and the follow-up that keeps all of it moving. Communication with field teams, suppliers and clients.
Project managers rarely leave because they are tired of managing projects. They leave because they spend their week doing paperwork about projects. This is the area that fixes that, and it is the first place to look before you hire another project manager.
Accounts payable and receivable, job costing, project billing, invoice processing, bank reconciliations, payroll support and financial reporting.
Construction accounting is its own discipline. Retainage, progress billing, cost codes and committed cost do not behave like they do in other industries, and a bookkeeper who has never seen them will produce numbers you cannot make decisions from.
Permit applications and tracking, CRM upkeep, scheduling, dispatching, service coordination, document handling and customer communication.
This is the closest to what people picture when they hear the phrase, and it is still worth doing properly. A dispatcher who understands that a technician sitting idle costs more than the phone call to reroute them is a different hire from someone answering a queue.
An honest version of this page has to include the boundary, because the vendors who blur it are the reason the category has a credibility problem.
That last one is the most commonly misunderstood. The role is not there to make decisions. It is there to make sure the decisions reach you with the work already done.
Before scoping a role, run the work you are considering through three questions. They are simple and they are unforgiving.
Work that clears all three moves cleanly. Work that fails one of them will fail after you hire, which is a considerably more expensive place to find out.
When these arrangements collapse, it is rarely the person. It is almost always one of three setup failures.
The role was never defined. Someone was hired for hours rather than for a position, and the work was assigned as it came up. That produces a person who is always busy and never responsible for anything, which is indistinguishable from a person who is not helping.
There was no review path. Nobody agreed who checks the output, how quickly, or what happens when something is wrong. Early work in any new role needs close review. Skipping it does not save time, it defers the cost to the first mistake that reaches a client.
The software was an afterthought. The position was scoped, someone was hired, and then it turned out the work required a platform they had never used. Which tools the role has to work in belongs in the job definition, before recruiting starts, not after.
None of these are remote problems. They are hiring problems that remote work makes less forgiving, because you cannot fix a vague role by walking past someone's desk.
A properly scoped remote role behaves like any other member of your team. They work in your systems rather than exchanging files. They attend the meetings the position requires. They own a defined piece of the operation and are accountable for it. They are hired for a schedule that overlaps yours, part time or full time depending on what the work needs.
The difference is that the search for them was not limited to people who can drive to your office.
For a lot of construction companies, that is the entire point. The local pool of experienced estimators, coordinators and construction accountants is small, expensive, and being fought over by everyone else in the market. Widening the search is not a cost-cutting exercise. It is how the position gets filled at all.
A virtual assistant service sells general support hours from a shared pool, with little or no industry context. Remote construction staffing recruits for a specific position in your company, screening candidates against experience, technical knowledge, English level, required software and availability before anyone reaches you. The first is capacity. The second is a hire.
Estimating and takeoffs, project coordination, RFIs and submittals, change order documentation, scheduling support, permit coordination, billing, bookkeeping, drafting, CRM upkeep, dispatching and customer communication. The common factor is that the work is recurring, definable and done on a screen.
That is the intended setup. Working in your existing platform rather than exchanging files by email is what keeps a single source of truth. Which platforms the role requires is agreed before recruiting begins, and candidates are screened against that requirement.
No. What matters is whether there is recurring work that can be clearly defined and handed over, not company size. A ten-person contractor with an owner doing takeoffs at night has a stronger case than a fifty-person contractor whose office work is already distributed properly.
Within a maximum of approximately two weeks we can normally present two to three pre-screened candidates who meet the requirements of the position and are ready to be interviewed. The final hiring time from there depends mainly on how quickly your own evaluation and decision process moves.
Start with the bottleneck rather than the job title. The work that is piling up, or that a senior person is doing at night, usually identifies the position on its own. Defining it properly is part of the consultation, not something you have to arrive with.
