Live ops
Find out while the trip is still fixable.
The gap between the field and the office is where an operator’s worst days come from: the manager knows something went wrong, and the office learns about it a week later from a review. Triprant gives the office a live view of every running departure, a private log per trip, and an incident queue that records who picked it up.
While it is running
What the office can see and write.
- Every active departure on one screen
- Not one trip at a time. The office view is shaped around “all of our trips that are running right now”, because that is the question somebody at a desk is actually asking.
- Positions that admit their own age
- A fix older than a few minutes is shown greyed out with how old it is, so a stale point is never mistaken for a live one. Knowing a position is unreliable is worth more than the position.
- A private log, per trip
- Notes, incidents, follow-ups and photo attachments, written by the manager in the field or the office, and readable only by your staff. Several attachments per entry, because an incident note is not a chat message.
- Incidents with an owner and a trail
- A traveller can report a problem — a safety or service issue, a photo of themselves, a billing question. Each one moves open → acknowledged → resolved, and every transition records who did it and when.
- Acknowledgement is a step of its own
- So the person who reported it is not left wondering whether anyone saw it, and so an admin has something concrete to hold a coordinator to rather than one final status.
- A photo takedown acts first
- A traveller reporting a photo of themselves has it hidden immediately, before any staff member reads the report. Consent is honoured, then triaged — the report becomes the request to restore it or make it permanent.
The trip log
Not the journal the travellers are reading.
The trip journal
The shared record of the trip — stops, photos, what happened. Visible to the people on the trip and, if the trip is published, to followers and to anybody with the link. It is meant to be read.
The staff log
A separate record on a separate table, gated on working for the agency. An incident note cannot leak into a published trip page, because it was never in the thing that gets published.
The trip manager in the field writes to it and the office reads it — deliberately, so the person who was actually there is the one recording what happened, rather than relaying it to somebody at a desk who writes it down.
What you can promise a traveller
The limits are the feature, not the small print.
Somebody will ask whether you are tracking them. These are the answers, and each one is a behaviour the product implements rather than a policy it states.
- Sharing is the traveller’s switch, not yours. Location sharing is off until a person turns it on, for the one trip they turned it on for. There is no agency setting that enables it on somebody’s behalf.
- It only runs while the trip is running. Sharing cannot be switched on for a departure that has not started. Turning it off, though, is ungated in every state — withdrawing consent must never depend on what status the trip happens to be in.
- Off means deleted. Switching sharing off removes the stored position rather than leaving a last-known point on the map for you to keep looking at.
- The trip ending ends the supervision. When a departure is completed, the stored positions from it are deleted. Your responsibility for those people is over, so the data from it does not outlive it.
- Seeing does not require sharing. A traveller can watch the group without broadcasting their own position — which matters most to whoever is on 4% battery.
The week-later surprise is a choice.
Run the departure where the office can see it, and the incident becomes a note with an owner instead of a review with a story.
An agency is created from an ordinary Triprant account, and reviewed before it goes live.