Project Manager design board
Project Manager labor category proof stack
A credible labor category is more than a title. It should explain what the person does, why the qualifications fit, and how the rate makes sense.
What a Project Manager actually does
Owns schedule, scope, risk, staffing, meetings, deliverables, and day-to-day execution.
Project plans, risk logs, status reports, meeting cadence, staffing coordination, deliverable calendars, and customer updates.
How to write the qualifications
Experience leading delivery teams, coordinating stakeholders, managing timelines, and controlling project risk.
The minimums should be specific enough to justify the role, but not so inflated that the category becomes hard to staff or hard for buyers to use.
How to think about pricing
Rate support should reflect team size, complexity, customer exposure, independence, worksite, and years of experience.
CALC+ can help with market research, but the final rate story should still connect to the company's commercial practice and the way the role is delivered.
Watch-out
Do not confuse this with Program Manager unless the role owns a broader portfolio or multiple related projects.
A clean labor catalog is easier to quote from because every role earns its place.
What this looks like in practice
In actionProject Manager in a real task order
A Project Manager coordinates a cloud migration task, manages sprint checkpoints, tracks risks, and keeps the agency lead informed.
A strong labor category page should make it easy to see why the role exists, what it produces, and how it would be staffed on a real order.
Add LCAT noteThe modification should show the before-and-after
If Project Manager is being added through eMod, the package should explain the new title, duties, qualifications, SIN support, pricing support, and whether the Services Plus File or service description needs to change.
- Title
- Duties
- Qualifications
- Rate support
- SIN mapping
- Service file impact
Frequently asked questions
Can Project Manager appear under more than one SIN?
Sometimes. The role can support multiple SINs when the duties and scope genuinely fit each lane. The description should not become so broad that it stops meaning anything.
Should this role have levels?
Only when the levels change duties, independence, customer exposure, experience, certifications, or technical depth in a way a buyer and reviewer can understand.
What should I check before adding it in eMod?
Check SIN fit, service description impact, pricing support, qualifications, commercial support, and whether the role appears in the Services Plus File or related documents.