Oprivia governance: roles, approvals, and audit trail
Role-based access, segregation of duties, escalations, and a continuous audit trail make decisions traceable in daily operations.

Six guardrails before work begins
Governance defines in advance who may act, which steps are automated or reviewed, when an exception escalates and how the resulting history remains traceable.
Ownership and access
Roles, permissions and visibility are limited to the assigned area of responsibility.
Status, deadlines, and response
Open items, time windows and overdue steps make required action visible early.
Checklists and evidence
Checklists, feedback, documents and photos remain linked to the relevant case.
Escalation and decision
Unresolved matters are routed to the responsible function through defined paths.
Continuous audit trail
Updates extend the record without overwriting earlier processing states.
Service boundaries
The platform supports control and documentation, but does not replace legal or regulatory assessment.
Segregation of duties in operations
Governance distinguishes operational execution, factual review and binding approval.
That separation makes clear who provides data, who handles assigned work, who assesses exceptions and who records decisions.
Data capture
Required information is entered by the designated person or role. Control fields remain separate from guest-facing input.
Execution
Assigned work is carried out, updated and supplemented with feedback or records.
Review
Incomplete details, deviations and critical items are assessed by the responsible function before closure.
Approval
Rules, access, escalations and decisions are confirmed by authorized people.
Exceptions follow a governed route
An open item is not merely captured. It receives a reference point, an accountable function, a review logic and a documented outcome.
Classification
Classification
Classify the issue
A request, task or deviation is assigned to the relevant stay, property or assignment.
.avif)
Accountability
Accountability
Assign accountability
An accountable person, processing status and, where required, a time window determine the next step.
.avif)
Evidence
Evidence
Document the handling
Checklists, feedback, documents and photos are linked directly to the relevant case.
.avif)
Escalation
Escalation
Route the exception
Missing details, overdue steps or unresolved matters are handed over to the designated function.
.avif)
Approval
Decision
Record the decision
The decision, rationale and responsible person are documented. The preceding history remains preserved.
.avif)
Changes extend the audit trail
Processing status, checklists, photos, documents and approvals remain linked to the relevant case over time.
New information extends the record instead of hiding earlier states. Critical decisions are made by accountable people, not by the system.
- Time and responsible person remain visible.
- Records and decisions remain preserved in the case history.
- Corrections are added, not hidden retrospectively.
.avif)
Rules before activation
Oprivia supports access control, process governance, documentation and auditability. It does not replace legal, tax, data-protection, regulatory or other case-specific professional advice.
Operating scope and accountability
Properties, modules, roles and responsibilities are limited to the agreed use case.
Data access and instructions
Processing purposes, data categories, permissions, retention and deletion are defined according to the specific setup.
Checklists and response times
Documentation requirements, processing paths and escalation levels are defined before operational use begins.
Configuration and changes
Roles, permissions and control rules are reviewed before activation. Later adjustments remain traceable.
Control strengthens accountability; it does not replace it
Personal data is processed for the relevant operational purpose. Visibility depends on roles, tasks and agreed access rights.
Oprivia supports process control and documentation, but does not replace legal, data protection or regulatory assessment.
Process only required data
Only data required for the relevant purpose is processed. Access depends on role and task. Retention and deletion follow the agreed or legally required rules.
No transfer of legal responsibility
Oprivia does not provide legal, data protection or compliance advice, regulatory certification or expert case-by-case assessment.
Test governance on your own operating case
In the pilot, roles, access, checkpoints, time windows and escalation paths are configured for one defined use case and assessed under real operating conditions.