Before you write up your first driver, spend ten minutes on the two building blocks behind every incident: templates, which decide what a write-up asks for and how it's delivered, and labels, the tags you'll later filter and report on.
Where the configuration lives
Open Incidents from the sidebar, then press Configure templates at the bottom right of the page. You'll land on a page subtitled "Configure your templates and labels," with a Templates section on top and a Labels section below it. Everything here is company-wide — what you set up is what every manager sees when they create an incident. If your company uses its own word for incidents, these pages use that word throughout.
Labels
A label is a named category with a fixed set of colored values — Severity, say, with values Low, Medium, and High. Each label card shows its name and how many values it holds.
Press Create Label to add one. Give it a Label Name (it has to be unique), then build the list under Values, described as "Define what potential values this label can have." Type the value, pick its color, and add it. Both the text and the color have to be unique within that label, so every value stays distinguishable; double-click a value or use the pencil icon to rename or recolor it.
On an existing label card, the pencil icon opens it for editing, the copy icon opens a duplicate you can save as a new label, and the trash icon deletes it. There's no archive: deleting asks you to confirm and warns that it can't be undone.
New companies start with three labels already created for you: Occurrence (1st, 2nd, 3rd), Severity (Low, Medium, High), and Category (Safety, Quality, Attendance). Rename them, recolor them, or delete the ones you won't use.
What labels actually drive
Labels are how you slice your write-up history later. The Incidents page has a Label filter that groups every value under its label name, so you can pull up every Severity: High incident in a date range. Label values also show as colored chips in the incidents table, on the incident's detail page, and on the Incidents tab of a driver's profile, and they're listed by name and value in the PDF you download. Keep the value lists short — a label with twenty values is a filter nobody uses.
Templates
Press Create Template to build a write-up type. A template holds:
Template Name — unique, and what managers pick from the Template dropdown when creating an incident.
Employee signature required — Yes or No.
Allow employee comments — Yes or No. When on, the driver can type a response before signing.
Fields — the questions the write-up asks. Each field is a name plus optional prefilled text: "Define what information to include in this template. Prefilled text is optional and can be edited when the template is used." A new template starts with two fields, Description and Consequences of failure to improve; keep, rename, or replace them. Field names must be unique within the template.
Labels — pick which labels apply from the "Select labels" dropdown, then choose one value for each. That value becomes the default on every incident created from the template.
Prefilled text is plain text, not a fill-in-the-blank form — there are no automatic placeholders for driver name or date, since the document already prints those. Use it for the paragraph you'd otherwise retype every time.
Template cards show the field count and the label chips they carry, with the same pencil, copy, and trash icons as labels. The copy icon is the fastest way to build a family of related write-ups: clone a base template, change one field, save it under a new name.
Depending on how your account was set up, you may already have a starter set: Netradyne Infraction, Tardy, Consistent Quality Issues, Vehicle Damage, and No Call, No Show. Each arrives with signature and comments turned on and a Severity and Category value chosen, but with no fields — so open the ones you plan to use and add the fields you want them to ask for.
How a template gets used
When a manager creates an incident, they pick a Template and a Driver first. Choosing the template fills in the rest of the form: the signature and comment settings, one text box per field seeded with its prefilled text, and the label values you set — all still editable for that one incident.
Every incident keeps its own copy of the wording and label values it was created with, so editing or deleting a template or label later never rewrites write-ups that already exist. A deleted template does disappear from the Template picker and the Template filter, though, so rename rather than delete if you still want that history grouped.
The Download button on an incident produces a PDF headed with your company name and the incident's name, then a Details table (Driver, Date, Status, Signature Required), a Labels section, an Additional Fields section with each field and its text, the employee's comment if they left one, and a signature block reading "Unsigned" until the driver signs.
For day-to-day handling of incidents once they exist, see the incident management article; for how the driver receives and signs a document, see the signatures article.