Set the Fire Department group active before touching the terminal. The terminal checks the active group before it requests staff access.
TPFD Fire Department Guide
This guide walks Fire Department staff through the TPFD terminal: opening and updating calls, building detailed incident reports with stacked notes, assigning responders, completing inspections, documenting investigations, and referring reports to TPPD when police follow-up is needed.
Cloud-backed TPFD records
Build the report as the scene develops.
The terminal keeps a permanent incident header for the basic call information, then lets staff keep appending report sections as the scene grows. You do not have to force the entire fire scene into one short input box.
FirefighterCalls, reports, responders, notes, investigations, referrals, inspections, and personal activity.
CommandEverything Firefighters can use, plus department staff administration.
Numbered listsFull names and report entries print privately in local chat; the dialog uses short number buttons for selection.
Records first: the cloud report is the permanent record. Meaningful creates and updates are also mirrored to the TPFD Discord log, while simply viewing a report does not create Discord spam.
Access and menu selection
The cloud must recognize you as active TPFD staff. Normal members receive FIREFIGHTER access; department leadership can be assigned COMMAND.
When a list contains reports, notes, responders, nearby avatars, or staff, the complete entries are printed privately to you in local chat.
Select the matching 1, 2, 3... button in the dialog. This keeps long names and report titles out of Second Life's button-length limits and reduces script memory use.
Main TPFD terminal menu
Tip: Active Calls and Reports both lead into the same incident record menu after you select a report. The difference is which report list you start from.
Create the incident header first
Choose New Incident
The terminal prints the available incident types in local chat and opens numbered selection buttons.
Select incident type
Choose the number matching the type. The list is paginated when needed.
Enter location
Type the incident address or scene location into the text prompt.
Enter a short summary
Use this as the incident header, not the full roleplay transcript. The terminal creates the call with an initial ON SCENE status.
Build the real report
After creation, use Add Note repeatedly for narrative, damage, witness statements, investigation details, medical assistance, and later updates.
Supported incident types
Structure FireVehicle FireBrush FireExplosionSmoke / AlarmGas LeakVehicle AccidentRescueMedical AssistHazmatWater RescueFalse AlarmOther
Keep the opening summary short. The permanent report is designed to grow through additional note sections, so the scene is not limited to a single Second Life text box.
Report notes stack instead of replacing each other
The incident header is intentionally compact. Detailed RP belongs in append-only note sections. Every time you use Add Note, you choose a note type and enter another section. Existing sections remain in the report history.
Main scene narrative, firefighter observations, suppression actions, rescue details, and the chronological story of the response.
Later developments, changing scene conditions, follow-up actions, or information learned after the initial entry.
Property, vehicle, structural, equipment, smoke, water, or other damage observations.
Witness statements or identifying information relevant to the fire/rescue report.
Origin-area observations, suspected cause, evidence observations, and investigation reasoning.
High-level on-scene medical-assist information. Hospital staff still own diagnosis and treatment records.
Command decisions, scene-control directions, review notes, or department-level additions.
Anything that does not fit the standard note categories.
No one-box report ceiling: if one section is not enough, save it and use Add Note again. The report can contain as many separate note sections as the RP needs.
Status, disposition, and investigation are different fields
Status = where the call is now
Dispatched → En Route → On Scene → Controlled → Cleared is the normal progression. Cancelled is available when the call does not continue.
Disposition = how the scene ended
Examples include Extinguished, Rescue Completed, Patient Transported, False Alarm, Unable to Locate, Scene Secured, or Investigation Pending.
Investigation = current cause classification
Choose Undetermined, Accidental, Natural, Incendiary, Equipment, or Other. Use Investigation notes for the actual reasoning and evidence details.
Do not use a dropdown as the whole report
Status and classification fields make records searchable and understandable. They should support the written notes, not replace them.
Referring a fire report to TPPD
Use PD Referral → Refer to TPPD when the fire scene needs police follow-up—for example a suspected incendiary fire, criminal activity discovered during the response, or another incident where TPPD needs the report.
Referral does not turn the fire report into a police report and does not let TPPD rewrite Fire Department notes.
The cloud lets authorized TPPD officers pull fire reports and PD-visible notes so they can review the Fire Department record without duplicating it.
When police create or identify the appropriate Justice case, the Fire report can be linked to that case reference so both departments can trace the same RP event.
A referral is a request for police follow-up. It does not automatically create a warrant, arrest, charge, or conviction.
Fire inspections
The Inspections button opens its own workflow so department staff can create ongoing inspection records separately from emergency incidents.
Open or Completed
Review existing inspections. Entries print in local chat and are selected with numbered dialog buttons.
New Inspection
Enter the property/business name, then its location/address, then a short reason or summary.
Add findings
Use Add Note as many times as needed for exits, extinguishers, alarms, hazards, follow-up, owner statements, or other findings.
Set Status
Use Open, Pass, Conditional, Fail, or Closed to show the inspection's current result.
Inspection notes use the same stacked-note idea as incident reports. Keep adding sections instead of trying to fit every finding into the initial summary.
Department staff administration
Command users receive the Admin button on the main menu. The administration helper keeps staff management separate from normal incident work.
Command actions are audited. Staff additions, role changes, and removals are saved to the Fire Department cloud and mirrored to the department Discord logging path.
A clean TPFD report from dispatch to clearance
Create the call
Choose the closest incident type, enter the location, and write a short opening summary.
Add responders
Record the firefighters participating in the scene so the incident has a response roster.
Write notes during RP
Add short, focused report sections as events happen instead of waiting until the end and trying to reconstruct everything.
Update operational status
Move the call through the appropriate status as the department responds and gains control of the scene.
Record outcome and cause
Set a disposition and, when appropriate, the current investigation/cause classification.
Refer when police are needed
Use TPPD Referral for criminal or suspicious follow-up and keep investigation notes detailed enough for another department to understand the handoff.
Clear the call
When the response is finished, update the status so the record moves out of the active-call workflow.