Job statuses and workflow examples for a sign shop

What a job status should explain

A job status is the shared answer to one operational question: where is this job in the workflow now? It should give sales, artwork, production, purchasing, installation and management enough context to understand the current stage without turning every task or blocker into another status.

Use statuses to separate work that is waiting from work that is genuinely executable. A short, consistently applied list is more useful than a detailed list that people interpret differently.

What SignBas3 lets an Owner or Admin configure

Settings > Job Statuses supports:

• status name and colour;
• semantic Status Type;
• Active or Retired state;
• visibility in My Jobs and Schedule;
• Job Costs and Timesheets locks;
• status-change alert routing to selected users.

When no statuses exist, Load Default Statuses creates the standard starting set: Queued, Job Created, In Production, Awaiting Materials, Ready for Dispatch, Ready for Install, Completed, On Hold and Cancelled. Owners and Admins can add other labels where the business has a materially different next action.

A practical custom workflow example

The following labels are recommendations, not SignBas3 defaults or automated gates:

Use only the statuses your team can define and apply consistently. A retail print counter may need fewer stages, while a manufacturer spanning design, fabrication, print, subcontracting and installation may need more.

Keep status, tasks, priority and blockers separate

A status describes the whole job's stage. A task describes a piece of work. Priority decides which ready job should be acted on first. A blocker explains why work cannot continue.

• Status: In production.
• Task: Print and laminate two vehicle graphics panels.
• Priority: Urgent because installation is fixed for Thursday.
• Blocker: Replacement vinyl is due tomorrow.

Keep the operational detail on the relevant job tasks, notes and records instead of expanding the status list for every exception.

Treat ownership and evidence as operating policy

Nominate who owns each important transition and what evidence the business expects. For example, artwork approval should identify the approved version, receiving should confirm delivered material, and installation completion may require photos and notes.

These are business controls, not options configured on Settings > Job Statuses. The page does not assign per-role transition authority or require attachments before a status can change. Store evidence in the relevant job artwork, task, purchasing, file, photo or note workflow and verify it separately.

Test with representative jobs

Run the proposed set against a repeat print, an artwork-heavy custom sign, a job waiting on purchased material, a multi-stage fabrication job and an installation with a fixed booking. Ask whether each department can tell what is ready, what is waiting and who acts next.

Then use the statuses in a production meeting. If the team still needs a parallel spreadsheet or verbal explanation to understand the queue, refine the status definitions or the supporting job information.

Consistent status labels can support operational reporting and ageing review, but the labels remain useful only when the team applies them to current jobs consistently.

A practical sign-shop job status workflow

Treat the example above as an operating-policy starting point. It is not a second set of SignBas3 defaults and it does not create automatic approval gates. Select only the stages that cause a genuinely different next action in your business, then configure those names, colours and visibility settings in SignBas3.

A small print counter may combine artwork and production readiness. A company that designs, fabricates, prints, subcontracts and installs may need separate stages for customer approval, material readiness, workshop execution and field completion. The useful test is whether the person opening the job can tell what happens next.

Job status, workflow stage and task: what is the difference?

Keep these signals separate even when they appear around the same job. One job can remain in the artwork stage while several design tasks are complete, a customer decision blocks release and a fixed site date makes the work commercially urgent. A single overloaded status label cannot explain all of that clearly.

Group job statuses into a simple lifecycle

A longer status list becomes easier to review when every label belongs to one of three broad operating groups:

• Not ready. Accepted work still requires artwork, customer input, material, survey information or another prerequisite.
• In progress. The job is actively moving through production, finishing, delivery or installation.
• Done. Operational work is complete, with commercial closeout handled deliberately.

These groups are a management convention rather than fields configured on the Job Statuses page. They can simplify production meetings without removing the exact status that determines the next action.

Choose status names that tell someone what to do next

Prefer a specific operating condition over a vague mood. Awaiting artwork approval tells the account owner to obtain a customer decision. Waiting on materials identifies a purchasing dependency. Installation booked protects a fixed commitment. Labels such as Pending, Open or On hold usually force the team to open the job and rediscover the reason.

Use familiar production language, then document what the label means. Keep the list short enough that people choose consistently and detailed enough that two materially different actions do not share one status.

Control status changes with ownership and evidence

Document who is expected to move each important status and what evidence the business expects before that change. Sales may confirm accepted scope, the authorised customer decides artwork approval, purchasing confirms receiving, production records quality checks, and the field team returns completion evidence.

This ownership is an operating control, not a permission matrix configured on Settings > Job Statuses. SignBas3 does not require a named role or attachment before every transition. Keep the evidence in the relevant artwork version, task, purchasing record, document, photo or Noticeboard entry and review it before moving the job.

When defining a ready-for-production policy, consider the accepted estimate, artwork, tasks, purchasing, schedule, installation evidence, invoicing and final margin. Those records remain separate sources of truth; the status label should summarise the stage rather than claim that every prerequisite was automatically enforced.

Measure whether the status workflow works

1. Count active jobs with vague, missing or stale status and drive that number down.
2. Review how long jobs remain in artwork approval, material wait and other external dependencies.
3. Check whether jobs described as ready are genuinely executable when production opens them.
4. Compare missed required dates with the status, tasks and blocker that preceded them.
5. Find completed work still awaiting invoicing, supplier-cost capture or commercial review.
6. Ask each department whether the current status tells it who acts next.

The purpose is not to reward people for moving labels quickly. The workflow should expose waiting, protect readiness decisions and make the next operational action obvious. Build any ageing or lifecycle report from current canonical job data and validate it before relying on the totals.

Job status questions

How many job statuses should a sign shop use?

Use the smallest set that distinguishes genuinely different next actions. A simple operation may use six or seven; a manufacturer spanning artwork, fabrication, print and installation may need more. Consider removing two statuses when they have the same owner, evidence and exit rule.

Should waiting be one job status?

Usually not. Name the dependency—artwork approval, materials, site information or another input—so the responsible person and next action stay visible. Use a broad On Hold state only when the detailed reason is recorded somewhere the team will actually review.

Should invoiced and paid be production statuses?

Keep operational completion distinct from invoice and payment state. A completed sign job, an issued invoice and a paid invoice answer different management questions. Use the job Financials workspace and accounting records for the commercial result.

Can job statuses support reporting?

Yes, when the team applies them consistently. Status can help group active work, identify waiting jobs and review ageing. It does not replace the underlying task, readiness, financial or evidence records, and the Job Statuses settings page does not itself create those reports.

Explore sign shop job management software →

See production scheduling and workflow visibility →