Skip to content

Weekly Trauma Response Tracker

Trauma responses feel random from the inside β€” ambushes out of clear sky. Tracked for a few weeks, they turn out to have a fingerprint: the Sunday-evening spike, the after-that-meeting shutdown, the specific person who precedes 70% of episodes. This tracker exists to lift that fingerprint. It watches all four responses at once (patterns often hunt in pairs), and it tracks the one number that most reliably improves first: how long before you noticed.

Track episodes, not days

An entry is one episode: any moment a response visibly fired (snapped, bolted, fogged, caved). Log it the same day β€” episode memory decays overnight. The "noticed after" column is the progress metric: two hours shrinks to twenty minutes shrinks to mid-episode, and that shrink IS the skill being built. Three-to-four weeks of sheets is when the fingerprint becomes undeniable.

The exercises

The weekly pattern tracker has 3 sections, in order, each with space to write.

1. The episode log

The week's firings, one line each.

Response codes: FI (fight), FL (flight), FR (freeze), FA (fawn). Blends welcome: "FA→FI" is a classic.

    Day/timeCodeTrigger (best guess)Where/whoIntensity 0-10Noticed after…

    2. The fingerprint read

    End of week: interrogate the table.

    The table knows things you don't. Ask it.

    • ●Time pattern (day of week, time of day my episodes cluster):
    • ●People pattern (who appears in the where/who column more than chance allows):
    • ●State pattern (was I tired/hungry/premenstrual/hungover/unslept before the big ones?):
    • ●My noticing gap this week, averaged β€” and versus last week:

    3. One experiment for next week

    Use the fingerprint on exactly one thing.

    Pick the single clearest finding and design one countermeasure: pre-eat before the Sunday call, walk after THAT meeting, deploy your grounding move at first contact with the named person. One experiment, run for one week, logged on next week's sheet.

    • ●The finding I'm acting on:
    • ●The countermeasure, precisely:
    • ●Next week β€” did episodes around that trigger change (count, intensity, noticing gap)?

    Before you use this

    The weekly pattern tracker is psychoeducation and self-reflection β€” not therapy, diagnosis, or crisis support. Go at your own pace; stopping when overwhelmed is information, not failure. If it stirs up more than you can settle, a trauma-informed therapist is the right next step (our therapy guide compares the options) β€” and the disclaimer has the fine print.

    Weekly Pattern Tracker: FAQ

    Doesn't all this self-monitoring make me MORE obsessed with my problems?

    The distinction that decides it: rumination re-lives episodes; tracking files them. One line per episode, same-day, closed with a column β€” the format is designed to be the opposite of dwelling, and most people find externalising the episode onto paper lets the mind release it rather than loop it. Watch for the genuine failure mode though: if you catch yourself logging in real-time-everything detail, grading yourself, or feeling worse after each entry, shrink to tracking one response only, or pause tracking and keep only the weekly read. Tools serve the person; the moment it inverts, adjust the tool.

    What if a week has almost no episodes β€” good week or bad tracking?

    Ask three questions in order. Was the week genuinely low-load (holiday, no contact with your named people)? Then it is real and informative β€” your pattern needs its triggers, which the fingerprint predicted. Were there moments that WOULD have been episodes once, handled early? Then it is better than real β€” log those as wins on the daily check-in sheet; the tracker undercounts exactly when you improve. Or did the fog/fawn just get quieter and less visible to you? Freeze and fawn especially can fire subtly β€” a lost afternoon, three absorbed impositions β€” and slip the log. If honest review finds these, lower your logging threshold: subtle episodes are episodes.