Use cases
Four workflows, one product
These are real routes, written as Templates. The first is a straight chain; the last is a board meeting that mostly runs itself. Nothing changes underneath them but the configuration.
Finance & ops
Purchase approval
Someone needs a thing. Their manager says yes, that manager's manager says yes, IT confirms it's supportable. Over $10,000 the CFO joins on the way past. Nobody had to remember the chain, and nobody had to know who anyone's manager is.
If IT rejects it, the request doesn't die — it goes back to the requester for a revised quote and runs the chain again as a clean second round.
Requester submits
Quote and justification go in the bundle. amount is a field on it.
Manager approves
Assigned by position, not name. Reminded after 3 days; escalated after 5.
Their manager approves
Two levels up the reporting line, resolved when the step opens.
CFO approves — only sometimes
Included when amount > 10,000. Otherwise the route skips straight past.
IT approves
Whoever holds it-approver today. A rejection here routes back to step 1.
Archive
Nobody's task. Orgworks files the bundle and closes the request.
Compliance
Insurance renewal
The failure mode here isn't a slow approval. It's that nobody starts it. The certificate expires on a date nobody has in their calendar, and you find out from a broker's email or an auditor.
So the request starts itself: 30 days before any document's expiry date, opened on behalf of whoever uploaded it, with the expiring document already attached. Exactly once — a re-scan or a second server won't open a duplicate. Upload the renewal and the old version stops asking.
A nightly scan opens it
30 days before expires_at, on the current version only.
Broker's renewal goes in
The new certificate is uploaded as a new version, beside the expiring one.
Finance signs off
The record shows which certificate version they signed.
Archive
Filed automatically, with a permanent record of where it went.
Governance
Board meeting
The secretary assembles the packet and starts the request. Everything after that is either a board member voting or Orgworks doing clerical work.
Board members get a link in their email. It opens the packet and their ballot, with no account and no password — and their vote is attributed and audited exactly like a signed-in one. Each motion is counted on its own, over the members who actually voted on it. A motion that fails is just a motion that failed; the meeting carries on and the minutes say so.
Secretary assembles the packet
Documents in the bundle, motions as agenda items. More can be added later.
Deliver the agenda
Emailed to everyone in the board group.
The board votes
One ballot each: yes, no, or abstain on every motion. Majority counted per motion.
Write up the results
Outcomes and tallies become a document in the bundle.
Deliver to the secretary
Sent to whoever holds the secretary role.
Archive the whole meeting
Packet, ballots, results, timeline. Filed in the corporate record.
Property
Move-in
A lease is signed in a system that isn't Orgworks. That system posts to a private URL, and the move-in checklist starts — keys, utilities, insurance certificate, inspection — each step assigned to whoever handles it.
The request is started as a real member of your organization, so "the building manager's boss" means something and the timeline reads the same as if someone had clicked Start.
The leasing system starts it
A POST with the unit and tenant details. Bad token, no request.
Three things at once
Keys, utilities, and the certificate of insurance run in parallel, not in a queue.
Inspection, once they're all done
The rejoin waits for every branch that's still live, and no longer.
Tell the leasing system
Posted back out when the unit's ready. Retried until it lands.
See it route something of yours
Bring a workflow you run on email today — an approval chain, a renewal, a board packet. We'll build it as a Template on the call and walk a real Request through it.
30 minutes. No slides.