Checklists

Checklists is where a branch does its routine checks on a phone: opening, closing, cleaning, fridge temperatures, deliveries. Head office or a manager writes a checklist once and says where and when it runs, and Mihwar makes the run for each branch at the right time. The crew answer it step by step, a critical step that goes wrong tells the managers and opens a follow-up, and every finished run is kept as a record you can show an inspector. Judging how well a branch is doing is a different job: that is an inspection in Quality.

One run of a checklist, from the schedule to the record
On scheduleThe run opensEach branch gets its run at the time you set.
CrewDone on the phoneStep by step, with readings and photos.
Critical step failsA follow-up opensThe managers are told at once.
Colleague or managerSigns where askedThe finished run is signed before it closes.
Head officeKept as a recordHistory, and a signed packet for an inspector.
A run nobody finishes in time is marked Missed, and the managers are told.

Find your part

Finding today’s checklists

Open Checklists. Today lists the checklists meant for you at your branch, the most urgent first. The line at the top says what is left. Each row shows the name, a label, when it is due, the branch and a button. The label says where it stands:

  • Due — open now. Overdue — its time has passed, but you can still do it. In progress — someone has started it.
  • Opens and a time — not open yet. You can read the steps; recording starts at that time.

The button is Start, Continue once you have started, or View for one that is not open yet. Two folded lists at the bottom hold what is closed: the checklists completed today and the ones missed today.

Missed is not the end. Open the checklist from the missed list and record what was done: it is marked Recorded late, so an inspector sees that it was done, and when. You can do this until the end-of-day seal (by default 02:00 the next morning); after that a manager has to unlock it first. You see a checklist when it is yours: it is assigned to you, it is for everyone at the branch, or it is for your role. If one you expect is not there, or Today says No checks scheduled for you today and that seems wrong, tell your manager.

On your branch’s home screen, Your next check shows the one to do next, and the checklists you missed recently are listed with Record late.

Starting a checklist yourself

Most checklists appear by themselves at their time. To do one that is not on your list, start it by hand. It is a one-off run outside the schedule, and the scheduled runs carry on as normal.

  1. In Tools at the bottom of Today, tap Start a checklist. (On a laptop it is a button at the top of Today.)
  2. Choose the checklist. Only live checklists you may do are listed. Check Where: if you work at one branch it is already set.
  3. Under Due choose In an hour, By the end of today or At a time today. A time that has already passed today is refused.
  4. Tap Start and open it. The checklist opens at once, in your name.

A manager also sees Who does it: Me, or a colleague of that branch, those on shift first. A checklist that is still a draft, or paused, cannot be started.

Doing a checklist

Tap Start on a row. The checklist shows one step at a time, with Step 3 of 10 at the top and a bar that fills as you go. Answer a step and the next one that still needs an answer opens by itself. Skip for now moves on without answering; go back with the arrow for the previous step. Tap the step counter to see every step in a list, and tap it again to go back to one step at a time (a bigger screen also has List and Cards buttons). If you leave half way and come back, it says Picking up where you left off and opens the next step that is still open.

  • A tick. Tap Mark done.
  • Pass or fail. Tap Pass or Fail. If the author asked for a photo when it fails, you take the photo first, then tap Save as a problem.
  • A temperature or a number. Use the minus and plus buttons, or type it. The first tap starts in the middle of the allowed range, and holding a button moves faster. The allowed range is shown. Tap Save & continue.
  • A reading outside the limits. Mihwar never refuses a reading: it records what you measured. On a step that is not critical it says the reading will be saved as a problem; tap Save as a problem. A critical step is explained in the next part.
  • Text, a choice, a date or a time. Write or choose, then Save & continue. A choice step says whether to select one or all that apply.
  • A photo. Tap Capture photo, then Mark done. Every photo carries a strip with the branch, the date and time, and your name.
  • A signature. Sign across the box and tap Sign & continue. A tap, or a very short line, is not a signature.

On any step you can tap Add note or photo. Tap Why? to read why the step matters, with a reference link or an example photo when the author added them. A step that points to a procedure shows Read the procedure.

A saved step turns green and says who saved it and when. You cannot change it yourself: a manager can Reopen to edit it, with a reason. A note you wrote shows under the label “Follow-up”; it is only your note. A follow-up that was really opened shows as Linked follow-up.

When you save the last step, the summary opens by itself: how many checks were done, how many passed, how many problems and how many follow-ups opened, and which checklist is due next. Tap See what was recorded to read it. If you skipped a step, or a required photo is missing, tap Finish and Mihwar names what is left.

When a critical step goes wrong

A critical step has a yellow bar: If it isn't right or can't be done, your manager gets a follow-up. It goes wrong when you tap Fail, a reading is outside the limits, or you tap I couldn't do it (or, for a reading, I couldn't take this reading). A red card opens: Fix it now — your manager will be told. (If you could not do the step or take the reading, the card says that instead.) If the author wrote what to do when the step fails, it is shown at the top of the card.

  1. Say what you did

    Tap what you did, such as Moved the food to another fridge, Adjusted the setting, Threw the food away, Told the manager or Called maintenance — or write it in your own words. It needs at least 10 letters.

  2. Take a photo

    Tap Take a photo of the problem.

  3. Save

    Tap Save and tell my manager. If you tapped by mistake, tap I entered it wrong instead.

It is saved at once, even before you finish the rest of the checklist. A follow-up opens with your note and photo, and says which checklist and branch it came from. The managers of the branch, and the person the checklist is assigned to, are told straight away; you are not, because you saw it. If the step is tied to a piece of equipment, a work order opens as well. The saved step shows Linked follow-up and, when there is one, Work order.

Steps that need a signature or a PIN

A procedure to sign first. Some steps say Sign the procedure to go on. Tap Read it and sign. The procedure opens: read it to the end, then tap Sign: I’ve read it (some ask a few questions first). The step then completes by itself. If the procedure is changed in a way that asks everyone to sign again, you are asked again; a small fix keeps the signatures already given. A step can also need a certificate: only people whose signature on the document is current can do it, and when it has run out you read it again and sign.

A step for one person. A step can be given to a colleague. It says Assigned to their name and PIN required. Whoever has the phone taps the step, and a pad asks for that colleague’s four-digit PIN. The step is then saved under their name. It is the same PIN as on the clock-in screen; each person sets it in Security settings, or a manager sets it. After five wrong tries the PIN is locked for 15 minutes. Checking a PIN needs a signal. A wrong PIN, no PIN set and a locked PIN all say That PIN doesn’t match: ask the colleague to check theirs.

Signing a finished checklist

Some checklists ask for a signature on the finished run: a witness, a supervisor (a manager), or both. When every step is answered the run says Waiting for a signature, and the person who did it sees Your part is done. It closes once it is signed. Anyone allowed to sign opens the run — a manager from Review, a colleague from History, where it says Waiting for a signature — and taps Sign as witness or Sign as supervisor, signs across the box and taps Sign & continue. The run closes when the last signature is in.

  • The person who signs must not have recorded any of the steps.
  • When both are asked for, the witness and the supervisor are two different people.
  • A supervisor’s signature has to come from a manager: a supervisor, a branch manager or head office.

Working without a signal

Your answers are saved on the phone first and sent in the background, so a weak signal does not stop you. A small pill at the top shows Offline and how many answers are queued, then Syncing, then All synced. Keep the app open until it says All synced.

  • Works without a signal: answering the steps of a checklist you already opened, including a critical step. It is sent when the signal comes back, and the follow-up opens then.
  • Needs a signal: starting a checklist, signing a procedure, a colleague’s PIN, signing a finished checklist, and everything a manager does. A tick on a step that needs a signature first is checked when it reaches Mihwar, and comes off again if the signature is missing.
  • If you are signed out meanwhile, the answers wait: sign in again and they are sent. On a phone that several people use, wait for All synced before the next person signs in, because waiting answers are sent as whoever is signed in when the signal returns.

Seeing how the day is going

On Today a manager sees six counts across the branches: Done today, Problems today, To do, Overdue, Missed and Awaiting signoff. Tap a count to open the list behind it. On a laptop Today also shows Needs action now, Branches today (how many each branch has done, and how many are overdue, missed or have a problem) and Recent activity. Tools on a phone, and Go to on a laptop, lead to Templates, Awaiting signoff, Packets and History.

Live status is the other view of the same day: every run across your branches, in groups — Overdue, Due today, In progress, Missed and the ones completed today, folded. Each row shows how far it is and the badges Critical fail, Awaiting signoff and Locked. Pick a branch or a checklist at the top, or Mine for the ones assigned to you. It updates every 30 seconds.

Reviewing what needs a decision

Review has three tabs. You see the branches you manage, and you can narrow them with Location.

  • Failed. Runs where a critical step failed, each with the failed steps, the note, the photo (View photo evidence), who recorded it and a link to its follow-up. Tap Open run to read the whole run. Tap Acknowledge — with a note if you like — to say you looked and take it off the list. Acknowledging does not close the follow-up; that stays open until what was done about it is written.
  • Missed. Runs whose time ran out unfinished. Each has Open run, to record what was done late (a run sealed overnight is unlocked first), and Acknowledge; on one missed run it opens the same box as for a failed run, titled “Acknowledge critical fail”, with an optional note. To clear several at once, tick them and tap Acknowledge with the number selected: you must give a reason (the branch was closed, staff were out), and it is saved on every one. When the same checklist is missed more than three times in a week at a branch, a line asks Open follow-up.
  • Awaiting signoff. Finished runs waiting for a witness or a supervisor. Tap Open run to sign. It shows today’s first; choose All time to see older ones too. A note may say that an older run sealed overnight needs a manager to unlock it first; it does not — open the run and sign.

Assigning, skipping and reopening a checklist

When a manager opens a run, the bar at the top holds the tools. Each one needs a reason or a person, and each is written in the run’s record.

  • Assign — choose who does this checklist. Only people who can do checklists at that branch are listed, those on shift first. They are told, and the run says Assigned to you on their phone. Only a run that is still open can be assigned.
  • Skip — for a branch that is closed, a holiday, a renovation. Write a reason of at least three letters. A skipped run does not count against compliance, is not reported as missed, and its reason shows in History and on the inspector’s packet.
  • Reopen to edit — on a saved step, to correct it. Write why, at least five letters. The old value is cleared, the reason is recorded, and the packet shows it.
  • Unlock with reason — see below.
  • More opens Activity (who did what, in order), and for managers Audit replay and Verify record, which check that nothing was changed after it was signed.

Sealed at the end of the day. A run due on an earlier day is sealed overnight, by default at 02:00. It says Checklist locked: its answers can no longer change, and the crew are told to ask a manager. A manager taps Unlock with reason (at least five letters) to correct something. A run that is waiting for a signature is not sealed overnight, and one that was sealed first still takes its signature.

  1. Missed, but the work was done

    Anyone who can open the run can still record it, until it is sealed overnight; after that a manager unlocks it first. It is marked Recorded late, and the inspector’s packet marks it too. Acknowledge it in Review only if you want it off the Missed list without recording anything.

  2. Cancelled or skipped

    Nothing more can be recorded on it. The reason, for a skipped run, stays in the record.

History and the CSV file

History lists the runs you may see, newest day first. At the top: Total, Completed, Missed and Completion rate. Pick a status, or Filters for Location, Template, From and To; it starts with the last 14 days. Each row shows the checklist, its state, the branch, when it was due and done, who it was assigned to, and how many steps are done. Tap View report for a finished run or Open run for one that is still open. The date boxes take Gregorian dates.

Export CSV and Export PDF make a file of up to 5,000 runs, newest first, with one line for each run: the checklist, its state, when it was due and done, who it was assigned to and how many steps were checked. They follow the status you picked, not the Location, Template or date boxes, and the CSV does not say which branch a run was at, so filter the file afterwards. With the Skipped status picked, they do not work.

Comparing branches

Performance shows how the branches are doing over 7 days, 30 days or 90 days: for each branch the runs, the completion, the on-time share, the missed runs, the critical fails and a risk score. The score weighs missed runs and critical fails, and Branches at risk counts the branches at 20 or higher. Tap a column to sort, or a branch to open its Live status.

Trends (the other view of Performance) adds Total runs, Completion rate, On-time rate and Missed against the period before, the Top missed items, the Repeat fails (a step that failed three times or more), the Top performers and this week against last week.

Making a checklist

Open Templates (in the strip across the top of the app, or in Tools on Today). Managers see it; it lists every checklist with its state. There are three ways to make one.

  • New checklist. Say four things: its name (English, Arabic or both), when it runs, where (every branch, or the ones you tick) and who does it. Tap Create and add steps: the editor opens on a draft with the first step ready.
  • Browse packs. Ready-made starting points: food safety (HACCP), opening, closing, receiving a delivery, cash count, a weekly deep clean, a vehicle check, and packs for the food regulators of Saudi Arabia, the UAE and Jordan. Tap Use this template and it is copied into your list as a draft, in English and Arabic.
  • Build with AI. It shows only when your organization has turned on AI for checklists. Describe the routine, bring the checklist you use today (a PDF, photos of the paper or a spreadsheet), or open a procedure in Documents and choose Make a checklist from it in its More menu. The AI writes it in English and Arabic; change anything, or ask for a change in your own words, then create it — again as a draft.

  1. Check the draft

    A new checklist is a Draft: it makes no runs and the crew do not see it. Tap Edit, look at the steps, and check when and where it runs.

  2. Save

    The editor has one Save for everything: a pill says what is Unsaved. If you leave with unsaved changes it asks first — but a phone’s Back gesture leaves without asking, so save before you go back.

  3. Go live

    Tap Go live and confirm. It needs at least one step. Mihwar makes today’s runs where the time has not passed yet, and from then on at each time you set.

Each checklist on the Templates page shows its state — Draft, Live with its version, Paused or Archived — when it runs, where, for whom, and how many of its steps are critical. A live one has Launch now, which starts a run right away, and Pause; the card’s menu has Duplicate, Version history, Archive and Delete. At the top are Generate today's runs now, Browse packs, Build with AI and New checklist.

When a checklist runs

In the editor, When & how does this run? (tap Show) holds the schedule.

  • Frequency — Daily, Weekly (pick the weekdays), Monthly (pick the day, or the last day) or Custom (cron), for a schedule written as a cron line.
  • Due by — the time it is due. Left empty, it is due at 23:59, and the card says so.
  • Due several times a day — tap Add a time for each, for example a fridge log at 08:00, 12:00, 16:00 and 20:00. Each time is its own run with its own record. It opens an hour before its time. Times are at least 15 minutes apart, up to 24 a day.
  • Late entries accepted for (minutes) — after the due time the run is late but can still be done; past this it is marked missed. It starts at 15.
  • Opens at (optional) — the crew cannot start before this time. Empty means the start of the day. Marked missed at (optional) — a fixed closing time instead of the late minutes; it must be after the due time. A checklist due several times a day uses neither.

Next runs shows the next three, so you can check the schedule before you save. Mihwar makes the day’s runs every 15 minutes. Generate today's runs now on the Templates page does it immediately, and is safe to tap again. When a checklist makes no run, it says why: it is a draft, paused or archived; it has no steps; today is a day you're closed; nothing is due around now; or today’s run was already due — a checklist that goes live after its time has passed starts with the next run. Saving new times also moves today’s runs that have not started.

Days you're closed is set once for the organization in Organization settings. A daily checklist makes no run on a day you tick. A weekly checklist runs on the weekdays you picked for it, and a monthly one on its day, even when that is a day you are closed, because you chose it on purpose. None is ticked at first, because food service opens every day. Mihwar has no holiday calendar: to leave out a holiday, skip that day’s runs with a reason.

Which branches, and who does it

Where does this run? With nothing ticked, a checklist runs at every branch, branches you add later too. Tick locations to limit it, for example to the stores that serve breakfast, or to add a warehouse or a commissary — those run a checklist only when you tick them. A branch manager ticks among her own branches, at least one.

Who does it? Tick the roles that do this checklist at each branch, for example staff for the opening check and supervisors for the cash count. Only people in those roles, and managers, see it on their list and can do it. Those people get the “due soon” reminder and the escalation steps for whoever does it; with Scheduling, only the ones on shift at the due time (all of them if nobody is). With nothing ticked, everyone at the branch sees it and the managers get the reminders. A run given to one person with Assign is theirs whatever the roles are.

Writing the steps

Open a checklist with Edit. Add step adds one; tap a step to edit it; drag the handle, or use Move up and Move down, to reorder. The Phone preview shows the steps As your crew sees it and follows the step you are editing.

  • Title in English and Title in Arabic — fill in at least one. Each person reads their own language, or the other when theirs is empty.
  • Step type — Checkbox, Pass / Fail, Number, Temperature, Text response, Photo required, Signature, Single-select, Multi-select, or Date / time. Number and Temperature take a Minimum, a Maximum and a unit; choices take Choices (one per line); Date / time takes What to record; Pass / Fail takes Require a photo when it fails.
  • If it fails — what to do — in English and in Arabic, for Pass / Fail, Number and Temperature steps. The crew see it the moment the step fails or reads out of range, for example “Move the food to another fridge and tell the manager”.
  • Critical step — failing it opens a follow-up — only Pass / Fail, Number and Temperature steps can be critical. Keep it for a failure that would stop service or make you refund a guest: a critical step that is not met opens a follow-up (in a part the crew repeat, the first copy that is not met).
  • More options — a description; the section the step belongs to, and The crew can add this section again during a run, for example once for each item received; Why this matters, up to 120 letters, which the crew read under Why?; Weight in the score (1–10); Reference link; the Per-item assignee, whose PIN is then needed; and a good and a bad example photo.
  • Links to other apps — Equipment checked, Procedure to sign first (with Ask for a signature on it before this step), Certificate needed, Stockout signal and Print the dish’s label. See where Checklists connects.

A step that already has answers is not deleted: Retire step keeps it on past runs and removes it from future ones. Why this matters, the choices and the units are written once, in one language, so the crew read whatever language you typed. A step cannot depend on an earlier answer: every step shows on every run.

Signatures, reminders and escalation

In the same When & how does this run? box, Require a witness signature (a second person must sign before the run can complete) and Require supervisor sign-off (a manager approves the finished run before it counts as complete) can each be turned on. Who may sign, and what the crew see, is in signing a finished checklist.

An hour before a run is due, the people who do it, and the branch’s managers, are told it is due soon. For a run that is overdue, Escalation picks a ladder:

  • Crew first — after 15 minutes remind whoever does it; after 45 minutes alert the branch manager.
  • Food safety (strict) — after 15 minutes alert the branch manager; after 30 minutes alert head office and open a follow-up.
  • Standard daily — after 30 minutes alert the branch manager; after 2 hours alert head office.
  • Light weekly — after 24 hours remind the branch manager.
  • No escalation — an overdue run only shows on Today, and its branch managers get an alert in the app once it is missed. There is also an advanced box for people who write their own steps.

Changing a checklist that is live

You edit a live checklist in place. Every saved change that alters it is kept as a new version, and the checklist’s Version history lists each version with what was added, changed or removed. Runs that have not started follow your change straight away; runs already started keep the steps they started with; a step that has answers is retired. To go back, put the steps back and save: that becomes the next version. Past packets still verify.

  • Pause stops new runs; the ones already made stay. Resume starts them again.
  • Archive stops new runs and takes it off the active list; its past runs stay for inspections. Restore brings it back.
  • Duplicate makes “Copy of” the name, as a draft that is not running. Delete works only on a checklist that has no runs.

Signed packets for an inspector

A packet is a PDF of the finished runs of one checklist over a period, signed so that any later change shows. Packets lists them. Managers tap Generate packet, or one of the quick choices such as Last 30 days · HACCP, pick the checklist, the branch (head office can choose all branches) and the dates, and tap Generate. Mihwar signs every finished run in the period and makes the PDF. A branch manager picks one of her own branches.

  1. Copy the link now

    The packet is ready with a share link and a QR code. Copy it now — it is shown only this once. The link works for 72 hours and needs no sign-in. Print the QR for the audit file, or send the link to the inspector.

  2. Lost the link?

    Open the packet and tap New share link: the old one stops working. Stop sharing ends it without touching the signed PDF.

  3. The inspector checks it

    The inspector sees the totals — completed, critical fails, missed — and can tap Verify hash to have Mihwar re-check that nothing was changed, and download the signed PDF. An expired or stopped link says the packet is not available.

Open a packet to see its Audit chain and tap Verify chain; it also marks the runs Recorded late and those Edited after unlock. The PDF is printed in English and Arabic together, and the inspector’s page opens in the language of the inspector’s browser.

Is the scheduler running?

Scheduler health is for the owner (Tools on Today). It shows when the scheduler last ran. It should run every 15 minutes. If the page says it is overdue, new runs may not appear and missed runs are not marked: tell Mihwar support. The page also shows whether the queue that opens follow-ups and work orders is draining.

Where Checklists connects

  • Follow-ups — a critical step that fails opens a follow-up at once, with the reading, the note and the photo, and says which checklist and branch it came from. The strict ladder also opens one for a run that is badly overdue, and Review offers one when the same checklist keeps being missed. Acknowledging a failed run in Review never closes its follow-up (Follow-ups).
  • Work orders — a critical step tied to a piece of equipment opens a work order when it fails, named “Failed check” and the step. At another branch it goes to that branch’s own equipment of the same type. If a work order is already open on that machine, the failure is added to it. When its fix is checked, the run’s record says so (Work orders).
  • Documents — a step can ask for a procedure to be signed first, or for a current signature on a certificate document; the signature is kept on the document. A manager can turn a procedure into a checklist from the document (Documents).
  • Labels — a step that makes a dish can print its label when it is ticked and passes, on the branch’s network printer, or the label waits on the branch’s list of labels waiting to print (Labels).
  • Smart Ordering — a stockout step, when it is ticked, flags the branch as out of that item for the rest of the day, and the demand forecast learns from it (Smart Ordering).
  • Scheduling — reminders, and the escalation steps for whoever does it, go to the people on shift at the due time, by the shifts sent to the team. A colleague’s PIN on a step is the same PIN as on the clock-in screen (Scheduling).
  • Quality — an inspection is answered the same way, on a phone, but it judges how a branch is doing and gives it a score. Routines the team does every shift stay here (Quality).

Who is told what

  • A critical step fails — the managers of that branch (supervisors and branch managers there, and head office) and the person the run is assigned to, within seconds. Never the person who recorded it, who saw it on the screen.
  • A run is due soon — an hour before, the people who do it, even if they muted Checklists, and on the phone if they turned phone alerts on. The branch’s managers see it in the app.
  • A run is marked missed — the person it is assigned to and the branch’s managers (“Checklist overdue”). A ladder, if the checklist has one, sends “Checklist needs attention” before that.
  • A run is given to you — “Checklist assigned to you”.
  • A run is finished — late: the branch’s managers and the person it is assigned to. With a failed critical step: the person it is assigned to, if someone else finished it. On time: nobody, except the person it is assigned to when someone else did it.
  • Every morning — people who run branches get the daily summary, with a Checks line for yesterday: how many were done of those due, how many missed, how many critical fails.

Nobody is told what they did themselves. Alerts reach the bell and, where people have set them up, their phone or e-mail, each in the language the person reads. How to choose is in Alerts.

Who may do what

  • Crew and staff — see and do the checklists meant for them at their branch, start one by hand, record a critical step, sign a procedure, sign as witness when asked, read History, and add a note or photo. They cannot make checklists, review, or generate packets.
  • Supervisors and branch managers — everything the crew can do, and every checklist of their own branches: Live status, Review, assigning, skipping, reopening a step and unlocking a sealed run, signing as supervisor, packets, Performance and Trends, and making and changing the checklists that run only at their own branches.
  • Head office (the owner and admins) — the same across every branch, plus the checklists that run at every branch, packs, AI, and packets for all branches. Only the owner opens Scheduler health.
  • Drivers — Checklists is not for drivers; they go to their deliveries.

Branch people see only their own branches’ runs, and the crew only the runs meant for them. Your administrator can change who can do what under Roles.

Questions

I can’t find today’s checklist.

It may be for another role or another branch, or it may not be live yet: a draft, a paused or an archived checklist makes no runs. Managers: open Templates, check the state, Where does this run? and Who does it?, and tap Generate today's runs now, which says why a checklist made none.

It says it opens later, and I can’t tick anything.

The checklist has an Opens at time. You can read the steps now; recording starts at that time.

It says Missed, but we did the work.

Open it and record what was done. It is marked Recorded late and nothing is lost. After the end-of-day seal a manager has to unlock the run first. If the branch was closed, a manager can acknowledge it with a reason in Review.

I can’t change a step I already saved.

A saved step is locked. A manager taps Reopen to edit and writes why. A run from an earlier day is sealed; a manager taps Unlock with reason first.

The save button on the red card does nothing.

A critical step needs what you did — at least 10 letters, a tap on one of the answers fills it — and a photo.

It asks me to sign something before I can tick a step.

The step needs your signature on a procedure first. Tap Read it and sign, read to the end and tap Sign: I’ve read it.

The PIN pad says it doesn’t match.

The PIN is wrong, or the colleague has not set one yet, or it is locked for 15 minutes after five wrong tries. They set it in Security settings, or a manager sets it.

I can’t sign the finished checklist.

You recorded one of its steps, or you already signed as witness and the supervisor must be someone else, or you are not a manager and it needs a supervisor. Ask another person.

We asked for a signature, but a run closed without it.

A run where a critical step failed is not held for signatures: it closes as Failed and goes to Review. Signatures are asked for on runs where every step is answered and the critical steps are right.

An answer shows a later time than when I tapped it.

You recorded it without a signal. The time on an answer, and on its photo, is when it reached Mihwar.

I tapped “found a problem” on Today and got an error.

That list is for managers. Your manager sees every problem you recorded.

A run stays on the Failed tab after I tap Acknowledge.

Acknowledge works on a run where a critical step failed, and on a missed run. A run that only has a problem on a step that is not critical is listed too, but cannot be acknowledged.

I made a checklist, but no runs appear.

It is a draft until you tap Go live. After that, runs appear at their time; if today’s time had already passed, the first run is tomorrow’s. Generate today's runs now says why a checklist made none.

A branch manager can’t edit a checklist.

It runs at every branch, or at branches that are not hers, so it says Set by head office. She can run it, or tap Copy for my branches and change the copy.

No alert came for a critical fail, or no work order opened.

The alert goes to the managers of that branch and the person the run is assigned to, not to the person who recorded it. A work order opens only for a critical step with Equipment checked, when Work orders is on. Both are done by the events queue: the owner can see on Scheduler health whether it is draining.

Three copies of a repeating part were not met, but only one follow-up opened.

A follow-up opens for the first copy that is not met. The others are in the run’s record, and Review lists each one on the run, but they do not open a follow-up of their own and nobody is told again.

Can a step show only after another answer?

No. Every step shows on every run. Make the step that must never be passed over critical.

Can a checklist skip public holidays, or only run in Ramadan?

No. Mihwar has no holiday calendar and no Ramadan-only checklists. A daily checklist skips the days you’re closed; for a holiday, skip that day’s runs with a reason.

Can a step ask for a barcode scan or a file?

No. A step can ask for a photo, a signature, a reading, text, a choice, or a date or time.

Can I make a checklist that only runs when someone starts it?

Any live checklist can be started by hand with Start a checklist, but the editor has no switch to stop it running on a schedule. The vehicle pre-trip pack is the exception: it only runs when it is started.

Why does Export CSV ignore my filters?

It follows the status only. See History and the CSV file.

The inspector’s link doesn’t work.

It expired after 72 hours, or you made a new link, or sharing was stopped. Open the packet and tap New share link.

Will my crew read the checklist in Arabic?

Titles, descriptions, sections and the “if it fails” text have an English and an Arabic box, and each person reads their own language. Why this matters, the choices and the units are written once.