Understand the outcome
Compliance reports are only as current as completed events and approvals.
Training records events, attendance, hours, continuing-education credit, and certificates. Officers publish sessions to the roles that need them, record attendance, and complete the event so hours and CE are credited. Requirements tied to roles or certifications show who is compliant, members can log outside training for approval when the department turns that on, and records export to PDF or CSV.
This guide focuses specifically on “Run training compliance and export records.” Complete it from an account with the appropriate Training access, verify it from the affected member or operational view, and preserve existing records rather than repurposing historical configuration.
Before you begin
Make the decision before changing the screen. Record the current configuration when the department already uses this feature, and use a test record or test account when the change can affect active members.
- Complete recent events.
- Clear pending approvals.
- Choose the period and audience.
Do not work around it from another member’s account. Confirm that Training is enabled, its dependencies are active, and your role grants the exact management action required for this task.
Where to work and what access you need
Start from the portal destination named in the procedure. Administrators normally need permission to view Training plus the specific create, edit, manage, approve, report, or all-record action used by the task. Visibility alone does not grant management access.
- My Training
/modules/training/my - Calendar
/modules/training/calendar - All Trainings
/modules/training/events - New training
/modules/training/events/new - Records
/modules/training/records - Compliance
/modules/training/compliance - Analytics
/modules/training/analytics - Reports
/modules/training/reports - Categories
/modules/training/categories - CE Types
/modules/training/ce-types - Requirements
/modules/training/requirements - Settings
/modules/training/settings
Required foundation
- Core must be enabled and correctly configured before this workflow can operate reliably.
If your department uses custom roles, test the procedure with that role—not only with a full administrator account. This confirms the people responsible for daily operations can complete the workflow without receiving unrelated access.
Complete the task
- Step 1Open Compliance
Review who is on track and who is behind.
- Step 2Open a member’s record
See exactly what is missing.
- Step 3Fix source records
Correct attendance or approvals in the record, not in an export.
- Step 4Build a report
Use Reports and save reports you run often.
- Step 5Export
Download PDF or CSV; exports are logged.
- Step 6Spot-check
Compare a few members against their records.
Operational safeguards
Apply these module-level controls while completing the procedure. They prevent a technically saved configuration from becoming an operational or access problem later.
- Control point
Define categories and CE types before entering historical records. - Control point
Decide who may create events versus complete them. - Control point
Decide whether to turn on self-logged training and who approves it. - Control point
Assign requirements to the right roles or certifications. - Control point
Check the compliance view on a regular schedule; there are no automatic compliance reminders. - Control point
Test an individual record export before an audit.
Verify the result
Do not consider the setup complete merely because the save action succeeded. Confirm the behavior from the user-facing or operational view, then retain evidence of the test when department policy requires it.
- Totals match source records.
- Gaps are understandable.
- Exports follow department policy.
If any verification fails, return to the source configuration and correct it there. Do not edit a report or downstream record to conceal an incorrect setup.
Troubleshooting
Export is missing
Exporting is a separate permission.
Numbers look stale
Complete events and clear approvals, then rerun.
A member appears twice
Check for duplicate personnel records.
Connected modules and downstream effects
A change here can alter what members see, what data appears in reports, or how another module completes its workflow. Review the connected areas below before making a department-wide change.
- ResourcesVersioned documents with acknowledgement and signature tracking (formerly Policies).
- RecruitingApplication Hubs, reviews, interviews, references, and conversion (formerly Applications Flow).
After deployment, test one complete workflow from the originating module through every connected destination your department uses. Document the final configuration so another administrator can audit or reproduce it later.
Continue in Training
Return to the Training module guide for connected workflows, dependencies, portal destinations, and additional procedures.