01
Expiration risk surfaces too late
Renewals get buried in calendars, inbox reminders, and cells that no one owns until a shift is already at risk.
Workforce compliance for healthcare staffing
Know who is ready before you offer the shift.
Satchel gives staffing agencies one place to see credentials, facility rules, verification work, expirations, and the evidence behind each eligibility decision.
Start with one facility, one role, and a roster export. No PHI is needed to evaluate the workflow.
Illustrative preview · Sample workspace
Shift eligibility
Memorial Hospital · RN
Search workspace
2
Needed
8
Eligible
1
Blocked
One worker is blocked by a facility requirement.
Kevin White
RN · Active
RN license
BLS
ICU experience
NIH Stroke
Sarah Martinez
RN · Active
RN license
BLS
ICU experience
NIH Stroke
Missing NIH Stroke Certification
Best fit for healthcare staffing agencies that have outgrown spreadsheet-led compliance.
- 75-500+ active clinicians
- Multiple facilities or requirement sets
- Compliance and staffing handoffs
Where spreadsheets fall short
A spreadsheet can track a date. It cannot defend a staffing decision.
Compliance teams need more than a place to store documents. They need to know what is current, which rules apply, what was verified, and why a worker can or cannot be placed.
02
Every facility asks for something different
A worker can be ready for one placement and blocked for another. Flat checklists do not explain that difference.
03
The reason behind a status disappears
Teams see “not ready” but cannot quickly find the missing requirement, verification result, or rule that caused it.
04
Audit prep becomes reconstruction
When evidence and decisions live in separate systems, the audit trail has to be rebuilt after the work happened.
Where Satchel fits
Not another place to store files.
Satchel sits between the credentialing work and the staffing call your team has to stand behind.
- Your ATS manages candidates
- Satchel explains workforce readiness
- Your drive stores documents
- Satchel keeps the rule and evidence together
- Your spreadsheet tracks dates
- Satchel applies the requirements for the placement
- Your VMS parser pulls the fields
- Satchel applies them and packages the submittal
How it works
From roster import to a clear staffing decision.
Satchel keeps the steps together that usually live in spreadsheets, inboxes, shared drives, and someone's memory.
- 01
Import the roster
Map a CSV or Excel export, validate required fields, and review possible duplicates before records are added.
- 02
Set the requirements
Create versioned requirement templates by facility, role, and worker type, then activate the right rules.
- 03
Work the exceptions
See expired, expiring, missing, and blocked items early enough for the team to act.
- 04
Document verification
Record the external primary-source check, reviewer, result, notes, and any explicit override.
- 05
Clear the placement
Apply the facility’s requirements to return Cleared, Conditional, or Blocked with the exact evidence, gaps, and next actions in hours, not days.
- 06
Submit to the facility
SatchelHub monitors incoming VMS requests and prepares a clean candidate profile so that your agency can submit first.
Keep your ATS. Start with the roster export you already have and prove the workflow before scoping deeper integrations.
Guided pilot setupInside Satchel
The record your team uses to decide who can work.
Views stay close to the work: records, requirements, verification, eligibility, and the evidence you may need later.
Credential readiness
Catch risk before a shift depends on it.
Compliance and staffing see the same live view of credential status, renewals, and records that need attention.
- Filter by status, facility, role, or renewal risk
- See expired and expiring records without reconciling sheets
- Export a real filtered workbook when the team needs it
Swipe to inspect the full workspace view.
Facility-aware eligibility
See who is eligible, and why someone is not.
Run the active facility requirements against the shift. Staffing can see who passes and which requirement blocks everyone else.
- Versioned requirement templates by facility and role
- Pass/fail results for each enforced requirement
- Plain-language block reasons before assignment
Swipe to inspect the full workspace view.
Verification and evidence
Keep today's work useful when questions come later.
Record manual verification as it happens, keep key staffing decisions on file, and pull a review-ready packet from what's already in Satchel.
- Manual primary-source verification history
- Timestamped assignment proof snapshots and activity
- Compliance packets scoped by facility, date, or worker
Swipe to inspect the full workspace view.
Built for how agencies work
Same picture of readiness. Different permissions.
Each team sees what they need to act. Compliance still owns the rules.
Compliance teams
Work the exception queue, record verification, manage rules, and keep the evidence connected to the record.
Own the compliance decision
Staffing operations
See who is eligible for a facility and shift without asking compliance to recheck the same file every time.
Staff from a shared status
Recruiting teams
Understand the credential gaps holding a worker back and route missing information to the right owner sooner.
Make follow-up specific
Agency leaders
See credential risk, open coverage, and progress without piecing the workflow together from several systems.
See readiness, not a pile of tabs
Before and after
Less chasing. Clearer answers when it matters.
Not a vague promise of automation. Just a cleaner way to run the compliance work your agency already owns.
Disconnected workflow
- Renewal dates split across spreadsheets and calendars
- Facility requirements interpreted from memory
- Verification evidence stored in inboxes or notes
- “Not ready” statuses without a usable explanation
- Audit requests answered by reconstructing past work
With Satchel
- One credential directory with visible renewal risk
- Active rules connected to each facility and role
- Verification source, result, reviewer, and history together
- Eligibility results with requirement-level block reasons
- Assignment proof, activity history, and scoped packets
Security overview
What we put in place for this kind of work.
We document the controls that exist today, then work through security, storage, retention, and BAA needs with you before rollout.
Review security practicesTenant-scoped workspaces
Customer records and operational data are scoped to the authenticated workspace.
Role-based permissions
Admin, compliance, staffing, and recruiting roles map to explicit product capabilities.
Timestamped history
Key uploads, edits, verification events, assignments, and approvals create traceable records.
Encrypted transport
Application traffic is transmitted over HTTPS. Data handling and BAA requirements are reviewed before a regulated pilot.
Integrations: Start by importing a real roster. Slack, Microsoft Teams, signed webhooks, calendar feeds, and NPI cross-checks are available. Deeper ATS work is scoped with you, not assumed.
Discuss your stackCommon questions
Straight answers before a pilot.
What's live today, what still needs a person in the loop, and what we scope with you for your agency.
What does a Satchel pilot start with?
The fastest first scope is one facility, one role, a usable roster export, and the people who own compliance and staffing decisions. Broader timing depends on data quality, users, integrations, and document-storage requirements, so the scope is agreed before the pilot begins.
Does Satchel replace our ATS?
No. Satchel runs alongside your recruiting and placement system for the compliance work. Start with a roster export, then scope any deeper ATS handoff only after the core workflow is proven.
Does Satchel automate primary-source license verification?
Not end to end today. A compliance user checks the appropriate external source, then records the result, source, reviewer, notes, and any explicit override in Satchel. That verification history stays connected to the credential record.
How does Satchel handle expirations?
Satchel surfaces expired and expiring credentials in the directory and renewals calendar. Configured users can receive in-app and email alerts at 30, 14, 7, and 1 day before expiration, on the expiration day, and in an optional weekly summary.
Can Satchel show why a worker is blocked?
Yes. Shift eligibility applies the active facility requirement template, any binding overrides, and shift qualifications. The result includes pass or fail status, requirement-level evidence, and clear block reasons before assignment.
How do you handle security and PHI?
Satchel uses tenant-scoped access, role permissions, audit logging, signed sessions, authentication safeguards, and encrypted transport. Before a pilot involving sensitive documents or PHI, the data flow, storage and retention approach, security requirements, and any required BAA are documented.
How much does the pilot cost?
The current 30-day founding customer pilot is $1,500 for one facility, one role, and up to 250 active clinician records. The fee is credited toward the first annual subscription if you continue, and ongoing pricing is put in writing before the pilot begins.
Free roster risk review
Bring one real workflow. Leave with the gap list.
A 30-minute diagnostic for healthcare staffing operators, not a generic software tour.
- Review expired, expiring, incomplete, and likely blocked records
- Test one facility and role requirement set
- Leave with a one-page gap list and an honest next-step recommendation