Getting started with Events

Events is where your organisation records and follows up on the things that matter: incidents, near-misses, observations, complaints, hazards, or anything else you decide to track.

Event types are fully configurable, so you can define the categories that match your organisation.

How Events are set up

Before anyone can report an Event, a user with Object Manager access configures the module: the forms reporters complete, the fields that store your data, the layout that organises the record, and the pipelines that tailor how different types of Events are handled.

For how these pieces fit together, see How Event Forms, fields, layouts and pipelines connect. For Object Manager itself, see What is the Object Manager?

The stages of an Event

With that setup in place, every Event follows a similar path, from initial report through to follow-up and closure:

1. An Event is reported: A reporter submits a form, from the Protector Mobile App, the Vatix Workspace web app, or a public QR code or web link that doesn't need a Vatix account. 

2. The right people get involved: When an Event comes in, the right people need to see it and it needs to go into the right pipeline. If you've set up assignment rules, this happens automatically, but they're optional. You can also add collaborators yourself at any time, not just when the Event is submitted, so you can bring people in as the follow-up develops. 
3. The Event is worked through a pipeline: A pipeline tailors how that type of Event is handled, highlighting the fields and guidance that matter at each stage so the people managing it know what to do. 
4. Tasks close the loop: From any Event record, you can raise tasks to assign, manage, and track follow-up actions.

Reporting on your Events

Your Event data can feed your Analytics dashboards, and Safety Metrics calculates your organisation's key health and safety rates (such as AFR, LTIFR, LTISR, and NMFR) from your Event data and the monthly work hours you enter. 

Who can access Events

• Object Manager access: configures the module, including its forms, fields, layout, and pipelines.
• Account Owners: can view and act on every Event in the organisation, and can be added as collaborators.
• Managers: can be added as collaborators on individual Events, and work on the Events they're added to.
• Users: can report Events and have limited access to the Events they've reported. They can't be added as collaborators.

Setting up Events for the first time

If you're configuring Events for the first time, it helps to read How Event Forms, fields, layouts and pipelines connect first, so you understand how the building blocks relate. Then work through the setup in this order:

1. Set up your Event Form and its questions. 
2. Create the fields you want on the record in the Field Manager, and arrange them with the Layout Editor. 
3. Optionally, map a form question whose answer should populate a field automatically. 
4. Tailor a pipeline for the types of Event that need a defined process. 
5. Add assignment rules to route Events to the right pipeline and add collaborators.