Home/Blog/How to Fill an ICS 214 Activity Log from an Event Timeline
Blog

How to Fill an ICS 214 Activity Log from an Event Timeline

P
promptstudio
How to Fill an ICS 214 Activity Log from an Event Timeline

Activity logs invent incident numbers. Rows only from the timeline.

The matching generator is the FEMA ICS 214 Activity Log from an Event Timeline (No Invented Incidents) (Fema Ics 214 Activity Log From An Event Timeline No Invented Incidents) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Header fields UNKNOWN when blank

Fill an ICS 214-style activity log from a pasted event timeline. Never invent incidents, resource IDs, or official forms data. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Pasted event timeline: [Timeline]
Incident name I lock (or UNKNOWN): [Incident]
Operational period I lock (or UNKNOWN): [Period]
Unit/name I lock (or UNKNOWN): [Unit]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Max rows: [Max]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

One row per timeline event

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Honesty ledger: Timeline events count, Incident, Period, Unit, Lang, Max. Forbidden: invented incidents, invented resource IDs.
  2. Event map: time + activity from Timeline only.
  3. ICS 214-style table: Date/Time | Notable Activities up to Max rows. Missing header fields UNKNOWN.
  4. Header block: Incident/Period/Unit as given or UNKNOWN.
  5. Refuse list: invented mutual aid IDs, invented casualty counts, invented official form serials.
  6. Diff notes: Banned/Never cuts.
  7. Not-advice banner: training/exercise documentation aid only if Brief says; still no invented facts.
  8. Compliance pass: Banned/Never hits. Row count vs Max. Gaps list of five. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Refuse casualty inventions

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • Activity log from Timeline only. Not a declaration and not press copy.
  • Never invent incidents, resources, or casualties.
  • Honor Max rows.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Keep the not-declaration banner

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (ics 214 activity log, no invented incidents, fema activity log) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.