Campaigns on published policies
A campaign addresses a published policy to a defined audience and tracks every response. Draft, active and closed states keep preparation, collection and the final record separate.
Policy Attestation
Policy attestation campaigns that record who acknowledged, who declined, and why
Address a published policy to a defined audience, collect acknowledgements and reasoned declines, and report coverage by organisational unit, role and individual. Closed campaigns remain as evidence of what was attested, by whom and when.
Attestation campaign lifecycle
DraftAudience and due date prepared, nothing issued yet
ActiveIssued to the audience; acknowledgements and declines collected
Declined with a reasonA first-class outcome that shows where a policy is unworkable
ClosedResults frozen and retained as a governed record
Campaign states in OrviQ. Campaigns are governed records and are never deleted.
Attestation Capabilities
Evidence that people have seen the policies that bind them
Publishing a policy puts it in force. Attestation records that the people it binds have seen it.
Acknowledge or decline, with a reason
Anyone asked to attest can acknowledge or decline. Declining is a first-class outcome: a reasoned decline shows where a clause conflicts with how a team actually works.
Coverage by unit, role and person
See acknowledged, declined and outstanding counts by organisational unit, role and individual. Concentrated non-response usually points to a distribution gap, not a refusal.
How a campaign runs
From published policy to a closed record
A short, repeatable cycle that keeps the audience precise and the response honest.
1. Publish the policy first
Attesting to an unpublished policy attests to nothing, so campaigns start from a published version.
2. Define the audience
Address the people the policy actually binds. A broad audience for a narrow policy trains people to click through.
3. Set a realistic due date
Due dates appear in the GRC Calendar alongside your other governance deadlines.
4. Collect responses
Employees respond from a self-service portal and from their personal Workbench.
5. Read the declines
Reasoned declines are reviewed before the campaign is closed, because they carry the most information.
6. Close and retain
Closing freezes the results. The campaign stays as evidence of what was attested.
Honest by design
Attestation is evidence of awareness, not of compliance
OrviQ keeps what an acknowledgement proves separate from what it does not.
Opened is not acknowledged
The platform records when an employee opens a policy, but opening does not count as acknowledging. The employee must respond explicitly.
Acknowledged is not compliant
A high acknowledgement rate confirms communication. It does not show that controls are operating or that an obligation is met.
Awareness evidence where required
Where an obligation specifically needs evidence of awareness, campaign results can be projected into the evidence record for review.
Connected Mesh
Related capabilities
Demonstration
See a policy attestation campaign in OrviQ
Walk through a campaign from publication to coverage reporting with our product team.