Skip to content

Actions

Actions are maintenance tasks that can be automatically generated from inspection failures or manually created for general maintenance needs, providing a workflow to track, assign, and resolve issues.

Actions enable:

  • Automatic creation from inspection failures and stock management
  • Manual creation for any maintenance need
  • Public issue reporting by community members
  • Assignment to team members
  • Status workflow tracking
  • Due date management
  • Categorisation for organisation
  • Out of service item tracking
  • Resolution documentation
  • Closure and review process

Actions are automatically created when inspections identify:

  • Failed items: pass_fail items that fail
  • Missing items: present_missing items marked missing
  • Expired items: expiry_date items past 30-day threshold
  • Low quantity: quantity_with_expiry below expected quantity

Each auto-generated action includes:

  • Reference to inspection and specific item
  • Section and subsection labels
  • Item label and type
  • Flagged by user (inspector)
  • Initial status: open
  • Auto-assigned category based on source

Brigade members can manually create actions for:

  • General maintenance needs
  • Building and facility issues
  • PPE and uniform requirements
  • IT system problems
  • Any other maintenance tasks

Manual actions require:

  • Brief description (item reference)
  • Category selection
  • Optional asset linking (vehicle/equipment)
  • Optional template linking for out-of-service tracking

When enabled, community members can report issues via the Station Portal:

  • No login required
  • Submit via web form
  • Include name (optional) and description
  • Select category
  • Add notes with details
  • Administrator notification on submission

Public-reported actions:

  • Flagged as publicly reported
  • Include reporter name (if provided)
  • Marked with category selected by reporter
  • Auto-assigned to “open” status
  • Require administrator review and assignment

Actions follow a defined status workflow:

  • Newly created action
  • Not yet assigned or started
  • Awaiting assignment and planning
  • Work has begun
  • Assigned to team member
  • Actively being addressed
  • Work completed
  • Awaiting verification
  • Can create out_of_service items at this stage
  • Verified and approved
  • Action complete
  • Out of service items auto-reinstated

Actions are organised into categories for better tracking and filtering:

Vehicle

  • Auto-assigned for vehicle inspection actions
  • Vehicle maintenance and repair tasks
  • Color: Blue

Equipment

  • Auto-assigned for equipment inspection actions
  • Equipment maintenance and repair tasks
  • Color: Cyan

Stock

  • Auto-assigned for stock management actions
  • Reorder and restocking tasks
  • Color: Purple

Building & Maintenance

  • Facility repairs and maintenance
  • Building infrastructure issues
  • Available for manual and public actions
  • Color: Amber

PPE & Uniform

  • Personal protective equipment issues
  • Uniform replacements and repairs
  • Available for manual and public actions
  • Color: Green

IT

  • Technology and system issues
  • Software and hardware problems
  • Available for manual and public actions
  • Color: Indigo

Other

  • General maintenance tasks
  • Uncategorised issues
  • Default for manual actions
  • Available for manual and public actions
  • Color: Gray

Categories are automatically assigned for inspection-based actions:

  • Vehicle inspections → Vehicle category
  • Equipment inspections → Equipment category
  • Stock actions → Stock category
  • Manual actions → Default to “Other” (user can change)
  • Public actions → Selected by reporter

When creating manual actions:

  • Select from all available categories
  • Change category after creation
  • Categories help with filtering and reporting

Each action tracks:

  • Item Reference: Brief issue description
  • Category: Organisational category
  • Notes: Detailed notes and comments
  • Inspection reference: Linked inspection and item (if applicable)
  • Stock item reference: Linked stock item (if applicable)
  • Flagged by: User who identified issue (or public reporter name)
  • Assigned to: Responsible team member
  • Due date: Target completion date
  • Status: Current workflow status
  • Created/updated timestamps: Audit trail
  • Manually created flag: Indicates manual vs. auto-generated
  • Template linking: Optional link to inspection template for out-of-service tracking

Actions can be assigned to:

  • Specific team members
  • Workshop technicians
  • External contractors
  • Brigade officers
  1. Review action: Assess issue and requirements
  2. Determine responsible person: Who should address it
  3. Set due date: When it should be completed
  4. Assign: Update action with assignee
  5. Notify: Assignee receives notification

Track action completion targets:

  • Set on creation: Initial due date
  • Modify as needed: Extend or advance
  • Overdue tracking: Alerts for past due actions
  • Due soon warnings: Upcoming due dates
  • Dashboard visibility: Overdue actions highlighted

When actions require marking items unusable:

During action resolution:

  1. Mark action as resolved
  2. Create out_of_service_item
  3. Link to action
  4. Specify reason
  5. Item flagged in system

Out of service items:

  • Prevent item from being selected in inspections
  • Display warning when viewing asset
  • Track reason and created_by user
  • Link to parent action

When action is closed:

  • Associated out_of_service_item automatically removed
  • Item becomes available again
  • Reinstatement recorded in audit trail

When enabled at the unit level, the public can report issues:

Brigade administrators can:

  • Toggle public issue reporting in settings
  • Appears on Station Portal
  • Shows count of open public issues
  • Provides “Report Issue” link

Public reporters:

  1. Access Station Portal
  2. Click “Report Issue” or view issues page
  3. Optionally enter name (or select from member list)
  4. Enter issue description
  5. Select category
  6. Add optional detailed notes
  7. Submit report

The system supports:

  • Anonymous reporting (no name required)
  • Manual name entry
  • Autocomplete from unit member list
  • Linking to existing user account if selected

When issue is reported:

  • Email sent to brigade administrators
  • Includes reporter name (if provided)
  • Shows issue description and category
  • Links to action in system
  • Marked as publicly reported

Only certain categories available for public reporting:

  • Building & Maintenance
  • PPE & Uniform
  • IT
  • Other

Vehicle, Equipment, and Stock categories are excluded as they require inspection context.

The public issues page shows:

  • Count of open public issues
  • List of active public issues
  • Category badges
  • Assignment status
  • Time since reported
  • Current status (open/in progress)

Brigade administrators:

  • Review and triage public reports
  • Assign to appropriate team member
  • Set due dates
  • Add additional notes
  • Resolve through normal action workflow
  • Can link to template/asset if needed
  • Actions assigned to current user
  • Personal task list
  • Sortable by due date, status
  • All actions for brigade/unit
  • Management overview
  • Filter by status, assignee, asset, category
  • Filter by specific category
  • Vehicle, Equipment, Stock, etc.
  • Helps organise work by type
  • Inspection actions
  • Stock actions
  • Manual actions
  • Public issues
  • Filter by creation source
  • Actions past due date
  • Priority attention required
  • Escalation candidates
  • Recently created or updated
  • Activity monitoring
  • Quick access to active work
  • Update status to in_progress
  • Begin addressing issue
  • Document progress in notes
  • Perform required repairs or maintenance
  • Test and verify fix
  • Document work performed
  • Capture photos if applicable
  • Update status to resolved
  • Add resolution notes
  • Set out_of_service if needed
  • Notify relevant parties
  • Supervisor reviews resolution
  • Verifies work completed
  • Closes action
  • Out of service items reinstated

Manual actions can be linked to inspection templates and assets:

Linking enables:

  • Out-of-service functionality for manual actions
  • Template item reference for consistency
  • Asset tracking (vehicle or equipment)
  • Better integration with inspection workflow

After creating manual action:

  1. View action details
  2. Click “Link to Template” if not already linked
  3. Select inspection template
  4. Select specific template item (optional)
  5. Select asset (vehicle or equipment)
  6. Save linking

Link manual actions when:

  • Action relates to specific inspection item
  • Need to mark item out of service
  • Want consistent tracking with inspections
  • Relates to specific asset

Manual actions can be unlinked:

  • Remove template association
  • Clear asset reference
  • Cannot mark out of service without link

Filter actions by:

  • Status: Open, in_progress, resolved, closed
  • Assignee: Specific team member
  • Asset: Vehicle or equipment
  • Category: Vehicle, Equipment, Stock, Building, PPE, IT, Other
  • Source: Inspection, Stock, Manual, Public
  • Due date: Overdue, due soon, all
  • Date range: Created or updated within period

Generate action reports:

  • Open actions: Current workload
  • Completion rates: Actions closed vs created
  • Response times: Time to resolution
  • By asset: Actions per vehicle/equipment
  • By assignee: Workload distribution
  • Overdue analysis: Bottlenecks and delays

Actions link back to inspections:

  • Inspection reference: Which inspection flagged issue
  • Item reference: Specific failed item
  • Section context: Where in checklist
  • Inspector: Who identified issue
  • Response data: Original inspection response

View inspection from action:

  • Click inspection link
  • See full inspection context
  • Review other items from same inspection
  • Review new actions daily
  • Assign actions promptly
  • Set realistic due dates
  • Update status regularly
  • Document work thoroughly
  • Match skills to action type
  • Balance workload across team
  • Consider availability and capacity
  • Set clear expectations
  • Follow up on assignments
  • Safety issues: High priority, immediate due dates
  • Operational impacts: Medium priority, near-term
  • Preventive maintenance: Lower priority, flexible timing
  • Compliance items: Priority based on deadline
  • Notify assignees of new actions
  • Update stakeholders on progress
  • Escalate overdue actions
  • Document resolution clearly
  • Close loop with inspectors
  • Mark out of service only when necessary
  • Document reason clearly
  • Update operational teams
  • Track impact on availability
  • Resolve quickly to reinstate