Short answer

The recurrence options go down to Daily — there's no "twice a day" or "every N hours" setting. So when a job needs doing more than once a day, create one daily series per time slot and put the time of day in the title. A toilet that's cleaned morning and afternoon becomes two daily jobs — "morning clean" and "afternoon clean" — each recurring every day. Three toilets cleaned twice a day is six daily jobs in total. Build them in one go with a routine (bulk creation) rather than one at a time.

Detail

One series per time slot

Daily is the shortest cadence available. To get two (or more) occurrences in a day, you create a separate daily series for each occurrence and distinguish them by the time of day in the title:

  • "Gents — morning clean"
  • "Gents — afternoon clean"

Each is its own daily recurrence, so the operative sees both jobs in their task list every day and signs each one off independently. The pattern scales: a toilet cleaned four times a day is four daily series.

Build them with a routine (bulk creation), not one at a time

If you're applying the same pattern to several assets (e.g. Gents, Ladies, Disabled), use a routine to bulk-create rather than building each job by hand:

  1. Select the assets in the asset list.
  2. Create a routine over them.
  3. Set the task type to Job — a clean is a Job, not an Inspection. There's no default, so this has to be set explicitly. Set it on the first row and copy it down to the rest.
  4. Set the frequency to Daily, add the spec in the description, and assign each row to the contractor / cleaner (an assignee is required on every row).
  5. The asset name pulls into each task title automatically — append "morning clean" (then repeat the routine for "afternoon clean").

So "twice-daily cleans across three toilets" is two routines (morning, afternoon), each generating three daily jobs.

How granular to make the assets

Match the asset granularity to how closely you want to monitor:

  • Whole block — one asset for the toilet block, one cleaning job per slot. Simplest.
  • Per gender / per cubicle — separate assets for Gents, Ladies, Disabled (and individual cubicles where you need that level). Worth it when you want photo proof or per-area accountability — e.g. a seafront block with five individual cubicles becomes Cubicle 1–5.

Proof it was done

The cleaner marks the job done on the mobile app and can add one photo to evidence the clean (this replaces the job's image only — the asset's own photo is untouched). If they spot a fault while cleaning (broken hand dryer, cracked seat) they can raise a defect from the job, which flows into the council's task list.

Watch-outs

  • There is no sub-daily recurrence. Don't look for a "times per day" field — model each occurrence as its own daily series.
  • Task type is mandatory and has no default. For cleaning/bin/maintenance work choose Job on the first row and copy it down to the rest. The routine won't save until every row has a type and an assignee.
  • Put the time of day in the title. It's the only thing distinguishing the morning and afternoon series in the operative's list — without it they look identical.
  • Two series, not one with two assignees. Don't try to fake twice-daily by assigning one daily job to two shifts; create the two series so each clean is signed off separately and the record shows both happened.