AVEN
Know what to do. Know where work stands. Do the work. Show the result.
Consulting and a platform connect requirements, work, evidence and decisions in one accountable flow.
A usable operating system
From questions to checkable records
An organisation needs more than another folder of dormant documents. It needs a way to connect applicable requirements to people, work, resulting records and review decisions. We combine role-based consulting with a platform that retains sources, versions and history within the agreed scope.
Start with one small enough flow to test, keep unknowns visible and expand when evidence exists. Final judgments belong to authorised people; independent certification bodies make certification decisions.
01
Five questions you should be able to answer
First: which scope and requirements truly apply to this product, site and way of working? Second: who owns each process and handoff? Third: how does work actually happen, and where does it differ from the document? Fourth: which versioned records show an activity occurred? Fifth: who reviews outcomes, decides actions and verifies effectiveness?
If an answer lacks a source, the system shows it as missing and assigns clarification. We do not turn a blank cell green. Reporting uses counts traceable to records and dates, rather than one general “compliance” percentage that hides unknowns.
- Requirement → control → evidence → verification underpins every service.
02
Three ways to begin
Implementation suits teams without a stable flow or whose documents diverge from practice. We discover, design only what is needed, test on real work, revise and hand over ownership. Outputs include processes, versioned forms, an adoption plan and records from actual activity.
Maintenance and control fit an operating system whose deadlines, deviations and document versions have become scattered. The team reviews open work, checks evidence sources, follows actions to verification and makes upcoming decisions visible. Standards expansion maps reusable work, needed changes and specialist questions for added scope or edition transitions.
System implementation
Move from current work and applicable requirements to processes, owners, operating records and effectiveness checks.
View detailsMaintenance & control
Keep the system working after handover: due work, evidence, audits, actions and leadership decisions.
View detailsStandards expansion
Reuse an existing management foundation, add specialist controls and manage edition changes through a sourced change map.
View details- Each service records completion conditions and exclusions before engagement.
03
Work with the people who own the work
We do not create operating records on a team’s behalf. Process owners describe reality, pilot controls, approve usable versions and retain responsibility after handover. Consultants question, structure sources, reveal gaps and support accountable decisions. Specialist safety, food and environmental work needs suitably qualified validation.
The project portal supports remote, permission-scoped collaboration, separates drafts from approved versions, tracks due dates and retains history. A sourced suggestion becomes a change only after its owner accepts it. Organisation and project data is server-authorised; the public form receives initial enquiries only.
04
A system distinguished by traceability
The checkable difference is that each action leads back to its requirement, source and decision owner. A later colleague can read the history instead of reconstructing who approved what. The system tracks due work, versions and counts; the team still performs the work and accountable people still decide.
There are clear limits: an unsourced suggestion is not verified; a blank form is not an operating record; another organization’s data does not enter search results. The Operational capabilities page traces one flow from scope to verification.
Sources beside conclusions
Each requirement and suggestion retains its source, edition, scope and reviewer. Missing grounds remain visible.
View detailsDecisions by the right people
Owner, approver and verifier have distinct roles; the server checks access to each record.
View detailsOne page for open work
See sourced counts of due work, missing evidence and actions awaiting verification, without an aggregate compliance score.
View details05
Prepare for the ISO 9001:2026 transition
ISO 9001:2026 was published on 16 September 2026. Organisations using the 2015 edition should identify their scope, source edition and operating controls before mapping changes. Under the confirmed transition dates, new certifications use the 2026 edition from 31 March 2028, and 2015 certificates cease to be valid after 30 September 2029. The Standards page carries source links and the update date.
Map sourced changes to current controls, assign owners, issue approved document versions and let records arise from work after their effective date. Cleaning version history, checking actual records, independent internal audit and management review all take time. Retitling a document cannot replace an operating cycle.
- Edition dates, official sources and current status are on the Standards page.
06
Begin with one checkable task
Use self-check to see the questions to answer, or request discovery with activity, sites, size and main difficulty. Do not upload sensitive records to a public form. After discussion, both sides agree a pilot scope, participants, available sources, outputs, sessions and responsibility boundaries.
If the main need is understanding the current state, a focused review may be enough. If gaps are already clear, implementation may fit. If the system operates, maintenance may be more useful. The service choice follows evidence of current work, not a certification promise.
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.