Events

End-user documentation

Events

A simple event calendar surface with event records, calendar views, and Google Calendar sync support.

Purpose and What Problem This Solves

The Events module keeps company events in one shared calendar instead of scattered messages. It helps staff know what is happening, when, where, and who is responsible.

Who normally uses this module

What You Can Do Here

• Create company meetings, reminders, holidays, launches, training sessions, or internal activities.
• Display events in a calendar view for staff planning.
• Sync approved events to Google Calendar when the integration is configured.
• Update or cancel events with a traceable record.
• Use events as a lightweight coordination tool before work becomes a full project.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

1. Enable the module and grant event access to the coordinator group.
2. Create a test event with clear title, date, time, and location.
3. Review the calendar view to confirm it appears on the expected day.
4. If Google sync is enabled, confirm the external calendar receives the event.
5. Agree on naming standards for recurring business event types.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Create an event

1. Choose the correct date, start time, end time, timezone context, and location.
2. Use a title that tells users what the event is without opening the details.
3. Add description, owner, and preparation notes.
4. Save and reopen the calendar to verify placement.

Change or cancel an event

1. Open the existing event instead of creating a duplicate.
2. Update the schedule or status and add a reason if people are affected.
3. Confirm any external calendar sync has completed.
4. Announce the change through the normal communication channel.

Weekly calendar review

1. Scan the next two weeks for missing owners, conflicting times, and vague titles.
2. Confirm high-impact activities have preparation notes.
3. Archive or clean cancelled duplicates.
4. Remind owners of events that require materials, rooms, or external invitations.

Industry Notes and Good Practice

• Calendar quality depends on plain titles, correct times, and fast cleanup of duplicates.
• Use events for scheduled coordination. Use Projects for work requiring tasks, milestones, files, and timesheets.
• When syncing to external calendars, treat ERPat as the source record and avoid editing the same event in multiple places.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

• Every event has a clear title, date, time, owner, and location or meeting link.
• Cancelled or moved events are updated, not duplicated.
• External sync errors are reviewed before users rely on the outside calendar.
• Recurring activities follow a consistent naming convention.

Related ERPat areas

FAQ and Troubleshooting

Why does an event appear twice?

It may have been duplicated manually or synced from another source. Keep one source of truth and remove stale copies.

Can I use Events for project deadlines?

You can show milestones as events, but use Projects when tasks and ownership need tracking.

Why did Google Calendar not update?

Check integration credentials, sync job status, and whether the event is eligible for sync.

What should the title contain?

Use the event type, subject, and audience, for example Payroll Cutoff Review or Safety Training.

ERPat Events user guide. This static HTML page is documentation-only and does not change module routing, permissions, or runtime behavior.