The necessary ones make the site work. The others measure which pages help and which ads bring the people who need DM11. Your choice, and you can revisit it from the footer.
Proposal
We define the scope, design the controls, build the evidence routine and write the system description. By the time the auditor starts fieldwork, nothing is improvised. We prepare both Type I, which photographs the design on a given date, and Type II, which proves the controls worked across a period.
No price appears on this page. Scope does: what we do, how we run it, who runs it and what is not included. The people who read your request are the ones who will look after you, and they come back with the proposal and with time to talk it through.
Preparation for the report your customer demands.
We define the scope, design the controls, build the evidence routine and write the system description. By the time the auditor starts fieldwork, nothing is improvised. We prepare both Type I, which photographs the design on a given date, and Type II, which proves the controls worked across a period.
Scope definition
We agree in writing what is in and what is out, and why. A badly defined scope is the most common cause of a project running over.
Gap assessment
We compare what exists today with what the standard requires and order it by risk and effort.
Implementation
We stand the controls up, write what has to exist on paper and train the people who operate them.
Evidence routine
We set out how each control proves it worked, with an owner and a frequency, so the audit does not turn into a scramble.
Audit support
A rehearsal before, our presence during and a corrective action plan afterwards.
Usually comes together with
Not a bundle, and it changes nothing you have already chosen. It is what tends to come up next, in the experience of companies that have been through this.