PeopleOps Audit Checklist for Safety Reporting Portal Access

A safety reporting portal is only as trustworthy as the list of people who can reach it. Reports often contain candid descriptions of events and sometimes sensitive details about colleagues, so the question of who may read, file, triage and close them matters. Whenever staff join, switch roles or leave, that list changes. This checklist applies the discipline of PeopleOps to the people-and-access side of a safety management setup, in a form that a safety manager or auditor can run in an afternoon.

Scope and sources

The controls below draw on the personnel-security ideas and lifecycle practices summarised in the PeopleOps entry of the Ops Atlas, which treats everything from hiring to exit as a countable operation, each stage owned and answered within an agreed time. The checklist is operational guidance. It does not interpret any aviation regulation, and it is no stand-in for your regulator, your counsel or your accountable manager. Where a legal point appears, confirm it locally.

How to use the list: for each item, record Yes, No or Not applicable, the evidence you looked at and the owner. Anything marked No receives an action, a person and a date.

Section A: The record of who works here

  • A single, dated staff list exists and is named as the authoritative source. Evidence: the list and its last-updated date.
  • Every person carries a permanent identifier that is not an email address, because the Atlas notes that email changes with name changes and rehires.
  • Each record shows a start date, an end date where known, a manager and a role, with future dates entered ahead of time.
  • Someone owns each data field; there is an attribution list showing who may edit what.
  • Contractors, temporary staff and volunteers are in the same list, each with an end date and a sponsor.

Section B: Joiners

  • Portal accounts are created from a confirmed start, not merely from an accepted offer. Evidence: the count of accounts belonging to people who have not started.
  • The role assigned matches the job: for instance, reporter-only rights for most staff and triage rights for named safety personnel.
  • Required training or briefing on how to use the portal is recorded.
  • Readiness on day one is measured. The Atlas gives at least 95 per cent as an example target.
  • The manager has shared a plan for the first three months and a buddy is named.
  • Identity and right-to-work checks required in your country were completed within the legal timing. Confirm timings with your adviser.

Section C: Movers

  • Every change of role triggers an access review within a defined number of days.
  • Someone who moved from safety triage into a commercial role no longer has triage or case-closure rights.
  • Temporary acting appointments carry an expiry date in the system.
  • Evidence: the last three role changes and a before-and-after comparison of rights. The Atlas calls movers the forgotten event, so this section deserves extra time.

Section D: Leavers

  • A leaving date and time is entered in the record in advance where it is known, so that closure can be scheduled.
  • Termination is treated as the highest-priority event between systems.
  • Portal, email, document storage and any chat tools are closed within the stated window. The Atlas uses one hour as an example policy and at least 99 per cent of leavers inside that window as an example target.
  • A daily reconciliation compares leavers in the record with disabled accounts, and any mismatch fires an alert the same day rather than waiting in a monthly report.
  • Physical items (badges, keys, headsets, laptops) are returned and logged.
  • Evidence: the last ten leavers, with the timestamp of each closure. Count orphan accounts and any breach of the window.

Section E: Shared and special accounts

  • No shared logins exist for the portal; where a shared mailbox is unavoidable, a named owner and a use log exist.
  • Service accounts and automated helpers are listed with an owner and a review date.
  • Tools outside the single sign-on are inventoried. The Atlas names non-SSO tools, shared credentials and bots as places where leaver access commonly survives.
  • Administrator rights are limited to a short, named list reviewed on a calendar.

Section F: Confidential routes

  • Reports about colleagues, or concerns raised about management, have a route that bypasses ordinary queues. The Atlas describes a confidential employee-relations path that must never sit in a shared view.
  • The people who can read those reports are few, named and reviewed.
  • Data about individual staff is not used to monitor their keystrokes, locations or activity; the discipline excludes surveillance.

Section G: Data handling and retention

  • A retention schedule exists for staff records and report files, and a yearly deletion run is recorded.
  • Access to personnel data follows the principle that people see what their job requires.
  • The privacy rules that apply to your people data (for example GDPR in the EU, or local data-protection law) have been identified by a qualified person. The Atlas dates its regulatory table and marks it for quarterly rechecking, so treat any summary as a pointer, not a ruling.
  • Any small-group figures published from people data apply a minimum group size, with the Atlas using five as an example.

Section H: Cadence and ownership

  • Daily: reconcile the HR list with accounts.
  • Weekly: review open staff requests and pending joiner or leaver tasks.
  • Monthly: report on day-one readiness, closure timing and overdue items.
  • Quarterly: sample data quality and run access reviews.
  • Annually: review policies and delete records that have passed their retention date.

Section I: The evidence pack

  • Screenshots or exports are dated and stored with the audit, not scattered across personal folders.
  • Each finding cites the record it came from, such as a ticket number or a list export, so that a second reviewer can repeat the check.
  • Interviews are noted separately from system evidence, because what people believe about access and what the system shows can differ.
  • The auditor is independent of the team that administers the accounts, or the reason for any overlap is written down.

Scoring the audit

Count your Yes answers per section and note which sections hold the Nos. A tidy way to prioritise is by consequence: leaver closure and movers come first, because a stale login on a reporting portal is the most direct harm; shared accounts second; retention and cadence third. Resist the temptation to produce one composite score. Averages hide the outlier, and in this domain the outlier is the risk. In the Atlas’s own sample reconciliation, a 50 per cent pass rate concealed a single account that was never closed.

After the audit

Write the findings on one page: what you checked, what you found, who owns each fix and the date you will re-test. Repeat the audit after the next batch of staff changes, and again before any external review. If a finding touches regulation or contracts, route it to the person responsible for compliance. The first run will take an afternoon; later runs, with a reconciliation already in place, take less than an hour. That is the real benefit of treating people processes as an operation: the check becomes a routine instead of an event.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top