Print shop analytics built from the work. Not from a form.
Every number here comes from a timestamp a worker created by tapping a button to move a job forward. Nobody writes a report. Nobody reconstructs a week from memory.
The KPI strip at the top of the analytics page — 30-day window, 14-day sparkline, change against the prior 30 days.
Screen printing production reports nobody has to write
Most shop reporting is somebody's recollection, typed in later. This is an event log, and the reports are arithmetic on top of it.
Append-only, never edited
Every workflow move writes a row: prep started, prep ended, approval requested, approval received, job started, job ended, paused, resumed. Each row carries who tapped it, when, which part of the job, and which print location. Nothing overwrites anything — a correction is another row, not a rewrite.
A phase is the gap between two events
Prep is prep-start to prep-end. Approval wait is the moment the proof goes out to the moment the customer answers. Production is job-start to job-end. No one estimates a duration and no one types one in, so there is nothing to round up on a Friday afternoon.
Paused time comes back out
When a run gets paused, that stretch is subtracted from the phase clock. Pauses are tracked per run and then unioned, so two parts paused across the same ten minutes cost the job ten minutes — not twenty. A press waiting on a missing box isn't press time.
One run reports as one run
When line items are grouped to print together — same screens, same setup, one pass per location — the floor logs one event for the whole group. A four-color group doesn't report the same press pass four times, which is exactly how an average gets quietly inflated.
The practical consequence: the numbers are trustworthy because nobody had the opportunity to round them. A duration is two timestamps and a subtraction.
The stage you blame is usually not the stage that's costing you
Shops assume production is the constraint, because production is loud and visible. Then the breakdown comes back and approval wait is three times prep — the press was never the problem, the customer taking two days to say yes was.
That's a different fix. You don't buy a press for it; you send the proof earlier, or you chase the approval. Either way you can only act on it once you can see it.
- Prep47m14%
- Approval Wait3h 12m57%
- Production1h 38m29%
Measured against your stages, not a vendor's
ManagePrint is modular on purpose. The report describes your process, in your words, because that's the only shape the data was ever recorded in.
Per-Part Breakdown
| Part | Prep | Approval | Production | Total |
|---|---|---|---|---|
| Part 1— Front | 18m | 6h 45m | 34m | 7h 37m |
| Group A(3 parts)— Left Chest | 26m | 6h 45m | 51m | 8h 2m |
| Group A(3 parts)— Full Back | 15m | 6h 45m | 1h 12m | 8h 12m |
| Part 4— Left Sleeve | 12m | 6h 45m | 28m | 7h 25m |
One job, four parts. The rows are labeled with this shop's own print locations, and Group A is three line items that press as a single run.
Every timing event records the location it belongs to by name. If your shop calls it “Left Chest,” the report says Left Chest — not “stage 2.”
You decide which line items print together. That decision is what the analytics buckets by, so a grouped run is timed once for the group instead of once per garment color.
Quote and invoice statuses are yours to name, recolor, and reorder, and pre-production stages are yours to define. The pipeline you look at is the one you built.
Setting all of that up is its own subject. See how the workflow is configured.
A print shop KPI dashboard, four numbers deep
Four numbers, each with a 14-day trend line and a percentage change against the prior 30 days. Here is exactly what each one counts.
Revenue (paid)
What actually landed — payment applied to invoices over the last 30 days, against the 30 before it. Not quoted, not invoiced. Paid.
Jobs completed
Jobs that reached completed in the window, with a 14-day sparkline underneath so you can see whether last week was the trend or the exception.
Avg cycle time
Screen printing cycle time end to end: the job is created, the job is finished, and this is the average of everything in between. Down is good here, and the trend badge is colored accordingly.
On-time delivery
Completion compared against the job's scheduled date — or the customer due date imported from Printavo — with one day of grace. Jobs with no date set aren't counted either way.
Managers see the timings. Revenue stays with admins. Cycle time, throughput, on-time delivery, and every phase duration are open to your managers, because that's the data they need to run the floor. The revenue card is withheld from them at the server, not hidden in the interface. And every query is scoped to your organization — no shop can read another's numbers.
The row that settles the argument
Shop throughput reporting down to the individual job: every completed job, every phase, and the averages underneath.
6 completed jobs
| INV-1043 Ridgeline HS — Cross Country | Ridgeline High School | Marisol T. | Aug 12, 2026 | 59m | 6h 45m | 1h 57m | 9h 41m |
| INV-1041 Northside Booster 5K | Northside Boosters | Danny R. | Aug 11, 2026 | 35m | 1h 30m | 1h 18m | 3h 23m |
| INV-1038 Corley Plumbing — Crew Tees | Corley Plumbing | Marisol T. | Aug 10, 2026 | 28m | 12h 0m | 1h 6m | 13h 34m |
| INV-1036 Lakeside Spirit Store | Lakeside Middle School | Jorge V. | Aug 7, 2026 | 1h 22m | 2h 30m | 3h 10m | 7h 2m |
| INV-1032 Vela Coffee — Retail Restock | Vela Coffee | Danny R. | Aug 5, 2026 | 32m | — | 1h 25m | 1h 57m |
| INV-1029 Harbor FC — Kits | Harbor FC | Jorge V. | Aug 3, 2026 | 51m | 2d 0h | 2h 24m | 2d 3h |
| Average (6 jobs) | 47m | 14h 9m | 1h 53m | 14h 28m | |||
Sort by production time to find the jobs that ate the week. Sort by approval to find the customers who sit on proofs.
Each row carries the worker the job was assigned to, so a staffing conversation starts from completed jobs and real phase times instead of impressions.
A reorder that needed no proof has no approval window, so it reads as a dash and is left out of the approval average rather than counted as zero.
And it makes the next quote honest. If your average production phase runs an hour and a half, you can promise a date you'll actually hit — and defend it.
Common questions
What shop owners ask before they trust a number on a dashboard.
Run ten jobs. Then look at the report.
14 days free, no credit card. The dashboard fills itself in as your floor works — there's nothing to configure to make the numbers appear.