AVEN
Five steps from current state to sustained operation
Each step has clear outputs, participants and exit conditions, with no shortcut around real operating records.
Working method
From requirement to verification of actual work
A management system helps when people know what to do, owners can see progress and leaders know which decisions are due. We connect applicable requirements → controls → evidence → verification in one flow, with an accountable person at each point.
The five stages below describe an indicative delivery method. Scope, approvers and dates are agreed with the organisation before work begins; the same obligations are not imposed across every industry.
Work path
Four links, one decision history
- RequirementCorrect edition, source and applicability decision.
- ControlOwner, decision point and exception path.
- EvidenceVersioned records from actual work.
- VerificationAuthorised reviewer checks the outcome and records why.
If a link is missing, that point remains open. An authorised person resolves the gap before moving on.
01
1. Agree scope and current state
The project lead and process owners first identify sites, products or services, included work and supplier handoffs. We interview by role, inspect existing records and trace one real task from input to output. Unverified answers remain open rather than being marked complete.
Outputs are a scope map, source register, current-state table and questions for specialist or leadership decisions. The organisation confirms boundaries before design starts. Missing records are shown as missing; minutes of events that never occurred are never reconstructed.
- Participants: sponsoring leader, project coordinator, process owners and record custodians.
- Move on once scope, sources and open questions have owners.
02
2. Design usable controls
Each applicable requirement becomes a management question: who decides, what work needs control, what demonstrates execution and who verifies it. The team then designs process maps, roles, acceptance criteria and forms. Specialist content enters a procedure only after qualified review and organisational approval.
A draft can suggest wording but cannot become a policy or compliance conclusion on its own. Accountable people inspect sources, correct it to match real work and approve versions before issue. Outputs include a versioned document register, requirement-to-control map and minimum useful record forms.
- Participants: process owners, form users, relevant specialists and approvers.
- Move on when users understand the work and the pilot version is approved.
03
3. Pilot on real work
Choose an observable flow, such as customer request to handover or a deviation from discovery to action. The organisation performs its own work; the consulting team guides and records friction. Documents are revised after examining causes, never to hide an exception.
Outputs are records from actual operations, exception lists, training questions and revised versions. If a control cannot produce suitable evidence, we revisit the design with its owner. Pilot length follows the real work rhythm, especially for monthly or seasonal activities.
- Participants: practitioners, line managers, process owners and project coordinator.
- Move on when real samples exist and exceptions have accountable owners.
04
4. Independently check and decide
An internal auditor samples against the agreed scope and sources, without auditing work they designed or performed. Findings are separated from assumptions; each action has an owner, due date and effectiveness method. The action owner does not verify their own effectiveness.
Leaders review results, open risks, resources and improvement opportunities in an actual meeting. Minutes record decisions made, never invent decisions for leadership. Consulting results describe readiness only within the examined scope; an independent certification body makes its own decision.
- Outputs: audit plan and records, action register, management-review minutes and evidence sources.
- Move on when accountable people can see closed and open work clearly.
05
5. Sustain through management cadence
After handover, process owners keep records as part of normal work. The system tracks due dates and document history and shows requirements lacking evidence. A one-page report uses sourced counts: due tasks, overdue tasks, missing evidence and actions awaiting verification. There is no aggregate “ISO compliance percentage”.
Open actions may be reviewed weekly and trends monthly; frequency follows the organisation’s risks and capacity. When scope or a standard edition changes, the team assesses impact before revising documents. The organisation retains decisions, data and operating responsibility.
- Data is scoped by organisation and project, with server-side role checks.
- Most work can be remote; on-site observation is proposed when evidence requires it.
Next step
Start with a scope that can be checked
Self-check first, or send an outline of your scope so we can agree outputs, sessions and specialist needs. Do not send sensitive records through the public form.
We provide consulting and training; certification decisions are made independently by certification bodies.