Log tasks

File on-demand records like temperature readings and cleaning logs, any time.

A log task is a record staff file whenever the work happens — a fridge temperature, a cold-brew batch, a cleaning round, a delivery spot check. Unlike a checklist, a log task has no schedule and no deadline: it can’t be “overdue”, and staff can log it as many times a day as needed. Each submission is stamped with a batch number, who logged it, and when.

Filing a log (staff)

Open the Logs tab. A switch at the top gives you two views:

• Log a task — the log tasks available to you, shown as cards grouped by department. Each card shows the task name, a short hint, and when it was last logged.
• History — everything already logged at your outlet, grouped by date.

A Department filter narrows both views.

To file a log:

1. Tap a task card. A sheet opens from the bottom and mints a batch number for this entry (you’ll see it in the header, e.g. BATCH · CB-014).
2. Fill in the fields — the same field types as checklist tasks, including the same camera-only photo rule (no gallery uploads).
3. Tap Mark done. Until every required field is filled, the button reads “Complete required fields”.

If a reading you enter is outside its safe range, the entry is flagged for review and your managers are alerted — log it honestly; the flag is the point.

Reading History

Each History row shows the values recorded as small chips, any note, the time and who logged it, and a camera marker if a photo was attached. Two things to watch for:

• A Flagged for review banner — a reading in that entry breached its safe range.
• A red ring with a priority pill — the entry has an open escalation attached.

Managing log tasks (managers)

Only managers can create and edit log tasks. In the Ops Console, go to Checklists and choose the Log task card — this opens the Log tasks list (or takes you straight to authoring if none exist yet).

The list shows each authored task with a Live or Draft badge, its department, its field count, and when it was last logged. From here:

• Click a row to open its activity drawer — recent submissions for that task.
• Click the pencil to edit it, or New log task to start one.

Authoring a log task

The authoring page has three sections:

• Basics — the task name, its department, and an optional cadence hint (e.g. “Every morning”). The hint is shown to staff as guidance only — it does not schedule the task or flag it when skipped.
• Who logs it — either Everyone in the department, or Specific people picked from that department.
• What staff record — the fields staff fill in each time. Five field types are available:

Each field has a Required switch; a log can’t be submitted until every required field is filled. A log task needs a name, a department, and at least one field before it can be saved.

When you’re ready, Publish makes it live for staff — or Save draft to keep working. Editing a published task shows Save changes instead: new logs use the updated version. Archive retires a task so staff no longer see it.

Safe ranges and escalations

A Reading field can carry a safe range — Min OK and Max OK bounds. When a submitted reading falls outside them, the entry is flagged for review and an escalation is raised to the outlet’s managers. This is how a routine fridge log becomes an early-warning system — see Escalations.

A Dropdown option can also be marked with a Raise ticket flag — staff who pick it see a warning that the choice opens a ticket for the manager.

Note: the ticket itself is not yet raised automatically from that choice. If equipment needs attention, raise a ticket from the Maintenance tab or the console Tickets page — see Maintenance and tickets.