A placement in, a cleared clinician out.
One message — from your ATS, email, or a text — starts the operation. The agents take it from there.
What it is
A placement is the unit of work in credentialing — one candidate, one facility, one start date. In most shops it becomes a spreadsheet row and three weeks of chasing. Here it becomes an operation: the agents read the facility's rules, generate the complete requirement list, match what you already hold, and work every remaining item simultaneously until the file is cleared.
- Start anywhereBullhorn, JobDiva, email, or SMS — placements arrive however your team works.
- Requirements builtFacility, role, and seasonal rules generate the full requirement list automatically.
- Worked in parallelEvery requirement runs at once — the slowest item sets the pace, nothing else.
How it works
01
Arrive
The placement lands from your ATS, an email, or a one-line text: "Lauren Chen, Cath Lab RN, Riverside, July 14."
02
Plan
Facility packet, role rules, and seasonal conditions generate the full requirement list — often 30 to 50 items — in seconds.
03
Match
Documents you already hold in the ATS and library are matched first, so nobody gets asked twice.
04
Work in parallel
Verification, screening, outreach, and signatures all run at once — with live status and start-date risk flagged early.
What's inside
ATS-native intake
Confirmed placements in Bullhorn or JobDiva start operations automatically — no re-keying.
Text-to-start
No integration needed on day one: text or email the placement and the agents take it.
Conditional rules
ICU vs Med-Surg, flu season, state quirks — the requirement list reflects the real conditions.
Parallel execution
The critical path is the single slowest item, not the sum of a specialist's queue.
Live pipeline
Every operation shows its stage, blockers, and age — no status meetings required.
Start-date protection
Files trending late are flagged days out, while there's still time to act.
Questions
How does a placement get started?
Three ways: automatically from a confirmed placement in your ATS (Bullhorn, JobDiva), by forwarding an email, or by sending a one-line text. The agents create the operation and build the requirement list from there.
How is the requirement list generated?
From layered rules: the facility's packet and matrices, role and specialty conditions, seasonal requirements like flu vaccination, and your company's own policies. A typical file generates 30–50 requirements, each traceable to its source rule.
What makes it faster than a specialist working the same file?
Parallelism and persistence. Every requirement is worked simultaneously, follow-ups happen around the clock, and nothing waits in a queue — so the timeline collapses to the single slowest item, usually days instead of weeks.
See it work a real file.
Thirty minutes, one placement, worked live — start to submit-ready.