Ready workers3 / 52 blocked by docs
Payroll exposure$3,840Based on approved hours
Advance available$4,62485% scenario
Packet readiness78%2 evidence items missing
Pay approval queue
Click a worker to update the preview and packet state.
| Worker | Role | Docs | Shift | Pay stage |
|---|
Worker pay path
Selected worker
MJ
Maya Johnson
CNA · Dallas · 18 months tenure
6/7 required documents complete
AI review
Operational brain, human approval still required.
Worker roster
Role coverage, documents, and payment blockers.
| Name | Role | Availability | Credential status | Payment blocker |
|---|
KNM worker appMaya Johnson · CNA
Next shiftNorth Dallas Rehab · 7p-7a
Pay statusTimesheet submitted · awaiting approval
Estimated pay$288 before taxes/deductions
Missing itemFlu attestation before hospital shifts
Shift marketplace
Kelly can decide who gets offered work first.
| Shift | Facility/client | Pay/bill | Best match | Status |
|---|
Funding package builder
Approved timesheets become clean funding evidence.
Cash model
Model whether funding covers worker pay.
1
$3,840Worker payroll need
2
$5,440Facility invoice
3
$4,624Funding advance
4
Likely fundableAdvance covers payroll before reserve/ops.
AI operating brain
Draft recommendations for Kelly to approve.
Trust, security, and compliance plan
How KNM becomes business-grade instead of just a prototype.
Data postureNo PHI by defaultPatient data stays out unless reviewed.
Access modelRole basedKelly/admin, worker, optional approver.
Audit layerEvery action loggedApprovals, packets, exports, overrides.
| Area | Control | Why Kelly should care | Status |
|---|---|---|---|
| Identity | MFA-ready auth, role-based permissions, least privilege | Only the right person sees worker/pay/funding data. | Design |
| Worker data | Encrypted document storage, signed URLs, retention rules | Licenses, I-9/W-4, IDs, and pay data are sensitive. | Design |
| Timesheets | Immutable approval trail with timestamps and approver identity | Payroll and funding depend on trusted proof of work. | Core |
| Funding | Versioned packet, missing-evidence checks, submission log | Cleaner packets should reduce rejections and delays. | Core |
| AI | Recommendation-only until approved; no protected traits | AI helps Kelly move faster without becoming unchecked HR logic. | Guarded |
| HIPAA boundary | No patient data fields in v1; flag any patient-data request | Healthcare staffing can stay lower-risk if patient data is excluded. | Default |
| Background checks | Consent capture, vendor result tracking, adverse-action workflow placeholder | Background screens need process controls before automation. | Needs provider |
| Payroll | Export only; payroll provider remains system of record for taxes/filings | KNM speeds the workflow without pretending to be payroll compliance. | Boundary |
| Operations | Backups, incident plan, access reviews, admin evidence exports | Shows maturity to Kelly, partners, funders, and future auditors. | Roadmap |
Compliance guardrails
What we can say in the meeting.
Built for auditabilityEvery approval, document upload, export, AI suggestion, and override gets a timestamp and actor.
Healthcare-safe boundaryV1 avoids patient data, reducing HIPAA exposure while still managing worker credentials and shifts.
Payroll-safe boundaryKNM prepares approved hours and funding evidence; payroll provider handles taxes, filings, paystubs, deductions, and garnishments.
External review requiredBefore live payroll or factor submission, Kelly’s accountant/payroll provider/factor should confirm the workflow.
Long-term assurance path
How this grows into business-grade software.
1
Secure MVPPrivate PWA, auth, RLS, encrypted docs, audit logs.
Now2
Compliance reviewPayroll, FCRA/background, I-9, funding, state wage rules.
Pilot3
Operational controlsBackups, access reviews, incident runbook, retention policy.
Next4
SOC 2-style readinessNIST CSF mapped controls, vendor risk, evidence exports.
Scale