Build a roster dispatch can use Audience: Administrators Build a roster dispatch can use Welcome to Resgrid Academy. In this lesson, we will build a roster dispatch can use. An out-of-date roster leaves dispatchers guessing which station, team, or role a member belongs to. We will explain the features, the setup decisions, and a practical way to check the result. A department scenario A volunteer department creates Station 1 and Station 2 groups, invites 24 members and assigns Engineer and Firefighter roles. Dispatch, notifications, permissions and reports all start from who belongs to which group, so set this up first. The examples in this series use a fictional department and are teaching scenarios, not default settings. Personnel Personnel. Member accounts, contact details and status. Invite members or add them directly, then check that each has a mobile number or email address. Manage Invites Manage Invites. Email invitations for new members to join the department. Send invitations and follow up on any that have not been accepted. Groups & Stations Groups & Stations. Stations and groups that organize members and units. Create a station group for each station with its address, and organizational groups for teams, then add members. Personnel roles Personnel roles. Roles such as Firefighter, EMT or Officer. Create the roles you dispatch or report on, and assign them to members. Add Person Add Person. Create a member account directly instead of sending an invitation. Have your member list with email addresses or mobile numbers, and decide how stations or teams are grouped. New Group New Group. Create a station or group. Have your member list with email addresses or mobile numbers, and decide how stations or teams are grouped. Configure one useful workflow For the training scenario, work in this order. Step 1. Create Station 1 and Station 2 with their addresses. Step 2. Invite sample members and assign their station groups. Step 3. Create Engineer and Officer roles and assign them deliberately. Verify the result Now verify the result. Verify a sample member appears in the correct group and role. Check an accepted invitation and the member contact details. A common problem to watch for: An invitation is not an accepted membership. A role label is not proof of a current certification. Review both separately. Try it with your department Your practice task is simple. Invite one sample member, assign a station and role, and have that member sign in. Track unaccepted invitations. Record the result, who owns the follow-up, and when it should be reviewed. Examples for your department Fire / EMS: Use a fictional fire or EMS department for this exercise. Your practice task is simple. Invite one sample member, assign a station and role, and have that member sign in. Track unaccepted invitations. Record the result, who owns the follow-up, and when it should be reviewed. Community paramedicine and mental health response: Create operational roles for clinicians and peer responders, then track credentials separately; membership does not establish clinical scope. Search and rescue: Use roles such as Search Team Leader and Navigation Specialist; review current qualifications and actual availability before assignment. Security companies and departments: Use Patrol Officer and Site Supervisor roles; scope group administration to the intended site and reserve department administration for department-wide ownership. Wildland contractors: Use Crew Leader, Saw Operator and Driver roles; review seasonal roster membership and current credentials before deployment. Industrial emergency response teams: Use ERT Leader, HazMat Technician and Equipment Operator roles; role labels do not replace qualification review.