Skip to content
FRSign inBook a walkthrough
ExplainerSMS fundamentals

Safety Action Group vs Safety Review Board

The Safety Action Group and the Safety Review Board are the two safety committees ICAO Doc 9859 describes: one tactical, one strategic. Most problems with them come from blurring the two, or from losing an item on the way between them. Here is what each one is for, who sits on it, and what should move from one to the other.
Mounir OuafiFounder and CEO of eAvioraPublished 10 min read

01What ICAO Doc 9859 says

The two names come from the Safety Management Manual, ICAO Doc 9859. In its chapter on safety management systems, under the appointment of key safety personnel, the fourth edition says service providers should establish appropriate safety committees that support the SMS functions across the organization, and should determine who sits on them and how often they meet.

It then describes two of them. The Safety Review Board (SRB) is the highest-level safety committee. The manual calls it strategic: it deals with high-level issues related to policies, resource allocation and organizational performance monitoring, and it should include the accountable executive and senior management. The board monitors the effectiveness of the SMS, the timely response of necessary safety risk control actions, safety performance against the organization's safety policy and objectives, and the effectiveness of the processes that support the declared priority of safety and its promotion across the organization.

The Safety Action Group (SAG) is the operational counterpart. Once the highest-level committee has set a strategic direction, the manual says implementation may be coordinated by a group that is more operationally focused: normally managers and front-line personnel, chaired by a designated manager, a tactical entity that deals with specific implementation issues per the direction of the board. The manual lists five jobs for it:

  • Monitor operational safety performance within the functional areas, and ensure that safety risk management activities are carried out.
  • Review available safety data, identify the implementation of appropriate risk control strategies, and ensure employee feedback is provided.
  • Assess the safety impact of operational changes or new technologies.
  • Coordinate the implementation of actions related to risk controls, and ensure they are taken promptly.
  • Review the effectiveness of the safety risk controls.

Two things are worth noticing. The wording is permissive (should, may), so this is a recommended shape, not a mandated pair. And the relationship has a direction: the board sets it, the group carries it out. Both sit inside Safety Policy and objectives, the first of the four components of an SMS, yet most of what they look at is produced by Safety Risk Management and Safety Assurance.

02Who sits on each, and how often they meet

On the action group you want the people who can change how work is done next week: the managers of the functional area (flight operations, maintenance, ground operations, cabin), front-line staff who know how the procedure is really flown or performed, and the safety manager or a safety officer who brings the data. The chair is a designated manager, not the safety manager by default. A large operator usually has several groups, one per functional area, because one group cannot hold the detail of every department.

On the board you want the people who can move money, people and policy: the accountable executive and the senior managers who answer for each area. Doc 9859 does not name the chair. In practice it is usually the accountable executive, which is consistent with that person holding final accountability for the SMS. The safety manager attends to present and advise, not to carry the decisions.

On frequency the manual gives no number; it leaves it to the service provider. A workable sample pattern, and only a sample, is a monthly action group per functional area and a quarterly board, with the right to convene the board early when something cannot wait. A small operator can run both as two halves of one meeting. Whatever you pick goes in the SMS manual, and then the cadence becomes evidence: when a manual says a board meets on a cadence, an auditor asks for the minutes.

03Side by side

The table follows the Doc 9859 description. Where the manual is silent, the cell says so.

Safety Action Group and Safety Review Board compared, following ICAO Doc 9859
DimensionSafety Action GroupSafety Review Board
LevelTactical, operationally focusedStrategic, the highest-level safety committee
Deals withSpecific implementation issues, under the direction of the boardPolicies, resource allocation and organizational performance monitoring
Who sitsManagers and front-line personnelThe accountable executive and senior management
ChairA designated managerNot fixed by Doc 9859; in practice usually the accountable executive
WatchesOperational safety performance in its functional area, and that risk management is carried outEffectiveness of the SMS and safety performance against the policy and objectives
On actionsCoordinates risk control actions and sees that they are taken promptlyMonitors the timely response of necessary risk control actions
On changeAssesses the safety impact of operational changes and new technologiesDecides what the organization will fund, accept or stop
Typical outputAssigned actions, effectiveness reviews, items escalated upwardDirection, resources, recorded decisions and risk acceptances

A quick test for any agenda item: if settling it needs a change to a procedure, a roster or a task card, it belongs to the group. If it needs budget, a policy change, or someone to accept a risk on behalf of the organization, it belongs to the board.

04What moves from one to the other

Traffic runs both ways, and the two flows are different in kind.

Up, from the group to the board. Anything the group cannot settle with its own authority: a risk control that needs funding or headcount, a risk that stays above the level the organization tolerates after the available controls, a problem that crosses departments, a trend that questions a safety objective, and a corrective action that has been tried and has not worked. A good escalation arrives with the group's proposed actions attached, so the board decides on a proposal instead of starting the analysis again.

Down, from the board to the group. Direction and means: priorities, the safety objectives and their targets, the resources granted, the decision on each escalated item with its conditions, and the question the board wants answered next time.

The link that most often breaks is the return trip. An item goes up, a decision is taken, and nobody at the working level can later find what was decided or why. Treat every escalated item as one record that travels up and comes back with its decision, and the loop holds.

05A sample agenda for each, and what minutes record

These are samples to adapt, not a standard. They follow the jobs Doc 9859 gives each body.

Sample agenda, Safety Action Group.

  1. Open actions from the last meeting: done, late, or blocked.
  2. New reports and hazards in the area since the last meeting.
  3. Indicators for the area, and any that have crossed an alert level.
  4. Changes coming (a new route, a new tool, a procedure revision) and their safety impact.
  5. Risk controls in place: which ones have been checked, and did they work.
  6. Items to escalate to the board, each with a proposed action.
  7. Feedback to give to the people who reported.

Sample agenda, Safety Review Board.

  1. Decisions and actions from the last board: status.
  2. Safety performance against the objectives and targets.
  3. Items escalated by the action groups, each with its proposal.
  4. Risk control actions that are overdue or have proven ineffective.
  5. Resources: what the groups asked for, and what is granted.
  6. Effectiveness of the SMS itself: audit results, reporting levels, promotion.
  7. Policy and objectives: anything to change.

Minutes are the evidence that the meeting governed something. Good minutes record, for every item:

  • Who attended, and whether the accountable executive was present at the board.
  • Why the item was on the agenda, and the risk level when it was raised.
  • The data that was looked at, not just a statement that it was reviewed.
  • The decision, in words that can only be read one way, with its conditions.
  • Who disagreed, and any conflict of interest that was declared.
  • Each action with one named owner and a due date.
  • For an accepted risk: who accepted it, on what grounds, and until when.

“Discussed, to be monitored” is not a decision. If a line in the minutes does not name a decision, an owner or a date, it records a conversation.

06How they fail

  • The board that only reviews lagging numbers. A pack of last quarter's event counts and a rate per thousand flights tells the board what already happened. Its job in Doc 9859 includes the timely response of risk control actions and the effectiveness of the SMS, which are questions about the present. Put leading indicators and overdue or ineffective actions on the agenda before the counts.
  • The action group with no authority. If the group can only recommend, every item turns into a request to someone who was not in the room. Give the chair the authority to assign actions inside the area, and a defined route upward for the rest.
  • The escalation that never comes back. Items go up and vanish. The group stops escalating, and the board stops hearing about real problems.
  • The same people, the same meeting, twice. When both bodies have the same members and the same agenda, the strategic job is the one that disappears.
  • The safety manager as owner of everything. The safety manager advises and facilitates. If every action is assigned to the safety office, line management has left the system.
  • Actions closed on completion. The group's fifth job is to review whether a control worked. An action closed because the task was done, with no check of the result, skips that job. A closure gate is how you stop it.
  • The verbal risk acceptance. A risk accepted by a nod in the room has no owner a year later. Acceptance needs a name, a reason and a review date in the minutes.

Questions

SAG stands for Safety Action Group. In ICAO Doc 9859, the Safety Management Manual, it is the operationally focused safety committee: normally managers and front-line personnel, chaired by a designated manager, dealing with specific implementation issues under the direction of the Safety Review Board. It monitors operational safety performance in its functional area, reviews safety data, assesses the safety impact of operational changes, coordinates risk control actions and reviews whether those controls work.

Mounir OuafiFounder and CEO of eAviora, the aviation safety intelligence platform.

Related reading

See an item arrive on the board and leave as an action.

Book a walkthrough on your own operation, or keep reading in all the insights.