AVEN
Services shaped around the work to be solved
Choose a starting point that fits your current situation—not the same document set for every organisation.
From current state to operating rhythm
Choose the work that needs solving
A document pack does not become a working system by itself. We start with scope, decision owners and samples of actual work; then choose foundation implementation, recurring control or standards expansion. Each service records work, outputs, participants, indicative timing and exclusions.
01
Three starting points, one traceable method
System implementation
Move from current work and applicable requirements to processes, owners, operating records and effectiveness checks.
View scope and deliverablesMaintenance & control
Keep the system working after handover: due work, evidence, audits, actions and leadership decisions.
View scope and deliverablesStandards expansion
Reuse an existing management foundation, add specialist controls and manage edition changes through a sourced change map.
View scope and deliverablesConsulting and platform access have separate scopes; your team may operate independently. Services are never tied to a certification decision.
02
When should we talk?
Illustrative sector scenarios, not client claims or completed outcomes.
Illustrative scenario
Manufacturing
Shift handovers, machine instructions and inspection records diverge, so defects recur. Build a foundation to locate handoffs and criteria; maintain a rhythm to address causes rather than only products.
Illustrative scenario
Multi-site services
Each site handles customers differently and handover details get lost. Start with a workflow and ownership, then a concise report that surfaces exceptions before a customer must remind the team.
Illustrative scenario
Food
Hygiene records exist but hazards, traceability and recall have not been tested together. A food-safety specialist must validate PRP/HACCP and scheme requirements before controls are agreed.
Illustrative scenario
Software and IT
Customers ask for security evidence alongside service quality. Reuse document control, audit and review; add information scope, risks, access and response records.
Illustrative scenario
Construction
Site crews and contractors change frequently; inspection forms lack versions or owners. Handoffs need control and a safety specialist must validate technical content at the site.
03
How both sides work together
AVEN
Prepare discovery questions, map requirements, facilitate process workshops, manage drafts and expose missing sources. Qualified specialists review sector content; independent auditors inspect work they did not design.
Your organization
Confirm scope, appoint process owners, supply authorized records, run the work and decide on objectives or resources. Records after each session reflect what actually happened; managers approve before issue.
Indicative timing: 10–50 people at one site usually start with 1–2 discovery sessions and one pilot flow; 50–200 people or multiple sites need sampling by workstream, often 2–4 discovery sessions. Implementation sessions and schedule are agreed after seeing the current state.
Platform in the service
One flow from scope to verification
Each step retains the decision, source and owner so a later review does not have to reconstruct the story.
- ScopeConfirm sites, activities, outputs and interfaces; unknowns remain explicitly open.
- Applicable requirementsSeparate standard, legal and contract requirements; each has a source and an approving owner.
- Current stateSample records from work that actually happened; a blank form is never counted as evidence.
- ActionAssign gap-closing work with owner and due date approved by the client.
- EvidenceLink permission-checked, scanned and versioned files or records to the right requirement.
- VerificationAn authorized person checks source and effectiveness and makes the decision; history is retained.
The client portal keeps tasks, document versions and evidence in the right project; server-side permissions apply before viewing, searching or exporting.
Reminders use dates approved by task owners. The one-page report uses the same data source as the screen: due work, open actions and missing evidence are shown as counts, never as one aggregate compliance percentage.
Teams can work remotely on interviews, draft reviews, assignments and authorized records. Work requiring on-site observation is scheduled separately after scope is agreed.
05
Outputs follow work, not page count
Depending on scope, the pack can include process maps and handoffs, policy/manual, versioned procedures and forms, risk–opportunity matrix, training plan, internal-audit programme, management-review minutes, action/CAPA register and a readiness pack for internal checking. Each item has a source, owner and status; work that has not happened is not marked complete.
Technical limits, sector criteria and obligations are not filled from a generic template. After discovery, the proposal states remote work, on-site observation, illustrative sessions and exclusions. Certification-body fees, audits and decisions belong to an independent certification body.
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.