A safety committee meeting with the list already on the table
The useful part of a safety committee meeting starts when people can discuss the work. If the first task is rebuilding the list, the discussion waits. Committee meetings in Sheets beta bring recorded work into a draft pack, with attendance, decisions and minutes beside it. The chair still chooses what needs attention and checks the record before filing.
Prepare from the records you already keep
Start a committee meeting for the facility. Sheets prepares a pack from the available sheet records and form actions, using the previous filed meeting as the starting point for the review window. The pack brings together open work, overdue items, the oldest open items, work without an owner and recorded fixes. It also includes repeat or reopened items where those are available.
This gives the chair a starting point. It does not decide the agenda. Before the meeting, read the items likely to need discussion and open the underlying records where the summary is unclear. A short title may be enough to recognize an issue, but the group may need the description or history to understand why it is still open.
The pack is prepared when the draft begins. If records change before the meeting, use Regenerate pack while it is still a draft. Treat that as a deliberate preparation step. Check the pack's review window and generation time so people know which version they are discussing, especially when a draft has been open for a while.
Put the work that needs a decision first
A practical agenda starts with the items that cannot move without help. Work with no owner needs someone to accept the next step. An overdue item needs an explanation of what is blocking it. A repeated or reopened issue needs a closer look at the earlier action. These are review habits your team can apply to the pack, rather than an automatic judgment by the software.
Avoid reading every row aloud. Ask the owner to explain what changed, what remains and what they need from the committee. Record a decision in words that will make sense after the meeting. 'Discussed' tells a later reader very little. A note that explains the agreed action and the reason for it gives the next review something concrete to check.
Keep completion and verification distinct in the conversation. A reported fix can be useful evidence, but the committee should understand what has actually been checked. The pack preserves the available status and related details; the people responsible still decide whether those details support the conclusion they are recording.
Prepare the list before the meeting. Use the meeting to decide what happens next.
Check attendance and connect decisions to follow-up
A new draft copies the facility's committee list into attendance and initially marks those members present. Check that list during the meeting. Mark absences and add anyone else who attended before saving. A prepared attendance list is a convenience, not proof that everyone attended.
The draft has space for decisions and minutes. Where an actions sheet is available, a decision can raise a record in that sheet and keep a link back to the meeting. That requires an active actions sheet for the facility or account. If one has not been configured, plan that setup before relying on the meeting to create follow-up records.
After raising an action, review its working details and assign responsibility through the normal record workflow. Creating a record does not establish that someone has accepted it. The chair's useful closing question is whether each agreed action has a clear next step and whether the person responsible knows where to find the decision.
Present the pack, then read the printed record
The meeting has a Present view for working through the pack on a shared screen. It offers sections with next and back controls, alongside the meeting's attendance and decisions when available. Use it to keep the room on the same part of the discussion. Pause when a summary needs explanation rather than letting the screen set the pace.
The Print view brings the meeting into a document layout with the pack, attendance, decisions and minutes. It is available behind sign-in. Read it before filing, particularly if paper will be the version people use later. Check the facility, meeting date, attendance and wording of decisions. A readable page is useful only when it accurately reflects the discussion.
File the account you want the next meeting to inherit
Filing changes the draft into a filed record. The pack, attendance, decisions and minutes are sealed together with a content hash. They cannot then be edited through the meeting workflow. If a correction is needed, start an amendment that identifies the original meeting. That preserves the distinction between what was filed and what was corrected later.
Before filing, confirm when the meeting was held. If no held time has been set, filing stamps it at that point. Read the decisions once more as someone who missed the meeting. The next review should be able to follow the discussion without reconstructing it from memory.
Sheets remains in beta, so begin with a familiar committee review and confirm the facility, permissions and actions sheet during setup. The Sheets feature page shows the existing meeting pack with demonstration data. The related tracker article offers a useful final check: can another person explain the record behind a completed finding?