AVEN
System implementation
Move from current work and applicable requirements to processes, owners, operating records and effectiveness checks.
Service scope
Understand the work before writing documents
A new system does not start by copying a template pack. First clarify what customers require, which processes create the output, which deviations matter and who can decide. We build an operable slice first: a narrow scope, named process owners and initial records created by real work.
01
Signals to start
These are illustrative scenarios for discovery, not actual clients or completed outcomes.
Illustrative scenario
Manufacturing
A later shift changes settings without a reason in the handover; final inspection finds defects with no trace to their origin. A process map, acceptance criteria and change history are needed.
Illustrative scenario
Multi-site services
Each site handles complaints by personal habit; managers see the issue only after a second reminder. An intake, escalation and closure-evidence flow is needed.
Illustrative scenario
Food
Hygiene forms exist but product- and process-specific hazards are unclear. Hazard analysis, PRP/HACCP and technical limits need food-safety specialist validation.
Illustrative scenario
Software and IT
Changes ship quickly but customer requests, approvals and tests are disconnected. Change control, access and release handover records are needed.
Illustrative scenario
Construction
Subcontractors hand off work by message, site documents lack versions and receivers lack acceptance criteria. Handoffs, ownership and approved check forms are needed.
02
Phased work with explicit exit conditions
Discovery & GAP
Interview leadership and operators; sample inputs, outputs and records from a recent cycle. Separate observed facts, reported claims and unverified points.
Deliverable: Scope, current-state map, sourced requirement list and GAP report.
Move on when: Both sides confirm scope and priorities.
Control design
Choose one requirement-to-evidence flow. Design processes, owners, acceptance criteria, risks and opportunities, and usable forms.
Deliverable: Process map, fit-for-purpose policy/manual, versioned procedures and forms.
Move on when: Process owners and leadership approve before issue.
Pilot & refine
Run real work, train by role, log exceptions and revise documents against facts. Do not generate records to fill gaps.
Deliverable: Training plan, sample operating records, action/CAPA register and revised versions.
Move on when: At least one real record cycle exists in the pilot scope.
Verify & hand over
Use independent internal audit, follow actions to effectiveness checks and have leadership review results and resources.
Deliverable: Audit plan/records, management-review minutes and a readiness evidence pack for internal checking.
Move on when: Authorized owners accept completed work and open items.
03
Deliverables that can be checked
The exact pack follows the agreed scope; records need sources and drafts are clearly marked for approval.
- Process map and handoffs showing inputs, outputs, owners and where records arise.
- Fit-for-scope policy/manual and document register, each with approver, effective date and version history.
- Procedures and forms for work that needs control; undecided fields stay marked for approval rather than filled with guesses.
- Sourced risk–opportunity matrix with owners and actions, without one aggregate risk score.
- Role-based training plan, approved materials and actual attendance records; knowledge checks never automatically become competence conclusions.
- Internal-audit programme, plan and records; auditors do not audit work they designed or performed.
- Management-review minutes record inputs, decisions, resources and follow-up owners; the meeting must actually occur.
- Action/CAPA register separates implementer from effectiveness verifier, retaining change history and post-action evidence.
- Readiness evidence pack by applicable requirement, with source, version and gaps; it does not replace a certification body’s conclusion.
04
Who does what, and how long?
AVEN
We design discovery, facilitate working sessions, map requirements and processes, configure the workflow, prepare versioned templates, train by role and return findings to decision owners. Food, environmental and occupational-safety content requires qualified specialist validation; we do not invent limits or duties.
Your organization
Your organization confirms scope, supplies authorized records, names process owners and approvers, operates controls and records what happened. Leadership decides resources, objectives and changes; internal auditors remain independent from the work they audit.
For 10–50 people, one site and one pilot flow: an illustrative 6–12 sessions over 2–4 months. For 50–200 people or multiple sites: often 12–24 sessions over 4–8 months. These are planning ranges; actual timing depends on shifts, available records and specialist needs.
A session may be an interview, design workshop, document review, training or sample check. Timing is illustrative, not a certification schedule; a formal plan follows discovery.
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.
06
Completion conditions and boundaries
Handover is complete when scope, owners and current versions are confirmed; forms contain records from actual work; deviations have actions and verifiers; leadership can see open items. “Readiness” is an internal, source-based check, not a certification promise.
Not included
- Certification-body fees, certification audits and certification decisions are outside the service; the client selects an independent body.
- We do not create measurements, minutes, training records or audit outcomes for events that have not occurred. Specialist legal, safety, food or environmental work needs qualified people and a separate scope.
- Software, equipment, testing or on-site surveys outside the agreed proposal are excluded. Any addition is described by output, owner and cost before work begins.
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.