Reviewing a proof is more than just glancing at a document and deciding whether to approve or reject it. It is a process of communicating opinions, improving quality by catching mistakes early, of providing direction for future versions, and ultimately of deciding whether to approve, reject, or send a document back for revisions and changes.

After years of feedback and research into customer review processes, we've discovered that the following general guidelines can help ensure quality and that all stakeholders and participants get the most out of their collaborative reviewing process:

• Use comments and annotations to communicate with other document stakeholders.
• Review previous versions, if they exist and if you are not already familiar with them. It only takes a moment, but it can help save time for everyone and avoids situations where the advice, feedback, and direction you provide contradicts or conflicts with that given on earlier versions.
• Read the Manager's Comment, if there is one. This may contain important information related to the proof and what the consequences of approval, rejection, etc. are.
• Provide clear direction for any requested changes.
• Provide clear explanations and reasons for rejecting or approving a a proof.

Procedures

Reviewing a Proof with Spark!

Related Topics

• The Spark! Reviewer's Handbook
• Using Common Spark! Proofing Tools
• Spark! Setup and Configuration