Skip to main content
A job is a quote the customer said yes to. It carries the same group / line / decoration structure, plus everything production needs: tasks, proofs, purchase orders and an activity trail.

​
The board

Jobs sit in a status. Built-in statuses cover the common path, and you can add your own in Settings → Custom statuses so the board reads in the language your floor already uses. Moving a job between statuses is what drives everything else. Automations fire on status change, and the activity feed records who moved it and when.

​
Tasks

Tasks are the actual steps: burn screens, mix ink, print, fold, pack. Each task can carry:
  • an assignee, so people can see just their own work
  • a checklist, for steps within the step
  • comments, so a question about a job stays on the job
  • attachments, like a screen setup photo or a supplier email
If your jobs repeat the same steps, define them once in Settings → Task templates and new jobs arrive with the list already built.

​
Purchase orders

When a job needs stock you do not have, raise purchase orders from the job. PRINTOOLS splits them by vendor automatically, so one job needing garments from two suppliers produces two POs. Receive against PO lines as stock arrives. Partial receipts are normal and the PO status reflects them; some statuses are derived from what has been received and cannot be set by hand. See Purchase orders.

​
Proofs

Before anything gets printed, the customer signs off artwork. See Proofs and approvals.

​
Activity

Every job has an activity feed naming the staff who acted. When a customer asks why their order shipped late, this is the answer.
If a quote is corrected after the job was created, use Sync from quote on the job rather than editing both. The job keeps its link back to the quote for exactly this.