This article guides administrators through the process of creating and managing riding positions for apparatuses within First Due. Riding positions define the specific crew assignments on fire apparatus (e.g., Driver/Operator, Officer, Firefighter 1, Firefighter 2) and are essential for accurate personnel accountability, crew tracking, and incident documentation. By establishing standardized riding positions, agencies ensure consistent reporting across all incidents and maintain clear records of personnel deployment on each apparatus.
Riding positions are a foundational element of apparatus configuration in First Due's Incident Documentation module. These positions represent the specific roles and locations where personnel are assigned on each piece of apparatus during emergency responses. Common riding positions include Driver/Operator, Officer, Firefighter (various positions), and specialized roles like Paramedic or Technical Rescue Technician.
Why Riding Positions Matter:
Common Use Cases:
Prerequisites:
To create and manage riding positions, users must have the following permissions:
Required Permission Level:







Do's:
Don'ts:
Tips for Success:
Q: I created a riding position but it's not appearing when I try to assign it to an apparatus. Why?
A: After creating riding positions in this setup area, you must separately assign them to specific apparatus through the apparatus configuration. Navigate to the apparatus management section and edit each apparatus to assign the appropriate riding positions.
Q: Can I rename a riding position after it's been used on incident reports?
A: Yes, you can edit position names at any time using the pencil icon. However, be aware that changing the name will affect how it displays on all past and future incident reports. If the position has been extensively used, consider whether the name change is necessary or if creating a new position might be more appropriate.
Q: What happens to incident reports if I delete a riding position that was used on those reports?
A: Deleting a riding position that exists on historical incident reports may cause data integrity issues. The position may still display on old reports but will no longer be available for new incidents. Exercise caution and review usage before deleting any position. Consider archiving or renaming unused positions rather than deleting them.
Q: How many riding positions should I create for each apparatus?
A: Create enough positions to match your maximum staffing capacity for each apparatus type. For example, if an engine can carry up to 5 personnel, create 5 distinct positions. It's better to have positions available even if they're not always filled than to lack positions when you need them.
Q: Can different apparatus types share the same riding position names?
A: Yes, riding positions are global across all apparatus. Once created, a position like "Officer" or "Driver/Operator" can be assigned to any apparatus type. This promotes consistency in reporting across your agency.
Q: I accidentally deleted an important riding position. Can it be recovered?
A: Deleted riding positions cannot be recovered through the system. You'll need to recreate the position using the same name. If the position was assigned to apparatus, you'll need to reassign it to those apparatus. To prevent accidental deletion, carefully review the confirmation modal before selecting Confirm.
Q: Should I create positions for temporary staffing variations?
A: Create positions for your standard staffing configuration rather than temporary variations. For example, if you occasionally staff an additional firefighter position, create that position even if it's not always filled. Field users can simply leave unfilled positions empty during incident documentation.
Q: How do riding positions relate to crew assignments?
A: Riding positions define the available slots on an apparatus. During incident response, personnel are assigned to these positions to create the crew. The positions themselves are the framework; the actual personnel assignments are the crew roster.