Events: How to Register and Manage Employee Incidents in Diamond Operations Pro

Who should use this module?

This article is intended for:

• Administrators.
• Human resources staff.
• Supervisors.
• Team leaders.
• Authorized users who document situations related to employees.

The goal is to help users register employee events, review them correctly, and maintain an organized history by person.

When should you use Events?

Use the "Events" module when you need to:

• Register an incident related to an employee.
• Document an absence.
• Record an important operational situation.
• Leave a formal note about an employee.
• Review history before making an administrative decision.
• Review past situations related to a person.
• Relate or review events from the calendar or schedule.

This module should be used carefully, as it may contain sensitive employee information.

Key concepts

Before working with this module, it is important to understand the following concepts:

Event
A record of a situation associated with an employee.

Employee incident
A formal note, situation, or incident related to an employee.

Grouped by employee
The way the system organizes events, showing records under the corresponding person.

Event detail
Specific information about the event, such as date, description, notes, and context.

Schedule context
The ability to open, review, or relate events from the calendar or schedule when applicable.

Understanding the main Events screen

The main "Events" screen shows records grouped by employee.

From this screen, depending on the user’s permissions, you can:

• Search for employees or events.
• Expand employee groups.
• Review registered events.
• Select records.
• Create new events.
• Edit existing events.
• Delete events, if the user has permission.

Grouping by employee helps review each person’s history without mixing information between different employees.

Before creating, editing, or deleting an event, remember that these records may be part of the employee’s internal history and should be handled responsibly.

Before creating an event

Before registering an event, confirm that the information is clear, necessary, and related to the correct employee.

Recommended questions:

• Does the event correspond to the selected employee?
• Is the event date correct?
• Is the description objective and professional?
• Is the information necessary for the history?
• Should the event be related to an absence, operational incident, or formal note?
• Does the user registering the event have permission to document this information?
• Could the information be considered sensitive?

Registering events with clear information helps maintain a useful and reliable history.

Once saved, the event will be registered in the history of the selected employee.

How to write a good description

The event description should be clear, objective, and easy to understand.

Recommendations:

• Write only information related to the event.
• Avoid personal opinions.
• Use professional language.
• Include dates or context when necessary.
• Do not add unnecessary information.
• Avoid ambiguous comments or information that is difficult to verify.

Recommended example:

"The employee did not show up for the scheduled shift on March 15 and did not notify the supervisor in advance."

Not recommended example:

"The employee always has problems and never lets anyone know."

An objective description helps make the history useful for future reviews.

Before editing, verify that the change is necessary and that it does not alter important information without authorization.

How to review an employee’s history

To review an employee’s registered events:

1. Open the "Events" module.
2. Search for the employee.
3. Expand the corresponding group.
4. Review the events organized by date.
5. Open the event detail if you need more information.

This history can help supervisors, administrators, or human resources review previous situations before making decisions.

Using Events with the schedule

In some cases, events can be viewed or related to the schedule.

This can be useful when:

• The event is related to an absence.
• The incident occurred during a shift.
• Context needs to be reviewed from the calendar.
• The supervisor wants to connect a situation with a scheduled date.
• It is necessary to understand which job, shift, or activity was related to the employee.

When using this information, confirm that the date, employee, and context are correct.

Best practices

To maintain a clear and responsible history:

• Write objective and professional descriptions.
• Register events close to the time they occur.
• Confirm that the event is associated with the correct employee.
• Avoid unnecessary or ambiguous information.
• Do not include personal opinions.
• Use correct dates.
• Add context only when necessary.
• Review permissions before sharing sensitive information.
• Do not delete historical events without administrative approval.
• Keep the information organized and easy to review.

Security recommendations

Employee events may contain sensitive information. For that reason, they should be handled carefully.

Recommendations:

• Give access only to users who truly need it.
• Avoid sharing information outside the system if it is not necessary.
• Do not register personal details that are not related to the event.
• Keep descriptions professional.
• Use the module as an administrative history, not as a space for informal comments.
• Review who can create, edit, view, or delete events.

Responsible management helps protect employee information and keeps operations organized.

Expected result

By the end, the user should be able to:

• Register events related to employees.
• Associate each event with the correct employee.
• Write clear and professional descriptions.
• Review event history by person.
• Edit information when necessary and permitted.
• Maintain an organized record of incidents, absences, or internal notes.
• Handle sensitive information responsibly.
• Use the "Events" module as a reliable tool for administrative follow-up within Diamond Operations Pro.