Agencies that run temp and perm through one undifferentiated pipeline eventually hit the same wall: temp compliance steps slow down perm deals, perm-style stages hide temp redeployment opportunities, and reporting turns into an apples-and-oranges argument in every leadership meeting.
Temp and perm aren’t two flavors of the same business. They’re different revenue engines — different cycle times, different compliance burdens, different margin behavior — and your workflow architecture should respect that while still rolling up to one view of the business. Here’s how to design it.
Two Revenue Engines, Not One
Perm is a project business: long cycle (weeks to months), fee-event revenue, margin concentrated in a single invoice, success driven by search quality and offer management.
Temp/contract is a recurring-revenue business: short cycle (days), margin earned weekly across the assignment life, success driven by speed, compliance, redeployment, and clean timesheet-to-invoice operations.
Treating a recurring-revenue engine with project-business processes (or vice versa) is how agencies end up simultaneously slow on temp and sloppy on perm.
Key Process Differences That Force Design Decisions
| Dimension | Temp/Contract | Perm |
|---|---|---|
| Cycle time | Hours–days | Weeks–months |
| Compliance load | High (onboarding docs, credentials, timesheets) | Low–moderate |
| Margin behavior | Weekly spread; erodes via pay/bill drift | One-time fee; erodes via fall-offs |
| Post-placement work | Heavy (timesheets, redeployment) | Light (guarantee-period care) |
| Critical SLA | Speed to submit | Feedback and offer velocity |
The compliance row alone justifies divergence: forcing perm placements through credentialing checkpoints adds friction with zero value, while letting temp skip them creates legal exposure.
Separate vs. Shared: The Decision Framework
You don’t need two systems — you need one platform with deliberately divergent paths:
- Share: intake and qualification, candidate database and skill taxonomy, client account records, communication templates.
- Separate: pipeline stages and SLA timers, compliance/onboarding steps, post-placement workflows (temp gets timesheet + redeployment automation; perm gets guarantee-period check-ins), commission logic.
Rule of thumb: share data objects, separate process flows. Shared data prevents silos; separate flows prevent friction.
Designing your dual-engine pipeline? Get the Temp + Perm Pipeline Architecture Map — shared vs. separate decisions, stage models, and accountability template included.
Unified Reporting Across Both Models
Leadership needs one picture, which requires translating both engines into common denominators:
- Gross profit, not revenue, as the universal comparison metric (temp revenue inflates topline comparisons).
- GP per recruiter per week works across both models.
- Model-specific panels: temp gets redeployment rate, assignment utilization, and timesheet exception rate; perm gets send-out-to-offer ratio and fall-off rate.
- One pipeline-value formula: expected GP × stage probability, defined separately per model, reported together.
This structure is the backbone of the staffing leadership KPI dashboard stack — build the workflow architecture first, and the dashboards fall out of it naturally.
Team Roles and Accountability Map
- Temp desk: speed-and-volume roles — dedicated compliance/onboarding owner, redeployment owner (often the most profitable seat in the building), timesheet exception owner.
- Perm desk: depth roles — search owner, client feedback owner, offer-management owner.
- Shared services: data steward, marketing, back office — with SLAs to each desk, so shared doesn’t mean slow.
Put names, not team labels, on each accountability. Ambiguity between desks is where placements and margin quietly die.
What to Do This Week
- List every stage in your current pipeline and label each: temp-only, perm-only, or shared.
- Identify one compliance step currently applied to perm that shouldn’t be (or missing from temp that must be).
- Define GP per recruiter per week for both desks from last quarter’s data.
- Assign a named redeployment owner if you don’t have one — it’s the fastest GP win in temp.
FAQ
Should temp and perm use different ATS platforms?
Almost never. Two platforms doubles cost and splits your candidate database. One platform with separate pipelines and shared records is the scalable pattern.
How do I compare temp and perm performance fairly?
Use gross profit as the common currency and GP per recruiter per week as the productivity metric. Revenue comparisons systematically flatter temp; placement-count comparisons flatter perm.
When should an agency add a second model (temp adding perm, or vice versa)?
When your client base is asking for it and your workflow architecture can absorb a second process flow without corrupting the first — which usually means after your data and stage discipline are solid, not before.
Build workflows that scale both engines. Download the Temp + Perm Pipeline Architecture Map and skip a year of trial-and-error redesign.
