Incidents are your written record of something that happened with a driver — a write-up, a coaching record, a safety conversation. They live under Human Resources → Incidents. If your company calls them something else, that word replaces "incident" everywhere in the app, including the menu.
How one moves
Every incident starts from a template, which is why it's worth setting templates up before your first write-up. Choosing one on the create form fills in the rest: the fields the record asks for, any prefilled wording, the label values, and whether a signature and driver comments are expected. You then pick an active driver, name and date the record, edit the text, and choose how the driver hears about it — a Viki coaching call followed by a text, or a text only — either now or scheduled for later.
From there the status chip tracks it: Not sent while nothing has gone out, Awaiting coaching while a coaching call is still pending, Pending signature once the document is with the driver, and Signed when they've signed it. Records for drivers who are no longer active read Employee inactive. When you didn't ask for a signature, those last two read Pending and Completed instead, since nobody is being chased.
What the driver does
Signing happens on the driver's phone. They get a text naming the incident with a link, open it in their browser — no app, no login — read the details and any documents you marked visible, leave a comment if you allowed one, and draw their signature. It comes straight back onto the record, and the incident downloads as a PDF for the personnel file.
Where to go next
Three articles cover this in depth. The incident management article is the day-to-day one: creating a record, attaching photos and documents and controlling which of them the driver can see, filtering the list, cloning, reminding, and deleting. The configuration article covers the templates and labels behind all of it — fields, prefilled text, and the label values you later filter and report on. And the signatures article follows a single request end to end, from what you set on the form to what the driver sees, plus how to chase a request that's stalled.
Every driver's profile also carries an incidents tab, if you'd rather come at the history from the driver's side.