Help Desk design board
Help Desk 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 Help Desk actually does
Provides user support, ticket triage, troubleshooting, escalation, knowledge-base updates, and customer communication.
Ticket resolutions, escalation notes, knowledge-base articles, call summaries, user guidance, and support metrics.
How to write the qualifications
Customer support skill, technical troubleshooting ability, ticketing-system experience, and escalation discipline.
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
Rates should reflect tier level, technical complexity, hours of coverage, SLA expectations, and worksite.
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
Tier I, II, and III should differ in escalation authority and complexity.
A clean labor catalog is easier to quote from because every role earns its place.
What this looks like in practice
In actionHelp Desk in a real task order
A Tier II Service Desk Specialist resolves application access issues and escalates infrastructure problems with clean notes.
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 Help Desk / Service Desk Specialist 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 Help Desk / Service Desk Specialist 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.