AVEN
Operational capabilities
Suggestions carry sources and respect access scope; authorized people review, decide and record changes.
System capabilities
See the source, owner and outcome
When requirements, documents, tasks and evidence live in different places, managers must reconstruct the story before every decision. The system connects those pieces within the right organization, client and project. Suggestions help teams see options; an authorized person checks sources, accepts or rejects and remains accountable for the decision.
01
Five questions for managing work
Which requirement applies?
Each line needs a source, scope and applicability decision. An unconfirmed specialist point remains marked for review rather than silently becoming an obligation.
Who owns the work?
Owner, approver and verifier are explicit. Server-side access checks apply, so hiding a button cannot substitute for permission control.
What actually happened?
Records and files carry dates, sources, versions and history. A blank form or verbal account is not presented as operating evidence.
What is due soon?
Due dates are agreed by owners; reminders take the right person to the record that needs action. Exceptions stay visible after the deadline until role-correct review and closure.
What can be reported?
Counts come from source records: due work, open actions, missing records and verified items. Missing data remains missing; it is never folded into one overall compliance percentage.
02
A system distinguished by what can be checked
The useful test is not how many buttons a system has. Open a task and check three things: which source led to it, who may decide, and which record demonstrates the outcome. If any part is missing, the status should say so.
Trace the source
Requirement, edition, scope and applicability decision sit with the action. Unverified points stay visible.
Separate decisions
Doer, approver and verifier have different rights; opening a link does not bypass server checks.
Count from source records
Reports show due work, missing records and pending verification from the same source counts, without an overall compliance score.
03
A path that can be checked again
The basic flow takes a team from the opening question to a sourced decision. Each step can be completed manually; status and history let the next person understand why work was accepted.
1. Confirm scope
Select sites, activities, outputs and decision owners. If no decision exists, the state remains open.
2. Link requirements
Each requirement is expressed as work to check, with source and edition. Unsupported content is never shown as verified.
3. Review current state
Operators describe work, bring actual records and identify exceptions. Missing evidence remains explicit for follow-up.
4. Assign actions
The organization approves owner and date. Assignees see the task, related sources and the condition for reporting completion.
5. Link evidence
Files follow one safety scan, hash and version path; viewing rights follow the project. Submitted records keep their history and cannot be rewritten.
6. Verify
An authorized person checks source and outcome, then accepts or requests more work. Uploading a file alone cannot close this step.
04
Sourced suggestions; people decide
Sources stay separate
Internal knowledge, each client’s records and public content have separate scopes. Permissions are filtered before search and before preparing a suggestion. Without a valid source, the answer states its limit rather than guessing missing facts.
Decisions are recorded
An authorized person reviews sources against actual work, then approves or requests changes. A draft never becomes an issued procedure, completed record or audit outcome on its own. History retains rejected versions to prevent repeated mistakes.
05
Keep due work and evidence together
A task list is not enough if assignees must search separately for requirements, instructions and related files. A task opens the right scope and record; when ownership changes, approved and missing parts remain visible. Reminders help prioritize but never choose dates or close work for people.
Due work
Show owner, date, status and decision needed. Overdue work is not hidden inside an aggregate metric.
Versioned evidence
Each file links to a requirement and submission; replacement does not rewrite the history.
Independent verification
The person who takes an action does not verify its effectiveness alone.
06
One page for decisions
The report has a summary, chart and conclusion built from the same source counts. Groups remain distinct: documents against scope, adoption through actual work samples and evidence coverage. Readers can open exception sources, see missing data and identify actions needing approval. There is no single overall compliance percentage or chart that disguises an unresolved gap.
If a source loses permission or has not been verified, a stale copy cannot inflate reported coverage. Missing items remain missing; owners can request records, adjust scope or explain a decision to leadership.
07
Work remotely within clear data boundaries
Interviews, draft reviews, task assignment, record submission and reports can work online under role-based access. Client content does not appear in another organization; platform administrators do not automatically read business data. Technical support requires consent, scope, expiry and an audit trail.
Public forms receive contact details and a high-level need only. Project records, sensitive personal data and secrets use an authenticated channel. If work needs on-site observation, the team records why and schedules it separately; a remote call is not described as on-site evidence.
Start with a question you can verify
Use the self-check to see open work areas, or outline your scope so we can propose discovery. Once sources and owners are clear, expand to the next workstream.
The platform does not guarantee certification outcomes; independent certification bodies conduct audits and make certification decisions.