When you log an incident, you pick a reason such as Damaged product, Location not ready, Weather, Installer error, or Missing product. This tells the team what went wrong and makes it easier to filter and spot patterns across jobs over time.
The default reasons
Damaged Product | Something was damaged during delivery, installation, or on site. |
Location Not Ready | The site was not prepared or accessible when the team arrived. |
Weather | Adverse weather prevented or disrupted the job. |
Installer Error | A mistake was made during installation or setup. |
Missing Product | A product or component did not arrive on site. |
Adding custom reasons
Custom incident reasons can be added to fit your operation, for example, Client canceled, Access denied, or Equipment failure.
Custom reasons are configured by the Vantage team, not from Workspace Settings. Get in touch and let us know what categories you need.
Using reasons to spot patterns
On the Incidents page, filter by Reason to see all incidents of a particular type across your workspace.
This makes it easier to identify recurring problems. For example, if Location not ready keeps coming up for a particular client or project type, it might point to a process issue upstream.
FAQ
Can I rename or delete a default reason?
Can I rename or delete a default reason?
Default reasons cannot be renamed or deleted by workspace admins. If a default reason does not fit your operation, get in touch and we can discuss adjustments.
Can I have different reasons for different event types?
Can I have different reasons for different event types?
Not currently. Incident reasons apply across the whole workspace regardless of event type.
Is there a limit to how many custom reasons I can have?
Is there a limit to how many custom reasons I can have?
There is no hard limit. Keep the list short enough to stay useful; too many reasons can make it harder for field teams to choose quickly on site.