Handle what comes back from site: field reports, re-visits and customer messages

Each event records what happened, on which survey (and, when relevant, which single item), who reported it, when, the note, a photo where one could be taken, and the phone's GPS position at the moment of reporting. The eight kinds:

Blocked and escalation events do not wait to be found: when the surveyor logs Could not get in, Site not ready, a question or a variation, an activity is raised immediately on the order's salesperson (or the request's manager), and every event is also posted on the survey's own chatter. The search view keeps a Blocked visits filter and group-bys per kind and per surveyor — repeated "site not ready" on one project is a scheduling signal worth reading.

A submitted survey is out of the surveyor's hands — its numbers may already feed a quotation or a production order — so going back is a request, not a right. Each request carries the survey, the requester, a fixed Reason (Items were missed, Doubt about a measurement, The customer asked for a change, Previously not ready, now ready, Drawing mismatch, since resolved, Other — a list rather than free text, because the pattern of reasons is itself a report), required Details, and the decision trail: state, decided by, decided on, decision note.

What Approve does depends on how far the survey went. A survey not yet approved is simply re-opened to In Progress. An approved survey is never re-opened — its quantities are already posted — so approval creates a linked revision survey instead: a draft copy, without signatures or posted quantities, recorded in the Revision survey field, while the original stays exactly as it was signed. Decline closes the request and posts the decision note on the survey's chatter. Surveyors cannot raise a second request while one is pending, and once the technical request's stage is folded the portal refuses new ones — at that point a return is a commercial variation, not a correction.

A surveyor in the field needs to tell the customer "I am 20 minutes away" — but free-typing to a customer under the company's name is an exposure. So the field app offers a picker over this library and nothing else; the office writes the wording once, in both languages. Each template:

A template that asks the surveyor for a value must contain {input} in its English body — saving one without it is refused with a message naming the template. Sending is rate-limited on the surveyor's side: at most six messages to one customer per survey per hour.

An event sits unresolved for days — nothing escalates it further by itself; the initial activity on the salesperson is the only automatic push. Make the Outstanding filter someone's daily screen.

A re-visit was approved but the surveyor still cannot edit the survey — the original was already approved, so a revision survey was created instead; the surveyor should open the new draft from their portal list, not the old record.

A surveyor reports the re-visit button refuses with "This job has already moved on" — the technical request reached a folded stage; handle the change commercially rather than re-opening the measurement.

A message template does not appear in the surveyor's picker — check its Active toggle, its Survey Type, and whether the survey's current state is in Send from states.