The workflow
From sliced file
to finished print.
A print job is submitted, checked against your rules, queued, dispatched, and tracked through its final outcome. This is what that looks like for a typical job.
A job is submitted
The requester uploads a sliced print file. Pluraprint parses it and shows the printer model, estimated duration, and material use found in the file. Deployment-specific project fields can collect the additional context your team needs.
Who does this
Requester
Where it happens
Web app or station
What's needed
A supported sliced print file
What happens next
Requirements are evaluated
The job's requirements are checked
Requirements come from the rules that match the job. They can ask for approval from a particular role, enforce a quota, or hold work until a required value is known. The job page shows what's done and what still blocks the queue.
Who does this
A permitted reviewer
What decides
Rules and quotas
Available actions
Prepare, approve, or reject
Audit trail
Every decision logged
Job enters the queue and prints
Once the checklist is complete, the job joins the queue. Its printer model and material requirements limit where it can run, and operators can adjust priority or hold a printer when the floor changes. Requesters can follow their own job status without asking for an update.
Queue type
Rule-based priority
Printer routing
Eligible printer selection
Requester visibility
Current job status
Admin control
Prioritize, hold, or mark down
The result stays with the job
A job can finish, fail, be cancelled, or be reprinted. Each event is added to the same history. If pickup is enabled, the record continues through bin placement and collection. Data retention is controlled by the deployment administrator.
Requester notified
Configured by job state
Data saved
Job history and outcome
Pickup
Optional bin and scan workflow
If it fails
Reprint from the existing job
For everyone in the process
Each person gets the view they need.
Requesters
- →Upload jobs from the web or a station
- →Track the status of their own work
- →Get notified when prints are ready
- →Start a reprint from the existing job
- →See full history of all their submissions
Operators
- →Review and approve jobs from one dashboard
- →See all printers and their current status
- →Manage the queue without interruptions
- →Record failures and notify requesters
- →Manage pickup bins and collection when enabled
Administrators
- →See usage across all teams and projects
- →Review material, quality, and failure data
- →Use reports for budget and capacity planning
- →Identify underused or overloaded printers
- →Justify the operation with real data
Go deeper on each stage
- The print queue, in detailStage three: shared backlog, priority, printer eligibility, dispatch, and failure handling.
- Approval workflow, definedStage two: why approval is a cost gate, and how it avoids becoming a bottleneck.
- Job intake, definedStage one: what structured intake collects, and what unstructured intake costs.
See it for your operation.
Tell us how work gets submitted, reviewed, printed, and collected today. We'll use that process for the walkthrough.
Request a walkthroughhello@pluraprint.com