Geometry changes propagate
Trim, bleed, orientation or target PPI can make an old preflight, imposition or safe-size result stale. The engine flags the affected tools so the operator knows what to rerun.
CHANGE IMPACT ENGINE
Know what a revision
invalidated.
Capture the job before a revision, then compare the current browser-local signals. The engine maps changed inputs to the calculations, production plans and approvals that should be rerun instead of silently trusting an old green result.
✓ Browser-local✓ Assumptions visible✓ Exportable record
Capture the current job state
The engine records a compact snapshot of the saved Brief, Preflight, Manifest, Costing, Capacity, Imposition and Quote signals. It does not copy image bytes.
NO BASELINE
Capture before the revision.
A baseline lets the engine distinguish a real specification change from a missing signal.
What changed, and what may be stale?
Changed fields0normalized job inputs
Systems affected0downstream checks
Impact stateBASELINEcurrent comparison
A changed quantity can invalidate a correct answer without making the formula wrong.
Commercial changes propagate too
Quantity, material, finishing or provider changes can invalidate cost, capacity and quote assumptions even when the artwork itself did not move by a pixel.
Freshness becomes evidence
The baseline is stored locally with a timestamp. A clean comparison means the normalized supported fields still match; it does not guarantee that an unrecorded external requirement stayed the same.