Short answer

The task your team sees on the phone is titled after the asset. If a checklist is attached, its name is added after the asset name, so a task reads Basket Swing - Swing Check. With no checklist, it is just the asset name.

That makes the asset name the single most-read piece of text on your account. Name assets for what the thing is, not where it is, and put your own reference codes in the name if you have them.

How the title is built

  • Asset name only, where no checklist is attached. This is the most common case by a wide margin.
  • <Asset name> - <Checklist name>, where one is. Real examples from live accounts: Goal Post - Simple Checklist, Wooden Play Tower - Multi Play Unit Check, Picnic Table - Visual Inspection for Outdoor Asset.

So the part you control is the first half, and you control it by naming the asset well.

The title is taken at the moment the task is created. Renaming an asset later does not retitle tasks that already exist. It only affects tasks generated from then on, which is a good reason to settle naming before you build routines.

How to name assets well

Name the thing, not the place. A bin called "Jubilee Park Play Area" produces a task reading Jubilee Park Play Area - Simple Checklist for what is actually a bin. Call it "Green Litter Bin" and the task makes sense at a glance.

Use the location tag for where it is. The location tag already shows on the task card in the field, so repeating the site in the name reads twice over: Ashwood Play Area - Ashwood Play Area. Keep the name for a local disambiguator when several identical things share one site, like "near the toilets" or "middle bin".

Put your operational codes in the name. Many councils already number their bins, lamp columns or grit bins (CS001, CS002 and so on). Put the code in the asset name and it flows into every task that asset generates, so the operative sees CS017 - Bin Check and can match it to the thing in front of them. This matters most for items that look identical: every wheelie bin, every grit bin, every defib cabinet. Without a unique code the field worker cannot tell which row of the list belongs to which physical object.

A code on its own is not enough. If the name is just DG25 and there is no checklist, the crew see a task called DG25 and nothing about what to do with it. Either attach a checklist, or make the name carry the meaning, for example DG25 Dog Bin.

Keep local names where the team uses them. If everyone calls it "the Mugger" or "the BruBowl", that is what should be on the phone. Recognition beats correctness here.

Watch-outs

  • Ambiguous names cost time every single day. A field worker scrolling for "the bin near the entrance" has to open each record when everything is named after the park.
  • ⚠️ Do not run AI auto-classify in bulk to tidy up names. It is good at asset types and it replaces the name with a generic one, so on a register that already carries your codes or local names it will undo them. Use it when capturing new assets, and correct names afterwards. See What does AI auto-classify do?.
  • Settle naming before building routines. A routine can generate many months of tasks in one go, and all of them keep the name the asset had at the time.