Download the editable template

Use this handoff after collection and before final response approval. The template structures a review; the authorized reviewer remains responsible for the decision.

Download the reviewer handoff template

Ungated Markdown file. No account or email address required.

How to use it

  1. Link to the controlled case record and approved evidence locations rather than attaching sensitive files to the template.
  2. Summarize the request, verification outcome, searches performed and known limitations.
  3. State each decision needed and identify the proposed response materials.
  4. Record the reviewer's decision, conditions and follow-up owner in the case record.

Open the Markdown file in a text editor, or copy the readable template below into your approved document tool. Use your browser’s Print command to make a paper or PDF working copy. No Markdown software is needed to read or print this page.

Remove fictional examples before use. Keep the working copy in an access-controlled location approved by your organization.

Read or print the complete template

This preview is built from the same file as the download. Use your browser’s Print command for a portable copy.

Free editable template from Privacy Requests. Use controlled links for sensitive records. This handoff supports human review; it does not make or certify a legal decision.

Blank working copy

Decision requested

  • Case ID: __________
  • Reviewer: __________
  • Decision needed by: __________
  • Exact question(s) for the reviewer: __________

Request and handling summary

  • Original request reference: __________
  • Request type and scope as reviewed: __________
  • Identity or authority outcome and record reference: __________
  • Applicable requirements considered by the authorized team: __________
  • Reviewed target date and rationale: __________

Collection summary

Collection summary
System or sourceWork completedResult summaryLimitation or follow-upEvidence reference
__________________________________________________

Proposed response

  • Draft response reference: __________
  • Exact files proposed for delivery: __________
  • Redactions or exclusions requiring review: __________
  • Third-party information question: __________
  • Delivery method and controls: __________

Open risks and alternatives

  • Known limitation: __________
  • Unresolved question: __________
  • Proposed next step if approval is withheld: __________

Decision record

  • ☐ Approved as proposed
  • ☐ Approved with conditions listed below
  • ☐ Changes required
  • ☐ Escalation or further advice required
  • Conditions, changes or rationale: __________
  • Reviewer and recorded decision time: __________
  • Follow-up owner: __________

Clearly labelled synthetic sample

This fictional example demonstrates the handoff structure. It is not a customer case, measured result, legal assurance or recommended decision.

  • Case: DEMO-1042
  • Reviewer: Avery Chen (fictional reviewer)
  • Decision requested: Review the proposed response after the archived support-attachment search is complete.
  • Collection summary: Fictional account database and support platform searched; archived attachments remain an open task.
  • Proposed response: Draft message and three fictional export files in SYNTHETIC-PACKET-02.
  • Current outcome: Changes required — complete and document the archive search before final approval.

What it includes

Sections and their purpose
SectionHow to use it
Decision requestedTell the reviewer exactly what needs approval or direction.
Request and verification summaryProvide context without repeating unnecessary personal data.
Search results and limitationsExplain the evidence base and unresolved gaps.
Proposed response and decision recordDefine what would be sent and preserve the resulting review.

About the synthetic sample

The populated example uses fictional people, organizations, identifiers and systems. It demonstrates the fields only. It is not a customer case, measured result, legal assurance or recommended decision for a real request.

Delete the sample before using the template. Do not put passwords, identity documents, response files or unnecessary personal data in it.