Retyping the incident on every form
The incident name, county, unit, and crew carry onto every daily 214 automatically.
Field operations State mutual aid deployments
TIFMAS Deployments New
Run Texas Intrastate Fire Mutual Aid System deployments from the road: daily ICS 214s, crew and equipment hours, travel and purchases, and a TDEM reimbursement packet built from what was recorded.
- Daily ICS 214s
- TDEM packet from recorded hours
- 45- and 90-day packet clocks
Why departments switch
What TIFMAS fixes.
Enter a deployment once — the incident, county, resource order or STAR, the resource as ordered, and when the crew left and came home. Each day’s ICS 214 is seeded from it, equipment hours on signed 214s become the equipment log, and labor, per diem, lodging, and purchases are priced against the state’s rules. When the crew is home, the packet shows what is claimed, what still needs checking, and the days left before TDEM’s deadline, then downloads the files to send.
- No day without a 214
- Hours priced at the state’s rates
- A packet ready before the deadline
Days with no 214
Missing days and unsigned drafts are listed across every open deployment, because equipment hours are claimed only from signed logs.
Pricing hours by hand
Equipment carries FEMA cost codes and rates, labor uses each person’s rate and fringe, and per diem fills itself at 75% on the first and last day.
Packets that miss the deadline
Every deployment shows the 45 days TIFMAS aims for and the 90-day TDEM deadline, and the packet lists what still needs checking.
Inside the module
A closer look at TIFMAS.
Real screens from Station Clipboard, shown with a sample department.
01
Every deployment
Crews out now, packets still open, and closed deployments in one register.
- Days out with extended flags
- Packet due countdown
- Wildland and all-hazard missions
02
Daily ICS 214
One activity log per day, seeded from the deployment and locked once signed.
- A tick on every finished part
- Signed by the strike team leader
- Export to PDF
03
Labor from the 214s
Deployed and backfill hours filled from the activity logs and priced at each person’s rate.
- Filled from the 214s
- Wages plus fringe
- Backfill priced on its own line
04
Documents checklist
Everything TDEM asks for, with policies and the W-9 uploaded once for the whole department.
- 12 of 16 items on file
- Department-wide files reused
- Missing items listed first
On the phone
214s from the road
Write and sign the day’s log on a phone while the crew is still deployed.
How it works
From setup to a record you can trust.
Start
Enter the incident, county, resource order, crew, and apparatus — from the station or from the road.
Log each day
Write the 214 for each operational period, record equipment hours and operators, and sign it.
Cost it
Fill labor from the 214s, fill per diem, and add lodging, meals, mileage, purchases, and rentals.
Send the packet
Check the documents list, review the amounts claimed, and download the workbook, signed forms, and supporting files.
Capabilities
Everything TIFMAS includes.
Daily ICS 214s
Seeded from the deployment, with activities, crew, equipment hours, and operators. Signed logs are locked and export to PDF.
Apparatus and FEMA rates
Equipment typed to the current FEMA schedule, with cost codes, hourly rates, and the reduced rate for TIFMAS grant engines.
Equipment logs
Built from signed 214s and signed by the operator and the supervisor.
Labor and backfill
Deployed and backfill hours filled from the 214s and priced at each person’s rate plus fringe.
Travel and per diem
GSA rates, lodging, group meals, mileage, and receipts, with lines that no longer add up flagged.
Purchases and damage
Materials, rentals, contracts, and apparatus damage, each with the documentation the state asks for.
Documents checklist
Every item TDEM asks for, with department-wide files uploaded once and counted on every deployment.
Reimbursement packet
Amounts claimed by cost type, the Invoice and forms PDF, the filled TDEM workbook, and a foldered zip of supporting files.
Part of one portal
Works with the rest of your department.
Members keep one secure sign-in and one set of role permissions across every module you turn on.
Questions
TIFMAS FAQ
Does a deployment use our schedule or apparatus list?
No. A deployment keeps its own crew and apparatus roster, so TIFMAS runs on Core alone. You don’t need Scheduling, Assets, or Payroll.
Who sees pay rates?
Only people with the TIFMAS costs permission. Others can run a deployment, keep the rosters, and write 214s without seeing what anyone is paid. Signing 214s is a separate permission.
What about training assignments?
Mark the deployment as a training assignment. Salaries and backfill are priced at zero, as TIFMAS requires, and lodging, meals, and fuel can still be claimed.
Does it submit the packet to TDEM?
No. It builds the files: the Invoice and signed forms PDF, TDEM’s workbook (uploaded once) filled from the deployment, and the supporting documentation. Your department sends them.
See TIFMAS with your department’s workflow.
Tell us how you handle this work today. We’ll walk you through it in the full Station Clipboard portal.
Need something we don’t have yet? We build custom modules.