Drafts & autosave

Qualio autosaves every NCR and CAPA you start. You can close the tab, lose your Wi-Fi, or come back tomorrow — your work is on the server, not in browser storage.

How autosave fires

Autosave runs 1.5 seconds after your last keystroke in any tracked field. The first save creates a row with status = 'draft'; subsequent saves update the same row.

While typing you will see one of three states next to the form header:

• Saving… — request in flight.
• Draft saved · HH:MM:SS — successful round-trip.
• Save failed — retrying — network or validation error; the next keystroke retries.

Need to force a save (for example before leaving the tab to grab a screenshot from another window)? Click Save draft now. It bypasses the debounce and writes immediately.

Note

Autosave requires at least one supplier (for NCRs) or one parent NCR (for CAPAs). Until that base field is set, the form holds your input client-side and starts saving as soon as it’s valid.

Resume a draft

1. Open the NCR or CAPA list. Drafts appear with a grey Draft badge and no number (the temporary identifier starts with DRAFT-).

2. Click the row. You land back on the new-NCR or new-CAPA form, pre-filled with every field you had typed.

3. Continue editing. The same autosave loop resumes against the existing draft row — no duplicates are created.

You can have many drafts open per user. There is no per-org limit on draft count.

Publish

When the form is complete, click Publish NCR or Publish CAPA. The publish RPC:

1. Validates required fields server-side (title ≥3 chars, description ≥10 chars for NCRs, supplier and issue type for NCRs, parent NCR for CAPAs).
2. Assigns the real, human-readable number for NCRs — NCR-YYYY-NNNN, sequenced per organisation per year.
3. Flips status from draft to open.
4. Sends the assignee email (CAPA) and starts the audit trail.

If validation fails, the record stays a draft and the form shows which field needs work. You will not get a half-published NCR with a missing supplier.

What drafts do not do

Drafts are deliberately invisible to the rest of the platform until you publish them:

Surface	Drafts counted?
Monthly NCR quota	No
Dashboard KPIs	No
Analytics charts	No
Supplier scorecard	No
Risk-score triggers	No
AI credit usage	No (AI calls are blocked on draft rows)
Email notifications	No

This is enforced in the count_org_usage RPC and the supplier-risk recompute triggers — draft rows are filtered before any aggregation.

Caution

Drafts persist until you publish or delete them. If you abandon a draft, it stays in the list (with the DRAFT-… placeholder number) until an org admin clears it. There is no automatic expiry yet.

Related

• NCR — the publish step assigns the NCR-YYYY-NNNN number.
• CAPA — publishing notifies the assignee.
• Plans & quotas — only published NCRs hit your monthly limit.