Tracking Changes and Marking Them as Communicated
How the Needs review flag on the Coverage page shows what moved since a person was told, and how to clear it with Mark as communicated or by sending an order.
A rigger confirmed a 2pm call. The call moves to 5pm. The rigger is still secured, because they agreed to work, but they agreed to 2pm and nobody has told them otherwise. BackOps keeps that gap visible: the need stays Covered, and its Change column reads Needs review until someone deals with it.
Coverage and change are deliberately separate. A stale agreement never downgrades a reservation, so Confirmed stays Confirmed and the coverage badge stays green. The change flag carries the staleness, and a person decides whether to go back to the rigger.
What Raises the Flag
When someone is first assigned to a need, BackOps records what the slot looked like at that moment. Each time a reservation moves to awaiting confirmation or Confirmed, it records again what that person was told. From then on it compares the current details with the last record, and flags the reservation when something that matters to the person has moved:
- Who fills the slot: someone assigned, reassigned, or removed.
- The quantity held.
- A schedule block added, removed, or its start or end moved, for example "Load in moved 3h later".
- The dates the reservation shows to the organization.
- The reservation released or marked a no-show after the person was told they were on.
Forward progress does not raise the flag: moving from tentative to awaiting to Confirmed is the conversation going as planned, and Completed is its expected end. Renaming a block, editing its notes, or moving it to another area does not raise it either.
The flag compares details, not timestamps. Move a call time and then move it back, and the flag clears on its own, because there is nothing left to tell anyone. That genuine revert is the only way it clears without someone acting.
A need is also flagged when one of its orders has an unsent revision, phrased as the order name followed by "has an unsent revision". That half clears by sending the order, not from here.
See What Moved
On the event's Coverage page, select the Needs review chip in a need's Change column. The What moved panel lists each flagged filler by name, with every change in plain language and the date it is being compared with, for example "Compared with what Dana Reyes was told on Oct 3, 9:15 AM." Filled by also marks each flagged filler with Needs review, so you can see whose agreement went stale.
To find every need waiting on this, group or filter the Coverage page by Change.
When every need on the event is covered, the event's Coverage page shows Everything covered instead of the table, so the Change column is not there. Open the need from the organization's Coverage page instead to see what moved and mark it communicated.
Mark a Change as Communicated
Tell the person, or decide it does not matter
Contact them about the change, outside BackOps. If the change is not one they need to hear about, that is your call to make too.
Open the change
Mark it
Marking records the current details as what the person was told, which clears their flag. It is one reservation at a time, because each person was told their own details. When every flagged filler on a need is marked and no order revision is waiting, the need's Change column goes blank.
Nothing clears the flag on its own except a genuine revert. There is no dismiss and no clear on view, because a flag that cleared itself would lose the reminder to go and talk to the person.
Swaps and Releases
When you swap someone out or release them, their own reservation is flagged as released or a no-show "after being confirmed". That is intentional: they were told they were on, and someone still has to tell them they are not. Mark it as communicated once they know.
Reservations held by a vendor order are not flagged individually. The order's own revisions are the record of that conversation, so sending the order is what clears it.
Changes Across Events
The organization's Coverage page shows the same flag on every event, with Needs review counts on each event row. Open a need's sheet to see what moved and mark it as communicated without opening the event. Marking from the organization works on active events only.