Stacks
What are stacks?
Most platforms ask you to buy the whole thing and grow into it. LaborStack is built as six stacks, each one answering a problem healthcare teams name out loud. Start with the stack that hurts today; the rest connect to the same record when you are ready.
Each stack is a working part of one workforce platform — shared record, shared suppliers, shared rules across every facility you run.
The six stacks that build a complete workforce solution
Each stack is a working part of the program, not a feature list. This is what each one owns.
- Workforce Stack: One requisition reaches every approved supplier under your rules, and every submission is scored on the same healthcare-specific criteria so shortlists are comparable.
- Compliance Stack: Hierarchical requirement rules by facility, profession, and unit, with expiration alerts at your chosen cadence and audit documentation generated on demand.
- Scheduling Stack: PRN, internal float pool, on-call, and agency coverage in one view, so internal resources get first look before premium spend.
- Billing Stack: Approved time meets rate cards and differential logic automatically, so invoices reconcile instead of getting rebuilt.
- Forecast Stack: Spend, fill rate, time-to-fill, and supplier scorecards across every facility, updated live rather than at month end.
- Connect Stack: Secure APIs into HRIS, ATS, scheduling, and payroll so hours and credentials stop being re-keyed.
How the stacks connect
A requisition, a credential, a shift, and an invoice are the same thread of work. Because the stacks share one record, each step hands cleanly to the next instead of being re-entered — which is where most programs lose their time and their audit trail.
Running one stack, or all six
Adoption is additive. Nothing gets migrated when you add a stack — the record is already there.
Start where it hurts
Most teams begin with Compliance or Billing, because those are the problems with a deadline attached.
Add without re-implementing
A new stack switches on against the same suppliers, facilities, and rules you already configured.
Choose your delivery model
Self-managed on Workforce, the platform plus a managed layer with Workforce Plus, or a full MSP program — the stacks are the same underneath.
Stacks: Frequently Asked Questions
Common questions about how the stacks are packaged and adopted.
Do I have to buy all six stacks?
No. Each stack runs on its own. Teams commonly start with one or two and add the rest as the program grows, because the suppliers, facilities, and rules are already configured after the first implementation.
Is a stack the same thing as a module?
The difference is the shared record. Modules typically pass data between themselves; the stacks read and write the same requisition, credential, shift, and invoice, so there is nothing to sync or reconcile between them.
How does this relate to Workforce, Workforce Plus, and MSP?
The stacks are what the software does. The three solutions are how it is delivered — self-managed, platform plus a managed layer, or a full managed program. Any stack can run under any of the three.
Which stack should we start with?
The one attached to a deadline. Answer a few questions in Build Your Stack & Solution and it will name the stacks that match the problems you pick.
Not sure which stacks you need?
Answer a few questions about where the program hurts and we will name the stacks that answer them, along with the delivery model that fits.