Chase log templates

Why log

• Compare forecast with reality.
• Identify pattern recognition improvements.
• Document targets that worked or didn't.
• Track chase decisions.
• Learn from mistakes.
• Build institutional knowledge.
• Reference for future similar setups.
• Insurance and legal documentation.
• Community sharing potential.
• Long-term career records.

Daily chase log elements

1. Date.
2. Location (start point, target zone, chase locations).
3. Distance driven.
4. Fuel used.
5. Weather forecast (which model, what timing, what accuracy).
6. Actual weather (times, locations, features observed).
7. Chase decisions and rationale.
8. Communication (chase partners, home base).
9. Photographs taken.
10. Reports made to NWS.
11. Lessons learned.
12. Reflections.

The specific fields to include

Digital log formats

The seasonal log

• Total chase days.
• Total tornado intercepts.
• Miles driven.
• Fuel cost.
• Best chase.
• Worst bust.
• Season lessons.
• Gear performance.
• Communication reliability.
• Community connections.
• Photography output.
• Business income if applicable.

The career log

Post-chase debrief format

1. 1. What went well?
2. 2. What went wrong?
3. 3. Was target right?
4. 4. Was positioning right?
5. 5. Was safety maintained?
6. 6. Was equipment ready?
7. 7. Was communication effective?
8. 8. What would I do differently?
9. 9. What did I learn?
10. 10. How does this compare to similar setups?

The specific things to record

The learning-focused log

1. What did I predict?
2. What actually happened?
3. Where did prediction fail?
4. Which model was closest?
5. What could I have known ahead of time?
6. What did I miss visually?
7. What did I do right?
8. What patterns did I recognize?
9. What did I not recognize?
10. How can I improve next time?

The business-focused log

1. Miles driven.
2. Fuel cost.
3. Hotel cost.
4. Meal cost.
5. Gear used.
6. Photos taken.
7. Photos sold.
8. Client communications.
9. Invoices sent.
10. Payments received.
11. Tax-deductible portion.

The safety-focused log

1. Escape routes identified.
2. Vehicle safety systems.
3. Communication reliability.
4. Fatigue level.
5. Medical status.
6. Weather monitoring.
7. Community position awareness.
8. Near-miss documentation.
9. Post-storm recovery.
10. Sleep before/after.

The community-focused log

1. Reports made to Skywarn.
2. Coordination with other chasers.
3. Content shared publicly.
4. Community education efforts.
5. Mentoring newcomers.
6. Chase group participation.
7. Public safety contributions.
8. Media appearances.

Frequency of review

Sharing your log

• Personal blog.
• Chase community forums.
• Educational content.
• Newsletter.
• Podcast material.
• Book potential.
• Some private always.
• Community benefit potential.
• Personal privacy considerations.

The Skip Talbot approach

Well-known chaser Skip Talbot maintains meticulous chase logs and shares detailed post-chase analysis publicly.

• Detailed weather setup analysis.
• Chase decision points explored.
• Photography and video with commentary.
• Community learning tool.
• Personal growth documentation.
• Model for chase logging.

The Chris Kridler approach

Chase author Chris Kridler maintains chase logs with photography focus.

• Storm structure documentation.
• Photography output tracking.
• Composition notes.
• Business tracking.
• Educational sharing.
• Long-term career records.

The template you should build

1. Structured fields.
2. Consistent format.
3. Photos linked.
4. Weather forecast comparison.
5. Lessons learned.
6. Cost tracking.
7. Business metrics if applicable.
8. Reflection space.
9. Categorization tags.
10. Search functionality.

Learn more

• Tornado chase log tracker
• Storm chase off-season
• Chase day timing guide
• Chase day forecasting mistakes