workbook
Client operating baseline workbook
Prepare a compact reviewed baseline that can be entered into the correct Privora Pro client workflow.
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 44 prepared
Client operating baseline workbook
Use these working pages before and during client onboarding. Complete only the fields needed for the engagement, review the answers with the accountable people, then enter approved records in Privora Pro. This workbook is a preparation aid, not a parallel system of record and not evidence that the client is compliant.
Keep the blank template appropriately confidential. Do not record passwords, authentication material, complete identity files, raw special-category datasets, or live incident details here. Use safe references and approved systems for sensitive operational records.
Engagement charter
Define the engagement in operational terms. Name the client boundary, sponsor, delivery owner, intended improvement, and first review. Avoid broad promises. The charter should be short enough to read aloud at kickoff and specific enough to guide the first month.
Add a concise working answer.
Client or business-unit name
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Legal entity, business unit, or operating boundary covered
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Accountable client sponsor
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Privora delivery owner
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Operating improvement expected from onboarding
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
First operating review date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
First workflow definition
Choose one real workflow that will make ownership and evidence visible. Define where it begins, what approved output ends the first cycle, and what is explicitly excluded.
Add a concise working answer.
First workflow name
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Current workflow problem to improve
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.
Entry condition and required inputs
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.
Completion condition and approved output
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.
Excluded or deferred work
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Role and RACI map
Record who prepares, reviews, decides, contributes, and remains informed. If one person holds several roles, keep the responsibilities distinct. Portal participation never creates approval authority.
| Work item | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Scope confirmation | ||||
| Evidence baseline | ||||
| First deliverable |
Add a concise working answer.
Person authorized to approve scope
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Accountable evidence reviewer
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Escalation owner for unresolved decisions
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Access checklist
Prepare access decisions only after confirming the organization, client, person, role, and business need. An authorized Owner or Admin applies Team changes. Portal users must remain within the intended client boundary.
Select the current decision.
Correct Privora organization confirmed
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Correct client boundary confirmed
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Select every check that is complete.
Team access actions
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Select every check that is complete.
Client portal access actions
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Owner for later access removal or review
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Evidence baseline
List what evidence is expected to demonstrate, not only its file name. Use safe descriptions. Enter the approved document, version, review, and requirement links in Privora Pro Documents.
| Evidence purpose | Owner | Period | Current location | Review state | Next action |
|---|---|---|---|---|---|
Capture the working notes, source, and decision context.
Evidence categories needed for the first workflow
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Select every check that is complete.
Baseline states present
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Owner for entering approved evidence records in Pro
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Priority gaps
Prioritize gaps by the decision or deliverable they block. Distinguish absent evidence from evidence awaiting review. Give every priority gap an owner and a next review date.
Capture the working notes, source, and decision context.
Highest-priority gap and blocked outcome
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Accountable owner for the next action
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
Gap review date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Escalation required
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Deadline register
Record operational dates and their source. Where a date depends on legal or regulatory interpretation, obtain qualified review before treating it as authoritative.
| Date | Event or decision | Owner | Source | Reminder or escalation |
|---|---|---|---|---|
Choose the relevant date.
First contributor due date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
First deliverable review date
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Add a concise working answer.
Owner for entering approved dates in Calendar
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
First deliverable
Define the first client-facing output. A generated or drafted item remains subject to review and approval.
Add a concise working answer.
Deliverable 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.
Audience, purpose, and decision supported
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.
Reviewed evidence and decisions required
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Approval route
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Kickoff agenda and decision
Use the agenda to confirm scope, roles, access, evidence, gaps, dates, deliverable, and the next review. Record material decisions explicitly; silence is not approval.
Select every check that is complete.
Kickoff agenda
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Kickoff decision
Select the current decision.
When approved, record the result in the matching Privora Pro workflow
Capture the working notes, source, and decision context.
Conditions, clarification, or deferred decision
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
30-day plan
Plan a realistic first cycle. Adjust the timing when client complexity, evidence quality, urgent work, or professional review requires a different sequence.
| Period | Operating focus | Owner | Expected output | Review point |
|---|---|---|---|---|
| Days 1–7 | Confirm baseline and requests | |||
| Days 8–14 | Review evidence and gaps | |||
| Days 15–21 | Prepare first deliverable | |||
| Days 22–30 | Review and set next cycle |
Capture the working notes, source, and decision context.
Days 1–7 commitments
Capture the working notes, source, and decision context.
When approved, record the result in the matching Privora Pro workflow
Choose the relevant date.
End-of-cycle operating review
Choose the relevant date.
When approved, record the result in the matching Privora Pro workflow
Completion review
Complete the onboarding cycle only when the operating record is usable. Open gaps are acceptable when their authority, owner, next action, and date are visible.
Select every check that is complete.
Completion checks
Select every check that is complete.
When approved, record the result in the matching Privora Pro workflow
Select the current decision.
Baseline completion decision
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 the client record
Open this workflow in Privora Pro and follow the steps in this runbook.
Lessons for the next cycle
Capture only lessons that can improve the next workflow: which request was unclear, where authority was missing, what access was broader than needed, what evidence context was absent, and which review reduced rework.
Capture the working notes, source, and decision context.
Practice to keep
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.
Practice to change in the next cycle
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 the improvement
Add a concise working answer.
When approved, record the result in the matching Privora Pro workflow
Sources and operating-record handoff
The workbook follows the current implemented Privora Pro routes and the canonical Privora Privacy Operations positioning, reviewed 2026-08-12. It makes no statutory deadline claim. Apply current client agreements, internal policy, verified regulatory sources, and qualified professional judgment to the engagement.
Source: Privora Pro workflow source of truth, Implemented workflow architecture and current product routes; reviewed 2026-08-12
Source: Privora brand identity, Privacy Operations category, voice, and claim boundaries; reviewed 2026-08-12
Source: Privora product marketing context, Audience, workflow problems, differentiation, and customer language; reviewed 2026-08-12
After review, enter approved records in Privora Pro across Clients, Team, Portal, Assessments, Calendar, Documents, Deliverables, and Audit History as appropriate. Use safe references rather than duplicating sensitive content. Retain or dispose of the completed workbook according to 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.