Loading the next page…
Program
Pick one program, such as risk, vendor risk, privacy, or policy management. We write how it runs, put a named person on each step, set up the registers, and run the first cycle with your team. At handover your owner has the records from a real cycle to work from.
Engagement brief
Fixed scope
AccountableYour named owner
ResponsibleA Truvara practitioner
Drafts and citesCASK
Phases
We confirm scope and timing after a first call.
When teams call us
Risk, vendors, privacy, and policy each live in a different tool or sheet
An auditor asked who owns a process and nobody could answer
You hired a first compliance lead and they need a program to run
The board wants regular risk reporting and no process sits behind it
What you receive
Drag the divider. On the left, where the work usually starts. On the right, the files you receive.
What you receive
The files from this engagement
Gap assessment
Implementation
Before the engagement
What we usually find on day one
A program chart. The first month still has no owner and no record.
What it works against
CASK maps every requirement to evidence in the workspace, so scoping starts from what already exists and what is missing.
Key areas covered
How it runs
One sequence, from the records you already have to the outcome in your hands.
Agree the program
Works with leadership to choose the function, its scope, and the decisions it has to support.
Write how it runs
Agrees roles with your managers until every step has a named person.
Build the registers
Decides fields, ratings, and review triggers with the program owner.
Run the first cycle
Chairs the first review, follows up with owners, and presents the first report.
Hand over
Trains your owner and confirms who runs the next cycle.
What we need from you
Questions