workbook
Evidence request and review cycle workbook
Prepare one Request to Report cycle with explicit acceptance criteria, safe context, accountable review, and a recorded decision.
Non-persisted working reference
Use this workbook to prepare notes, evidence references, owners, decisions, and follow-up. Entries are temporary in this browser. Nothing entered on this page is saved. It is not submitted; enter the approved record in Privora Pro when the review is complete.
Browser-local worksheet
Prepare working answers
Entries are temporary in this browser. They are not submitted or saved. Enter approved records in Privora Pro.
0 of 46 prepared
Evidence request and review cycle workbook
Use this workbook to prepare and review the operating sequence Request → Owner → Evidence → Review → Decision → Report. It does not persist responses and does not approve evidence. After accountable review, enter approved records in Privora Pro so the task, document version, review outcome, decision, and reporting link remain connected.
Keep the working copy appropriately confidential. Do not record passwords, authentication material, full identity documents, raw special-category data, live incident payloads, or unrelated client information. Use safe references and authorized systems for sensitive records.
Request brief
Write one coherent request. A contributor should understand why the evidence is needed, what period and client scope apply, what to submit, and how to ask for clarification.
Add a concise working answer.
Action-led request title
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Decision, requirement, or report this evidence will support
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Client, entity, process, and period in scope
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
Contributor due date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Request priority
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Sensitive content to exclude or minimize
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Evidence acceptance criteria
Define acceptance before sending the request. Separate required criteria from preferred presentation. State what the evidence must demonstrate and who may approve the outcome.
Capture the working notes, source, and decision context.
What the evidence must demonstrate
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Required source, owner, or approval context
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Required period and currency threshold
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Select every check that is complete.
Required context
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Select every check that is complete.
Allowed review outcomes
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Owner map
Keep request ownership, evidence ownership, contribution, review, and final decision authority distinct. Technical permission does not expand the agreed authority model.
| Role | Named person | Responsibility | Escalation path |
|---|---|---|---|
| Request owner | |||
| Evidence owner | |||
| Client contributor | |||
| Evidence reviewer | |||
| DPO or privacy lead | |||
| Report owner |
Add a concise working answer.
Accountable request owner
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Accountable evidence owner
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Authorized evidence reviewer
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Authority for reserved or escalated decisions
When approved, record the result in the matching Privora Pro workflow
Submission context
Capture safe context, not the sensitive record itself. Use Privora Pro task and document records for the approved submission and version history.
Add a concise working answer.
Evidence source or originating system
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Period covered
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Version or approval date
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Contributor statement of what the evidence demonstrates
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Known gaps, limitations, or changes since approval
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Safe submission method
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Reviewer sheet
Apply accountable human review against the predefined purpose and criteria. A linked requirement, upload, task completion, prior review, or automated summary can inform the reviewer but cannot make the current decision.
Select the current decision.
Relevant to the stated criterion and client scope
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Source and approval authority are sufficient
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Period and currency are sufficient
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Required components and context are complete
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Consistent with other known approved records
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Reviewer rationale and material limitation
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
Review date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Decision record
Record the decision for the stated purpose. Approval is not universal; return or rejection should identify an actionable correction.
Select the current decision.
Evidence decision
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Purpose, period, and limitation attached to the decision
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Named accountable reviewer
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
Next review or expiry date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Returned-work log
Use a new row for each return. Preserve the original version and explain the smallest sufficient correction.
| Return date | Criterion not met | Requested correction | Owner | New due date | New version |
|---|---|---|---|---|---|
Capture the working notes, source, and decision context.
Specific reason for return or rejection
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Owner for clarification or new version
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
Returned-work due date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Exception log
An exception requires named authority, rationale, consequence, interim control, and review date. A portal contributor cannot approve an exception.
| Exception | Authority | Rationale | Residual uncertainty | Interim action | Review date |
|---|---|---|---|---|---|
Select the current decision.
Exception path required
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Named exception authority
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Rationale, consequence, and interim control
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
Exception review date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Reporting link
Connect the reviewed result to the requirement, assessment, deliverable, or management report. Preserve limitations and unresolved gaps in the summary.
Add a concise working answer.
Requirement, workflow, or deliverable receiving the result
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Careful reporting statement based on reviewed evidence
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Limitations, assumptions, and open actions to carry forward
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Report or deliverable owner
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Cycle-close checklist
Close only when the full chain is traceable. Upload and task completion are inputs to review, not approval outcomes.
Select every check that is complete.
Cycle-close controls
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Cycle status
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Person who will enter approved records in Privora Pro
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Open client evidence tasks
Open this workflow in Privora Pro and follow the steps in this runbook.
Sources and operating-record handoff
This workbook follows current implemented Privora Pro portal-task, document-review, deliverable, audit, and client-scope behavior reviewed 2026-08-12. It uses the canonical Privora Privacy Operations category and claim boundaries. It asserts no universal retention period or statutory evidence format.
Source: Privora Pro workflow source of truth, Implemented portal-task, document-review, deliverable, audit, and client-scope behavior; reviewed 2026-08-12
Source: Privora brand identity, Privacy Operations category, evidence and ownership language, and claim boundaries; reviewed 2026-08-12
Source: Privora product marketing context, Audience needs, evidence pain points, operational differentiation, and customer language; reviewed 2026-08-12
After accountable review, enter approved records in Privora Pro. Keep the task brief and assignment in Portal Tasks, the authorized evidence and version in Documents, the decision in the review record, and the reporting relationship in the appropriate workflow or Deliverable. Retain or dispose of the working copy under the organization's approved records practice.
Download this operating resource
Download the workbook
Use PDF for review and print. Use the editable DOCX when the team needs a working copy.