When a proof includes multiple design options or files, customers should be able to review each one on its own and choose exactly what they want to approve. This idea would make approvals more flexible and much clearer, so signing off on one option doesn’t automatically approve everything else in the proof.

Why this would help

• Approve the exact design you want — If a printer sends several proof variants, such as different colours or layout options, customers could approve their preferred version without affecting the others.

• Reject or leave other options pending — Instead of all files being marked the same way, each option could have its own status, so unselected versions can stay pending or be explicitly rejected.

• Review files individually — When a proof contains multiple files, customers could sign off on some while requesting changes to others, rather than having to approve or reject the entire set at once.

• Clear approve/reject controls for each file — Each file or design option would show its own Approve and Reject buttons, making the decision process much more straightforward.

• Reduce confusion and mistakes — This would help prevent accidental blanket approvals, mix-ups, and incorrect job submissions caused by treating every file in a proof as a single approval.

• Make multiple files easier to understand — Some customers may not realise a proof includes more than one file, so clearer file-by-file reviewing would make it more obvious what’s included and what they’re approving.

• Optional when needed — File-level approval could be available as an option when creating a proof, so it can be used for jobs that need more granular customer feedback while keeping simpler proofs simple.

This would give customers more confidence during proofing, especially when comparing design choices or reviewing several files in one proof.