All Forms At a Glance
ICS FormForge covers eight of the most-used NIMS ICS forms. Forms with a green border are required in every IAP. Forms with a blue border are commonly included.
ICS-201
Incident Briefing
Completed first, at incident onset. Transferred to incoming IC. Sets the foundation for all other forms.
Core IAP
ICS-202
Incident Objectives
IAP cover page. SMART objectives, command emphasis, safety plan location. IC must approve.
Core IAP
ICS-203
Org Assignment List
Every activated ICS position by name. The incident "who's who." Updated every operational period.
Core IAP
ICS-204
Assignment List
Work assignments for each Division/Group. One per division per period. Ops Chief approves.
Core IAP
ICS-205
Radio Comms Plan
Master frequency list. Every channel, function, tone, and assignment. Distributed before the period starts.
Core IAP
ICS-205A
Communications List
Personnel phone/radio directory by ICS position. Mark sensitive if it includes cell numbers.
Optional IAP
ICS-206
Medical Plan
Aid stations, ambulance services, hospitals, emergency procedures. Safety Officer must review.
Core IAP
ICS-208
Safety Message / Plan
Hazards, PPE, evacuation, emergency contacts. Updated every period by Safety Officer.
Optional IAP
ICS-207
Org Chart Generator
Auto-built from ICS-203 data. Visual org chart — IC, Command Staff, four sections. Fill ICS-203 first, generate here.
Auto-generated
How to Use ICS FormForge
A quick walkthrough of the tool from start to a print-ready form.
Fill the Incident Header — once, for all 21 forms
The blue Incident Header bar at the top auto-fills Incident Name, Incident Number, and Operational Period dates across every form simultaneously. Enter it once and never retype it. Individual form fields can still be overridden manually if needed.
Select your form from the sidebar
Use the left-hand tabs to choose between all 21 forms (ICS-201 through ICS-233CG, plus the ICS-207 Org Chart Generator). Each tab shows a color-coded progress dot — gray means empty, amber means started, green means all required fields are filled.
Fill in the fields
Fields marked with a red asterisk (*) are required before generating. All other fields are optional — fill only what's activated for your incident. Leave unused positions blank.
Add repeatable rows as needed
Objectives, resources, channels, hazards, and contacts can all be expanded with the + Add button. Remove any row with the × button in its corner.
Click "Generate Form →"
Your completed form appears below the input fields. Choose between Clean View (screen-readable, easy to scan) or Print Layout (structured like the official ICS form with section headers and signature blocks).
Save your session
Hit 💾 Save Session in the Incident Header bar to save all form data to your browser. Your data will be offered for restore next time you open FormForge. Use ⬇ Export JSON to download a backup file, and ⬆ Import to reload it on another device or share with another planner.
Print or export
Use the 🖨️ Print / Save PDF button. In your browser's print dialog, set margins to Minimum and enable Background graphics for the best output. Or use 📋 Copy Text to paste into another system.
💾 Save your session: Use the 💾 Save Session button in the Incident Header bar to save all form data to your browser. On your next visit, FormForge will offer to restore it. Use ⬇ Export JSON to download a portable backup file, and ⬆ Import to reload it on another device or share with another planner.
Note: Saved sessions are stored in your browser's local storage. Clearing your browser data or using a private/incognito window will erase saved sessions. Always export a JSON backup before closing if you need to guarantee data is preserved.
IAP Build Order
Build forms in this sequence — each one informs the next. Operational period times must match exactly across all forms.
1
ICS-201
Incident Briefing
Captures the initial situation, objectives, org, and resources. This is completed at incident onset — everything else references it.
2
ICS-202
Incident Objectives
Formalizes the period objectives and command emphasis. The IAP cover page — IC approves before anything is distributed.
3
ICS-203
Org Assignment List
Names every activated position. Only fill what's staffed. Only fill positions that are actually activated — blank = not staffed.
4
ICS-204
Assignment List
One per Division or Group. Pulls from the ICS-203 for supervisors and from ICS-205 for communications channels.
5
ICS-205
Radio Comms Plan
Master frequency reference. Must be completed before ICS-204, since channel names are referenced there. Distribute before the period starts.
6
ICS-206
Medical Plan
Safety Officer must review before inclusion in IAP. Medical contact info from this form goes onto the ICS-204.
7
ICS-208
Safety Message / Plan
Prepared by Safety Officer every period. Hazards and PPE must reflect current conditions — not copied from the previous period.
8
ICS-205A
Communications List
Built last because it references every person already assigned in ICS-203. Mark sensitive if cell numbers are included.
💡 Then wrap it with IAPForge
Once your forms are complete, IAPForge generates the narrative IAP wrapper — situation overview, command intent, and operational period narrative — that binds everything together into a complete, distributable Incident Action Plan.
📊 ICS-207 Org Chart Generator
After completing ICS-203, open the ICS-207 tab and click Generate Org Chart →. FormForge reads the names you entered in ICS-203 and automatically builds a print-ready visual org chart — IC at the top, Command Staff below, four sections across the bottom. No manual drawing needed. Use landscape orientation when printing.
ICS-201
Incident Briefing
Completed at incident onset. Transferred to incoming Incident Commander during transitions. The foundation document for every other form.
Purpose: Captures the initial incident situation, life-safety concerns, objectives, current organization, and resources in one document. It is the first thing a new Incident Commander reads when taking over. If nothing else gets completed, this form must be.
✓ Use When
- ICS is being activated for any incident
- Handing off command to an incoming IC
- First responders need a documented situation picture
- Documenting initial resources and org before a full IAP is possible
✗ Not For
- Routine status updates mid-incident (use ICS-209)
- Ongoing operational period planning (use ICS-202 + 204)
- Documenting individual unit activities (use ICS-214)
Field Reference
| Field | Required? | Guidance |
|---|---|---|
| Incident Name | Required | Short, consistent name used on all forms. Use the same name across the entire incident — changes cause documentation problems. |
| Incident Number | Optional | Jurisdiction-assigned tracking number. Include if your jurisdiction uses one — it's the key to pulling all documentation post-incident. |
| Operational Period | Required | The time window this form covers. Must match exactly across all forms in the same IAP. |
| Situation Summary | Required | What happened, current conditions, affected area, life-safety threats. Write as if the reader knows nothing — because the incoming IC may not. |
| Health & Safety | Optional | Known hazards, PPE in use, access restrictions. This seeds the ICS-208 — be specific. "Hazardous conditions present" is not enough. |
| Objectives | Required | List in priority order. Use action verbs and time targets: "Establish unified command by 0800." Vague objectives produce vague operations. |
| Command Staff | IC Required | Only fill positions currently activated. Include agency for Unified Command: "J. Smith, Wake County / T. Jones, NCFS." |
| Resources Summary | Optional | Resources on scene or en route. Include unit identifier, personnel count, and current location or assignment. |
| Prepared By | Required | The person completing the form — not necessarily the IC. Include position title (e.g., Initial Attack IC, Planning Section Chief). |
💡 Field Tips — ICS-201
- Fill it fast, fill it first. A rough ICS-201 completed in 10 minutes is more valuable than a perfect one completed in an hour. You can update it.
- Situation summary is not a timeline. Describe the current state, not how you got there. The IC needs to know where things are now, not every step that led here.
- Objectives drive everything else. If something isn't tied to an objective, question whether it should be in the plan at all.
- For Unified Command, the IC field should list all agency representatives: "Williams (County EM) / Torres (Fire) / Patel (Health)."
ICS-202
Incident Objectives
The cover page of every Incident Action Plan. Completed by Planning Section, approved by the Incident Commander before distribution.
Purpose: Formalizes the incident strategy and measurable objectives for a specific operational period. Every other IAP form traces back to the objectives on this page. No IAP is complete without it — and no IAP should leave the planning section without the IC's signature.
✓ Use When
- Starting any formal operational period
- Assembling an Incident Action Plan packet
- Conducting a planning meeting or tactics meeting
- Transitioning command or handing off between operational periods
✗ Not For
- Initial incident capture at onset (use ICS-201 first)
- Documenting individual tactics (use ICS-204)
- Upward status reporting to MAC/EOC (use ICS-209)
Field Reference
| Field | Required? | Guidance |
|---|---|---|
| Objectives | Required | SMART format: Specific · Measurable · Action-oriented · Realistic · Time-sensitive. Example: "Complete evacuation of Zone 2 by 1400 hrs." List in priority order — the first objective is the most critical. |
| Priority | Optional | High / Medium / Low. Helps Operations Section prioritize resource allocation when tradeoffs arise during the period. |
| Command Emphasis | Required | Where the IC wants focus placed this period. Not a restatement of objectives — it's directional guidance: "Prioritize Zone 2 before any movement to Zone 3." Keep it concise; this gets read at briefings. |
| Situational Awareness | Optional | Weather forecast, current conditions, brief safety cue. Must be consistent with ICS-208 if that form is also included in the IAP. |
| Site Safety Plan Required | Optional | Yes/No. If Yes, document where the approved plan is physically located — "Planning Section, ICP Trailer B." Responders need to know where to find it. |
| IAP Checklist | Optional | Check every form and attachment physically included in this IAP packet. Discrepancies between what's checked and what's actually in the packet are an audit flag. |
| IC Approval | Required | IC must sign. An unsigned ICS-202 means the IAP has not been formally approved for the operational period. |
💡 Field Tips — ICS-202
- Objectives are not tasks. "Conduct search operations in Grid 4" is a task. "Account for all missing persons in Grid 4 by 1800" is an objective. The difference matters in after-action review.
- Command emphasis is the IC's voice in the IAP. Write it as a direct statement, not a summary of the objectives already listed above it.
- The checklist matters. If ICS-206 is checked but the Medical Plan isn't stapled to the packet, that's a documentation gap. Check only what's physically attached.
- No verbal approval substitutes. The IC signature is a legal record that this plan was reviewed and authorized. Get the signature before the period starts.
ICS-203
Organization Assignment List
Names every activated ICS position. The incident "who's who." Updated every operational period as staffing changes.
Purpose: Provides a complete, current list of every person filling an ICS position during the operational period. Supports the ICS-207 org chart, informs the ICS-204 supervisor fields, and gives any responder a single reference for who is responsible for what.
| Field | Required? | Guidance |
|---|---|---|
| IC / Unified Command | Required | For Unified Command, list all agency representatives: "Smith (County) / Jones (Fire) / Patel (Health)." Use / to separate. |
| Command Staff | Fill activated only | Safety Officer, PIO, Liaison. If a position is not staffed, leave it blank. "TBD" creates accountability gaps — blank means not activated. |
| Agency Reps | Fill activated only | Representatives from cooperating agencies who are at the ICP. Different from Unified Command members — these are liaisons, not decision-makers. |
| Section Chiefs | Fill activated only | Planning, Logistics, Operations, Finance/Admin. If a section is handled by the IC directly, leave it blank and note it on the ICS-201. |
| Unit Leaders | Fill activated only | Resources Unit, Situation Unit, Supply Unit, etc. Only fill positions actually staffed with a named person. |
| Branches / Divisions | Fill activated only | List Branch name/identifier, Director, and the Divisions or Groups underneath. For shift changes, use: "Smith / Jones (1800)". |
| Finance/Admin | Fill activated only | Time Unit, Procurement, Comp/Claims, Cost Unit. For short-duration incidents, Finance/Admin may not be activated — leave blank. |
💡 Field Tips — ICS-203
- Blank = not staffed. This is correct and expected. Never fill a position with "TBD" or a placeholder — it creates false accountability in documentation.
- Shift changes: If the same position is filled by two people across a shift change during the period, list both: "Williams / Torres (1800 shift)."
- This feeds the ICS-204. The supervisor name on each ICS-204 should match the name on the ICS-203 for that Division/Group.
- The ICS-203 is not an org chart — it's a name roster. The ICS-207 is the visual chart. Both are needed for a complete IAP.
ICS-204
Assignment List
Work assignments and resources for a specific Division or Group during one operational period. Handed directly to Division/Group supervisors.
Purpose: The field supervisor's tactical reference for a single operational period. One form per Division or Group. The supervisor should be able to execute the entire period from this single page — it contains their tasks, their resources, their comms channels, and any special instructions.
| Field | Required? | Guidance |
|---|---|---|
| Branch / Division / Group | Division Required | Geographic (Division A, B, C) or functional (Rescue Group, Medical Group). Branch is the layer above — include it if your incident uses branches. |
| Division/Group Supervisor | Required | Must match the name on ICS-203 for this position. This is who signs for accountability at end of period. |
| Work Assignment | Required | Use action verbs: Conduct, Establish, Maintain, Search, Extinguish. Include location, time targets, and specific outcomes. "Help with operations" is not an assignment. |
| Special Instructions | Optional | Access routes, hazard notes, contingencies, unique PPE. Anything the supervisor needs to know that isn't in the standard assignment. |
| Resources Assigned | Optional | Each unit by identifier (E-205, MEDIC-3), leader name or call sign, personnel count, reporting location and time. Anything not listed here is not officially assigned to this division. |
| Communications | Optional | Pull channel names directly from ICS-205 — use the same names. List command channel, division/ops channel, and medical emergency channel separately. |
💡 Field Tips — ICS-204
- One form per division. Don't combine Division A and Division B on one form. If the supervisor can't find their assignment at a glance, the form has failed its purpose.
- Channel names must match ICS-205. If the ICS-205 says "TAC-1," the ICS-204 must say "TAC-1" — not "Tactical Channel" or "Channel 1."
- Work assignments drive accountability. In an after-action review, the question is "did Division A complete its assigned tasks?" If the assignment was vague, the answer is always "mostly."
- Special instructions are not optional for hazardous incidents. If there are known hazards in this division's area, document them here — not just on ICS-208.
ICS-205
Radio Communications Plan
The master frequency and channel reference for the incident. Every responder should receive a copy before the period begins.
Purpose: Documents every radio channel, frequency, talk group, and tone assignment used on the incident. Eliminates confusion about which channel to use for what. Referenced in ICS-204 for per-division channel assignments. Must be distributed before the operational period starts.
| Field | Required? | Guidance |
|---|---|---|
| Channel Name / Talk Group | Required | The label assigned to this channel for the incident. Be consistent — if you call it "TAC-1" here, everyone calls it "TAC-1." Never use frequency numbers as channel names in field operations. |
| Function | Optional | What this channel is used for: Command, Operations, Medical, Logistics, Air-to-Ground, Tactical, Law Enforcement. One function per channel where possible. |
| Frequency (MHz) or System | Optional | For conventional analog: the MHz value (e.g., 155.340). For trunked/P25: the system name and talk group (e.g., "VIPER / Wake TAC-1" or "P25 / TG 2150"). |
| TX Tone / NAC | Optional | For conventional: the CTCSS/DCS tone for transmitting (e.g., 100.0 Hz, D023N). For P25 digital: the Network Access Code in hex (e.g., 0x293). Without this, radios may not open the squelch. |
| RX Tone / NAC | Optional | Receive tone — often the same as TX for simplex, different for repeater systems. Include both to prevent programming errors. |
| Assigned To | Optional | Who monitors or uses this channel — by role or all personnel. "Command staff only," "All supervisors," "All units." |
| Special Instructions | Optional | Radio discipline rules, channel switching protocols, fallback channels, simplex vs. repeater distinctions. |
💡 Field Tips — ICS-205
- ICS-205 goes out first, always. Responders need frequencies before they go to work. A late communications plan creates an unsafe incident.
- For P25/digital systems, the NAC code is critical. Recording only the frequency on a trunked system is like having only a street address with no building number. Get the NAC.
- Limit talk groups per channel. Multi-agency incidents get complicated fast. Name channels by function (Command, Medical, Air Ops) — not by agency. Interoperability fails when each agency uses its own naming scheme.
- Document the fallback. If the primary channel fails, what does everyone switch to? That instruction belongs in Special Instructions on this form.
ICS-205A
Communications List
The incident phone and radio directory — all contact methods for every assigned person by ICS position. Sensitive if it includes cell numbers.
Purpose: Supplements the ICS-205 with personal contact information. While ICS-205 documents radio channels, ICS-205A documents who is on each channel and how else to reach them. Critical for multi-agency incidents where not everyone knows each other.
| Field | Required? | Guidance |
|---|---|---|
| ICS Position / Assignment | Required | The ICS role the person is filling — not their home agency title. "Division A Supervisor," not "Battalion Chief." Must match ICS-203. |
| Name | Optional | Last name and first initial is sufficient for most incidents. For multi-agency incidents with common last names, include agency affiliation. |
| Primary Contact | Optional | Radio call sign and channel first (e.g., "DIV-A / TAC-2"), then cell number as backup. Field personnel reach each other by radio first. |
| Secondary Contact | Optional | Cell number, satellite phone, or pager. This is why the form may be marked sensitive — cell numbers are personally identifiable. |
| Vehicle ID / Notes | Optional | If the person is assigned to a specific vehicle (ENG-7, HAZMAT-1, MEDIC-3), note it here. Makes them findable on scene when radio comms are congested. |
💡 Field Tips — ICS-205A
- Build it last — after ICS-203 is complete, so you have every activated position to reference.
- Mark it sensitive if it contains personal cell numbers. It is not for public release, media distribution, or posting on public-facing documentation boards.
- Update it at shift changes. If the same position is filled by a different person in the second operational period, the entire contact entry changes.
- Vehicle IDs matter more than people expect. On a busy staging area or complex scene, "find the Division A supervisor" is harder than "find HAZMAT-3."
ICS-206
Medical Plan
Documents all medical resources and emergency procedures for the incident. Safety Officer must review and initial before inclusion in the IAP.
Purpose: Ensures every responder on the incident knows where to get medical help, how to get a person to a hospital, and what to do in a medical emergency. The Safety Officer's signature certifies it has been reviewed for accuracy and adequacy — no signature means the form is not valid for the IAP.
| Field | Required? | Guidance |
|---|---|---|
| Aid Stations | At least one | Name, grid location, contact frequency or phone, paramedics on site. Location must be findable by someone who doesn't know the incident area — use grid coordinates or a landmark, not just "near staging." |
| Ambulance Services | Optional | Service name, staging location, contact, ALS vs BLS level. Note if they're pre-positioned or on-call — response time is different for each. |
| Hospitals | Optional | Full address (not just name), contact number, travel time from ICP, trauma center level (I, II, III), and helipad availability. Travel time changes during an incident — update if routes change. |
| Emergency Procedures | Required | Step-by-step: who calls it, who responds, evacuation route, assembly point. Every responder should be able to recall this from memory — the procedure should be simple enough to brief in 60 seconds. |
| Safety Officer Review | Required | Name, date/time, and signature. The Safety Officer is certifying the information is accurate and procedures are adequate. This is a chain-of-accountability record. |
💡 Field Tips — ICS-206
- ALS vs BLS matters. A BLS unit can stabilize and transport — but can't perform advanced interventions. Know which units you have and document it accurately. A cardiac event managed by a BLS-only unit at a remote incident is a preventable tragedy.
- Trauma center level determines patient destination. Level I can handle everything. Level III is a community hospital. Document the level so Transport knows where to go — not just the nearest facility.
- Emergency procedures must be briefed, not just distributed. Document them on the ICS-206, but ensure supervisors brief their teams before work begins.
- The Safety Officer's signature is non-negotiable. An ICS-206 without it is incomplete and should not be included in the IAP packet.
ICS-208
Safety Message / Plan
Documents site hazards, PPE requirements, and emergency procedures for the current operational period. Prepared by the Safety Officer every period.
Purpose: Communicates the safety environment specific to this incident and this operational period. Unlike a standing SOP, the ICS-208 is incident-specific and period-specific — it must reflect actual current conditions, not generic safety language.
| Field | Required? | Guidance |
|---|---|---|
| Safety Message | Required | Plain-language overview of the safety environment — conditions, priorities, and the single most important thing every responder needs to know before starting work this period. Read at briefings. |
| Hazards | Optional | Every identified hazard by name. Be specific: "downed power lines at Grid 4C" not "electrical hazards." Vague hazard descriptions don't protect anyone. |
| Risk Level | Optional | High / Medium / Low. Used to prioritize briefing emphasis and resource allocation for safety controls. High-risk hazards must have documented mitigations. |
| Mitigation / Control | Optional | The specific control in place: "50-foot exclusion zone established," "Buddy system required," "Level B suit mandatory." Not "PPE required" — that tells nothing about what's actually been done. |
| PPE Requirements | Optional | Specify by zone or task. "Level B hazmat suit in hot zone / N95 and nitrile gloves in warm zone / standard PPE in cold zone." Generic PPE requirements produce PPE gaps. |
| Evacuation Procedures | Optional | Signal (horn, radio, verbal), route, assembly point. Must be known before work begins — not looked up during an emergency. |
| Emergency Contacts | Optional | Safety Officer's radio channel and cell, Medical Unit Leader, and any external emergency numbers specific to this incident. |
💡 Field Tips — ICS-208
- Do not copy-paste from the previous period. Conditions change. Yesterday's ICS-208 does not cover today's hazards. The Safety Officer must review actual current conditions before completing each period's form.
- Hazards without mitigations are just observations. The value of the ICS-208 is documenting that a control is in place — not just that a hazard exists.
- The safety message gets read at briefings. Keep it under 90 seconds spoken. If it's longer, the most important things get buried.
- Align with ICS-202. If the ICS-202 includes a situational awareness note about weather, the ICS-208 should reflect the same weather conditions. Discrepancies between forms create confusion.
- Evacuation signals must be practiced, not assumed. "Three long air horn blasts" means nothing if responders have never heard it before. Note if pre-incident briefing on the signal was conducted.
Power Features
Three built-in features that make FormForge significantly faster and more reliable than working on paper.
🔵
Incident Header — Auto-Fill All Forms
The blue bar at the top of the tool. Enter your Incident Name, Incident Number, and Operational Period dates once — FormForge instantly fills those fields across all 21 forms. This eliminates the most common documentation error: mismatched incident names or op period times across forms.
💡 How to use it
- Fill it first — before opening any individual form. Everything flows from it.
- Individual form fields can still be manually overridden — just type in the field directly. The header won't overwrite manual edits.
- If you change the header mid-session, only fields that haven't been manually edited will update.
- The Incident Name in the header also populates the ICS-207 org chart title automatically.
💾
Save & Resume — Never Lose Your Work
FormForge saves all form data to your browser's local storage. Close the tab, refresh the page, come back hours later — your data is still there. On your next visit, FormForge shows a restore banner offering to reload your session.
| Button | What it does |
|---|---|
| 💾 Save Session | Saves all current form data to your browser. The dot next to it turns green when saved, amber when there are unsaved changes. |
| ⬇ Export JSON | Downloads a portable .json file containing all your form data. Use this to back up, share with another planner, or move to another device. |
| ⬆ Import | Load a previously exported .json file back into FormForge. Useful for starting a new operational period from the same base data. |
| 🗑 Clear All | Wipes all form data and deletes the saved session. Requires confirmation. Cannot be undone. |
Important: Browser local storage is tied to your browser and device. Clearing browser data, using private/incognito mode, or switching browsers will erase saved sessions. Always export a JSON backup before closing for any incident where data loss would be a problem.
📊
ICS-207 Org Chart Generator
The one ICS form that was always better as a visual — now auto-generated from the names you enter in ICS-203. Fill ICS-203 first, then open the ICS-207 tab and click Generate. FormForge builds a complete org chart: IC and Unified Command at the top, Command Staff (Safety Officer, PIO, Liaison) on the second level, and all four Section Chiefs across the bottom.
💡 How to get the best chart
- Fill ICS-203 completely first. The org chart reads directly from those fields — empty fields show as dashes.
- Use landscape orientation when printing. The chart is wider than it is tall.
- Set print margins to Minimum so the chart fills the page without cutting off section names.
- The chart title defaults to the Incident Name from ICS-203. You can override it in the ICS-207 chart options.
- For Unified Command, the IC field in ICS-203 supports slash notation: "Williams (County) / Torres (Fire)" — this displays correctly on the chart.
📂
Template Library — Incident Type Starter Content
Ten built-in incident type templates that pre-fill your forms with field-appropriate starter content. Select an incident type, preview the content, and load it — FormForge fills situation summaries, command emphasis, SMART objectives, safety messages, and hazard/mitigation tables. You review and edit before generating anything.
| Template | Category | Forms Pre-filled |
|---|---|---|
| 🚑 Mass Casualty Incident (MCI) | EMS / Rescue | ICS-201, 202, 208 |
| 🔥 Structure Fire | Fire Operations | ICS-201, 202, 204, 208 |
| 🌲 Wildfire | Wildfire | ICS-201, 202, 204, 208, 209 |
| 🌊 Flood / Natural Disaster | Natural Disaster | ICS-201, 202, 206, 208, 209 |
| ☣ HazMat / Chemical Incident | HazMat | ICS-201, 202, 206, 208 |
| 🏔 Search & Rescue (Technical) | Technical Rescue | ICS-201, 202, 204, 206, 208 |
| 🔍 Missing Person Search | Search & Rescue | ICS-201, 202, 204, 208 |
| 🚔 Active Shooter / LE Incident | Law Enforcement | ICS-201, 202, 206, 208 |
| 🌪 Tornado / Severe Storm | Natural Disaster | ICS-201, 202, 208, 209 |
| 💻 Cyber / Infrastructure Incident | Critical Infrastructure | ICS-201, 202, 203, 209, 233CG |
💡 How to use it
- Open the Template Library using the blue 📂 button at the top of the sidebar (or in the mobile menu).
- Filter by category — Fire, Rescue/EMS, HazMat, Search, Disaster, or Law Enforcement — or search by name.
- Click any card to preview before loading. The preview shows situation summary, command emphasis, safety message, and all objectives.
- Click "Load Template →" to populate the forms. FormForge only fills empty fields — it never overwrites anything you've already typed.
- Always review and edit before generating. Add your jurisdiction name, specific unit identifiers, exact locations, and any incident-specific details.
- Templates work with Save Session — load a template, customize it for your agency, and save as your default starting point for that incident type.
Important: Template content is suggested language based on common ICS practice. It must be reviewed, edited, and approved by the responsible planner before any form is generated or distributed. Never distribute templated content without review.
Master Field Tips
Lessons from ICS practice that apply across the full suite of forms.
📋 Documentation Discipline
- Operational period times must match exactly across all forms. If ICS-202 says 0600–1800 and ICS-204 says 0700–1800, you have a documentation discrepancy that will surface in an after-action review.
- Incident name must be identical across all forms. "Raleigh Flood 2026," "Raleigh Flood," and "Wake Flood Incident" are three different incidents in a documentation audit.
- Don't use placeholders. "TBD," "Unknown," or "N/A" in a required field is worse than leaving it blank. Blank means not activated. "TBD" implies someone was supposed to fill it and didn't.
- Every signature block is a chain-of-accountability record. These are not formalities — they establish who reviewed what, and when.
🔗 Form Interdependencies
- ICS-205 before ICS-204. Channel names on the Assignment List must come from the Radio Comms Plan. Build ICS-205 first.
- ICS-203 before ICS-205A. The Communications List references every position on the Org Assignment List. Build ICS-203 first.
- ICS-206 medical contacts go on ICS-204. The medical emergency channel on each Assignment List should reference the channel documented in the Medical Plan.
- ICS-202 objectives drive ICS-204 assignments. Every work assignment on an ICS-204 should be traceable to at least one ICS-202 objective. If it isn't, question whether it belongs in the plan.
📡 Radio / Communications
- For P25/VIPER trunked systems, record the NAC. The Network Access Code (e.g., 0x293) is what makes the radio work on the right logical channel. A frequency without a NAC is incomplete for digital systems.
- Name channels by function, not by agency. "Wake County Channel 3" fails interoperability. "TAC-1 / Command" works for everyone at the incident.
- Document the fallback channel in Special Instructions. Primary channels fail. Everyone needs to know what to switch to before it happens.
🖨️ Printing & Output
- Print Layout mode produces output structured like the official FEMA ICS form — use this for formal IAP packets and documentation that will be filed.
- Clean View mode is better for screen sharing, quick briefings, and situations where you need readability over format.
- Browser print settings: Set margins to Minimum, enable Background graphics, and use landscape orientation for wide tables (ICS-205, ICS-205A).
- ICS FormForge doesn't save between sessions. Print or PDF each form as you complete it. Don't rely on the tab staying open.
Key Terms
ICS terminology used throughout FormForge and this guide.
| Term | Definition | |
|---|---|---|
| IAP | Incident Action Plan | The written plan for a single operational period. Contains the ICS-202 through ICS-208 and any other approved attachments. |
| Operational Period | The scheduled time window during which assigned resources execute a specific set of tactical actions. Typically 12–24 hours. | |
| ICS | Incident Command System | The standardized management system used for all types of incidents. ICS FormForge generates NIMS-aligned ICS forms. |
| NIMS | National Incident Mgmt System | The federal framework that establishes how agencies at all levels coordinate incident management. ICS is a component of NIMS. |
| SMART Objectives | Specific · Measurable · Action-oriented · Realistic · Time-sensitive. The standard format for ICS-202 objectives. | |
| Division | Geographic subdivision of the incident — Division A, Division B, etc. Has a named supervisor (Division Supervisor). | |
| Group | Functional subdivision — Rescue Group, Medical Group, etc. Crosses geographic boundaries. Has a named supervisor (Group Supervisor). | |
| Branch | The organizational layer above Divisions/Groups. Activated when the span of control for the Operations Chief is exceeded. | |
| Unified Command | ICS structure used when multiple agencies have jurisdiction. All agencies share command, but one IAP governs the incident. | |
| NAC | Network Access Code | A code used in P25 digital radio systems to prevent cross-talk between agencies on the same frequency infrastructure. Required for digital channel programming. |
| ALS / BLS | Advanced/Basic Life Support | ALS units can perform advanced medical interventions (IVs, medications, intubation). BLS units provide basic stabilization and transport. |
| ICP | Incident Command Post | The physical location from which the IC manages the incident. Where IAP forms are prepared and distributed. |
| EOC | Emergency Operations Center | Supports on-scene incident management with coordination, resource management, and policy decisions. Separate from the ICP. |
| MAC | Multi-Agency Coordination | A system that supports incident management by prioritizing and coordinating resources across multiple incidents or jurisdictions. |
The chrislw.com Tool Suite
ICS FormForge is part of a growing suite of emergency management and accessibility tools built for operators who need to move fast under pressure.
Active Tool
ICS FormForge
Generate ICS-201 through ICS-208. Clean view + print-ready output. You're here.
IAPForge
Incident Action Plan
Full IAP narrative generator — the wrapper that binds all FormForge outputs into a complete plan.
CommandShield
Accessibility + EM
Alert accessibility, WCAG compliance, and accessible emergency communications consulting.
Built by Christopher Williams
Operations · Accessibility · Emergency-Informed Systems. Questions, feedback, or custom tool requests: chrislw.com