Healthcare VMS Requisition-to-Submission Workflow for Staffing Agencies: Tiering, Rate Cards, and SLAs
In a healthcare VMS workflow, a facility posts a requisition, the VMS or MSP releases it to approved agencies in tiers, and each agency has a set window to submit qualified, credentialed candidates at the rate card price. Agencies that move fastest inside that window win the order. This guide maps the agency side of that workflow, stage by stage.
Most content about a healthcare VMS is written for hospitals buying one. If you are a staffing agency working inside a client's VMS, the questions are different: how do you see requisitions first, what does tiering do to your fill chances, and why do good candidates still miss the submission window?
What is the workflow from healthcare VMS requisition to candidate submission?
A requisition passes through the same stages in most programs, though names differ. The table shows who owns each stage, what response time agencies are usually held to, and where the process tends to fail. SLA times are examples. Your contract and the client's program set the real numbers.
Stage | Owner | Typical SLA (example) | Common failure |
1. Requisition created | Hiring manager at the facility | Set by facility | Unclear shift, specialty or start date |
2. Approval and release | MSP or VMS administrator | Same business day | Order sits in an approval queue |
3. Tier release to agencies | VMS rules engine | By tier window | Agency in a later tier never sees the order |
4. Agency acknowledgment | Agency recruiter lead | Within hours | Notification lands in a shared inbox |
5. Candidate matching and credential check | Agency recruiter | Within the tier window | Candidate is a fit but credentials are stale |
6. Submission | Agency recruiter | Before the window closes | Rate or documents rejected on first pass |
7. Client review and decision | Hiring manager | Set by facility | Feedback never reaches the recruiter |
Key takeaway for operations leaders: most lost orders are lost at stages 4 to 6, inside your own agency, not at the client.
What do tiering and rate cards mean for staffing agencies?
Tiering controls the order in which agencies see a requisition. A program might release an order to tier 1 agencies for a short window, then to tier 2, then to everyone. Movement between tiers usually depends on fill rate, submission speed, quality and compliance performance. Your tier decides how much time you have.
A rate card sets the maximum bill rate by specialty, shift or role. It is the pricing ceiling for each requisition. A submission above the card is usually rejected or flagged, and a submission far below it may leave margin on the table or trigger a review.
Both affect operations more than sales. If you know a program's rate card, your team can screen out candidates whose pay expectations leave no margin before anyone writes a submission. If you know where you sit in the tier order, you can staff your fastest recruiters on that program during release windows.
For background on how MSP fees interact with these rates, see our post on MSP fees in healthcare staffing.
How does one requisition move from release to submission? A worked example
This is a general scenario, not a specific client.
An MSP releases an ICU night-shift requisition to tier 1 agencies at 9:00 a.m. with a four-hour exclusivity window. The agency's notification goes to a shared inbox. A recruiter sees it at 10:30, which has already used a third of the window.
The recruiter searches the database and finds two ICU nurses with the right experience. One has a state license that expired last week. The other has a current license but no recent skills checklist on file. The recruiter requests the missing items by email, waits, then submits at the end of the window with one candidate. A tier 2 agency submitted a ready candidate an hour earlier and wins the order.
Nothing in that story was a sales failure. The agency had the right candidates. It lost time on notification, credential visibility and document collection.
Common operational mistake: treating the VMS as a job board. Programs track response time, and slow acknowledgment can lower your tier or your share of future releases.
How can an agency respond faster inside a healthcare VMS?
Speed comes from preparing before the requisition arrives:
Route VMS notifications to a person, not an inbox. Assign an owner for each program and a backup.
Keep credentials current for your bench. Expiry alerts well ahead of the date, such as 60 and 30 days, reduce stale-file surprises.
Store program rules per client. Rate card, required documents, shift definitions and submission format should sit in one place.
Pre-screen against the rate card. Know your margin before the submission, not after the rejection.
Track response time by program. If you do not measure it, you will not see tier slippage until the volume drops.
These steps also hold if you work through several VMS platforms. The names of the portals differ, but the stages do not. Our posts on automating per diem MSP staffing workflows and VMS automation in healthcare staffing go deeper on tooling.
Where does Vars Health fit in an agency's VMS workflow?
Vars Health is healthcare staffing software for agencies, not a staffing firm and not a VMS. It sits on the agency side, behind the portal you receive requisitions from.
In the example above, the delay came from three places: the notification, the credential check and the document request. With the ATS, credentialing and onboarding on one record, the recruiter can see which bench candidates have current licenses and complete files while matching, instead of checking each one separately. Gaps show before submission, not after.
The effect is on time-to-submit and recruiter workload: fewer manual checks, fewer rejected first submissions and a clearer view of which candidates are ready to be put forward.
Pro tip for staffing agencies: run a quick audit of your last ten VMS requisitions. For each, note the time from release to acknowledgment and from acknowledgment to submission. The longest gap is your first fix.
What should you fix first and what can wait?
Fix first: notification ownership and credential freshness. They cost little and affect every program.
Fix next: program rules in one place, and rate-card screening at the start of matching.
Wait on: advanced reporting and tier forecasting until you have a few months of response-time data.
A tool will not change a tier decision made by the client, and it will not repair a bench full of expired files. It can make gaps visible earlier and cut the manual work around them. For the difference between the two system types, see ATS vs VMS.
FAQs
What is a healthcare VMS from a staffing agency's point of view?
It is the portal where a client or MSP releases requisitions, collects submissions, and tracks agency performance. The agency uses it to receive orders and submit candidates, but does not usually own it.
How does VMS tiering affect which agencies get orders?
Tiering sets the order and timing in which agencies see a requisition. Higher tiers get earlier access, so faster, more compliant agencies see more orders first.
What is a rate card in healthcare staffing?
A rate card lists the maximum bill rates for roles and specialties in a program. Submissions above it are typically rejected or flagged.
What is a typical SLA for responding to a VMS requisition?
It varies by program, from a few hours for urgent orders to a day or more for standard ones. Check your contract and the client's program guide.
Can a small agency compete inside a healthcare VMS?
Yes, if it responds quickly and keeps credentials current. Smaller agencies often win on speed for niche specialties.
Is a VMS the same as an ATS?
No. A VMS is the client-side system that manages vendors and requisitions. An ATS is the agency's system for managing candidates.
Conclusion
Working a healthcare VMS well comes down to response time, credential readiness and knowing the program's rate card and tier rules. Most of the work happens inside your agency before a requisition arrives.
A realistic next step: pull your last ten VMS requisitions and measure the time from release to acknowledgment and to submission. The longest gap shows where to start.
