Quality

Quality is where a branch is inspected. An inspector walks a form step by step on a phone, Mihwar scores it, and every finding becomes a follow-up the branch has to fix. The rule of thumb: every shift is a checklist; judging how the branch is doing is an inspection. Temperature logs, receiving and cleaning belong in Checklists.

An inspection, from the plan to the signed report
Plan or scheduleIt opensA plan or a schedule opens it, or someone starts it.
InspectorAnswered on a phonePass or fail, a rating, a reading, a photo.
MihwarSubmitted and scoredEach finding opens a follow-up for the branch.
The branchThe branch signsSomeone who answered none of it signs.
A managerA manager approvesThen it is final, with a report to share.
A critical step that is not met opens its follow-up the moment it is saved. A form that asks for no signatures is final when it is submitted.

Find your part

Starting an inspection

Open Inspections. The buttons at the top choose what the list shows: Today (the one you see first), This week, Overdue, Failed today, Waiting for a signature, Planned and All. Each row shows the form, the branch, how many steps are done and whether it is late. Today’s inspections for your branch also show on its home page.

Most inspections open by themselves: on a schedule, when a delivery arrives, or from a plan head office made (see when inspections open). To inspect something now, tap Start an inspection, choose the form — and the branch, if you work at more than one — and tap Start inspection. Leave Due by empty and it is due in an hour.

  • Only live forms that are meant for you are offered. A form can be for certain roles only, so you may not see every inspection of your branch. If nothing is offered, ask a manager to take a form live.
  • An inspection past its time says Late; when its window closes it is Missed. You can still record it, and it shows as recorded late.
  • Crew see three tabs at the top of Quality: Inspections, Follow-ups and Compliance. Managers also see Overview, Forms and the settings gear.

Answering the steps

Open an inspection and answer it one step at a time. Steps are grouped by area, and the bar at the top shows how many you have answered. A step can say what to check, the clause of the regulator’s form it comes from, and the result the last time at this branch. Tap the answer that fits:

  • Pass or Fail. Pass saves at once. Fail asks what you saw, and for a photo where the step needs one.
  • A rating. Tap a number from 1 (poor) up to the top of the scale, which is 5 unless the form says otherwise. A rating under the step’s target is a finding.
  • A reading. A temperature, a weight, a swab result, a use-by date: type it and tap Save. The step shows its limits, and a reading outside them is a finding.
  • A note, a photo or a signature. Type it, take the photo or sign in the box. For a maintenance note, choose Which equipment, or tap Nothing needs maintenance. These are recorded and never scored.

Anything that falls short — a Fail, a rating under its target, a reading outside its limits — is a finding. Each finding becomes a follow-up for the branch (see below).

On any step you can Add a photo — up to six on one answer, and on a phone it opens the camera — and Add a note. Where a step does not apply, tap Not applicable here: only where the form allows it, and never on a critical step. A manager can set aside any step, with a reason.

No signal? Your answers wait on the phone — the step says On this device — it syncs when you are back online. — and go when you reconnect. Starting an inspection, submitting it and signing need a signal.

When a critical step is not met

A Critical step is a real risk, such as a fridge that is too warm or hand-washing that was missed. When you tap Fail on one, or a reading falls outside its limits, Mihwar asks what you did about it and for a photo. Then tap Record the fail and open a follow-up.

  1. The answer is locked

    Breach recorded appears. If the answer was wrong, a manager can Correct this step, with a reason.

  2. A follow-up opens at once

    It opens at your branch with the reading, the limit it broke, what was done and the photo. If the step is tied to a piece of equipment, a work order opens for it too.

  3. Managers are told

    The branch’s managers are told straight away, each in their own language. The person who recorded the step is not told about their own entry.
  • I couldn’t take this reading — if the probe is broken or the fridge is locked, tap it. The reading is recorded as not met, with what you did and a photo, never a made-up number. It is only for critical readings.
  • Probe calibration overdue — a red box means the thermometer tied to this step is past its calibration date, and its readings may not be trusted until it is calibrated again (see calibration).
  • A step that is not critical but falls below target becomes a follow-up when you submit, not before.

Reviewing and submitting

  1. When every step is answered, or marked not applicable, tap Review and submit. The sheet shows the score, the pass mark and whether it passes, the areas weakest first, the findings, the maintenance notes and anything Still to answer.
  2. Choose who is Responsible at the branch: the person who is told the result, can sign for the branch and owns the follow-ups.
  3. Tap Submit inspection, or Keep editing to go back.

Submitting locks the answers and gives the inspection its reference, such as QC-2026-00008 (the first letters are a Quality setting). Every step below target becomes a follow-up for the branch, due in a day, three days or a week as the step says; a critical step already has its follow-up. Every maintenance note with text becomes a work order. The screen says how many follow-ups the branch has now.

After that the inspection is final, or it says Waiting for the branch’s signature or Waiting for approval until the people the form asks for have signed (see signing). Answers can no longer be changed; a manager can send it back.

How the score and the result work

Each step that can be scored counts between 0 and 1. A Pass counts 1 and a Fail counts 0. A rating counts its share of the scale: 4 out of 5 is 0.8. A reading inside its limits counts 1, outside them 0. Steps marked not applicable, notes, photos, signatures and maintenance notes are left out. The score is the average of the steps that count, as a whole percent, and each area has its own. A step can be given a weight from 1 to 100 so that it counts for more.

The result is Passed when the score reaches the form’s Pass mark and no critical step is below target. A critical step below target makes it Failed whatever the score, and the status turns to Failed as soon as that step is recorded. A form with no pass mark is decided by its critical steps alone; the score is still shown.

When your branch is inspected

Head office can inspect your branch, by hand or through a plan. Until the inspector submits, the inspection is not yours to see: it is not in your lists, on the Overview, in a packet or on an inspector link. If the plan is announced, your managers are told one is coming — not who, and not exactly when. An unannounced plan tells nobody.

When it is submitted, the person named Responsible at the branch is told the result: passed, failed or not scored. You can read the inspection, sign for the branch if the form asks, and answer its findings through the follow-ups it opened (see Follow-ups). You cannot send it back, reopen it, approve it or share its report: head office decides.

If you are head office and inspect a branch yourself, choose the branch when you tap Start an inspection, answer as usual, and name who is responsible at the branch when you submit. The branch cannot see it until you do.

Signing for the branch, and approving

A form can ask for the branch’s signature, a manager’s approval, both, or neither. With neither, submitting makes it final. Until the signatures are in, the inspection is listed under Waiting for a signature in Inspections and on the Overview.

  1. The branch signs

    Open the inspection, tap Sign for the branch, sign in the box with your finger, or type your full name, and tap Sign. Only someone who works at the branch, or the person named responsible, can sign for it — and, by default, not anyone who answered a step.

  2. A manager approves

    Tap Approve and sign. The approver is a manager who may decide on this inspection, never the person who signed for the branch and, by default, not anyone who answered a step. Head office’s own inspection of a branch is approved by head office, never by the branch it inspected.

Sending back, reopening and correcting

These are for the managers of the branch and, for the inspections head office made, for head office. Each one needs a reason of at least five characters, and the record keeps it.

  • Return to the inspector. While an inspection waits for signatures, say what should change. It becomes a draft again: the signatures and the result clear, it keeps its reference, and the inspector is told (“Inspection returned to you”). The inspector changes what is needed — a locked critical finding stays locked — and submits again.
  • Reopen with reason. A finished inspection, or one that was left unsubmitted and is Locked at the end of the day, can be reopened the same way. The inspector is told to finish it again.
  • Correct this step. Corrects one critical finding that was recorded and locked. The record keeps what was entered before, who corrected it and why.
  • Not applicable. A manager can set aside any step, even a critical one, with a reason. It leaves the score.

When the inspection is submitted again, a finding that is gone is taken back and its follow-up is cancelled — but only while that follow-up is still New. One that someone has started on stays, and a finding that was already closed is not raised again.

The report, and sharing it

Every submitted inspection has a report. Tap Report (PDF) on the inspection to download it, in your language. It holds the score and the result, the areas weakest first, every answer, each finding with where its follow-up stands, the maintenance notes with their work orders, and the signatures. A finding that the branch’s last inspection of the same form also had is marked as a repeat. On the inspection itself, Linked follow-ups and Linked work orders list what it opened.

A manager who may decide on the inspection can tap Share by link. Anyone with the link sees the report and can download it for 7 days, with no account. The link is shown once, when you make it; New link replaces it, and the old one stops. Stop sharing ends it at once. The branch cannot share head office’s inspection of itself.

Building a form

Inspections come from forms. Managers build them under Forms: the steps, a pass mark, who signs, and when and where it runs. A new form is a draft, and it does nothing until you tap Go live.

  1. Start the form

    Tap New form. Name it in English or Arabic — one is enough — choose the regulator it follows, then set When does it run?, Where does it run?, Who does it? and Who signs it off?. Tap Create and add steps.

  2. Add the steps

    Tap Add step for each thing to check. Give it a title and choose What it records: a rating, Pass / Fail, a temperature with its limits, a number, a weight, a swab, an expiry date, allergens, a cleaning check, a receiving check, a note, a photo, a signature or a maintenance note. Tick Critical step for a real risk. You can also tick Photo when it fails and Can be “not applicable”, say how urgent the follow-up is (When it fails, the follow-up is low, medium or high), write what to do the moment it fails, add the clause of the regulator’s form it comes from, and name the equipment it checks.

  3. Set the pass mark

    Under When does it pass? type a Pass mark from 1 to 100%. Leave it empty and only the critical steps decide.

  4. Go live

    Tap Go live. It stays grey until the form has a step. Then the inspections start to open, and crew are offered the form.
  • Who signs it off? Choose Submitting makes it final, or The branch signs the report and, as a second tick, A manager approves it.
  • Who does it? Leave every role unticked and everyone at the branch can. Tick roles and only those people, whoever the inspection is assigned to, and managers can.
  • A branch manager builds forms for their own branches only. A form that runs at every branch, or at branches outside theirs, says Set by head office: only head office changes it, and the branch still runs it and sees its results.
  • A live form can be edited at any time. Each save is a new version and applies to the next inspections; a step that already has answers is retired, not deleted. A finished inspection keeps the score and result it was submitted with, but it shows its steps as the form reads now, so change a step’s words, scale or limits only to correct them.
  • On the list, Start now begins an inspection of a live form, Edit opens its editor and Archive form hides a form you no longer use.
  • Start from a pack adds a ready-made form as a draft you can change: the daily food-safety forms for SFDA, JFDA and Dubai Municipality, HACCP readings every four hours, Halal Operations and Ramadan Operations. The ones that are daily logs are routine work, which belongs in checklists (see the rule of thumb at the top).
  • While your organization has no forms, the Overview shows Get started in 3 steps.

Building a form with AI

When your organization has AI turned on for Quality forms, Build with AI appears on Forms. Choose Describe it and say what you want inspected, or Bring your form — a PDF, photos of the paper form, or a spreadsheet. The AI writes the form in English and Arabic, with its areas, steps, critical steps and pass mark. You read it, change anything, and tap Create the form. It is created as a draft and its editor opens. Nothing runs until you tap Go live.

Don’t see the button? Ask an administrator to turn AI on for Quality forms in the organization’s settings. How AI works, and what it never does, is in AI in Mihwar.

When inspections open, and when they are late

A form’s frequency decides when its inspections open:

  • Daily, Weekly, Monthly and Custom run on a schedule: one inspection per day, week or month at each branch. A form is not given inspections for a time that had already passed when it went live.
  • Ad hoc has no schedule: it runs only when someone starts it.
  • Four start from something that happens at the branch, and each inspection says what started it. Per delivery follows a transfer or supplier order that is received. Per batch follows a prep label printed for a recipe (a reprint is not a new batch). When a follow-up opens follows a follow-up opened at the branch. All three are due an hour after they open.
  • At each shift opening and At each shift closing follow the shifts you have sent to the team. An opening one opens half an hour before the shift starts and is due half an hour in; a closing one opens an hour before the shift ends and is due as it ends. If everyone on a shift is cancelled before anything is recorded, its inspection is cancelled too.

An inspection still open after its due time is Late. When its window closes — 15 minutes after it was due, unless the form says otherwise — it is Missed, the branch’s managers are told, and it can still be recorded late.

Under When an inspection is late a form can have a ladder: steps that fire when an inspection runs late.

  • Each step says after how many minutes, who hears — whoever does it, the branch’s managers, the organization’s admins or one named person — and what happens: Notify, Reassign or Escalate. It reaches people in the app, and by e-mail where the step asks.
  • Pick one of four ready ladders — Crew first, Strict HACCP, Standard daily or Light weekly — or write your own steps. Each step runs once.
  • A ladder works for scheduled inspections, not for plan inspections, head office’s own, or ones that already wait for signatures. With no ladder, a late inspection only shows as late.

Head office also has Update today’s inspections on Inspections: it adds today’s scheduled inspections now and marks overdue ones missed. Mihwar does the same by itself every 15 minutes. This button does not make plan inspections.

Inspection plans

A plan is how head office, or a branch manager for their own branches, schedules inspections of its own. Managers open Inspection plans from Inspections and tap New plan: name it, choose a live form, say Every how many weeks or months Starting on which day, tick the Branches, and choose the Inspectors. Only people who can inspect every branch you ticked are offered. One inspector inspects every branch; several take the branches in turn, one step further each period, so no branch always meets the same eyes.

  • Each period makes one inspection per branch, due at the end of the period, and tells each inspector what is theirs (“Inspections to do”). Mihwar makes them by itself, about every 15 minutes — not when someone opens the page.
  • Tell the branch it is coming makes the plan Announced: the branch’s managers are told at the start of each period. Otherwise it is Unannounced. Either way the branch sees the inspection only once it is submitted.
  • Each plan’s card shows This period and a label for each branch: To do, Under way, Done with its score, or Missed. Pause stops new periods and Delete cancels the inspections not yet submitted; submitted ones stay.
  • Only the plan’s maker, or head office, changes or deletes it. A plan cannot overlap another active plan with the same form and branch. A branch manager sees announced plans on their own branches, as labels, without buttons.

How the branches are doing

Overview is the first tab for managers; crew start on Inspections. Its headline says how today is going — for example “Every inspection passed today” or “2 inspections failed today”. Under it:

  • The cards Today’s inspections, Failed today, Waiting for a signature (only while something waits), Pass score (7 days), Active inspector links and Open follow-ups.
  • The buttons Start an inspection, Run a mock audit and Generate inspector link.
  • Recent breaches (last 7 days) lists the failed inspections with the step that failed.

Under How the branches are doing you choose the last 30 or 90 days. It shows:

  • The Average score, and how it changed on the period before.
  • How many Inspections the branches made and head office made, how many Failed, the Open follow-ups and the Missed inspections.
  • Fix first, Branches, weakest first, Areas across the branches (green, amber or red against the pass mark) and Found again, for a step that failed twice at the same branch.
  • When AI is on, an AI summary comes first, with the numbered facts it read.

A branch manager sees their own branches only.

Compliance: the records a regulator asks for

The Compliance tab holds what an inspector asks to see. At the top, a Calibration card and, when halal mode is on, a Halal certificates card show what is due or overdue and open their registers; crew can read both registers. Managers also see three cards: Regulator packs (signed packets), Mock audit and Inspector access. The next sections take them in turn.

Calibration

A temperature log is only as good as the thermometer. The Calibration register lists every measuring device — a probe, a thermometer, a scale, an ATP luminometer, a pH meter, a humidity meter, a pressure gauge or a timer — with its last calibration and the next one due. At the top: Active devices, Due in 7 days, Due in 30 days and Overdue.

  • Add device — a name, a type, where it is (a branch, or the whole organization for head office), the maker and serial number, how often it needs calibrating (180 days unless you change it), and when it was last calibrated if it is already in use.
  • Log calibration — who calibrated it (required), the certifying body and certificate number if there are any, the date and the Result. Pass and Pass (after adjustment) move the next due date on by the device’s cycle. Fail — replaced and Fail — out of service do not, and the second takes the device out of service.
  • Take out of service keeps its history, and Back in service returns it. A device is never deleted.

A temperature step can be tied to a device. While that device is overdue, whoever records the reading sees Probe calibration overdue. The branch’s managers are told 7 days before a calibration is due and again when it is overdue. Managers look after the devices of their own branches; a device that belongs to no branch is head office’s.

Halal certificates

Halal certificates is the register of your suppliers’ and items’ certificates. Head office keeps it; everyone with access to Quality can read it. Tap Register certificate: a supplier or a specific item, the certifying body, the certificate number, the dates it was issued and expires, and notes.

  • The status follows the expiry date: a certificate past its date is Expired whatever was stored. The numbers at the top are Active, Expiring (30d), Expired and Revoked.
  • Renew sets a new expiry date. Revoke records that the certifier withdrew it. Remove from register takes a certificate entered in error off the list, keeps its record, and Put back returns it.
  • Supervisors, branch managers and head office are told 30 days and again 7 days before a certificate expires. When a supplier order is received, Mihwar looks the supplier and items up here. It never stops a delivery or a purchase order; a lapsed certificate only leaves a line in the audit trail.
  • If the organization has no halal-certified operations, an owner can turn Halal mode off in Quality settings.

Mock audit

A mock audit is a rehearsal before a regulator visits. Open Mock audit from Compliance, or tap Run a mock audit on the Overview.

  1. Choose the form to audit against and the branch (head office can choose the whole organization). The audit’s name is filled in; change it if you like.
  2. Go through the steps. Each starts as PASS. Mark a gap FAIL, choose how serious it is and add a note, or mark a step NA.
  3. Tap Submit audit + open follow-ups. Each gap becomes a follow-up from “Mock audit”, and you land on the list. Submitting the same gaps again opens nothing twice.

A mock audit is not an inspection: it has no score, no reference number and no signatures. What it leaves behind is the follow-ups.

Packets: a signed PDF for a regulator

A packet puts the inspections of a period into one signed PDF that a regulator can check. Managers open Inspection packets from Compliance (the card is called Regulator packs) and tap Generate packet: choose the form, the branch — head office can choose all branches — and the window, from the last 7 days to the last 12 months. The packet holds the form’s submitted inspections whose due time falls inside the window.

  • Packet ready shows the share link once. It opens the packet and its PDF without signing in, for 72 hours. The packet page has the signed PDF and the check described below.
  • Every inspection keeps its record in a chain, each entry tied to the one before it. Verify chain walks those chains again and re-checks the PDF: the packet is intact, or a record or the PDF was changed. The check covers each inspection’s recorded results and the PDF. Typed text, such as notes and written answers, is not part of it.
  • New share link replaces the old link, Stop sharing ends it, and Share again makes a new one. The row shows how many times it was opened.

For a visit from a regulator, make a link instead of sharing a login. Open Inspector links from Compliance, or tap Generate inspector link on the Overview. Fill in the visit label — it goes into your audit trail and the inspector sees it too — the branch (head office can choose all branches), how long it stays valid (1 hour, 4 hours, 24 hours, 3 days or 7 days; your organization may allow less), the evidence window (the last 7, 14, 30, 60 or 90 days) and the inspector’s language. Tap Generate link.

  • Link ready shows the link and its QR code once. Copy or print them then. If the link is lost, make a new one and revoke the old.
  • Active links lists each link with when it expires and how often it was opened. Revoke stops it at once. Past links keeps the record.
  • What the inspector sees, and what they never see, is described in If you were sent an inspector link.

Quality settings

Quality settings (the gear at the end of the tabs) apply to every branch. Managers can read them; head office changes them and taps Save settings.

  • Regulator profile — SFDA, Dubai Municipality Food Watch, MoH Jordan / JFDA, HACCP (generic), ISO 22000 or Custom. It sets the default critical limits for cold storage, freezer and hot holding, the allergens Mihwar tracks, how early expiry is warned and which regulator a new form follows. Until someone chooses, Mihwar starts from the regulator that matches your country. An organization has one profile, and its limits are shown, not edited.
  • Inspector links — the default and the longest time a link may stay valid, in hours, and the evidence window in days.
  • Inspection reference numbers — the Prefix, one to eight capital letters or digits. QC gives QC-2026-00008.
  • Closing a finding’s follow-up — A photo of the fix is needed: When the finding needed a photo, For every finding or Never. It applies to the follow-ups opened from then on.
  • Sign-off integrity — Require independent sign-off (four-eyes) is on. Turn it off only for a branch where one person works alone.
  • Halal mode — shows the halal card and wording. Turn it off only if the organization has no halal-certified operations.

If you were sent an inspector link

A manager at the business made this link for your visit. It opens one read-only page: you do not sign in, and you cannot change anything. It shows:

  • The business, the branch, the visit label, the period and how long the link is valid.
  • Inspections in the period, by form — how many, how many were completed or missed, the critical fails, the last inspection and its last score.
  • Follow-ups register — how many are open, overdue and closed in the period.
  • Calibration register — devices in service, due in 30 days and overdue, with the names of the overdue ones. Halal certificates — active, expiring in 30 days, expired and revoked.
  • Critical breaches — the step that failed, the form, the reading, the regulator’s clause and when. A critical step that was not met appears as soon as it is recorded, even before its inspection is submitted.

It does not show staff names, photos, ordinary answers, signatures, the titles of follow-ups, other branches (on a branch’s link) or a head-office inspection not yet submitted. Every visit is written in the business’s audit trail. Switch language with the English / العربية link; the QR code reopens the same page on a phone.

  • If the page says Inspector link not available, the link ran out or was withdrawn. Ask the branch for a new one.
  • To take records away, ask for a packet or a report link. A packet page has Verify integrity, which answers Records intact, Tamper detected or PDF altered. A report link opens one inspection’s summary and its PDF for seven days.

Where Quality connects

  • Follow-ups — every finding becomes a follow-up for the branch: a critical step the moment it is saved, every other one when the inspection is submitted (Follow-ups). It is owned by the person named responsible; if nobody is named, by the branch’s follow-up manager; if there is none, head office and the branch’s managers are told. The Follow-ups tab lists the ones Quality opened. A form set to When a follow-up opensstarts an inspection when a follow-up opens at its branch.
  • Work orders — a critical step tied to equipment opens a work order together with its follow-up, for that branch’s own machine: the tagged one if it is there, otherwise the one machine of the same kind. With none or several it opens without equipment and says which kind to check. A maintenance note with text opens a work order when the inspection is submitted (Work orders).
  • Documents — a step can ask whoever records it to sign a procedure first (Procedure to sign first) or to hold a current signature on a document (Certificate needed); until then it says Sign the procedure to go on. A procedure can also draft a form: Make an inspection form from it(Documents).
  • Smart Ordering — a received transfer or supplier order starts the forms set to Per delivery at that branch. When a supplier order is received, Mihwar also looks at the halal register; it never stops the delivery (Smart Ordering).
  • Labels — printing a prep label for a recipe starts the forms set to Per batch (Labels).
  • Scheduling — forms set to At each shift opening or At each shift closing follow the shifts you have sent to the team, and a late-inspection step that names whoever does it reaches the people on shift (Scheduling).
  • Checklists — the routine of every shift lives there: temperature logs, receiving and cleaning (Checklists).
  • Start pages and the daily summary — your branch’s home page shows Today’s inspections, the main dashboard counts the failed ones, and managers’ daily summary has an Inspections line (Reports).
  • AI — Build with AI and the AI summary on the Overview appear only when your organization has AI turned on (AI in Mihwar).

Who is told what

  • The branch’s managers, and head office — “Critical fail at …” when a critical step is not met (also to whoever the inspection is assigned to, never to the person who recorded it); “Inspection to approve”; “Inspection done at …”, which is also sent by e-mail when the inspection failed; “Inspection missed”; and “An inspection is coming” for an announced plan.
  • The person responsible at the branch — the result once the inspection is submitted: passed, failed or not scored, with a request to sign when the form asks for the branch’s signature.
  • The inspector — “Inspection returned to you” or “Inspection reopened — finish it again”, and “Inspections to do” when a plan makes theirs.
  • Whoever a late-inspection step names — “Inspection overdue”, as your steps say.
  • Supervisors, branch managers and head office — a halal certificate 30 days and 7 days before it expires, and a calibration that is due soon or overdue (for the device’s own branch; a device that belongs to no branch reaches every manager).

Nobody is told what they did themselves. Alerts reach the bell and, where people have set them up, their phone or e-mail. Managers also get an Inspections line in the daily summary: how many were done, how many fell below the pass mark and how many were missed.

Who may do what

  • Crew and the warehouse team — see and record the inspections that are theirs at their branch, start one by hand, add photos and notes, review and submit, and read the calibration and halal registers and the follow-ups. They can set a step aside only where the form allows it.
  • Supervisors and branch managers — everything crew can do, for every inspection at their branches, plus setting any step aside with a reason, correcting a locked critical finding, and returning, reopening, approving and sharing the report of the branch’s own inspections. They build forms and plans for their own branches, look after their branches’ calibration devices, run mock audits, and make inspector links and packets for their branches. They read Quality settings and the halal register but do not change them.
  • Head office (the owner and admins) — the same across every branch, plus forms and plans for all branches, inspecting any branch, approving head office’s inspections, the halal register, devices that belong to no branch and Quality settings. Organization admins can also see whether Quality’s background jobs are running.

Branch people see only their own branches’ inspections. Drivers do not use Quality. Your administrator can change who can do what under Roles.

Questions

I can’t see Overview, Forms or the settings.

Those are for managers: supervisors, branch managers and head office. Crew start on Inspections, which is where their work is. Ask a manager if you need one of them.

The inspection I need isn’t in my list.

The list starts on Today. Try This week, Planned or All. A form made for certain roles shows its inspections only to those roles, head office’s own inspection of your branch stays hidden until it is submitted, and a form that is still a draft makes none.

There is no form to start.

Only live forms with at least one step, meant for your role and your branch, are offered. A manager can check Where does it run? and Who does it? on the form.

My critical fail won’t save.

It needs what you did about it and a photo, and the button stays grey until both are there. If you can’t read the probe, tap I couldn’t take this reading.

I typed a reading and it’s gone.

A typed reading is kept only when you tap Save. Until then the review sheet lists the step as still to answer. Tap Save, then review.

It says Waiting for a signature, and I can’t sign.

The branch’s signature comes from someone who works at that branch, or the person named responsible, and who answered none of the steps. The approval comes from a manager who may decide on it and who is not the person who signed for the branch. Head office approves its own inspection of your branch.

The score is above the pass mark, but it says Failed.

A critical step was not met. That decides the result, whatever the score.

I need to change an answer after submitting.

Ask a manager. They send it back while it waits for signatures, or reopen it once it is final, with a reason. You change what is needed and submit again, and it keeps its reference.

A plan made no inspections.

Mihwar makes plan inspections by itself, about every 15 minutes from the plan’s start day — not when you open the page. A paused plan makes none. Check This period on the plan’s card.

Why is there a red box about the probe?

The thermometer tied to that step is overdue for calibration. Log its calibration in the Calibration register.

I can’t register a halal certificate or change a device.

The halal register, and devices that belong to no branch, are head office’s. A branch manager looks after the branch’s own devices and reads the halal register.

The inspector says the link doesn’t work.

It was withdrawn, it ran out (an hour to seven days), or it was mistyped. A manager makes a new one; a link is shown only once when it is made.

My packet is empty, or misses today’s inspection.

A packet holds submitted inspections whose due time falls inside its window. One you started minutes ago is due in an hour, so it is not in a packet yet.

A report link says page not found.

Sharing was stopped, or a newer link replaced it. An old one says it has expired, and an inspection that was sent back says it is being revised.

A follow-up or work order I expected is missing.

A critical step opens its follow-up when it is saved; every other finding opens one when the inspection is submitted. A work order for equipment opens only for a critical step, and at a branch with no machine of that kind it opens without equipment and says which kind to check.

Why does a form show words in the other language?

A form and its steps show the title in your language when they have one, and the other language when they don’t. Whoever builds the form can fill in both.

Where do I keep the daily temperature log?

In Checklists, which is built for what a team does every shift. Quality is for judging how a branch is doing. Some ready-made packs in Quality still come as daily or every-four-hours logs; for a log your team fills in every shift, a checklist is the better place.

Can an outside inspector see everything in our account?

No. An inspector link is read-only and ends by itself. It shows counts and the critical breaches for the period you chose, and never staff names, photos, signatures or other branches.

Does a mock audit count as an inspection?

No. It has no score, no reference number and no signatures. What it leaves behind is a follow-up for each gap.