Compliance Service
Document chasing, primary source verification and audit prep, run for you.
Compliance Service →Services
Why would I need services?
Every facility that calls us already has systems. What they do not have is someone with the hours to work them. Services exist for that gap — the distance between a program that tracks the right things and a program where the work actually gets finished.
Where Workforce Plus sits
Same stacks · more help
Tier one
Workforce
Your team runs the program on the platform.
Technology
Services — you
Tier two · you are here
Workforce Plus
Same platform. We execute the services you pick.
Technology
Compliance Service
Agency Service
Either one, or both
Tier three
MSP
Every service managed, standardized across sites.
Technology
All services
Program ownership
Constant
The six stacks and your data do not change between tiers — only who does the work.
The technology is identical across all three tiers. What changes is who does the work behind it.
The problem is rarely the software
A platform can enforce a rule, surface an expiration, route a requisition, and hold an audit trail. It cannot make the phone call, read the submission, run the verification, or sit in the interview. That work is labor, and in most facilities it lands on people whose actual job is somewhere else.
- It lands on nurse leaders: Unit managers end up reviewing agency profiles and coordinating interviews after their shift, because the requisition cannot wait and nobody else owns it.
- It lands on one coordinator: Credentialing knowledge concentrates in a single person. The process runs well until they take PTO, and the exposure is invisible until something lapses.
- It lands nowhere at all: Supplier scorecards get built and never reviewed, so tiering reflects who was available two years ago rather than who is performing now.
Two services, added independently
Services are not a bundle. Each one takes a specific function off your team, delivered by LaborStack specialists working inside your instance, against the rules your facility already defined.
Compliance Service
Managed credentialing — document collection and chase, primary source verification, requirement upkeep, and audit packet assembly. Add it when what is expiring is known and nobody has the hours to close it.
Agency Service
Managed requisition and supplier work — job orders, submission review, pre-screens, interview coordination, and ongoing agency pool management. Add it when clinical leaders are running the staffing desk.
Both together
The most common configuration, because selection and clearance are one continuous process. Running them under one team removes the handoff between a candidate being chosen and being cleared to work.
How to tell which tier you are
The three tiers are not sizes. They are answers to a single question: who does the work?
- Workforce: Your team runs the program and has the capacity to do it. The platform is the constraint you were trying to solve, and now it is solved.
- Workforce Plus: The rules are right and the follow-through is slipping in one or two specific functions. You want those executed without giving up ownership of the program.
- MSP: You want the program run for you — every service managed and standardized across sites, with a partner accountable for the outcome rather than a function.
Where Workforce Plus sits
Same stacks · more help
Tier one
Workforce
Your team runs the program on the platform.
Technology
Services — you
Tier two · you are here
Workforce Plus
Same platform. We execute the services you pick.
Technology
Compliance Service
Agency Service
Either one, or both
Tier three
MSP
Every service managed, standardized across sites.
Technology
All services
Program ownership
Constant
The six stacks and your data do not change between tiers — only who does the work.
What does not change when you add a service
This is the part facilities ask about first, so it is worth stating plainly. Your requirement hierarchy, distribution rules, supplier tiers, rate logic, and approval chain stay facility-defined. Vendor neutrality is a property of the platform, not of the tier you buy. Every action our team takes happens in your instance with the same audit trail your own staff would leave — oversight never depends on asking us for a status report.
Your standards
We adopt your workflow at implementation rather than asking you to adopt a template.
Your decisions
Hiring calls, exception approvals, and supplier strategy remain yours. We execute; we do not set policy.
Your data
Same record, same stacks, same reporting. Nothing moves to a separate system, so nothing has to migrate back.
The two managed services
Both run inside your instance, on your rules — the difference is which work your team hands over.
Agency Service
Job orders, submissions, pre-screens and interview coordination, run for you.
Agency Service →Services: Frequently Asked Questions
The questions that come up when a facility is deciding between doing it themselves and adding help.
Is a service just outsourcing under a different name?
The distinction is where accountability sits. Outsourcing typically moves a function to a vendor with its own process, its own system, and its own definition of done. A service layer puts trained specialists inside your platform, working your rules, with every action visible to you. Standards and approvals stay with your facility.
Can we start with one service and add the other later?
Yes, and it is the common path. Because both services run against the same configured suppliers, facilities, and rules, adding the second one is a staffing change rather than a new implementation. Most teams start with whichever function is currently costing them shifts.
How do we know it is a capacity problem and not a process problem?
A useful test: if you can name what is expiring, who is underperforming, and which requisitions are open, but none of it is being worked to completion, that is capacity. If you cannot answer those questions at all, fix the platform configuration first — a service layer on top of unclear rules just adds people to the confusion.
What is the smallest reasonable starting point?
One service, on the function with a deadline attached. Facilities that try to hand over everything at once spend the first quarter defining boundaries instead of getting work done. Start where shifts are being lost, then widen.
When is a full MSP genuinely the better answer?
When you want a single partner accountable for program outcomes across every service and every site, rather than for specific functions. Multi-facility systems standardizing a fragmented program usually land there. If you still want to own the program and only need certain work executed, Plus is the honest answer and costs less.
Not sure which tier you are?
Answer a few questions about where the program is slipping and we will name the stacks that address it, along with whether the platform alone, a service layer, or a full managed program is the right fit.