Workforce forecasting for construction
The hard part of labour planning is not the schedule. It is knowing, in March, that June is short three welders while you can still do something about it. Forecasting in CrewSnap is built around that gap: the requirement comes first, the names come later.
Four mechanics worth understanding
Requirements first, names later
A forecast is entered as crew requirements by project and trade, on an interactive grid. You are saying a project needs four carpenters in the week of the 12th, not who those carpenters are. The names come later, and the forecast still holds without them.
Pending projects count
Projects move through a full lifecycle, pending to active to archived. Work you have not won yet can sit in the forecast as pending, which is the only way to see a labour problem that is two months out rather than two weeks.
Daily or weekly granularity
Plan at whichever resolution matches how you actually run. A lookahead window is configurable, so the board shows the horizon you care about instead of everything at once.
Then assign specific people
Once names exist, specific resources are assigned to project positions. That is the point where the forecast stops being a plan and starts being somebody's week, and where conflict detection starts doing work.
A spreadsheet makes you guess too early
The usual way this goes wrong is that a labour plan and a crew assignment get kept in the same grid. Once the only way to say "we need four carpenters" is to type four names, you cannot record a requirement you have not staffed yet. So the plan quietly becomes a list of people who are already busy, and the shortfall in June is invisible until June.
Separating the two is the whole point. The requirement is a fact about the project. The assignment is a decision about a person. Keeping them apart is what lets a forecast tell you something you did not already know.
The signals you are actually watching for
A forecast is only worth keeping if it tells you when something is wrong. These are on the dashboards rather than buried in a report:
- Crew size forecast graphs
- Understaffed projects alerts
- Overallocated resources warnings
- Unassigned and available resource visibility
- Assignment conflict detection
Equipment forecasts by day, week or project on the same timeline, because a crew that arrives without the lift has the same problem as a crew that does not arrive.
From forecast to somebody's Tuesday
Once people are assigned to positions, the assignment is what the crew is told. Each person is texted or emailed their next-day job, address and site contact, read from the same board, so there is no second place to keep current. How crew notifications work.
If you run prevailing-wage, PLA or union work, the apprentice ratio is checked at the same moment, while the schedule is still a draft and moving somebody is still free. Apprentice ratio tracking.
The full picture of how forecasting, dispatch and ratios fit together is on the crew scheduling page.
Forecast your own next quarter.
Thirty days, no card, no sales call. Load your projects and see where the gaps are.