# Track a Print Job from Intake through Production and Shipping Give each physical print order one job reference and record the evidence that supports every important handoff. Confirm the approved artwork version and order details before production, then update the record when work actually reaches a new stage. Keep proof of dispatch or receipt with the job so a status label can be checked against what happened. A fictional print shop is handling a short run of postcards, a set of event signs, and a batch of labels. Each order has a different quantity and production stage, so one general status cannot tell the office what is physically complete. The job card below records the approved version, the work observed, and the evidence reference for each order. The print shop, customers, job details, approval references, quantities, stages, and evidence in this example are fictional. Canonical: https://areinum.com/guides/track-print-job-through-shipping/ Language: en Updated: 2026-10-31 ## Create one job record when the order is accepted Give the order a stable job number and link it to the customer reference already used by your shop. Record the product, quantity, material or stock, finishing choices, requested delivery method, and the date the details were confirmed. Copy these values from the accepted order record rather than relying on a memory or a note in a separate conversation. Keep the customer request, the version sent for review and the version approved for production distinguishable. Record the exact approved artwork and an affirmative approval reference, such as a dated email or signed proof. If approval is still open, show that the job is waiting for the decision. ## Record production stages when they actually change Choose stage names that match the work your shop performs. A small order might move through prepress, printing, finishing, quality review, packing, and dispatch, while another order may skip a stage. The card is a suggested tracker, not a universal production standard. Record the stage observed, the time, the person recording it, and a reference to the relevant job ticket, check sheet, or other evidence. When responsibility moves between people or work areas, state what was handed over and what remains. If a quantity is short, a finish is delayed, or a machine issue changes the schedule, record the actual exception and the next owner. Do not leave an order marked in production when the team has already packed it or discovered that it needs a customer decision. Three fictional print jobs have different observed stages and evidence references. - Job: PR-401 postcards; Approved version and evidence: Proof V2, approval email AP-401; Observed stage: Queued for press; Observed date/time: 2026-10-16 09:15, fictional shop time; Observed by: Quinn, fictional job coordinator; Stage evidence: Job ticket JT-401; Packed quantity: Not packed; Dispatch date/method: Not dispatched; Next action owner: Casey, fictional press operator; Next action: Record actual press start and completed quantity - Job: PR-402 event signs; Approved version and evidence: Artwork V3, approval note AP-402; Observed stage: Finishing; Observed date/time: 2026-10-16 14:10, fictional shop time; Observed by: Sam, fictional production checker; Stage evidence: Press check PC-402; Packed quantity: Not packed; Dispatch date/method: Not dispatched; Next action owner: Avery, fictional finishing lead; Next action: Record finished count and quality check - Job: PR-403 product labels; Approved version and evidence: Proof V1, approval email AP-403; Observed stage: Dispatched; Observed date/time: 2026-10-17 10:05, fictional shop time; Observed by: Robin, fictional dispatch clerk; Stage evidence: Packing record PK-403 and carrier scan SH-403; Packed quantity: 800 of 800; Dispatch date/method: 2026-10-17 by carrier; Next action owner: Jordan, fictional shop coordinator; Next action: Check delivery status against the shop's agreed process ## Keep approval and production evidence attached to the order A job record should point to the evidence rather than duplicate every file or message. Use your approved document store for artwork and customer approvals, then put a stable reference in the tracker. When a revision replaces an earlier file, preserve which version the approval referred to and which version the team actually used. Use evidence that matches the event. An approval reference supports the approved artwork version; a production check supports the recorded production stage; a carrier scan supports dispatch. None of these references proves every other milestone. If an event has not yet happened or the evidence is missing, show that explicitly instead of filling a row with a planned date. ## Close the physical handoff with a dispatch record Before an order leaves the shop, record the packed quantity, the dispatch date, and the carrier or collection reference used by your existing process. If the customer collects the work, record the collection evidence your shop normally keeps. Track delivery as a separate event from dispatch, and use a receipt confirmation only when you have one. If the carrier status is delayed or the customer reports a problem, retain the prior event and add the new observation with its own time and owner. This creates a short history of what the shop knows. It does not guarantee that a shipment will arrive on time or resolve a dispute about the physical product. ## Use the card for the next handoff At the start of a shift or production meeting, filter the register for jobs whose latest stage lacks evidence or whose next action has no owner. Ask the person who recorded the stage to supply the reference or correct the status. This review turns the card into a list of concrete follow-ups instead of a dashboard color that nobody can explain. A production coordinator can use the job card to connect scheduling, material availability, artwork approval and the next physical handoff. Record what actually happened before moving the job to the next stage. ## Interpret the sample as fictional evidence The CSV shows one job waiting for press, one in finishing, and one dispatched. Each stage has a separate reference, and the next action belongs to a named fictional role. The sample has no delivery confirmation for PR-403, so the row does not call it delivered. Replace these references with the records your shop actually creates and keep planned events separate from completed ones. ## Using Areinum Ask Areinum Assistant to organise the job details, artwork approval reference and recorded stage into a handoff summary. The shop checks the physical job and records each production or dispatch event in its usual system. ## Questions you may have ### Does sending a proof mean the artwork is approved? No. Keep the exact approved version and an affirmative approval reference with the job; an unanswered proof is still waiting for a decision. ### When should a job be marked dispatched? After the shop records the actual handoff and retains the relevant packing or carrier reference. A planned dispatch is a separate status. ### Is a carrier scan the same as confirmed receipt? It records the event shown by the carrier. Check the available delivery or recipient confirmation separately when the shop needs that information. ### Can Areinum see my print shop's production status live? The demo uses sample company data. Ask whether your job source and the status information you need are available. ## Sources and further reading - [A print and sign shop owner asks for help with growing operations](https://www.reddit.com/r/smallbusiness/comments/1k67iun/small_business_is_exploding_and_need_help/): One self-described print-shop owner lists scheduling, material orders, design approvals, installation, and daily problem-solving among their responsibilities. Single historical self-report with no independently verified identity, prevalence, or measured process outcome. It does not establish that any particular stage tracker is required. (2026-10-18) Download the original worksheet: https://areinum.com/guides/track-print-job-through-shipping/print-job-stage-evidence-register.csv ## Print job stage and evidence register The print shop, customers, job details, approval references, quantities, stages, and evidence in this example are fictional. | Job reference | Client or project | Product and quantity | Material or finish | Approved artwork version | Approval evidence | Observed stage | Observed date/time | Observed by | Stage evidence | Packed quantity | Dispatch date | Dispatch method | Next action | Next action owner | Dispatch or receipt evidence | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | PR-401 | Harbor Finch Cafe | Postcards, 500 | Matte stock | Proof V2 | Approval email AP-401 | Queued for press | 2026-10-16 09:15, fictional shop time | Quinn, fictional job coordinator | Job ticket JT-401 | Not packed | Not dispatched | Not dispatched | Record actual press start and quantity | Casey, fictional press operator | Not dispatched | | PR-402 | Mallow Field Events | Event signs, 12 | Rigid board, edge finish | Artwork V3 | Approval note AP-402 | Finishing | 2026-10-16 14:10, fictional shop time | Sam, fictional production checker | Press check PC-402 | Not packed | Not dispatched | Not dispatched | Record finished count and quality check | Avery, fictional finishing lead | Not dispatched | | PR-403 | Stonebridge Goods | Product labels, 800 | Roll labels | Proof V1 | Approval email AP-403 | Dispatched | 2026-10-17 10:05, fictional shop time | Robin, fictional dispatch clerk | Packing record PK-403 | 800 of 800 | 2026-10-17 | Carrier, tracking reference SH-403 | Check for a delivery event when available | Jordan, fictional shop coordinator | Carrier scan SH-403, delivery not confirmed | 1. The shops, customers, job numbers, artwork versions, and evidence references are fictional. Use references from your own order and production records. 2. Record approval against the exact artwork version. A sent proof or silence is not an approval event. 3. For each stage update, record the observation date and time and the person who observed it. Every next action needs a named owner. 4. Record packed quantity, dispatch date, and dispatch method when those events occur. Until then, use Not packed or Not dispatched. Keep dispatch and delivery as separate states. 5. Use the next action to identify the person who must do something. Do not store customer passwords, payment data, or unrelated private information in this register. ### Record production stages when they actually change Three fictional print jobs have different observed stages and evidence references. | Job | Approved version and evidence | Observed stage | Observed date/time | Observed by | Stage evidence | Packed quantity | Dispatch date/method | Next action owner | Next action | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | PR-401 postcards | Proof V2, approval email AP-401 | Queued for press | 2026-10-16 09:15, fictional shop time | Quinn, fictional job coordinator | Job ticket JT-401 | Not packed | Not dispatched | Casey, fictional press operator | Record actual press start and completed quantity | | PR-402 event signs | Artwork V3, approval note AP-402 | Finishing | 2026-10-16 14:10, fictional shop time | Sam, fictional production checker | Press check PC-402 | Not packed | Not dispatched | Avery, fictional finishing lead | Record finished count and quality check | | PR-403 product labels | Proof V1, approval email AP-403 | Dispatched | 2026-10-17 10:05, fictional shop time | Robin, fictional dispatch clerk | Packing record PK-403 and carrier scan SH-403 | 800 of 800 | 2026-10-17 by carrier | Jordan, fictional shop coordinator | Check delivery status against the shop's agreed process | ### Limits of this method - The stage names and evidence choices are a proposed manual pattern that should match the actual work and records of each print shop. - A recorded production or dispatch event is not a guarantee of product quality, delivery timing, or customer receipt. ## Related reading - [Turn an accepted service package into separate scheduled jobs](https://areinum.com/guides/accepted-service-package-to-scheduled-jobs/) - [One conversation for the work behind your business](https://areinum.com/product/assistant/) Explore the demo: https://platform.areinum.com/ The demo uses sample company data. Access may need to be arranged.