Job intelligence layer
Run every print job from one local record.
A job is more than a calculator result. Capture what you know, see what is missing, and hand the work to the right Print Prep Lab stage without creating an account.
v26 · Job intelligence
Command center
Create a local job record, snapshot the technical signals already in this browser, and see what is missing before production.
Current browser signalsA job record stores settings, status and notes only. Image bytes are never copied into the job record.
Operational methodA job record turns calculations into a production decision.
A print project can have correct math and still fail because the chosen product, delivery file, proof or provider requirement was never confirmed. The command center exists to keep those decisions visible together.
Use signals as evidence, not as automatic approval
The command center can see browser-local signals created by supported Print Prep Lab tools: a saved brief, specification profiles, Studio plans, a file-manifest summary, the last preflight result and a saved quote comparison. A signal means work exists; it does not mean the work is correct for the current job.
That distinction is deliberate. A previous quote may be for another quantity, a specification profile may be only a starting point, and a manifest may contain the wrong exports. Review the linked stage before marking it complete.
Use the pipeline to expose the next unresolved decision
The six stages are intentionally broad: brief, specifications, files, preflight, quote and sign-off. They represent different failure modes. The brief defines what is being made; specifications define technical acceptance; files identify what will be delivered; preflight checks geometry and confirmations; the quote records commercial assumptions; sign-off is the human decision to release the job.
Not every personal print needs all six stages. The value is in seeing what you skipped rather than silently assuming it happened.
Keep the record portable without creating an account
Job records are stored in local browser storage. They contain names, status, quantities and snapshots of technical signals—not image bytes. Export jobs as JSON when you need a portable record, and use the Workspace Vault when you want a broader backup of supported local workspace data.
Because local storage belongs to one browser profile, clearing site data can remove records that were not exported. Treat important JSON backups like project notes.