Logistics Analyst design board
Logistics Analyst 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 Logistics Analyst actually does
Supports supply chain, transportation, inventory, deployment, warehousing, asset movement, or logistics planning.
Movement plans, inventory reports, route analyses, warehouse metrics, readiness summaries, and process recommendations.
How to write the qualifications
Logistics operations experience, planning skill, systems familiarity, data discipline, and understanding of movement constraints.
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 operational complexity, systems knowledge, geographic scope, and responsibility for readiness or movement outcomes.
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
Tie duties to logistics systems and deliverables, not generic administrative support.
A clean labor catalog is easier to quote from because every role earns its place.
What this looks like in practice
In actionLogistics Analyst in a real task order
A Logistics Analyst tracks equipment movement, analyzes bottlenecks, and updates a distribution plan for a field deployment.
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 Logistics Analyst 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 Logistics Analyst 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.