Appearance
Merge Tags & Triggers
This is the complete list of every tag you can select in evo.ehs. The same list powers two features, and a tag means something slightly different in each:
| Where | What a tag does |
|---|---|
| Email Templates | A placeholder. When the email is sent, the tag is replaced with that field's current value. |
| Action Manager | A trigger. The action fires when that field changes. |
So {Permit.status} in a template body inserts the permit's status ("Active"); the same {Permit.status} chosen as an Action fires an email whenever a permit's status changes.
In the Action Manager the tags are shown by their label (the "Field label" column below) rather than their raw {Tag} form.
Three rules worth knowing first
Lifecycle tags fire on the record, not a field. _created, _modified, and _deleted don't watch one field — they fire when the record is created, changed in any way, or deleted. {Permit._modified} is the tag you want for "tell me about any edit to this permit."
Lifecycle tags insert a word, not a date. Used in an email body, {Permit._created} inserts the literal text Created — likewise Modified and Deleted. They are far more useful as triggers than as placeholders.
An unresolved tag is left as-is. If a tag has no value in context — an incident tag in a permit email, say — the raw {Tag} text appears in the sent email rather than an empty space. Only use tags that belong to the record the email is about.
Email-only tags
These five are available in Email Templates but not in the Action Manager; they describe the message, not a record, so there's nothing to watch.
| Tag | Description |
|---|---|
{temp_password} | The generated one-time password for a newly created account. Used by the welcome/invite emails so a new user can sign in for the first time. |
{code} | The confirmation code for email verification. Used by the confirmation-code template. |
{link} | The action link for the message — the password-reset or invitation URL the recipient needs to click. |
{action_name} | The name of the Action Manager action that sent the email, as you typed it in the Action Name column. Useful for a subject line like "Alert: {action_name}". |
{company_name} | Your organization's name from the company profile, so one template can be reused without hard-coding it. |
Permit
| Tag | Field label | Description |
|---|---|---|
{Permit.title} | Permit Name | The permit's name as it appears in Permit Manager. As a trigger, fires when a permit is renamed. |
{Permit.status} | Permit Status | Where the permit sits in its workflow. One of the most common triggers — use it to announce a permit becoming active or lapsing. |
{Permit.assigned_to} | Permit Assigned To | The user responsible for the permit. As a trigger this fires on reassignment, which makes it the basis of "a permit was assigned to you" notifications. |
{Permit.plant_id} | Permit Plant | The plant the permit belongs to. Fires when a permit is moved to a different site. |
{Permit.override_date} | Permit Due Date | The permit's effective due date. Fires when someone moves a deadline — worth watching for compliance oversight. |
{Permit.due_note} | Permit Notes | The free-text note attached to the permit's due date, usually explaining why a date was set or changed. |
{Permit.statute} | Permit Statute | The regulation or statute the permit is issued under. |
{Permit.source_agency} | Permit Source Agency | The issuing agency, such as the EPA or a state authority like TCEQ. |
{Permit.source_id} | Permit Source ID | The agency's own identifier for the permit — the number to quote when contacting the regulator. |
{Permit.date_assigned} | Permit Date Assigned | The date the permit was assigned to its current owner. |
{Permit._created} | Permit Created | Fires when a new permit is created. Inserts the word Created in an email. |
{Permit._modified} | Permit Modified | Fires on any edit to a permit, whichever field changed. Inserts the word Modified in an email. |
{Permit._deleted} | Permit Deleted | Fires when a permit is deleted. Inserts the word Deleted in an email. |
Permit sub-tasks
The checklist items beneath a permit.
| Tag | Field label | Description |
|---|---|---|
{PermitSubTask.name} | Permit Sub-Task Name | The sub-task's name. Fires when it is renamed. |
{PermitSubTask.status} | Permit Sub-Task Status | Whether the sub-task is outstanding or complete — the usual way to notify someone that a checklist step was finished. |
{PermitSubTask.assigned_to} | Permit Sub-Task Assigned To | The user responsible for this sub-task. Fires on reassignment. |
{PermitSubTask.due_date} | Permit Sub-Task Due Date | The sub-task's deadline. Fires when the date is changed. |
{PermitSubTask.notes} | Permit Sub-Task Notes | Free-text notes on the sub-task. |
{PermitSubTask._created} | Permit Sub-Task Created | Fires when a sub-task is added to a permit. |
{PermitSubTask._modified} | Permit Sub-Task Modified | Fires on any edit to the sub-task. |
{PermitSubTask._deleted} | Permit Sub-Task Deleted | Fires when the sub-task is removed. |
Incident sub-tasks
The corrective actions and follow-up steps beneath an incident.
| Tag | Field label | Description |
|---|---|---|
{IncidentSubTask.name} | Incident Sub-Task Name | The corrective action's name. Fires when it is renamed. |
{IncidentSubTask.status} | Incident Sub-Task Status | Whether the corrective action is outstanding or complete — useful for closing the loop on incident follow-up. |
{IncidentSubTask.assigned_to} | Incident Sub-Task Assigned To | The user responsible for the corrective action. Fires on reassignment. |
{IncidentSubTask.due_date} | Incident Sub-Task Due Date | The corrective action's deadline. |
{IncidentSubTask.notes} | Incident Sub-Task Notes | Free-text notes on the corrective action. |
{IncidentSubTask._created} | Incident Sub-Task Created | Fires when a corrective action is added to an incident. |
{IncidentSubTask._modified} | Incident Sub-Task Modified | Fires on any edit to the corrective action. |
{IncidentSubTask._deleted} | Incident Sub-Task Deleted | Fires when the corrective action is removed. |
Work tasks
Standalone recurring work items from the task scheduler.
| Tag | Field label | Description |
|---|---|---|
{WorkTask.name} | Work Task Name | The task's name. Fires when it is renamed. |
{WorkTask.status} | Work Task Status | Whether the task is outstanding or complete. |
{WorkTask.assigned_to} | Work Task Assigned To | The user responsible for the task. Fires on reassignment, so it drives "a task was assigned to you" emails. |
{WorkTask.due_date} | Work Task Due Date | The task's deadline. Fires when it is rescheduled. |
{WorkTask.notes} | Work Task Notes | Free-text notes on the task. |
{WorkTask._created} | Work Task Created | Fires when a task is created, including each occurrence generated by a recurring cadence. |
{WorkTask._modified} | Work Task Modified | Fires on any edit to the task. |
{WorkTask._deleted} | Work Task Deleted | Fires when the task is deleted. |
Work task sub-tasks
The checklist items beneath a work task.
| Tag | Field label | Description |
|---|---|---|
{TaskSubTask.name} | Task Sub-Task Name | The sub-task's name. Fires when it is renamed. |
{TaskSubTask.status} | Task Sub-Task Status | Whether the checklist item is outstanding or complete. |
{TaskSubTask.assigned_to} | Task Sub-Task Assigned To | The user responsible for this checklist item. |
{TaskSubTask.due_date} | Task Sub-Task Due Date | The checklist item's deadline. |
{TaskSubTask.notes} | Task Sub-Task Notes | Free-text notes on the checklist item. |
{TaskSubTask._created} | Task Sub-Task Created | Fires when a checklist item is added to a task. |
{TaskSubTask._modified} | Task Sub-Task Modified | Fires on any edit to the checklist item. |
{TaskSubTask._deleted} | Task Sub-Task Deleted | Fires when the checklist item is removed. |
Incident
| Tag | Field label | Description |
|---|---|---|
{Incident.incident_number} | Incident Number | The incident's reference number — the identifier to quote in reports and correspondence. |
{Incident.title} | Incident Title | The incident's short title. |
{Incident.category} | Incident Category | The kind of incident (injury, spill, near miss, and so on). |
{Incident.stage} | Incident Stage | Where the incident sits in its investigation workflow. A common trigger for keeping stakeholders informed as a case progresses. |
{Incident.priority} | Incident Priority | The incident's priority. Watch it to escalate when something is raised to high priority. |
{Incident.assigned_to_user_id} | Incident Assigned User | The user investigating the incident. Fires on reassignment. |
{Incident.reporter_user_id} | Incident Reporter User | The user who reported the incident. |
{Incident.occurred_at} | Incident Occurred At | When the incident actually happened. |
{Incident.discovered_at} | Incident Discovered At | When the incident was discovered, which can be much later than it occurred and is what several reporting clocks run from. |
{Incident.location_text} | Incident Location | Where in the plant the incident happened, in free text. |
{Incident.osha_8hr_candidate} | Incident OSHA 8hr Candidate | Flags an incident that may require an OSHA report within 8 hours. As a trigger this is a genuine escalation alert — a fatality clock. |
{Incident.osha_24hr_candidate} | Incident OSHA 24hr Candidate | Flags an incident that may require an OSHA report within 24 hours, such as an amputation or hospitalization. |
{Incident.nrc_candidate} | Incident NRC Candidate | Flags an incident that may require a National Response Center report, typically a reportable release. |
{Incident._created} | Incident Created | Fires when an incident is reported. The usual trigger for immediate notification of the EHS team. |
{Incident._modified} | Incident Modified | Fires on any edit to the incident. |
{Incident._deleted} | Incident Deleted | Fires when an incident is deleted. |
Plant
Plants have no lifecycle tags — sites are created rarely and by an administrator, so there is nothing to watch.
| Tag | Field label | Description |
|---|---|---|
{Plant.name} | Plant Name | The site's name. Commonly used in email subject lines to say which plant a message concerns. |
{Plant.city} | Plant City | The city the site is in. |
{Plant.address} | Plant Address | The site's street address. |
{Plant.state} | Plant State | The state the site is in, which often determines which agency has jurisdiction. |
{Plant.zipcode} | Plant Zipcode | The site's postal code. |
{Plant.phone} | Plant Phone | The site's main phone number. |
{Plant.timezone} | Plant Timezone | The site's timezone, which governs how its dates and deadlines are interpreted. |
{Plant.plant_manager} | Plant Manager | The site's plant manager. |
{Plant.ehs_supervisor} | Plant EHS Supervisor | The site's EHS supervisor. |
{Plant.ehs_manager} | Plant EHS Manager | The site's EHS manager. |
{Plant.nws_alert} | NWS Weather Alert (Plant) | The current National Weather Service alert for the site. As a trigger it fires when a new weather alert is issued, which is how severe-weather notifications are sent. |
User
User tags describe the person a message concerns — typically the recipient.
| Tag | Field label | Description |
|---|---|---|
{User.first_name} | User First Name | The user's first name. The usual way to open an email: "Hello {User.first_name}". |
{User.last_name} | User Last Name | The user's last name. |
{User.email} | User Email | The user's email address. |
{User.plant_id} | User Plant | The plant the user is assigned to. |
{User.work_phone} | User Work Phone | The user's work phone number. |
Calendar event
| Tag | Field label | Description |
|---|---|---|
{Event.event_type} | Event Type | The kind of calendar event (inspection, training, audit, and so on). |
{Event.user_id} | Event Team Member (User ID) | The team member the event is for. Fires when an event is reassigned. |
{Event.plant_id} | Event Plant | The plant the event belongs to. |
{Event.date_start} | Event Start Date | The event's start date. Fires when an event is rescheduled. |
{Event.date_end} | Event End Date | The event's end date. |
{Event.time_start} | Event Start Time | The event's start time. |
{Event.time_end} | Event End Time | The event's end time. |
{Event.all_day} | Event All Day | Whether the event covers the whole day rather than a set time. |
{Event.location} | Event Location | Where the event takes place. |
{Event.notes} | Event Notes | Free-text notes on the event. |
{Event._created} | Event Created | Fires when an event is added to the calendar — the basis of "you've been scheduled" notifications. |
{Event._modified} | Event Modified | Fires on any edit to the event. |
{Event._deleted} | Event Deleted | Fires when an event is cancelled or removed. |
Legacy permit sub-task tags
These older {Task.*} tags are the original names for the permit sub-task fields and are still resolved, so existing templates and actions keep working. They appear in the picker marked (legacy). Use the {PermitSubTask.*} tags above for anything new — the legacy tags mean exactly the same thing.
| Legacy tag | Equivalent |
|---|---|
{Task.name} | {PermitSubTask.name} |
{Task.status} | {PermitSubTask.status} |
{Task.assigned_to} | {PermitSubTask.assigned_to} |
{Task.due_date} | {PermitSubTask.due_date} |
{Task.notes} | {PermitSubTask.notes} |
{Task._created} | {PermitSubTask._created} |
{Task._modified} | {PermitSubTask._modified} |
{Task._deleted} | {PermitSubTask._deleted} |