Skip to main content

Record attendance at a team briefing

Build a briefing Checklist with named attendees and supporting notes, without treating one submission as individual certification.

Written by Logan Bowlby

Overview

Use a briefing Checklist when a supervisor needs one record of the topic discussed and the people present. A Member Question can collect named Users, while the submitted Result identifies who completed the record.

At a glance

Who can do this

Super Users, Checklists › Modify, or authorized Checklist folder Editors. Schedule setup needs the appropriate Schedule permissions.

Where

Checklists and Schedules

Works on

Backend (web), Mobile app

Availability

All organizations

💡 Why this matters: A consistent attendance record is easier to review than an unstructured list of names typed differently each time.


Before you start

Decide whether you need a meeting record or individual acknowledgement. This guide produces one Result for the briefing. If every person must complete and acknowledge a procedure separately, use individual procedure sign-off.


Walkthrough

1. Describe the briefing

Create a Checklist with a clear title and questions for the topic, date where needed and any follow-up notes. Explain whether the performing User is recording attendance or also delivering the briefing. Keep the purpose explicit in the introductory Text Element.

2. Add named attendees

Add a Member Question, choose Multiple Select and allow Users. Use the question title “Who attended this briefing?” if it fits your process. Selecting a User Group would record a group, not a verified list of individual attendees.

3. Limit the attendee list deliberately

Use Limit to users and groups where appropriate. The performing User’s Location access, group membership and delegation still constrain the picker; a limit does not grant access to otherwise unavailable people. Test it as the supervisor who will complete the form.

4. Schedule the briefing record

Schedule the Checklist for the intended supervisor and Location, with an appropriate timing and reviewer. Use an Ad Hoc Slot for a one-off briefing. Complete a controlled example and confirm the attendee names and notes appear as intended in its Result.


Check the outcome

Use this Checklist in the mobile app, not RideOps, which does not support Member Questions. Check the attendee picker is populated: an empty eligible list can count as answered without names. A Member Question records selections; it does not award a Competency, record each selected person’s login or prove their individual acknowledgement. A Signature Question on this shared record does not create separate sign-offs for every selected attendee. Use a Certification Process when the work must award a qualification.


Best practices

  • Select named Users for an individual attendance list.

  • Keep sensitive discussion details out of a broadly shared form.

  • Agree who reviews follow-up actions after the briefing.


Frequently asked questions

Why can’t the supervisor select someone?

The picker applies Location access and User Group or delegation rules, plus any Limit to selection. Check those settings rather than recreating the person’s account.

Does selecting attendees certify them?

No. A Member Question records who was selected. Awarding a Competency requires a Certification or Certification Process.

Can each attendee receive their own sign-off record?

Use a workflow where each person completes their own Checklist or Certification Process. One shared attendance Result is not a set of individual acknowledgements.

Did this answer your question?