For schools and programs
Your rules, applied before the request reaches you
Reviewing incomplete placement requests is the expensive part. Encode your requirements once and review packets that already meet them.
- No cost to the school
- Approval is a required stage
- Rules are versioned
Rules applied before review
1.Program requirements saved
Published as a versioned rule set with an effective date.
2.Student request evaluated
Matched against the version in force when the student submitted it.
3.Requests that miss a rule are held
Rules are applied before a student sees a candidate, so an ineligible request never becomes a packet.
4.Qualified packet sent for review
Credentials, site, dates, and signed paperwork, in one place.
What a rule set covers
- Accepted credentials
- Specialties and site types
- Patient populations and settings
- Agreements and student documents
What your program controls
Two things decide whether a placement service is worth a program office's time. These are ours.
Versioned placement rules
Programs change requirements between cohorts, and a change should not invalidate placements already in flight. Your rules are stored as versions with an effective date: a student's rotation request is bound to the version current when they submitted it, and that binding is recorded on the request itself.
- Accepted credential types
- Permitted specialties and site types
- Required patient populations and settings
- The agreements a site must hold
- The documents a student must produce
Matching applies them before a student sees a candidate.
You keep approval authority
A placement moves through matching, mutual acceptance, and paperwork, and then it stops at your review. Three outcomes, and a reason code recorded either way.
- Approve it, and the placement proceeds to site onboarding
- Request revisions, and it comes back to be corrected
- Deny it, and it stops there
A denial records a reason code and opens a case; it never silently closes, and the student is refunded under our published exception policy rather than being left to argue about it.
Where our authority stops
A recording layer, not a reviewing one
School approval is a required stage that a placement cannot proceed past. What happens at that stage is your decision; the platform records it and acts on it.
What the platform does not do
- Approve a placement. Your reviewers approve, request revisions, or deny.
- Replace institutional or academic review.
- Charge your school. Schools are not charged for reviewing or approving placements.
What your reviewers receive
- The preceptor's verified credentials
- The site and the agreements it holds
- The rotation's dates and hours
- The paperwork already signed
Reviewers see what they need to make a decision and nothing about payment arrangements.
School questions
Does this bypass our placement process?
The opposite. School approval is a required stage that a placement cannot proceed past. Your reviewers approve, request revisions, or deny, with a reason code recorded either way. If your program does not permit outside placement services, no placement for your students can complete without you declining it.
How do our requirements get applied?
You publish placement rules — accepted credentials, specialties, site types, patient populations, required agreements, and required documents — as a versioned rule set. A student's request is matched against the version in force when they submitted it, so a mid-cycle rule change does not retroactively invalidate placements already under way.
What do reviewers actually see?
A complete packet: the preceptor's verified credentials, the site and its agreements, the rotation's dates and hours, and the paperwork already signed. Reviewers see what they need to make a decision and nothing about payment arrangements.
Is there a cost to the school?
No. Schools are not charged for reviewing or approving placements.
Tell us how your program places students
We would rather fit your existing process than ask you to change it.