● The StaffLaunch Suite · product manifest · 2026
Launch every person on the right trajectory.
Twelve connected apps that take someone from their first sign-in to running the floor, and give the company one source of truth for every person, client, shift, map, report and certificate. It was built inside a working staffing company, for the people who actually do the work.
01 Quick index
Every job in the building has an app. They all share one door and one memory.
StaffLaunch is the door: identity, roles, training and the app catalog. StaffQuery is the memory: a typed, linked database every other app reads and writes. The rest are focused tools for scheduling, communication, operations and records.
One door for the whole company.
Google, email with two-factor, or a link from any app. Riley signs in once and never sees another login screen.
Two tiles. Nothing to get lost in.
The New Hire role shows the docs library and the welcome guide. Everything else stays out of the way until Riley is ready for it.
Slides, quizzes, signatures.
Admins write guides in plain markdown or a guided builder. Each one can require a role to open, and grant or remove roles when it is finished.
Pass at 80% and the role is granted.
“Key Control & Vehicle Walkaround” is graded. A passing score adds the Valet role on the spot. A promotion checklist works the same way one rung up.
- Grant on pass or on complete
- Remove the previous tier in the same step
- Survey mode for anonymous pulse checks
New apps simply appear.
Schedulrama, Valetra and speedTPS show up on the dashboard with the right permissions already set inside each app. Nobody filed a ticket.
One playbook for the whole team…
The Event Night Playbook is a long-form guide with a table of contents and an “explain like I’m new” mode for first-week staff.
…with paragraphs only managers see.
Billing contacts and damage-claim rules sit in the same document, gated per paragraph. The server never sends them to a valet’s browser.
Roles → apps → the role inside each app.
Each role lists its apps, how they launch (one-tap SSO, direct link, or re-enter password for sensitive data) and the role it assigns inside that app. Changes follow people on their next launch.
- Email presets seed a new manager straight into the right role
- Every role and login syncs to StaffQuery
The record everyone else reads.
Staff, clients, events, equipment and reports, as typed and linked tables. Facets, grouping, saved views and per-field visibility come built in, without a spreadsheet’s fragility.
Every value knows which app wrote it.
Schedulrama set this shift’s start at 5:00 PM. LogicLot moved it to 4:30 when the lot plan changed. The colored underline on every cell names its source, and history shows each change.
Drag a field onto a table to link them.
Drop on a header to create a relation. Drop on a field to create a lookup, like “Client Address” pulled through the event’s client. Admins reshape the model without a developer.
CSV or Excel in, columns matched for you.
“Mobile” maps to Phone and “Job Title” maps to Position. Each import goes through the same validation and audit trail as a hand edit.
Two tables side by side.
Events grouped by status next to the staff roster, each with its own filters and facets.
Keys scoped per table, per action.
table:events:write lets an app write events and nothing else. Sensitive fields such as pay rates need an explicit flag. The same API powers an MCP server for AI agents.
Valet & events.
Staff, Clients, Events, Equipment, Reports. Gate codes and pay rates are admin-only fields.
Clinicians, facilities, credentials.
RNs, LPNs and techs with compact-license flags, specialties and bill rates. Every BLS, ACLS and TB test is a linked record with an expiry date.
Crew, job sites, dispatch, safety.
Trade, level and union local on every person. Toolbox talks link their attendees, and equipment knows which site it sits on.
Officers, posts, shifts, incidents.
Guard-card numbers and expirations, armed or unarmed clearances, post orders, and incident narratives with severity.
Crew, productions, calls, gear.
Departments and skills like A1 or up-rigger, day rates and meal penalties. Venue is a lookup through the production.
Know what needs attention before the day starts.
Coverage against target, campaigns waiting on replies, and alerts for gaps.
Ask everyone at once. Watch the replies come in.
Holiday season, Thanksgiving coverage, an on-call rain pool. Each campaign goes out by text and email, and coverage fills toward its target.
Staff answer from a link on their phone.
Riley taps the text, marks the dates they can work and whether overtime is fine, and the manager’s tracker updates live.
Drag shifts. Publish when ready.
Shift types carry point values, default positions, required fields, a lot map and a text template. Staff can pick up open shifts they qualify for.
Events created elsewhere become shifts here.
A client request logged in StaffQuery shows up for review. One click turns it into a staffed shift, and the result writes back.
Who hears about what, and how.
Per-event routing to roles, over text through VoxStaff, email, or in-app.
Every finished shift needs a report.
Shifts that need a TPS report get a prefilled speedTPS link. Completion flows back into the event record.
06 ShiftBrain
The good shifts go to whoever is due, not whoever is loudest.
Every shift type has a point value. A gala is worth 6 and a hospital day is worth 1. Every tier has a weekly quota. ShiftBrain reads the real assignment history from Schedulrama or an imported When I Work export and ranks who is behind.
- Fairness leaderboard on a rolling window
- Tiers: Bronze 15, Silver 20, Gold 30, Priority 25 points a week
- Imports from When I Work, Schedulrama, or any CSV
- No mainstream scheduling tool scores fairness this way
07 VoxStaff
One company number. Every text, every teammate.
Clients, house managers and crews text one shared line. Everyone sees who read what, leaves internal notes that are never sent, and drafts replies together. Contacts sync from StaffQuery, so a phone number changed there is right here too.
- Group threads for a crew on a given night
- Blasts and reminder templates, with send permissions by event
- The suite’s texting backend: Schedulrama sends through it
- Google Voice, Twilio, Telnyx or Quo as the carrier
Every site is a live map.
Zones, cone lanes, flow arrows, runner posts and overflow lots. When the lead edits, every phone on the crew updates within a second.
The house rules, drawn on the ground.
Motor court drop, lawn parking on mats, a catering lane that stays clear.
Loops, stops and live drivers.
Drive maps track drivers in real time, and a 30-minute share link lets a client watch their car arrive.
Crew parking, truck docks, fire lanes.
The same tools that plan a valet lot also plan a load-in.
Laydown yards and delivery routes.
Badge trailer, crane pick zone, crew parking, as one link every sub can open.
Checkpoints on a perimeter.
CP-1 to CP-4 and the vehicle patrol loop, inside the post orders.
The briefing embeds the live map.
Call times, client notes and key control in one markdown lead sheet, protected by a PIN per lead. The LogicLot map inside it stays current.
Check in, park, retrieve.
Car requests appear the moment a guest texts. VIPs are flagged, and every ticket carries photos, spot and keys.
- Customer portal with live status texts
- Stripe payments and tips per location
- Staff presence and clock-in per site
34 cars, two venues, one list.
Sort by check-in, search by plate or name, check out in one tap.
Close out the shift in two minutes.
A phone-first wizard: crew, hours, cars, tips. Forms differ per venue (even split, by hours, ticket revenue) and are all built in the form builder.
Tips divided fairly, down to the cent.
Proportional to minutes worked or split evenly. Flagged reports such as damage claims land in StaffQuery with the event already linked.
Tips per hour, cars per night, by venue.
Anomaly flags catch a night that doesn’t add up.
Design once, issue thousands.
A snap-to-guide editor for certificates, envelopes and cards, with bound fields for the recipient, quantity, expiry and a QR code. Versions are published and immutable.
“Three valet visits left of five.”
Each certificate has a private customer page with its ID and a call-to-redeem button. Staff redeem one unit at a time at the stand.
Used means used.
Once fully redeemed, the customer’s open page gets the ink stamp within seconds and offers a review link.
Training completion, issued automatically.
The same engine issues staff credentials: Key Control cleared, toolbox talk attended, guard card verified. The certificate can be verified by its QR code.
Issue from a URL or the API.
Scoped tokens, kits of front and back sides, customers synced with StaffQuery, and a full audit trail.
11 OrgFlowChart · EndeavorDeck
Fourteen months later, Riley runs a site. The tools grow with them.
Leadership needs to see who carries which work, and whether they should be. Projects need owners drawn from the real staff list.
Who Does What
An org chart where every seat carries its weekly hours of duties. Each duty is tagged as primary purpose, supporting, someone else’s job, or something that should be reallocated or stopped. Open seats and AI agent seats sit on the same chart.
- Drag a duty onto a person to reassign it; capacity rings update
- Claude connector and MCP server, with dry-run on every change
- Every edit logged as “who via which app,” and restorable
EndeavorDeck
A Kanban board whose projects and tasks are stored in StaffQuery. Assignees are real staff records. Who can be assigned is a role tag such as deck-admin or a per-project tag, so access follows people.
12 Connection map
One door, one memory, many hands.
The dotted violet ring is single sign-on: every app trusts a short-lived launch token from StaffLaunch. The amber lines are data moving between apps. Select an app to trace its connections.
13 Fields & niches
Born in valet and events. Shaped for any company that puts people on shifts.
The engine doesn’t know what a valet is. Tables, fields, roles, maps and documents are all configured, so the same suite runs a nurse registry, a guard company or a stage crew. Choose an industry to see how each app is used there.
| Industry | A person is a… | A place is a… | Work is a… | Proof is a… | A promotion is… |
|---|
14 What’s covered, what’s coming
The inside of a staffing company is done. The outside comes next.
Today the suite covers how people are hired in, trained, scheduled, coordinated and reported on. Next it covers how a client signs, how money moves, and how a person grows over years, so StaffLaunch can launch people at every level of the business.
PactPadContracts
Client service agreements, event orders and staff offer letters, from templates, signed on any device. A signed contract creates the client in StaffQuery and the event requests in Schedulrama.
Builds on: CertBuilder templates · StaffQuery clients · Schedulrama syncPayRelayPayments
Deposits and invoices for clients, then payouts to staff: tips from speedTPS splits, shift pay and per-diem, with a payroll export.
Builds on: Valetra Stripe · speedTPS splits · ShiftBrain hours15 Manifest
Every app, in detail.
What each app does, the data it owns, what it talks to, and what it replaces.
16 Security & architecture
Serious about who can see what.
Every launch is a signed token that lives 45 seconds and only works in the app it was minted for.
A promotion or demotion in StaffLaunch re-applies inside every app on the next launch, unless an app admin deliberately locked a local role.
TOTP on email sign-ins, optional re-entry of the password for sensitive apps, and Google sign-in.
Pay rates, gate codes and risk notes are admin-only, and the API needs an explicit flag to read them.
Every cell records which app wrote it and what it replaced. Every change is in the audit log.
MCP servers for StaffQuery, LogicLot and OrgFlowChart. Scoped keys, dry runs, and agents that can never exceed their person’s role.
Containerized apps on Google Cloud Run with managed Postgres. Data stays in your own project and can be exported at any time.
New tables, fields, roles, docs, forms, maps and templates are admin work, not engineering tickets.
● Next step
Put your people on a trajectory.
A tailored demo runs on your own vocabulary: your roles, your sites, your shift types, and your industry’s credentials, set up in StaffQuery in an afternoon.