Photo documentation for restoration — without losing evidence between stages.

• Stage-tagged — every photo carries the workflow stage it was captured in.
• Operator + timestamp — automatic, server-side, not editable.
• Item-anchored — the photo lives on the item, not on a phone or shared drive.
• Coverage-aware — managers can see which items are missing required photos.
• Exportable — bundled into the per-item proof package automatically.

Photos taken via the ItemStage mobile app, never via the personal camera roll.

Item + stage + operator + timestamp attached automatically.

Configure required photo counts per stage.

Items can't advance past stage without required photos.

• Operators take photos but never upload them back to the item.
• Stage handoffs happen verbally — the next operator has no photo context.
• QC is forced to re-photograph what intake already captured.
• The proof package is manually assembled the day before an audit.

A useful baseline for restoration item processing:

• Intake: 4-6 condition photos (front, back, sides), serial plate, any pre-existing damage.
• Process: work-in-progress photos for any major action taken.
• QC: after-photos matched to before-photos, any callouts.
• Disposition: final state, packaging, location.

It is the practice of capturing condition photos for each item at defined stages — typically intake, processing, QC, and final disposition — and keeping those photos attached to the specific item, stage, and operator who captured them.

Enough to defensibly show the item's condition at each stage. For high-value or contested items, that often means multiple angles per stage. ItemStage doesn't impose a cap — required-photo rules per stage are configurable.

Because they live in the operator's camera roll, not attached to the item record. The fix is to capture inside the workflow tool itself, so the photo lives on the item from the moment it's taken.

A 30-minute ItemStage workflow demo, configured to your stages.