How an Enterprise HR Services Company Built Print Inspection That Reads Every Piece Against Its Job Ticket

Open the walkthrough

Five-Step AI Workflow with Human Oversight

Each step shows the workspace, what the AI completed, and what still needs human review.

Steps 4 and 5 need a person. Step 4 is waiting for approval right now. Click it to open the full walkthrough.

Estimates are directional and based on stated assumptions. All names, organizations, and identifying details have been anonymized in accordance with our confidentiality agreements.

The Transformation

How an Enterprise HR Services Company Built Print Inspection That Reads Every Piece Against Its Job Ticket

Before

✗A person used to walk the line each hour checking the cameras still pointed true.

✗A person used to pull one tray in ten and check it against the ticket by hand.

✗A person used to make every defect call off the sample tray.

→

After

✓every piece photographed, every frame tied to its job

✓every piece read against the ticket that ordered it

✓every mismatch called, cleared, or held as new

✓fifty-one pieces off the belt, the run decision waiting

✓the shift closed, two rule changes waiting on you

Executive Summary

Every piece the fulfilment line prints and mails for a client employer, from the frame the camera takes to the moment the piece is released or pulled. The line used to be checked one sample tray in ten; now every piece is photographed, read against its job ticket, and called. The agents make the calls the defect library already answers, and hand a person only the pieces nobody has seen before and the decision to stop a run. Five stations, run as a loop: the rule a person accepts at station 5 is the rule station 2 reads against tomorrow.

What Was Broken

A person used to walk the line each hour checking the cameras still pointed true

A person used to pull one tray in ten and check it against the ticket by hand

The real cost

A person used to make every defect call off the sample tray.

What We Built

Five stations and 12 subagents. Each subagent carries its own tasks and its own refusal.

Frame Capture

Capture every piece off all four cameras as it passes, three frames each

Camera Watch

Check each camera's focus and exposure against its own last thousand frames

Piece Reader

Read every piece off its frames: pages, inserts, address block, barcode

Spec Match

Match what was read against what the job ticket says the piece carries

Track Keeper

Track each flagged piece across its three frames, so one piece gets one verdict

Defect Caller

Classify each mismatch against the defect library, entry by entry

Pattern Watch

Compare the shift's defect count against the same line's last thirty shifts

Alert Desk

Divert every called defect off the belt into the pull lane before the wrap station

Rework Notes

Draft a rework note for each pulled piece: the frame, the ticket line it fails, the fix

Line Ledger

Check every piece that came down the line against where it ended

Trend Board

Map the shift's defects across lanes, hoppers and hours on one board

Rule Proposal

Propose the flagging rule that would have caught each repeated miss earlier

How It Runs

Line Capture

Nobody is asked anything here

Agents capture every piece off every camera as it passes, tie each frame to the piece and the job run it belongs to, and re-shoot any frame too blurred to read. Nothing waits on a person here. A drifting camera holds its own lane; no piece gets a verdict off a blur.

Spec Checking

Nobody is asked anything here

Agents read every frame end to end, pull the fields the job ticket names, and check each piece against the ticket that ordered it and the mailing record it goes out under. Nothing waits on a person here. A piece with no job behind it is never released on a guess about whose mail it is.

Defect Calling

Nobody is asked anything here

Agents follow each flagged piece across its frames so it gets one verdict, call each mismatch against the defect library, and hold anything the library has never seen for a person. Nothing waits on a person here. A mark that matches no known defect is held, never called a pass because nothing on file matches it.

The Pull Lane

A person answers here

Agents divert every called piece off the belt before the wrap station, put its frame beside its ticket, and draft the rework note; the decision on a cluster and on the pieces nobody could call is a person's. This is where a person works. Everything upstream exists so that 51 pieces, not 6,240, reach this lane.

Shift Close

A person answers here

Agents check every piece against where it ended, map the shift's defects across lanes, hoppers and hours, and propose the rules that would have caught today's cluster earlier. A person accepts or rejects each rule. What gets a piece pulled off the belt is not something an agent changes quietly.

Where a Person Decides

•Step 4, The Pull Lane. Decide lane 2: refill hopper 2 and rerun the 31, or stop the run. Clear the 7 uncalled pieces, the 3 smears and the 4 with no job behind them. a cluster holds the run until you say otherwise.

•Step 5, Shift Close. Accept or reject the two proposed rules. Name the smear and decide whether it joins the defect library. the rules are yours to accept.

Operating Model

This changes how work flows through the team.

Role

Responsibility

The Pull Lane owner

Decide lane 2: refill hopper 2 and rerun the 31, or stop the run. Clear the 7 uncalled pieces, the 3 smears and the 4 with no job behind them. a cluster holds the run until you say otherwise.

Shift Close owner

Accept or reject the two proposed rules. Name the smear and decide whether it joins the defect library. the rules are yours to accept.

Line Capture, when it goes wrong

Look here only if a piece reached the pull lane with no photo behind it.

Spec Checking, when it goes wrong

Look here only if a client reports a packet gone out wrong and the shift record shows no mismatch.

Defect Calling, when it goes wrong

Look here only if a defect you caught by hand never got called.

What Transfers, What Must Be True

What transfers

•A person is in the loop wherever a run's release is at stake or the rules that pull a piece change. Two stations refuse to proceed on their own, The Pull Lane and Shift Close, and those are the two a person carries. Everywhere else the agents photograph, read, call and clear, and reach a person only with the pieces nobody has seen and the decision to stop a run.

•The Pull Lane stops for a person, and a cluster holds the run until you say otherwise.

•Shift Close stops for a person, and the rules are yours to accept.

•Every subagent says what it will not do. 12 of them do.

What must be true in your environment

•The agent can read the systems your records already live in. This one reads 18.

•Somebody owns The Pull Lane and has time for it.

•Somebody owns Shift Close and has time for it.

Failure Modes

What breaks this pattern:

✗ A blur becomes a verdict

Without the re-shot rule, the system calls a piece off a frame nobody can read. That call sits in the ledger looking exactly like a good one.

✗ The orphan piece ships anyway

A piece with no open ticket behind it gets matched to the nearest run on a guess. It ships to whoever that run belongs to.

✗ New defects get old names

A mark the library has never held gets scored as the closest defect on file. The first sign of a new problem enters the record under the wrong name.

✗ The run releases itself

A live cluster stands on the lane and the run keeps releasing. A person finds out after the shift ends, not before the pieces leave.

Directional Outcomes

What the agent counts, and the station that counts it.

These counts are the tallies from one monitored run of the agents. They are not monthly or annual totals.

Pieces photographed

Counted at Line Capture

486,000

Pieces that passed unphotographed

Counted at Line Capture

Lanes held for a re-shot

Counted at Line Capture

Pieces read against their ticket

Counted at Spec Checking

486,000

Pieces released against the wrong job

Counted at Spec Checking

Pieces it would not match

Counted at Spec Checking

214

Defect calls made

Counted at Defect Calling

4,860

Good pieces scrapped on its call

Counted at Defect Calling

Calls it handed to a person

Counted at Defect Calling

310

Our measurement policy: We do not publish precise ROI without baseline methodology. Every figure above carries its basis.

What Runs Where

Every step names the subagent that does the work, the record it writes, the thing that raises a question for a person, and what it is allowed to touch. This is drawn from the source, not from a diagram somebody kept in sync by hand.

1Line Capture

subagentframe-intake

writesline/frames/<piece-id>.json

raiseshold-unreadable-frame

may touchline/frames/**, the cameras read-only

2Spec Checking

subagentspec-check

writesline/read/<piece-id>.json

raisesno-job-found

may touchline/read/**, line/frames/** read-only, the job tickets read-only

3Defect Calling

subagentdefect-call

writesline/calls/<piece-id>.json

raisespattern-never-seen

may touchline/calls/**, line/read/** read-only, the defect library read-only

4The Pull Lane

GATE

subagentpull-lane

writesline/pulls/<piece-id>.md

raisesawait-run-decision

may touchline/pulls/**, reprints/queue/**, everything else read-only

5Shift Close

GATE

subagentshift-close

writesrules/proposed/<rule-id>.json, reports/shift-<date>.json

raisesaccept-rule-change

may touchrules/proposed/**, reports/**, the shift record read-only

Stack

Every system this agent reads or writes.

System

Read at

Stations

the belt encoder

Line Capture

1 of 5

the client rosters

Spec Checking

1 of 5

the defect library

Defect Calling

2 of 5

the flagging rules

Shift Close

1 of 5

the four line cameras

Line Capture

1 of 5

the frame store

Line Capture

3 of 5

the hopper refill log

Defect Calling

1 of 5

the insert hoppers

The Pull Lane

1 of 5

the job run schedule

Line Capture

1 of 5

the job tickets

Spec Checking

2 of 5

the line alert board

The Pull Lane

1 of 5

the mailing record

Spec Checking

1 of 5

the pull lane diverter

The Pull Lane

1 of 5

the pulled-versus-released log

Shift Close

1 of 5

the reprint queue

The Pull Lane

1 of 5

the shift baseline

Defect Calling

1 of 5

the shift dashboard

Shift Close

1 of 5

the shift record

Shift Close

1 of 5

Next Step

Want to see if this pattern fits your computer vision?

Start a Conversation See More Work

No build commitment·Real samples, not a demo·Estimate in writing