Quality & HACCP

Quality is Checklists tuned for food safety and regulators. It adds temperature and HACCP item types, a regulator profile (SFDA, Dubai Municipality), equipment calibration, Halal certificate tracking, and an inspector mode that gives a visiting auditor a read-only window into your signed records — without a login.

A 30-second tour

Open Quality in the sidebar. The header leads with the day's status — a plain sentence about open breaches — then a stat ribbon and the most recent breaches. What you can do depends on your role:

• Branch / line staff — run the QA checks assigned to them today (temperature rounds, receiving checks), the same phone-first runner as Checklists.
• QA manager / owner — the dashboard plus Templates, Runs, Calibration, Halal, and the two manager actions in the header: Run mock audit and Generate inspector link.

QA checks & temperature logs

A QA check is a Checklists run built from a Quality template. The difference is the item types: alongside the usual checkbox and pass/fail, quality items can be a Temperature reading with a valid range, or a HACCP critical control point. When a reading lands outside its range, Mihwar records a breach.

Breaches open a CAPA — automatically

This is the cross-pillar wire that makes Quality more than a logbook. When a critical QA item fails or a temperature reads out of range, Mihwar opens a CAPA (Corrective & Preventive Action) incident with the breach attached as evidence. If the failing item is tagged to a piece of equipment, a work order to repair the asset is opened at the same moment.

So one out-of-range fridge reading produces three linked records: the breach on the run, a CAPA to investigate and close the loop, and a work order to fix the fridge — each on the audit trail.

Inspector mode

When an auditor visits, you do not hand over a login. A manager clicks Generate inspector link on the Inspector page to mint a time-boxed, read-only token. The link shows the inspector your signed checklist and quality packets, breaches, and corrective actions for the window you choose — and nothing else. Revoke it any time.

Past inspector visits and access tokens are listed under Inspections. An inspector's share link also carries a packet PDF download, so a verifier can take the signed records away with them rather than only viewing them on screen.

Calibration

A temperature log is only trustworthy if the thermometer is. The Calibration register tracks each measuring device, its last calibration, and when the next one is due, so a probe that has drifted out of certification surfaces before an auditor finds it.

Halal certificates

Halal tracks Halal certificates per supplier and per item, with expiry alerts. Because it shares data with Inventory, an expired or missing certificate can flag a receiving check — so an uncertified delivery is caught at the door, not after it is in the walk-in.

Mock audit

Before a real inspection, a manager can Run mock audit from the Audit page. It scores your current records against the regulator profile so you can fix gaps on your own schedule instead of in front of an inspector.

When checks run & how they escalate

A template's frequency decides when its runs appear. Alongside daily / weekly / monthly and on-demand, two event-driven options are wired:

• Per supplier delivery — a run is created when you receive a delivery, so the receiving check is there the moment goods arrive.
• When an incident fires — a run is created when a new CAPA incident opens, so a problem automatically pulls in the check that should follow it.

Per-batch and per-shift frequencies are not available yet — they have no trigger source, so the editor doesn't offer them.

If you configure an escalation ladder, it now actually runs. When a critical run goes overdue or is missed, Mihwar walks the steps you set — reassigning or paging up the chain — with in-app notifications always sent. Steps that page over WhatsApp only fire once WhatsApp is configured for your organization; until then those legs fall back to in-app.

Witness & sign-off

Quality templates can require a witness signature or a supervisor sign-off before a run closes, the same as Checklists.

Permissions — who can do what

• quality:read — view the QA dashboard, browse breaches, see inspector tokens for your own organization.
• quality:write — run QA checks, log temperatures, capture witness signatures.
• quality:manage — edit the regulator profile and quality settings, generate or revoke inspector links, and run mock audits.

Branch and warehouse users only ever see the breaches, runs, and inspector tokens for the locations they are scoped to.

FAQ

A fridge reading was out of range. What happens next?

The reading is recorded as a breach, a CAPA opens automatically with the breach as evidence, and — if the item is tied to an asset — a work order opens to fix the equipment. Work the CAPA to close the loop; an inspector will look for that trail.

Can an inspector see everything in our account?

No. An inspector link is read-only and time-boxed, and it only exposes the signed quality and checklist records for the window you set. It is not a login and grants no write access.

What is the difference between Checklists and Quality?

They share the same template and runner engine. Quality adds the food-safety item types (temperature, HACCP), the regulator profile, inspector mode, calibration, and Halal — the things an auditor cares about. Use Checklists for general operations and Quality for the regulated, food-safety checks.