← All white papersOperator workflow · September 2026

The Rejected Pack Workflow

The job is not “generate a policy”. The job is: a pack leaves only when it can be handed to a builder, an insurer or an inspector without a scavenger hunt. The binding layer is the hard step. A person still accepts.

12 min read·Companion to the build standard·Published by AI Pathway

Used by

HSEQ Administrator
Compliance Administrator
Office Manager

How to get this live in your business

Done for you: the calls behind your quotes and stage invoicesEvery open quote asked for a decision, every stage invoice confirmed with a date, against your Xero. Get Paid $199 a month, flat, no call caps.

Build it myself

Free. The Rejected Pack Build Standard: the objects, the checks in order, and the pass test.

Ready for

Microsoft 365Google Workspace

The Rejected Pack Build Standard says what a working build looks like. This page is the other half: who does what on a Tuesday, which of four triggers started the work, what the office clears first, and which system is allowed to write into which. Done looks like this. One location has one current pack. Every applicable artifact is in it. Every field traces to the graph. A named person accepted this version. Fail does not leave the building.

In short

What this is: The operator's runbook for the Rejected Pack standard: four roles, four loops, four queues, one daily board, and a table of which system reads and writes what.
The core rule: Clear Yellow by correcting the graph, never by editing the PDF. Export only from Pass. Fail blocks dispatch and does not leave as an email, an upload or a print.
What stays with a person: Accepting anything that would be signed in ink, deciding a Fail, and chasing a missing ticket. The machine never says compliant and never files with a regulator.
Where to start: Loop A, once per entity. If you skip the graph and start generating documents, you have built another Drive.

Take the spec to Claude, ChatGPT or Copilot. The sentence to paste is one click away.

Want the whole thing by email?

This paper, plus the rest of the library. One click to stop them.

1. Who is in the workflow

Role	Does	Does not
Owner or licensed person	Accepts anything that would be signed in ink. Adds a location. Owns Fail decisions.	Retype the ABN onto the tenth form. Hunt for last year's PDF.
Office, HSEQ or compliance	Clears Yellow. Chases Hold. Sends the handover pack.	Invent applicability. Override an expired ticket to make a job start.
Bookkeeper or practice (the channel)	Runs Yellow and Hold across clients. Keeps tickets and ABNs current from Xero.	Sign a SWMS. Tell a client they are compliant.
The build (the binding layer)	Graph, applicability, fill, queues, diffs, pack export, the as-of stamp.	File with a regulator. Say the word compliant. Promote Yellow to Pass.

2. The four loops

One workflow, four triggers. Do not mix them into a single inbox.

A. Stand up the graph

Trigger: New client, new entity, or first location

Output: Graph, ticket Hold list, first applicability

Cadence: Once, then whenever the entity changes

B. Job or site pack

Trigger: Job booked, site named, or a builder asks for prequal

Output: Location pack ready to hand over, or sitting in a queue

Cadence: Per job or per site

C. Keep it current

Trigger: Ticket expiry, rule change, headcount, new award clause

Output: Patch card. The pack leaves Pass until accepted again.

Cadence: Daily watch, plus as events land

D. Rejected after the work

Trigger: Builder, insurer, council or QBCC says no

Output: Finding becomes an obligation. New version. Old version frozen.

Cadence: When it happens

3. Loop A: stand up the graph

Do this once per entity. Everything else reads it. If you skip this and start generating documents, you have built another Drive.

Create the entity. Legal name, trading name, ABN, officers, registered address, postal address.
Add locations. Address, state, council if known, and what happens there: office, workshop, site, property.
Connect the systems you already run. Job system: ServiceM8 or Simpro. Ledger: Xero or MYOB. Property: PropertyMe or Console. Documents: Microsoft 365, the SharePoint library or OneDrive folder where the certificates already live, or Google Drive. The build reads. It does not become a second job board or a second document store.
Point the build at the existing packet. Licence PDFs, insurance certificates, workers comp, white cards, the last SWMS, the last handbook, the last prequal, wherever they sit in SharePoint or Drive. The build extracts into the graph with confidence scores and files each original back under its node.
Tickets that did not extract go to Hold. Expired tickets go to Fail until renewed. Do not store them as “fine for now”.
Run applicability at entity level: what is always on for this business in this state, regardless of today’s job.
The owner accepts the entity profile. That is the first human gate.

The machine, on Loop A

Read the ABN lookup, extract certificates, list the likely obligations, flag expired dates, write the first Hold list.

The person, on Loop A

Confirm the trading name, confirm the work they actually do, accept the profile, chase a missing ticket.

4. Loop B: the job or site pack

This is the daily motion. A job is booked. Someone will ask for the pack before the truck leaves, or after the work when a claim is filed. Same checks either way.

The job lands in the job system with a site address and a work type. That is the trigger. Nobody retypes it into the build.
The build attaches the job to a location. A new address becomes a new location node, not a one-off PDF.
Applicability runs for this work type, this site, this headcount, this state. The output is two lists: applies, and does not apply because.
The eight checks run in order and stop at the first failure. Identity, tickets, applicability, artifact completeness, field reuse, source and as-of, human gate, handover. Do not skip to the pretty document.
The factory fills official forms from the graph and drafts narrative artifacts: a SWMS for the common job type, notices, handbook pages. Yellow fields only.
The pack sits in a queue. Nothing in Fail is emailed, uploaded or printed for a third party.
The office clears Yellow. Hold stays Hold until the missing ticket or artifact exists in the graph.
The owner or licensed person accepts. A version is minted. As-of is stamped.
Handover. Link, zip, print, or a SharePoint link the counterparty can open. A QR code on the pack resolves to this version, not to a folder of drafts.

The eight checks themselves, and what each one stops, are in section 4 of the standard.

5. Loop C: keep it current

A pack that passed in March and is handed over in September without a check is how claims bounce. Store the rule with an effective date. Derive the due date. Never the other way round.

Watchers run daily: ticket expiry inside 30, 14, 7 and 0 days, ABN status, known form revisions, and published WHS, Fair Work, QBCC or council changes that touch this vertical.
A headcount change from payroll or the job system is a trigger. Thresholds are rules, not calendar reminders.
When something moves, every pack that cited it leaves Pass. A patch card opens: old text or old date, new text or new date, why, due by.
Yellow if the build inferred the mapping. Hold if a new artifact is required and does not exist yet. Fail if a ticket is already expired.
The same human gate as Loop B. Accepting the patch mints a new pack version. The old one stays in history.

6. Loop D: rejected after the work

The homepage job. The work was fine. The pack was not.

Log the rejection as a finding: who rejected it, which artifact, the reason in their words, the date.
The finding becomes an obligation on that location. It is not a Slack message.
The fix lives on a new version. Do not silently edit the copy they already have.
If the rejection is a missing ticket, the contractor or staff member goes to Hold for future jobs until the ticket is in the graph.
If the rejection is a rule you did not have, add the rule with an effective date and re-derive. That is how the calendar survives.

7. The four queues

Queue	Meaning	Who works it	May it leave?
Pass	Eight checks held. Accepted. Current as of now.	Nobody, until something moves.	Yes.
Yellow	Extracted or inferred. A person must confirm.	Office, bookkeeper, or the owner on their phone.	No.
Hold	Applies, and the ticket or artifact is not in the graph.	Whoever owns that ticket.	No.
Fail	Expired, conflicting identity, stale rule, or no gate.	The owner. This is a stop.	No. Not as email, not as a portal upload.

8. The daily board

For the office or the practice. This is the screen, not a chat window.

1Open due-this-week
Tickets inside 14 days, packs still in Yellow, Holds older than 48 hours, patch cards unaccepted.
2Clear Yellow first
Confirm or correct the graph. Do not edit the PDF by hand and leave the graph stale.
3Chase Hold
A missing workers comp certificate is a phone call, not another reminder email to nobody.
4Fail stays visible
A job that needs that pack does not dispatch until Fail clears or the job is pulled.
5Export only from Pass
If someone asks to just send what we have, that is how packs get rejected.

9. What touches what

System	Reads	Writes back	Never
ServiceM8, Simpro	Job, site, work type, assigned techs	Pack status on the job (Pass, Hold, Fail) and a link to the current pack	Become the system of record for licences
Xero, MYOB	ABN, legal name, contacts, a headcount proxy if used, contractor bills for Invoice Check	Nothing legal. Optionally a note on the contact that the pack is on Hold	Raise invoices from a SWMS
PropertyMe, Console	Property, tenancy, existing compliance dates	Derived due dates onto the calendar the office already opens	Replace the agency's property record
Microsoft 365 (SharePoint, OneDrive, Outlook), Google Drive, photos	The library where certificates and old packs already live, dropped files, site photos, certificates arriving by email	Extracted fields into the graph, originals filed back to the library under the node, the current pack as a link	Remain the live pack, or be reorganised into a second copy of the graph
The pack build	All of the above	Graph, queues, versions, the handover pack	Silent submit to QBCC, SafeWork, or a council portal

Invoice Check stays its own standard and runs on the payables side. A failed invoice check can put that subcontractor on Hold for Loop B. Do not merge the two queues.

10. The first pack for QLD trades

Do not boil the ocean. This is the set that already rejects packs for the firms this site already serves.

Artifact	Type	Source of fields	Gate
QBCC licence copy and class check	Ticket	Extract, plus the QBCC public register if used	Fail if expired or the class does not cover the work
Workers compensation	Ticket	Certificate drop	Fail if expired
Public liability	Ticket	Certificate drop	Fail if expired or under the site minimum
White card and high-risk tickets per tech on the job	Ticket	Staff graph plus job assignment	Hold the job if the assigned tech is missing one
SWMS for the common job type	Narrative plus site fields	Work type from the job system, site address from the graph	Licensed person accepts. Yellow if site conditions were inferred
WHS notices and posters that apply at this headcount	Narrative	Headcount plus state	Accept once, patch on a threshold or rule change
Subcontractor mini-pack	Their graph, not yours	Their tickets against this site's minimums	They do not go on site from Fail
Handover folder	Pack	Everything above, current versions only	Export only from Pass

Property management comes second: wrap the published Compliance Calendar as a pack around the smoke alarm, pool barrier, minimum housing and entry notice dates the office already tracks.

11. What you do not run

Do not start this workflow if first response or getting paid is still the leak. Sequencing stands.
Do not let the build tell a client they are compliant.
Do not e-file to a regulator from version one. Export, plus a submit checklist.
Do not flatten Fair Work, state WHS and a builder’s site rules into one handbook page.
Do not silently reflow last year’s answers onto a new official form.
Do not train a public model on a customer pack.

12. ROI Snapshot

Illustrative levers, not measured results: there are no client averages behind them. Assumes the first pack for QLD trades and one entity with a few locations. Your pack and cadence will differ.

One pack

Per location, current

One location has one current pack, every applicable artifact in it, and a named person on the version

30 days

First warning on a ticket

Watchers run daily on ticket expiry at 30, 14, 7 and 0 days, plus ABN status and published rule changes

Zero

Retyped fields on a form

The job system is the trigger and the graph is the source, so nobody retypes the ABN onto the tenth form

The largest gain is the loop that watches the dates: the pack that passed in March is not the pack handed over in September unless something did.

13. Path through the firm

Use the standard

The owner or the office runs the eight checks and four queues in a sheet and a Drive. Fine for one location that rarely changes.

Build the binding layer

Graph, form fill, queues, diffs, handover. The human gate stays. This is the hard step: build it to the conformance checklist, not to a demo.

We implement

Three systems, messy subcontractors, a practice with many client graphs, or a team that will not maintain a Zap. Diagnosis, then the $500 audit, credited.

Start with the workflow, not the tool. You keep judgement. The machine does the volume. If the pack cannot be handed over at the door, the workflow is not running, regardless of how good the documents look.

Want it done for you?

Nothing ready-made binds the pack today. If you would rather have it stood up than stand it up, start with the 8-minute diagnosis: it checks fit before anything is charged. What is ready-made for a builder is the calls beside the paperwork: every open quote asked for a decision and every stage invoice given a payment date, against your Xero.

See it for builders Start the 8-minute diagnosis I am stuck on the pack

Technical? The build standard is open. Take it.