Noventra Automation
Quality & Records

Evidence and Audit Pack

Proof gathered as you go, not rebuilt the week before.

Proving a process ran is rarely the same work as running it. The records exist, but they sit in an inbox, a folder, a spreadsheet, and someone's sent items, and pulling them together after the fact is a fortnight of archaeology that produces nothing new.

Live workflow
Assembled this morning, 5 processes
Pack contents
  • Management review2 of 2 held, minutes and actions
  • Internal audit6 of 6 held, reports and sign-off
  • Calibration11 of 12 held, one certificate not found
  • Corrective actions9 of 9 held, raised through to closed
  • Supplier assessment3 of 4 held, one review not recorded
On the two gaps
Both were visible in March, not the week before the audit. The pack reports what is held and what is not; whether that is sufficient is not its call.
Gathers what exists, shows what does not
How it works

From record created to pack assembled, in four steps.

01Collect as it happensRecords are captured when they are created rather than hunted for later: the email that approved it, the form that recorded it, the file that resulted.
02File against the processEach record is filed under the process it evidences, so the question stops being where something is and becomes whether it exists.
03Show the gapsA process expecting a monthly record and holding nine of them is visible as nine, not as a folder somebody has to count.
04Assemble on requestA dated pack is generated whenever one is asked for, listing what is held per process and what is missing.
Before and after

What changes after we deploy this.

TodayRebuilding a year of evidence in a fortnight
With the workflowRecords filed against their process as they happen
TodayEvidence spread across inboxes and folders
With the workflowOne place, organised by process
TodayNot knowing what is missing until asked
With the workflowGaps visible before anyone asks
TodayA pack assembled by hand each year
With the workflowA dated pack generated on request
Where it shines

If any of these describe your business, this workflow earns its keep.

An annual external audit

The cost of an audit is rarely the audit. It is the fortnight before it, spent gathering records that already existed, by people who have other work.

Processes that must be evidenced

Where running a process is not enough and you have to show it ran, the showing is a second job. It is usually done once a year and badly, because it is done from memory.

Records held in several places

Evidence spread across an inbox, a drive, and a spreadsheet is not missing. It is just expensive to find, and the expense lands in one concentrated fortnight.

How long did it take to put last year's evidence together?

Tell us the processes you have to evidence. We will show you what a pack would hold today, and where it would already be short.

Ask for the review
What engaging involves
It gathers, it does not createEvery record in a pack is one your business already produced. The workflow never generates evidence, and never fills a gap with something plausible.
Gaps are shown as gapsA process missing a record is reported missing. A pack that reads complete throughout would claim a completeness the workflow cannot judge.
Sufficiency is not its callIt reports what is held against what a process expects. Whether that satisfies an auditor is a judgement for you and them.
What it does not coverIt works from the processes and expected records you define. It cannot know a process exists if nothing about it is written down.
Integrations

It runs inside the tools you already use.

And 30+ others. If your tool is not listed, ask.

See every integration
Common questions

The questions we get before we build.

Still unsure? Ask us directly and we will answer before you commit to anything.

Does it create records we do not have?

No, and this is the line that matters most. It gathers records your business already produced and files them. Generating evidence for a process that did not run would be worse than useless; it would be a fabrication sitting in an audit pack with your name on it.

What happens where evidence is missing?

The gap is reported as a gap, in March rather than in the fortnight before the audit. That is most of the value: the pack is useful long before anyone asks for it, because it tells you what to go and do.

Does it decide whether our evidence is good enough?

No. It reports what is held against what each process expects. Whether that is sufficient is a judgement for you and your auditor, and it depends on context the workflow does not have.

How does it know which record belongs to which process?

From rules you set when it is built: where a record comes from, what it is called, who sent it, what it contains. Anything it cannot confidently file is held for a person rather than filed somewhere plausible.

Is this the same as a backup?

No. A backup is about getting a file back after something goes wrong. This is about being able to show a process ran, which is a different question and usually needs records from several places rather than a copy of one folder.

Does it replace our quality manager?

No. It removes the gathering, which is the part that is mechanical and miserable. Deciding what a process needs to evidence, and whether the evidence stands up, stays exactly where it is.

Want to know what your evidence pack holds today?

Tell us the processes you have to evidence. We will show you what would already be in the pack, and where it would be short.

Every workflow is a managed monthly service. No credit card, and we respond within one business day.