How far ahead of each phase gate should sourcing begin?

It varies by phase, from roughly 4 to 8 weeks for Pre-FEED roles up to 8 to 12 weeks for the detailed design phase, reflecting differences in role seniority, scarcity, and headcount volume.

Why anchor a staffing roadmap to phase gates instead of calendar dates?

Because capital program schedules commonly shift, and a roadmap tied to phase gates remains functionally accurate as the underlying calendar dates move, while a fixed-date plan becomes obsolete.

Should the roadmap specify individual roles or just headcount ranges?

It should specify discipline mix at each gate, translating headcount ranges into concrete discipline targets rather than leaving sourcing to interpret a generic number.

How should a workforce partner use this roadmap?

As a basis for proactive pipeline building ahead of each phase gate, rather than waiting for individual requisitions to open before starting to source.

Phase-Gate Staffing Roadmap for Capital Programs

For each upcoming phase gate, define discipline requirements, headcount targets, and lead times, and build the hiring roadmap 8 to 12 weeks ahead of each transition. That single principle, applied consistently across a program's full lifecycle, is what a phase-gate staffing roadmap actually is, and it is more durable than a plan built against fixed calendar dates.

Why phase gates, not calendar dates, should anchor the roadmap

Capital program schedules shift, sometimes significantly, due to permitting delays, design changes, or external market conditions. A staffing roadmap tied to fixed calendar dates becomes obsolete the moment the schedule moves. A roadmap anchored to phase gates instead, with lead times expressed relative to each gate, remains functionally accurate even as the underlying calendar dates shift, since the lead-time countdown simply moves with the gate.

Pre-FEED / Conceptual: 2 to 5 senior specialists, 4 to 8 weeks lead time; engage a workforce partner before the phase formally begins
FEED: 10 to 30 engineers, 6 to 10 weeks lead time; discipline leads must be in place before FEED starts, not during it
Detailed Design: 50 to 200-plus engineers, 8 to 12 weeks lead time; the highest-volume, highest-complexity staffing phase
Procurement: 10 to 40 specialists, 4 to 6 weeks lead time; often needs to begin before detailed design fully completes
Construction: 20 to 100-plus engineers, 2 to 4 weeks lead time, achievable only if the pipeline was built during detailed design
Commissioning & Startup: 10 to 50 engineers, 2 to 6 weeks lead time; the scarcest resource at project completion, engage during construction

Build the template with discipline detail, not just headcount ranges

A roadmap that only specifies headcount ranges by phase repeats the same mistake a generic workforce plan makes. Each phase-gate entry should specify the discipline mix expected at that gate, translating a range like "10 to 30 engineers" into something closer to "process, mechanical, civil, and electrical leads plus supporting engineers," which gives sourcing a concrete target.

Phase-gate staffing roadmap template
Phase gate	Key disciplines	Workforce scale	Sourcing start (relative to gate)
Pre-FEED	Owner's engineers, project managers, cost estimators	2–5 senior specialists	4–8 weeks before gate
FEED	Process, mechanical, civil, electrical leads	10–30 engineers	6–10 weeks before gate
Detailed Design	Full discipline teams across all functions	50–200+ engineers	8–12 weeks before gate
Procurement	Materials engineers, expeditors, inspection engineers	10–40 specialists	4–6 weeks before gate, often overlapping detailed design
Construction	Field engineers, construction managers, QA/QC	20–100+ engineers	2–4 weeks before gate, contingent on pipeline built earlier
Commissioning & Startup	Commissioning engineers, startup specialists	10–50 engineers	2–6 weeks before gate, engage during construction

Attach an owner and a review trigger to each phase-gate row

Every row in the roadmap should have a named owner responsible for tracking sourcing progress against that gate, and an explicit trigger, whether a calendar milestone or a schedule-change event, that prompts a review of whether the sourcing timeline still holds.

Use the roadmap to communicate urgency internally

One of the most practical uses of a phase-gate roadmap is communicating to program leadership, well before a gap is felt, that a specific discipline's sourcing needs to start now to meet an upcoming gate. A visible roadmap makes this a scheduled, expected conversation rather than a surprise escalation.

Share the roadmap with your workforce partner directly

A workforce partner who has visibility into the full phase-gate roadmap, not just the current open requisition, can begin building pipeline for upcoming gates proactively, which is what ultimately makes fast, high-quality submissions possible when each gate actually arrives.

Summary

Key takeaways

Anchor the staffing roadmap to phase gates rather than fixed calendar dates so it stays accurate even as the schedule shifts
Specify discipline mix at each phase gate, not just a headcount range, to give sourcing a concrete target
Assign a named owner and a review trigger to each phase-gate row in the roadmap
Share the full roadmap with a workforce partner so they can build pipeline proactively for upcoming gates, not just the current opening

Answers

Frequently asked questions

Question not covered here? Ask a recruiter directly - you will get a straight technical answer, not a callback from a salesperson.

Keep going

Need this applied to your own requisition?

Our recruiters will run the same analysis against your scope and send back a written market view for the disciplines you are planning.

Talk to our team Request talent

A Phase-Gate Staffing Roadmap Template for Capital Programs