Purpose Statement

The Activities Logging feature in Fire Investigations allows investigators to create and maintain a chronological record of actions performed throughout an investigation.

Activity logs can document supplemental or critical investigative actions, such as meetings, evidence collection, coordination with outside agencies, or other actions that may occur outside standard protocols. Maintaining these records helps provide a complete investigation history for reporting, supervisory review, and potential court testimony.

Background Information

Investigations often involve activities that need to be documented separately from the primary investigation report. The Activities Logging section provides investigators with a centralized location to record, review, edit, and manage these activities throughout the lifespan of an investigation.

Examples of activities may include:

• Meetings with forensic teams or other personnel.
• Obtaining or executing warrants.
• Collecting CCTV footage or other evidence.
• Coordinating with outside agencies.
• Documenting actions that deviate from standard protocols.
• Recording other supplemental investigative actions.

Each activity is associated with the investigation, allowing investigators and supervisors to reference a chronological history of actions taken.

Required Permissions

Users must have access to the Fire Investigation module and the appropriate permissions to access and modify investigations.

Specific permission names required for Activities Logging could not be confirmed from the available documentation. If a user cannot access the Fire Investigation module, open an investigation, or modify its activities, verify their assigned role and Fire Investigation permissions with a First Due administrator.

Video

Step-by-Step Guide
 

1. Navigate to the Investigation List

From the First Due module stack, select Fire Investigation, then navigate to the Investigation List.

2. Open an Investigation

From the Investigation List, either:

• Open and edit an existing investigation.
• Create a new investigation.
  
  
  
  
   

3. Open Activities Loggin

Within the investigation, select Activities from the investigation menu to open the activities grid.



 

4. Add and Save an Activity

Select Add to create a new activity entry.



 

Complete the applicable activity information. Available fields may include:

• Activity name or type. (Required)
• Start and end date/time.
• Personnel or users.
• Notes.

After entering the activity information, select Save.

The activity is added to the Activities Logging grid, where investigation activities can be reviewed as part of the investigation record.



5. Manage Existing Activities

From the Activities Logging grid, use the available actions to:

• Edit an existing activity.
• Delete an activity.
• Add another activity as needed.
  
  

6. Save the Investigation

After you have finished adding or managing activities, select Save on the investigation to save your changes.



 

Best Practices

• Add activities as they occur to maintain an accurate chronological investigation record.
• Include enough detail in notes, results, and findings for another investigator or supervisor to understand the action that was performed.
• Assign the appropriate personnel to activities so investigative actions can be attributed to the individuals involved.
• Record significant actions outside standard protocols, including applicable deviations, to maintain a complete investigation history.
• Review activity entries for accurate dates, times, personnel, and details before saving.
• Use consistent terminology when documenting similar investigative activities.
• Avoid relying on the Activities Logging section for consent or warrant documentation when those records are managed through a separate workflow.

Use Case Example

An investigator conducts a supplemental meeting with a forensic team during an active investigation. The investigator creates an activity entry documenting the meeting, its date and time, the personnel involved, and relevant notes or findings.

A supervisor can later review the Activities Logging grid to verify that supplemental investigative actions have been documented. The investigator can also reference the chronological activity history when preparing reports or providing an account of actions taken during court proceedings.

Troubleshooting & FAQs

Why can't I access Activities Logging?

Confirm that you have access to the Fire Investigation module and permission to access the applicable investigation. If the option remains unavailable, contact your First Due administrator to review your assigned permissions.

Can I change an activity after I save it?

Yes. From the Activities Logging grid, use the Edit action to modify an existing activity and save your changes.

Can I delete an activity?

Yes. Use the Delete action available for the applicable activity in the grid.

What information is required when creating an activity?

The video workflow identifies the activity Name as required. Additional fields can be completed as applicable to the investigative activity being documented.

Can multiple personnel be associated with an activity?

Yes. The activity entry supports adding applicable users or personnel to the activity.

What types of actions should be documented as activities?

Activities can be used for supplemental investigative actions such as meetings, evidence collection, obtaining warrants, collecting CCTV footage, coordinating with outside agencies, or documenting actions outside standard protocols.

Are consent and warrant documents stored in Activities Logging?

The release notes indicate that consent and warrant documentation may be managed separately through Form Builder in a future release. Follow your agency's current documentation process for these records.

Suggested Tags

fire-investigation, activities-logging, investigation, activity-log, workflow, data-entry, permissions, investigator