Orgworks

Features

Everything Orgworks does

The whole surface, in one list. Nothing here is a separate product, an add-on, or a different plan.

Sec. 1 — Templates

Build the route once

  • Steps in order, with who acts and what counts as done
  • Draft it, publish it, retire it when it's replaced
  • A published template can't be edited — changes start a new version
  • Requests pin the version they started on, so in-flight work is never disturbed
  • Publishing checks the whole route: no dead ends, no steps that can never run

Steps that ask for different things

  • Approval — approve or reject, with a comment
  • Signature — sign off on a specific version of a document
  • Vote — a ballot across the agenda
  • Input — fill in fields the rest of the route needs
  • Acknowledge — read it and say so

Sec. 2 — Routing

Order

  • Sequential by default — no configuration for the common case
  • Several people on one step, working in parallel
  • Split into parallel branches and rejoin them
  • A rejoin waits only on branches that can still arrive

Conditions

  • Branch on any field in the bundle
  • Compare with >, <, equals, not-equals, one-of, or is-it-set
  • First matching condition wins; a catch-all is required
  • Missing or wrong-typed fields never match, so a typo can't misroute

Rework

  • Route a rejection back to an earlier step instead of ending the request
  • The step reopens as a new round with freshly resolved people
  • Only the newest round counts — an old rejection can't sink the retry

Assignment

  • By person
  • By org chart position — N levels up from the requester
  • By role, by group
  • By a person named in a bundle field
  • Resolved when the step opens, recorded permanently
  • If a rule can't resolve, the request stops rather than skipping the step

Sec. 3 — The Bundle

Documents

  • Every upload is a new version; nothing is ever overwritten
  • Each version is fingerprinted, so you can prove it hasn't changed
  • Every approval records the exact versions that were on the table
  • Documents can carry an expiry date — and act on it

Fields

  • Structured values that travel with the request
  • Read by conditions to route, and by rules to assign
  • Written by input steps as the request moves
  • Delivered and archived alongside the documents

Sec. 4 — Time

Reminders

After N hours with no action, everyone still holding the step hears about it again. Anyone who abstained is left alone.

Escalation

After N more, a stalled task moves to that person's manager — replaced, not added, so what "done" means doesn't shift underneath the step. If there's no manager to escalate to, it stays put rather than vanishing.

Requests that start themselves

A nightly scan opens the renewal 30 days before the certificate expires — exactly once, and only for the current version of the document. Upload the renewal and the old one stops asking.

Sec. 5 — Work Orgworks does itself

Archive the bundle

Copies the current version of every document to archive storage and stamps the request with where it went.

Deliver it

Emails the bundle — documents, fields, and a link — to whoever a rule resolves to. "Send the signed packet to the secretary" is a step, not a chore.

Post to another system

Sends the request's state to a URL you name. If it doesn't land, it retries.

Write up the results

Turns the vote outcomes and tallies into a document in the bundle — so delivery and archiving pick it up like anything else.

Start a child request

Kicks off another workflow and waits for it. When the child finishes, the parent moves on — or stops, if the child was rejected.

Start from outside

Another system posts to a private URL and the request begins, assigned to the right people, on the record from the first second. Or run it on a schedule: the first of the month at 9am.

Sec. 6 — Board voting

A ballot, not an approval

  • Yes, no, or abstain on each agenda item
  • Items are set when the meeting starts, or added while it's running
  • A ballot has to cover every item — no half-submitted votes
  • The majority is counted per item, over the people who actually voted on it
  • Outcomes and tallies land on the timeline and in the results document
  • A motion that fails doesn't fail the meeting — the vote is the result

Voters who never log in

  • Each assignment email carries a signed link to exactly one task
  • No account, no password, no app
  • The link opens the packet, the documents, and that person's ballot
  • It expires, and it can't be edited into a link for anything else
  • Votes are attributed and audited exactly like a signed-in action
  • Voting twice, or after the meeting closes, does nothing

Sec. 7 — Day to day

Inbox

Everything waiting on you, across every request, updating live. Approve, reject, abstain, or delegate with a comment without leaving the page.

Request page

The bundle on one side, the timeline on the other, and the thing you're being asked to do at the top. Document versions, expiry warnings, and the agenda with its tallies.

Org chart

Reporting lines, roles, and groups in one place. It's what every "the requester's manager" rule reads from, so it stays worth keeping accurate.

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.

Request a demo

30 minutes. No slides.