Most contractors track headcount and utilization across their projects. Few track the balance of experienced and newer team members. Rookie ratio, the proportion of seasoned people to newer ones on any given project, fills that gap. It’s not a formal industry metric, and that’s part of the problem. A project can be fully staffed by every measure and still be carrying too many people who haven’t done this type of work before.
Table of Contents
“When you’re placing a person, you’re not just placing a robot. You’re placing a human. And understanding their relationships can be a big part of a project team,” says Matthew Walsh, Senior Operations Technology Manager at Power Construction.
The construction experience gap
The numbers behind this are straightforward. 41% of the current construction workforce is projected to retire by 2031, according to the National Center for Construction Education and Research. The industry needs approximately 500,000 new workers just to meet current demand. And the people replacing retirees aren’t staying long, with average employee tenure in construction sitting at just 3.9 years according to the Bureau of Labor Statistics.
The workforce is turning over faster than institutional knowledge can transfer. A project manager who started three years ago is now one of the more experienced people on staff. The superintendent with 20 years of relationships, sector knowledge, and judgment about which subcontractors actually deliver is approaching retirement and has no direct replacement in the pipeline. That superintendent’s knowledge isn’t documented anywhere. It lives in their head, in the relationships they’ve built with owners and architects, and in the instincts they’ve developed from seeing hundreds of situations play out on job sites. 92% of construction firms report having a hard time finding workers to hire. That’s one of the top challenges facing construction right now, and it affects who ends up on which project just as much as it affects headcount.
What the rookie ratio looks like on a project
To make this concrete, consider an eight-person project team:
| Role | Years with company | Build type experience |
|---|---|---|
| Project Executive | 15 years | Healthcare, education, commercial |
| Senior PM | 8 years | Healthcare, mixed-use |
| Project Manager | 2 years | One commercial project |
| Assistant PM | 1 year | None completed |
| Superintendent | 12 years | Healthcare specialist |
| Asst. Superintendent | 3 years | Two commercial projects |
| Field Engineer | 6 months | Training |
| Project Coordinator | 1 year | One project |
Three experienced members and five newer ones. Whether that works depends on the project. For a straightforward commercial build where the superintendent has done dozens of similar jobs, it probably does. For a first-time healthcare project with a demanding owner, that balance creates risk that nobody officially measured or accounted for.
Newer team members can and do perform well, especially with strong leadership around them. The concern is that nobody tracks this balance across the portfolio, so it happens by accident rather than by design.
What happens when too many team members are new
A high rookie ratio doesn’t usually produce a single dramatic failure. The effects are more like friction that builds across dozens of small interactions over the course of a project.
Submittals take longer because the PM doesn’t know the architect’s preferences from a previous project. RFIs increase because field engineers are learning systems they haven’t encountered before. The superintendent spends more time coaching and less time managing subcontractors. Decisions that an experienced team would handle in a hallway conversation become formal escalations because people don’t yet have the relationships or pattern recognition to move quickly.
“Team dynamics are really important to us. We don’t just throw people on a project without thinking about how they’ll work with each other. We look for strengths that complement each other,” says Jamie Miller, Director of Engineering Development at Sellen Construction. That kind of complementary pairing requires knowing who has worked together before, who has sector-specific knowledge, and who needs mentorship on a given build type. Without that information centralized and visible, team assembly becomes a best guess.
There’s also a safety dimension that deserves plain language. “Company morale goes down, employees are burnt out because they’re going to do whatever it takes to get the job done. It affects your employee retention and increases safety incidents on a project,” says Shawn Gallant, COO of Columbia Construction. “You never want an unsafe site because you’re cutting a dollar on staffing. It just doesn’t make sense.”
A team where experienced supervision is stretched thin across too many people who need guidance creates conditions where things get missed. Not because anyone is careless, but because one superintendent can only be in one place at a time. The newer assistant superintendent who hasn’t seen a particular sequencing issue before won’t necessarily catch it without someone nearby who has. These aren’t dramatic failures that make the news. They’re the kind of everyday quality slippage that shows up later as rework, schedule delays, and strained client relationships.
Measuring experience across your project portfolio
The rookie ratio becomes useful when you can see it at the portfolio level.
You probably know who is assigned to which project. Building balanced project teams requires answering a harder question: across all your active projects, which ones have the highest concentration of newer team members? Which projects have experienced people who could be shared or reallocated. Where the mentorship opportunities are, and where the risk concentrations sit.
“Previously, there was a gatekeeper. We would communicate project needs, and they would go back to their desk to figure it out. It was siloed,” says Gallant. “We quickly identified that we could improve how we manage our workforce. It needs to be collaborative. You need the input of your leaders and your team.”
When experience data is centralized, a few things become possible that spreadsheets can’t support. You can assess a proposed team lineup before it’s finalized, checking whether it has enough sector experience, enough tenure, and enough people who have worked together before. That assessment takes minutes instead of a week of phone calls and emails. A newer PM in one office might benefit from pairing with a senior superintendent from another office who has deep experience in the relevant build type. If the rookie ratio across your portfolio is trending toward inexperience in a specific role type, your HR team can start recruiting before the gap becomes a crisis rather than reacting to it after a project struggles.
“I think we’ve been building better teams from the project’s inception. We have the RFP in hand and are all on the same platform. We collaborate on the team we assemble immediately, which can help us win a project,” says Miller.
How much experience does a project team need
There is no universal benchmark here. The right rookie ratio depends on project complexity, client expectations, build type, and the specific strengths of the individuals involved. But some patterns hold.
Higher-risk projects need a lower rookie ratio. A first-time-for-the-company build type, a project with a difficult owner history, or a job with tight schedule constraints all need more experienced coverage. The margin for learning on the job is thinner, and the cost of rework or schedule delays on these projects is proportionally larger.
Growth phases require particular attention. When a contractor is winning more work than usual, the natural tendency is to spread experienced people thin across more projects and fill in with newer hires. Gilbane Building Company faced exactly this when expanding into data centers and advanced manufacturing, sectors that required specialized expertise their existing teams hadn’t built before.
“Bridgit gave us a centralized, data-driven approach that’s fully integrated and user-friendly. It’s helped us eliminate silos and turn workforce data into a competitive advantage,” says Alexander Gutman, Gilbane’s Chief Technology Officer. Without that kind of visibility, the projects that suffer tend to be the ones where the experienced person was technically assigned but practically unavailable because they were covering problems on another job.
Mentorship also requires deliberate pairing, not just proximity. Putting a newer PM on the same project as an experienced superintendent doesn’t automatically create knowledge transfer. The two roles interact differently with the work, the owner, and the subcontractors. A newer PM learns project management from a senior PM, not from a superintendent, no matter how experienced that superintendent is. Effective mentorship happens when someone with relevant role-specific experience is paired with someone who needs that particular guidance, and that pairing is planned rather than coincidental.
Experience tracking and workforce planning
The practical challenge is that the underlying data, who has experience with what, rarely lives in one place.
Internal resumes that track build type, market sector, client history, and past team collaboration give operations leaders the information they need to assess experience distribution before assigning teams. The question “who has done this before?” should take seconds to answer, not a series of phone calls across offices.
When that experience data connects to workforce forecasting, the rookie ratio becomes forward-looking rather than reactive. Instead of discovering experience gaps after a project starts and problems emerge, you can see six months out where the portfolio will be heavy on newer team members and plan accordingly. That might mean accelerating a hire, reassigning an experienced PM from a project entering closeout, or making a go/no-go decision on a pursuit based partly on whether the right team exists to deliver it.
“I never really felt like I had the time to keep up with the resource management during my day job. To be honest, it was a Saturday when I used to try to hammer through all of our resource planning,” says Jeremy Moe, Operations Manager at The Boldt Company.
The rookie ratio should be a visible dimension of the workforce data that already informs weekly planning meetings, pursuit discussions, and hiring conversations. The contractors who track this balance are building teams that perform consistently even as the workforce gets younger. Experience won’t take care of itself, not at the rate people are retiring and turning over. Workforce planning platforms like Bridgit make it possible to see that balance before the project starts, rather than discovering it after problems surface.
