Every process, in about 20 minutes

Welcome to Provetta. This is a two-minute tour of how to sign in and find your way around.

Sign in at provetta-dot-A-I with your work email. If you've forgotten your password, the reset link here emails you a new one.

This is your dashboard. Everything with your name on it — work assigned to you, things waiting for your decision.

The dark sidebar is home. Your modules are grouped in plain sections — overview, quality, people, and compliance. What you see here depends on your role: an inspector sees one item; a quality manager sees them all.

From anywhere, press control-K — command-K on a Mac — and just type. Records, documents, people — search finds them all.

Two things you'll see everywhere. Colored chips — green is good, amber is due soon, red needs attention. And record IDs, like D-O-C dash zero-zero-zero-one. A record keeps its ID forever. Nothing in Provetta is ever quietly deleted.

One idea makes everything else make sense: every change is recorded, permanently, with a name on it. That's not surveillance — it's what makes your records worth trusting when an auditor asks.

Provetta — the quality system your team actually wants to use.

Something went wrong on the floor — a bad part, a spill, a near miss. Here are the two ways to report it, and neither takes more than a minute.

First, from the app. Open Incidents and CAPA, and hit Report.

Pick the type that fits best. Don't overthink it — the quality team can adjust later.

Describe it in your own words. Plain beats formal: "coolant has run past the chip guard and the floor is slippery" is a perfect report. Submit — and that ID is your receipt. You can open it any time to see what happened next.

Second way: no login at all. Posters like this hang where the work happens. Scan one with your phone.

The form asks what you'd like to report — in your words, not quality-manual words. Tap the one that fits best.

Say what happened — a sentence is plenty. Then add photos. A picture taken in the moment is worth three paragraphs written an hour later.

Your name is optional, and the form means it: anonymous reports are taken just as seriously.

Submit. Either way, your report lands in front of the quality manager within a minute — with help already on the way. That's the next video.

Provetta — the quality system your team actually wants to use.

When an incident is reported, Provetta's triage agent reads it and drafts an assessment — usually before you've opened the queue. Here's what it gives you, and how you stay in charge.

The triage queue. Every new report waits here for a human decision.

On each card: a panel headed "Incident Triage suggests," with a timestamp. Everything in it is a draft.

It starts with reasoning, in plain language. When your register holds a similar case, it says so — "this is a repeat issue on CNC-02." That sentence alone can save an hour.

Severity and likelihood are proposals in live dropdowns. Disagree? Change them. What you apply is what's recorded — alongside what was suggested.

Similar past incidents are real records from your own register, with a similarity score. The AI retrieves — it never invents. Click through and check its work.

Drafted containment steps start unticked. Tick what you actually want; the caption tells you exactly what happens — ticked steps become containment actions on this incident.

The footer is the contract: drafted by the agent — you decide.

Accept applies your version — edits and all — under your name.

Or dismiss. One click, no justification demanded, permanently recorded. A suggestion you can't easily refuse would train rubber-stamping — so refusing is the easiest thing on the card.

One more honest detail: AI use is budgeted per organization. When the agent hasn't run — switched off, or the month's budget spent — the card simply arrives without a draft on it. The queue still works, and every incident still waits for the same human decision.

Provetta — the quality system your team actually wants to use.

Every controlled document walks the same road: draft, review, approval, effective. This is the approval step — the one you sign.

The register shows where everything stands. One revision is effective at a time; older revisions stay readable forever.

A document in review. Read it — your signature is about to say you did.

The signature dialog shows you everything before you commit: the record you're signing, the meaning — Approved — and a comment field for any qualification.

It asks for your password again. That's deliberate: a signature has to prove it was you, at this moment, for this content.

The dialog states exactly what's stored: your name, the meaning, a server timestamp, and a cryptographic fingerprint of the content. Signatures cannot be edited or deleted — by anyone.

Sign, and your approval is on the record permanently. This document also needs its owner's sign-off — and then it becomes the controlled copy, with read acknowledgments going out to the people who need to know it.

And it's checkable forever — who signed, what it meant, when, and the fingerprint. If the content ever differed from what was signed, the hash would say so.

Provetta — the quality system your team actually wants to use.

An inspection assigned to you, start to signed submission, in about two minutes.

Your assigned inspections are on the Inspections screen — the tile tells you how many are waiting on you. Open one and start.

The runner walks you section by section. Answer what you observe — measurements want numbers.

Where evidence is required, you'll see this. On a phone it opens your camera; on a computer it takes files — photos, PDFs, documents. The green check means it's attached.

And every item — not just the required ones — can carry evidence. If you saw something worth keeping, attach it.

Your answers save as you go. A flaky connection doesn't lose your work.

If something fails badly, say so honestly. A hard failure can raise a nonconformance right here, carrying your evidence with it. That's the system working — not you causing trouble.

At the end: review and submit brings up the summary, with your results tallied.

Sign and submit opens the signature dialog — your password, the meaning Verified, an optional comment. From that click, the inspection freezes exactly as you submitted it. Nobody can change your answers afterward. Not even the quality manager.

Provetta — the quality system your team actually wants to use.

You've concluded an investigation. Before you open the CAPA tab, the drafting agent has read what you wrote — and drafted the plan.

It starts from your investigation. Your whys, your root causes — not a generic template.

The card leads with root-cause hypotheses, each carrying an evidence line from your own investigation.

Then a proposed CAPA — title, type in plain words, root cause.

Proposed actions carry owners and due dates — owners only from your real, active team. The AI cannot invent a person.

Every field is live — change owners, rewrite, delete. What you apply is recorded beside what was proposed.

Behind the draft: similar incidents from your register and their CAPAs — including plans that failed their effectiveness checks. The agent learns what didn't hold.

Accept, and it becomes a real CAPA under your name — owners notified, due dates live.

Or dismiss it and write your own. One click, permanently recorded, no justification demanded.

Provetta — the quality system your team actually wants to use.

One incident, start to finish — reported, triaged, investigated, corrected, checked, and closed. Every step you'll see is a real record.

A third occurrence of an oversize bore on the same machining cell — twenty-five point zero four two millimetres against a twenty-five H7 spec, caught across the first five parts. The lot was quarantined that day.

The triage agent flagged it as a repeat and proposed a severity, a likelihood and four containment steps. A person accepted them — so the assessment sits on the trail under the quality manager's name, and the containment on this record is here because someone said yes to it.

The investigation asked why until it hit process: the tool-change routine covered the insert and stopped there — the wear offset was left to judgement. And the gauge that should have caught it was out of calibration.

The CAPA: two owned actions — in-process gauging, a calibration recall. Both completed, on the record, with dates.

Then the step that makes it a real CAPA: an effectiveness period, and a signed verdict at the end of it. Signed means someone's name is on the claim.

And underneath all of it, the trail — every step, every person, every change, append-only. This is what you hand an auditor instead of a story.

Closed — with the evidence of why it won't happen again.

Provetta — the quality system your team actually wants to use.

Your supplier file — qualification, the approved list, and what happens when a supplier ships you a problem.

Suppliers walk their own lifecycle: prospective, under evaluation, approved — with conditional and suspended beyond. Approval is signed; it's what puts them on your ASL.

The approved supplier list an auditor asks for — generated from the register, so it's always current and always true.

Evaluations run by criticality, and risk scores fold in incident history. A critical supplier overdue for re-evaluation goes conditional on its own.

When a supplier ships you a problem, raise a SCAR. This link is their portal — private, expiring. Copy it, send it; they respond without an account.

Their response comes back structured: root cause, what they did about the affected material, corrective action.

Your review is a decision: accept and close — signed — or return for rework, sending them back to the same link with your comments.

The record keeps score: status and timeliness side by side, with the due date.

Provetta — the quality system your team actually wants to use.

Assignments, quizzes, acknowledgments — and the matrix that proves it all at a glance.

Training items — courses, document reads, quizzes — assigned by person, role, or department, each tracking completion and expiry.

Quizzes grade themselves, with limited attempts and recorded scores.

When a controlled document goes effective, the people who must read it get an assignment — and their sign-off is a signature, not a checkbox.

The matrix is the wall chart an auditor believes: person by item. Six states — completed, due soon, assigned, overdue, expired, and not required. That last one matters: a blank cell means the item doesn't apply, not that someone's behind.

Overdue and by-department views answer the two questions managers actually ask.

Certificates generate per completion — evidence you can hand over.

Provetta — the quality system your team actually wants to use.

Signed in as an auditor, you can see everything and change nothing — and that's enforced by the database, not by good manners.

Every record carries its trail. Append-only — the panel says so itself. Events in plain language: status changed, investigation concluded, containment added.

Before-and-after values sit behind each change — open the disclosure rather than hunting for columns.

Filter by person, action, or date. "Show me everything this user changed in March" is one screen.

Signatures show the signer, the meaning, the server timestamp, and the record's fingerprint — the first sixteen characters on screen, the full hash stored and exportable.

One property underneath it all: every event carries a cryptographic link to the one before it. A gap or an alteration anywhere breaks every link after it. Tampering isn't just forbidden — it's detectable.

The registry spans every module, with retention states visible. What's kept, how long, what's frozen under legal hold — one screen.

Provetta — the quality system your team actually wants to use.

You've been engaged to inspect on a customer's behalf. Here's your whole workflow — from the invitation to your signature.

Your invitation shows what you're accepting: the organization, your role, your email. Create your account in one step.

Sign in — and choose your language. English or Chinese, applied to every screen you use.

You land on your inspections — and only yours. If it isn't on this list, it isn't visible to you. That boundary protects you as much as them.

Work through the checklist: lots, quantities, workmanship, packaging. The checklist is the customer's; the observations are yours.

Photos where marked — shoot in place, in the moment. A certificate or packing list attaches the same way.

Classify what you find where it asks — critical, major, minor.

When every section is done: review, then sign — your password, the meaning Verified, and an optional comment.

The moment you sign, your inspection freezes. The customer sees exactly what you submitted, and no one can alter your answers.

Provetta — the quality system your team actually wants to use.

The admin's first week, in one pass: people, roles, and the fixed machinery.

Invite your team by email, each with a role. Five team roles: admin runs the org, the quality manager runs the system, supervisors approve in their area, employees do the work, auditors see everything and touch nothing. A sixth — the external inspector — is for outside parties, with its own video.

People leave — deactivate them. Never deleted: their name stays on every record they touched, because a trail with holes isn't a trail. And the system won't let you remove the last admin.

Supervisors can be scoped to a department. Note what the dialog says — this is an access boundary enforced by the database, not a label.

Create Quick Report postings for the floor — print the poster, hang it where the work happens, and anyone can report with a phone and no login.

Inspection checklists live here — sections, field types, photo requirements. Templates version, so a checklist in use is never edited underneath its inspections.

Retention policies per record type. Nothing deletes itself — the registry flags what's past its period; archiving is always a person's deliberate act.

And this page shows every time Provetta support has ever accessed your org — time-boxed, named, revocable. If it's empty, that has never happened.

Provetta — the quality system your team actually wants to use.

Where everything lives, how long it's kept, and how it gets handed to an auditor.

The registry spans every module — filter by type, status, date, retention state. One place to answer "show me."

Retention policies mark what's past its period. Legal holds freeze records against archiving entirely. Nothing is ever deleted on a timer.

Audit binders assemble evidence as a package: pick the scope, and the binder collects the records and builds a manifest.

"Everything supporting section 8.4, last twelve months" becomes a package — not an afternoon of screen-sharing.

And everything exports. Exports generate from the live records at the moment you ask — there's no shadow copy to drift.

Provetta — the quality system your team actually wants to use.

Before an audit, the question is simple: where are we strong, and where are the gaps? Provetta's readiness agent answers from your own records.

Pick a standard, the clauses you care about — or all of them — and a time window. Ask.

The agent works through the clauses you picked, counting what your register actually holds. The ask itself becomes a record — who wanted it, over which clauses, for which period.

First thing on the result — and always first: this is an AI draft. Not a certification assessment, not signed, not evidence of conformity.

Gaps come from counts, not opinions. A clause with no records in the window is a gap because the number says so — and the number is right there, so you can check the machine's arithmetic.

Some clauses Provetta simply doesn't hold evidence for — leadership commitment, calibration. The picker labels them outside scope before you even ask, and the assessment keeps them out of the gap list entirely. "We don't hold this evidence" is never spoken as "you have a gap."

Where you're strong, it says so, citing your real records — retrieved from your register, never invented.

And when you're ready to assemble the evidence, one action hands this scope to the audit binder. It tells you how many records that is before you commit, and it runs through the same permission checks a hand-built binder gets.

Provetta — the quality system your team actually wants to use.

Ninety seconds on where everything you just watched is written down.

The user workbook — every process in this series, step by step, with pictures of the real product. It's in your user menu, whatever your role. Find your track: admin, quality manager, employee, inspector, or auditor.

Each track is written to be read in minutes, not memorized. The appendices cover the AI cards, the status colors, and the record IDs.

It's also on provetta-dot-A-I, freely downloadable.

And if you ever work with Provetta support, remember: their access is time-boxed, visible on your settings page, and on your audit trail — by name.

Provetta — the quality system your team actually wants to use.