This section records the factual skeleton of the event: what happened, when, who was involved, and how the situation unfolded. Please answer as precisely as memory and available records allow. Where you are uncertain, say so rather than estimating. This form is an internal learning tool and does not replace any formal review, legal, regulatory, or compliance process your organization may require.
Incident reference or tracking ID
Short incident title (as it is now referred to internally)
Person completing this form
Role or function of the person completing this form
Which category best describes this incident?
Product or service outage/availability loss
Performance degradation or partial feature failure
Data loss, corruption, or unauthorized access event
Security vulnerability disclosure or exploitation
Public relations or reputation crisis
Supply chain, vendor, or third-party failure
Physical, facilities, or workplace safety event
Financial, billing, or transaction error
Regulatory, contractual, or partner dispute
Other (please describe)
Please describe the outage: what was unavailable, to whom, and for how long.
Please describe what data or access was affected and how the issue was discovered.
Please summarize the public narrative, the channels involved, and the main concern raised.
Please describe the incident in your own words.
How was the incident first detected?
Automated monitoring or alerting
Customer or end-user report
Internal team member noticed manually
Partner, vendor, or supplier notification
Public or media inquiry
Scheduled audit, review, or test
Other (please describe)
Roughly how long after the problem began was the first customer report received?
Please describe how the incident came to light.
When did the incident begin (best known start)?
When was the incident first detected or reported?
When was the incident declared or escalated formally?
When was service, operations, or normal conditions restored?
When was the incident formally closed or stood down?
Total duration of customer or operational impact (in minutes)
Time to detect the incident (in minutes, from start to detection)
Time to acknowledge or mobilize a response (in minutes, from detection to first response action)
Time to full resolution (in minutes, from detection to restoration)
What was the highest severity level reached during the event?
Severity 1 - Critical: widespread or total loss of a core service or function
Severity 2 - Major: significant impact to a large group of users or operations
Severity 3 - Moderate: limited impact with a workaround available
Severity 4 - Minor: minimal impact, mostly internal
No formal severity scale is used in this organization
Did the incident affect external customers, users, or the general public?
Please describe who was affected, in what way, and roughly how many people or accounts were impacted.
Please describe the internal groups or functions that were affected instead.
Was any data lost, exposed, altered, or made unavailable as a result of this incident?
What kinds of data were affected?
Customer or user account data
Transaction or billing records
Internal documents or knowledge base content
Configuration or system state data
Credentials, keys, or access tokens
Analytics or reporting data
None confirmed - still under assessment
Other (please describe)
Please describe the data affected and the current assessment.
Which systems, products, or functions were involved or impacted?
Customer-facing website or application
Mobile application
Backend services or APIs
Data platform, database, or storage layer
Internal tooling or employee systems
Payments, billing, or order processing
Communications systems (email, messaging, notifications)
Third-party or vendor-integrated services
Physical infrastructure, facilities, or equipment
None of the above/not applicable
Was a formal incident response process or on-call rotation activated?
Who led the response, and how quickly was the response team assembled?
What response approach was used instead, and what made a formal process impractical or unnecessary?
Who held decision-making authority during the response?
A designated incident commander or response lead
A senior engineering or technical lead
A product or operations manager
A communications or public relations lead
An executive or business leader
Decisions were made collectively with no single owner
Authority was unclear or contested
Please describe how unclear authority affected the response and what would have helped.
Please reconstruct the sequence of events below. Include the moment the problem began, key decisions, mitigation attempts, communications sent, and the point of resolution. Add as many rows as you need.
Incident timeline reconstruction
Timestamp | Event, action, or decision | Person or team involved | Category | Minutes since incident start | Notes, outcome, or lesson | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | 4/17/2027, 9:12 AM | Automated alert fired for elevated error rates on checkout service | Platform monitoring | Detection | 0 | Alert routed to on-call channel; first human acknowledgement came later | |
2 | 4/17/2027, 9:31 AM | Response team assembled and severity declared | Incident commander | Escalation | 19 | Declaration took longer than expected due to uncertainty about blast radius | |
3 | 4/17/2027, 10:05 AM | Mitigation applied: traffic rerouted to secondary cluster | Backend team | Mitigation | 53 | Restored partial availability within 12 minutes | |
4 | 4/17/2027, 11:40 AM | Full service restored and monitoring confirmed stable | Platform team | Resolution | 148 | Follow-up verification window extended to 2 hours | |
5 | |||||||
6 | |||||||
7 | |||||||
8 | |||||||
9 | |||||||
10 |
In two or three sentences, describe what happened in plain language that someone outside the team would understand.
Was there any prior warning, near-miss, or related issue in the weeks before this incident?
Please describe the earlier warning signs and what was done (or not done) at the time.
Please attach any supporting material: logs, timelines, dashboards, screenshots, or prior post-incident notes (optional).
Root-cause analysis is about understanding the conditions that made the incident possible, not about assigning blame. Most significant incidents arise from a combination of technical, process, and organizational factors. Please describe what you know, what you suspect, and what remains unverified.
What is the clearest statement of the problem that this analysis needs to explain?
Immediate trigger: what was the last action, change, or event before the incident began?
Underlying cause: what conditions allowed the trigger to become an incident rather than a minor blip?
Five whys exercise: write out the chain of 'why' questions and answers that leads from the symptom to the deeper cause.
Which contributing factors played a role? Select all that apply.
Software defect or code change
Configuration or environment change
Infrastructure, capacity, or scaling limits
Dependency or third-party failure
Human error during an operational task
Unclear ownership or responsibility
Insufficient monitoring, alerting, or observability
Gaps in testing, review, or change control
Knowledge gaps or undocumented assumptions
Time pressure, competing priorities, or resource constraints
Communication breakdown between teams
Legacy or technical debt in the affected system
Other (please describe)
Please describe the task being performed and what made the error easy to make. Focus on conditions, not individuals.
Please describe the additional contributing factor.
Which single factor would you consider the primary root cause at this stage?
A technical defect or design flaw
A process or procedure gap
A missing or inadequate control or safeguard
A communication or coordination failure
A resourcing, prioritization, or workload issue
A third-party or external dependency
Insufficient knowledge, training, or documentation
Too early to determine with confidence
Was there a safeguard, check, or control that should have prevented or caught this incident but did not?
Which safeguard failed or was missing, and why do you think it did not work as intended?
What safeguard would have been needed to prevent this class of incident, and does anything similar exist today?
Was the incident made worse by how it was handled after it began?
Please describe which response decisions, delays, or actions extended or amplified the impact.
How confident is the team in the current root-cause explanation?
High confidence - supported by logs, evidence, or reproduction
Moderate confidence - consistent with the evidence but not fully verified
Low confidence - largely based on inference or partial information
Not yet established - analysis is still in progress
What evidence supports your current explanation? Please list the specific logs, metrics, test results, or observations that confirm it.
What alternative explanations were considered and ruled out, and on what basis?
Has the root cause been reproduced in a test or staging environment?
Please describe the reproduction and its result.
What would be needed to reproduce it, and who is best placed to do so?
How well did the organization's existing detection capability perform for this incident? (1 = failed to detect at all, 5 = detected almost instantly)
Why was the incident not detected earlier? What signal was missing, delayed, or ignored?
Have similar incidents or near-misses occurred before, within this team or elsewhere in the organization?
Please describe the earlier events and what was learned or changed at the time. If nothing was changed, please note why.
What is the most important single insight from this analysis that leadership should understand?
Incidents take a toll on people as well as systems. This section is about the human cost of the response and the conditions the team is working in now. There are no right answers, and individual responses should be treated as confidential feedback rather than performance data. If your organization offers employee support resources, consider reaching out to them directly as well.
How many people were directly involved in responding to this incident?
Approximately how many hours did you personally spend on the incident response and its aftermath?
Did the incident require work outside your normal working hours, including nights, weekends, or scheduled time off?
Which of the following applied to you during the response period?
Worked through the night or across multiple time zones
Missed or shortened a scheduled break or meal
Canceled or interrupted personal or family commitments
Worked on a day I would normally have off
Continued working while unwell or exhausted
Skipped sleep or significantly reduced sleep
None of the above
Please indicate how much you agree with each statement about your experience during and after the incident.
Strongly disagree | Disagree | Neither agree nor disagree | Agree | Strongly agree | |
|---|---|---|---|---|---|
I felt clear about what I was personally responsible for during the response | |||||
I had the information I needed to make good decisions under pressure | |||||
I felt supported by my teammates and colleagues | |||||
I felt supported by my manager or leadership during the response | |||||
The workload during the response was manageable | |||||
I felt able to speak up about concerns or mistakes without fear of blame | |||||
I have had adequate time to recover since the incident ended | |||||
I feel proud of how the team handled the situation | |||||
I am currently feeling emotionally drained by my work | |||||
I am worried that a similar incident could happen again soon |
How are you feeling right now, overall, in relation to your work?
How would you rate the team's current energy and morale?
Which statement best describes your current capacity to take on new work?
Fully recovered and ready for normal workload
Mostly recovered, but I am pacing myself
Still stretched thin and struggling to keep up
Running on empty and close to burnout
I would prefer not to answer
What is contributing most to the strain right now, and what would help reduce it?
Please describe what you are experiencing. If you feel comfortable, note what kind of support would make the biggest difference.
Do you feel that the incident response affected your confidence in your own work or judgment?
Please describe what affected your confidence and what would help rebuild it.
Would you like someone to follow up with you privately about support or workload?
Who would you prefer to hear from?
My direct manager
A people, human resources, or wellbeing contact
A peer or colleague I trust
An external or confidential support service
No preference
Understood. Please tick to confirm you are aware of how to reach support later if your needs change.
Which forms of support would be most helpful to you and the team right now?
Additional time off or a lighter workload for a period
Clear prioritization so that non-urgent work can be paused
A debrief or facilitated team conversation
Recognition or acknowledgment of the effort involved
Practical help with follow-up tasks and documentation
Training, mentoring, or pairing to close knowledge gaps
Access to confidential wellbeing or counseling support
Better staffing or on-call coverage going forward
Nothing additional is needed at this time
How psychologically safe did the team environment feel during and after the incident?
Very unsafe
Mostly unsafe
Mixed
Mostly safe
Very safe
Did anyone on the team experience criticism, blame, or negative consequences that felt unfair in connection with this incident?
Please describe what happened in general terms. Do not name individuals unless you feel it is necessary and appropriate.
Is there anything else about the human or team impact of this incident that you want to make sure is understood?
This section examines how well existing processes, tools, and communication channels supported the response, and where they fell short. The goal is to identify structural improvements rather than individual shortcomings. Please consider both internal coordination and any communication with customers, partners, or the public.
Please rate how effectively each of the following worked during this incident.
Very poorly | Poorly | Adequately | Well | Very well | Not applicable | |
|---|---|---|---|---|---|---|
Detection and alerting | ||||||
Acknowledgement and escalation | ||||||
Roles, ownership, and decision rights | ||||||
Access to relevant systems, logs, and data | ||||||
Coordination between engineering and non-technical teams | ||||||
Coordination with external vendors or partners | ||||||
Internal status updates to the wider organization | ||||||
External communication to customers or the public | ||||||
Documentation and record-keeping during the response | ||||||
Handover between shifts, time zones, or responders | ||||||
Post-incident follow-up and action tracking |
Where were the most significant process or communication gaps? Select all that apply.
No clear runbook or documented procedure for this scenario
Existing runbook was outdated, incomplete, or hard to find
Escalation path was unclear or too slow
Too many people involved, causing duplication of effort
Too few people involved, creating bottlenecks
Unclear who had authority to approve customer-facing decisions
Communication channels were fragmented or overwhelmed
Status updates were infrequent or inconsistent
Customer or public messaging was delayed or unclear
Insufficient context shared with frontline or support teams
Handover between responders lost important information
Monitoring and dashboards did not answer the key questions
Vendor or partner communication was slow or one-sided
Other (please describe)
What should a runbook for this scenario cover, and who would be best placed to write it?
Please describe what was delayed or unclear in external communication and how it affected trust or outcomes.
Please describe the additional gap you observed.
How quickly was accurate information shared with the people who needed it?
Within minutes, and it was accurate
Within minutes, but early information was later corrected
Significant delay before the right people were informed
Some people who needed to know were never informed
Information spread informally and inconsistently
What caused the early information to be wrong, and how did the correction go?
Who was left uninformed or informed late, and what was the impact?
Were customer-facing or public communications issued during the incident?
Which channels were used to communicate externally?
Status page or service health page
In-product or in-app notification
Email or direct message to affected users
Social media or public posts
Direct outreach to key accounts or partners
Media or press statement
Community forum or support channel
Other (please describe)
Please specify the channel used.
What prevented external communication from being issued, and what would be needed to enable it in future?
How clear, honest, and timely was the communication to those affected?
Very poor
Poor
Acceptable
Good
Excellent
No communication was issued
Did internal teams receive enough context to answer questions from customers, partners, or colleagues?
What made this work well, and how can it be repeated?
What information were frontline or support teams missing, and how did that affect the people they were helping?
How well did existing documentation and knowledge base content support the response?
Excellent - responders found what they needed quickly
Adequate - some searching was needed but it worked
Poor - documentation was outdated, scattered, or missing
Non-existent - responders relied entirely on individual knowledge
Not applicable
Did the incident reveal a dependency on a single individual's knowledge or availability?
Which area is most affected by this single point of knowledge, and what would reduce the risk?
Which tools or systems helped most during the response?
Monitoring and alerting platform
Logging and tracing tools
Chat or messaging platform
Video or voice conferencing
Shared incident document or dashboard
Ticketing or case management system
Runbooks or internal documentation
Direct phone calls or text messages
None of these were particularly helpful
If you could change one process or communication practice before the next incident, what would it be and why?
What should we stop doing, start doing, or continue doing based on this experience?
This final section converts learning into concrete commitments. Each action should have a clear owner, a realistic timeframe, and a way of knowing when it is done. Please favor a small number of high-impact actions over a long list of vague intentions. Actions recorded here are internal planning commitments and are not guarantees of future performance.
Which categories of preventive action are most needed? Select all that apply.
Technical fix or code change
Architecture or design improvement
Monitoring, alerting, or observability improvement
Automated testing or verification
Runbook, documentation, or knowledge capture
Process or workflow change
Training, drills, or simulation exercises
Staffing, on-call, or workload adjustment
Vendor, contract, or third-party management
Communication templates or channel improvements
Governance, review, or approval changes
Culture, psychological safety, or team practices
Has an interim mitigation already been put in place to reduce the immediate risk?
Please describe the interim mitigation, when it was applied, and any limitations or side effects it introduces.
What is preventing an interim mitigation from being applied, and what would unblock it?
Please list each planned action below. Use one row per action. Assign a single accountable owner rather than a group, and set a target date that reflects the real capacity of the team.
Preventive action and accountability matrix
Action to be taken | Category | Accountable owner | Supporting people or teams | Priority (1 = low, 5 = critical) | Target completion date | Estimated effort in person-hours | Success measure or verification method | Current progress percentage | ||
|---|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | I | ||
1 | Add an automated consistency check that blocks configuration changes when dependent services are not updated in the same release | Automated testing or verification | Priya Raman, Platform Lead | Release engineering | 6/30/2027 | 120 | Change is rejected in staging when a dependent service is out of sync | 10 | ||
2 | Create and publish a runbook for partial checkout failure, including escalation thresholds and customer messaging templates | Runbook, documentation, or knowledge capture | Daniel Okoye, Support Manager | Incident commander guild | 5/31/2027 | 40 | Runbook reviewed and used successfully in the next simulation exercise | 0 | ||
3 | Reduce on-call load by adding a second responder to the weekend rotation for the payments area | Staffing, on-call, or workload adjustment | Mei Lin, Engineering Director | People operations | 7/15/2027 | 24 | Weekend pages are shared across at least two responders | 0 | ||
4 | Introduce a monthly 45-minute incident simulation covering detection, escalation, and communication | Training, drills, or simulation exercises | Sam Whitfield, Reliability Program Manager | Team leads | 8/1/2027 | 60 | At least one simulation completed per quarter with documented findings | 0 | ||
5 | ||||||||||
6 | ||||||||||
7 | ||||||||||
8 | ||||||||||
9 | ||||||||||
10 |
Please rank the following improvement themes in order of priority for the next quarter, from most to least important.
Preventing recurrence of this specific failure mode | |
Improving detection and time to respond | |
Reducing team workload and burnout risk | |
Improving communication with customers and partners | |
Strengthening documentation and shared knowledge | |
Reducing dependency on individual experts |
How will progress on these actions be reviewed?
Reviewed in a dedicated follow-up meeting within two weeks
Reviewed as part of a regular team or operations meeting
Tracked in a shared action register reviewed monthly
Reviewed by a steering group or leadership forum
No review mechanism has been decided yet
Who should own setting up a review mechanism, and by when?
Target date for the follow-up review of this incident and its actions
Is any additional investment, budget, or executive decision required to deliver these actions?
Please describe what is needed, the approximate scale of the request, and who the decision-maker is.
Should any findings or actions from this incident be shared more widely across the organization as a learning opportunity?
What level of sharing feels appropriate?
A short written summary shared with all teams
A presentation or learning session open to interested staff
A sanitized case study for onboarding or training
Sharing only the general lessons, without incident specifics
Not yet - share only after the review is complete
What is the single most important thing that must not be forgotten once the urgency of this incident fades?
Any final comments, risks, or concerns you would like to add?
I confirm that the information I have provided is accurate to the best of my knowledge, and that any areas of uncertainty have been identified as such.
Name of the person submitting this form
Date of submission
Please sign to confirm this submission.
Analysis for Post-Incident Intake & Recovery Assessment Form
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This Post-Intake & Recovery Assessment Form is a well-structured, five-section intake instrument designed for teams recovering from a major corporate incident, product outage, or public relations crisis. It balances factual documentation with human-impact assessment and forward-looking action planning. The form’s architecture mirrors a natural post-incident workflow: first capture what happened, then understand why, then assess how people were affected, then evaluate process effectiveness, and finally commit to concrete improvements. This logical progression supports both completeness of data and cognitive ease for respondents who may still be under stress.
Incident reference or tracking ID — This field anchors the entire submission to an existing incident record. Operationally, it allows the form response to be cross-referenced with monitoring systems, ticketing platforms, or internal logs. Its placeholder example makes the expected format clear.
Short incident title (as it is now referred to internally) — A concise internal label gives reviewers immediate context. Asking for the “as it is now referred to” phrasing acknowledges that incidents often acquire informal names during response, which can be useful for quick identification.
Person completing this form — Establishing who authored the submission supports follow-up conversations and accountability. It also clarifies whose perspective is represented in the answers.
Role or function of the person completing this form — This optional field adds useful context about the respondent’s vantage point without adding mandatory friction. It helps reviewers weigh the perspective behind each answer.
Which category best describes this incident? — A broad single-choice taxonomy with ten options covers a wide range of incident types. The conditional follow-up prompts (for outages, data events, PR crises, and “other”) are a strong design choice: they collect detailed narrative only when relevant, avoiding unnecessary questions for simpler incidents.
How was the incident first detected? — Understanding detection pathways is operationally valuable for evaluating monitoring and escalation effectiveness. The follow-ups for customer-reported and “other” detection routes add targeted detail without burdening all respondents.
When did the incident begin (best known start)? — A precise start timestamp is foundational for all subsequent timing calculations. The qualifier “best known” appropriately acknowledges that exact start times may be uncertain.
When was the incident first detected or reported?, When was the incident declared or escalated formally?, When was service, operations, or normal conditions restored?, and When was the incident formally closed or stood down? — These four optional date-time fields form a comprehensive timeline skeleton. Together they allow computation of detection lag, response mobilization time, restoration time, and formal closure. Keeping them optional is pragmatic since not all organizations track every milestone.
Total duration of customer or operational impact (in minutes) — A single numeric field capturing the headline impact duration. Using minutes as the unit provides consistency across submissions and simplifies aggregation.
Time to detect the incident (in minutes, from start to detection), Time to acknowledge or mobilize a response (in minutes, from detection to first response action), and Time to full resolution (in minutes, from detection to restoration) — These three optional numeric fields operationalize common incident-response metrics. They enable trend analysis across incidents and highlight where time is being lost.
What was the highest severity level reached during the event? — A five-option severity scale (including a “no formal scale” option) accommodates organizations with and without established severity frameworks. This is a thoughtful inclusivity choice.
Did the incident affect external customers, users, or the general public? — A yes/no gate that branches into descriptive follow-ups for both outcomes. This design ensures the form captures impact scope without assuming the incident was externally visible.
Was any data lost, exposed, altered, or made unavailable as a result of this incident? — A conditional data-impact assessment. The yes-branch includes a multiple-choice list of data types, which supports structured categorization. This is a proportionate way to surface data-handling concerns without presuming a data breach occurred.
Which systems, products, or functions were involved or impacted? — A multiple-choice field covering customer-facing, backend, data, internal tooling, payments, communications, third-party, and physical infrastructure. This breadth ensures the form is useful across diverse incident types.
Was a formal incident response process or on-call rotation activated? — This yes/no question with follow-ups on both branches reveals whether the organization’s formal response mechanisms were used and, if not, why. It surfaces process maturity gaps.
Who held decision-making authority during the response? — A single-choice question with a follow-up for unclear authority. This directly addresses a common source of response friction and is well-targeted.
Incident timeline reconstruction — A structured table with columns for timestamp, event, person/team, category, minutes since start, and notes. The example rows demonstrate the expected level of detail. This table is one of the form’s strongest features: it produces a reusable, chronological narrative that can feed directly into review documents.
In two or three sentences, describe what happened in plain language… — This plain-language summary field is excellent for ensuring the incident can be communicated to non-technical stakeholders. The placeholder example sets a clear tone and length expectation.
Was there any prior warning, near-miss, or related issue in the weeks before this incident? — A yes/no question that surfaces precursor events. This is operationally valuable for identifying recurring patterns and missed signals.
File upload (supporting material) — An optional attachment field for logs, dashboards, screenshots, and prior notes. This supports evidence-based review without making uploads mandatory.
What is the clearest statement of the problem that this analysis needs to explain? — Framing the problem statement before diving into causes is a strong analytical practice. It ensures the subsequent investigation stays focused and that the final explanation addresses the right question.
Immediate trigger: what was the last action, change, or event before the incident began? — Distinguishing the trigger from the underlying cause is a hallmark of mature root-cause analysis. This field captures the proximate event without conflating it with systemic factors.
Underlying cause: what conditions allowed the trigger to become an incident rather than a minor blip? — This question pushes respondents toward systemic thinking. The placeholder example illustrates the distinction between trigger and root cause effectively.
Five whys exercise — A structured field for the classic iterative questioning technique. The detailed placeholder example walks through the method, making it accessible even to respondents unfamiliar with the approach.
Which contributing factors played a role? Select all that apply. — A comprehensive multiple-choice list of twelve contributing factors plus “other.” The follow-ups for human error and “other” are appropriately framed to focus on conditions rather than individuals.
Which single factor would you consider the primary root cause at this stage? — Forcing a single-choice selection from eight options (including “too early to determine”) encourages prioritization while acknowledging analytical uncertainty.
Was there a safeguard, check, or control that should have prevented or caught this incident but did not? — Both yes and no branches lead to constructive follow-ups: either why the existing safeguard failed, or what safeguard would be needed. This is a balanced design.
Was the incident made worse by how it was handled after it began? — This question separates incident cause from response quality, which is an important distinction for learning.
How confident is the team in the current root-cause explanation? — A four-level confidence scale (including “not yet established”) calibrates how much weight reviewers should place on the analysis. This is a thoughtful epistemic-honesty feature.
What evidence supports your current explanation? — Requiring evidence grounds the analysis in verifiable data rather than speculation. This is one of the form’s most valuable mandatory fields.
What alternative explanations were considered and ruled out, and on what basis? — Asking about ruled-out alternatives strengthens analytical rigor and prevents premature conclusions.
Has the root cause been reproduced in a test or staging environment? — A yes/no gate with follow-ups on both branches. Reproduction is a strong validation step, and the no-branch follow-up asks what would be needed, keeping the conversation constructive.
How well did the organization’s existing detection capability perform for this incident? (1–5) — A simple digit rating that provides a quick quantitative signal about detection effectiveness.
Why was the incident not detected earlier? What signal was missing, delayed, or ignored? — This open-ended field complements the rating with qualitative detail about detection gaps.
Have similar incidents or near-misses occurred before? — A yes/no question with a detailed follow-up. Surfacing recurrence patterns is critical for prioritizing systemic fixes.
What is the most important single insight from this analysis that leadership should understand? — This mandatory field distills the analysis into a single actionable takeaway for decision-makers. It is an effective way to ensure the form produces a clear message, not just raw data.
How many people were directly involved in responding to this incident? — A simple headcount that provides context for workload and resource assessments.
Approximately how many hours did you personally spend on the incident response and its aftermath? — Personal effort quantification helps estimate the human cost of the incident. Allowing one decimal place accommodates approximate values.
Did the incident require work outside your normal working hours… — A yes/no question with a detailed multiple-choice follow-up covering nights, missed breaks, canceled commitments, unwell work, and sleep loss. This captures the breadth of disruption without being intrusive.
Matrix rating: Please indicate how much you agree with each statement… — A ten-item agreement matrix covering role clarity, information access, peer and leadership support, workload manageability, psychological safety, recovery time, team pride, emotional drain, and recurrence worry. This is a comprehensive well-being instrument that covers both positive and negative indicators.
How are you feeling right now, overall, in relation to your work? — An emotion rating field that captures current affective state. This is a human-centered design choice that complements the structured matrix above.
How would you rate the team’s current energy and morale? — A five-star rating providing a quick team-level sentiment signal.
Which statement best describes your current capacity to take on new work? — A five-option single-choice (including “prefer not to answer”) with follow-ups for the two most strained options. The follow-ups ask what would help, making the data actionable.
Do you feel that the incident response affected your confidence in your own work or judgment? — A yes/no question with a constructive follow-up. This addresses a less commonly captured but important psychological impact.
Would you like someone to follow up with you privately about support or workload? — A yes/no gate that branches into either a preference question or a confirmation checkbox. This is a well-designed consent-and-routing mechanism that respects respondent autonomy.
Which forms of support would be most helpful to you and the team right now? — A multiple-choice list of nine support options (including “nothing additional”). This provides actionable data for well-being planning.
How psychologically safe did the team environment feel during and after the incident? — A five-point rating from “very unsafe” to “very safe.” Psychological safety is a meaningful indicator of team health and learning capacity.
Did anyone on the team experience criticism, blame, or negative consequences that felt unfair… — A sensitive yes/no question with a follow-up that asks respondents not to name individuals unless necessary. This is a responsible framing for capturing blame-related concerns.
Is there anything else about the human or team impact of this incident that you want to make sure is understood? — An open-ended catch-all that gives respondents space to surface concerns not covered by structured fields.
Matrix rating: Please rate how effectively each of the following worked during this incident. — An eleven-item matrix covering detection, escalation, roles, access, cross-team coordination, vendor coordination, internal and external communication, documentation, handover, and follow-up tracking. The inclusion of “not applicable” as a scale option is a thoughtful design detail.
Where were the most significant process or communication gaps? Select all that apply. — A fourteen-option multiple-choice list with targeted follow-ups for runbook gaps, external communication delays, and “other.” This is a comprehensive gap-identification tool.
How quickly was accurate information shared with the people who needed it? — A five-option single-choice with follow-ups for corrected information and uninformed parties. This addresses both speed and accuracy of information flow.
Were customer-facing or public communications issued during the incident? — A yes/no gate with a detailed channel-selection follow-up on the yes branch and a constructive “what prevented it” follow-up on the no branch.
How clear, honest, and timely was the communication to those affected? — A six-point rating including “no communication was issued.” This captures communication quality from the affected party’s perspective.
Did internal teams receive enough context to answer questions from customers, partners, or colleagues? — A yes/no question with follow-ups on both branches. This addresses frontline readiness, which is often overlooked.
How well did existing documentation and knowledge base content support the response? — A five-option single-choice covering excellent through non-existent, plus “not applicable.” This surfaces knowledge-management maturity.
Did the incident reveal a dependency on a single individual’s knowledge or availability? — A yes/no question with a follow-up on key-person risk. This is a valuable structural observation for organizational resilience.
Which tools or systems helped most during the response? — A multiple-choice list of nine tool categories (including “none were particularly helpful”). This provides practical data for tooling investment decisions.
If you could change one process or communication practice before the next incident, what would it be and why? — This mandatory open-ended field forces prioritization and produces a single, actionable recommendation. It is an effective way to cut through noise.
What should we stop doing, start doing, or continue doing based on this experience? — A classic retrospective framing that encourages balanced reflection.
Which categories of preventive action are most needed? Select all that apply. — A twelve-option multiple-choice list spanning technical, process, training, staffing, vendor, communication, governance, and cultural improvements. This ensures action planning is holistic.
Has an interim mitigation already been put in place to reduce the immediate risk? — A yes/no gate with follow-ups on both branches. This surfaces immediate risk-reduction status before longer-term planning.
Preventive action and accountability matrix — A detailed table with columns for action, category, accountable owner, supporting people, priority, target date, estimated effort, success measure, and progress percentage. The example rows demonstrate the expected granularity. This table is the form’s primary output for follow-through and is well-designed for tracking.
Please rank the following improvement themes in order of priority… — A ranking exercise covering six improvement themes. This forces trade-off thinking and produces a clear prioritization signal.
How will progress on these actions be reviewed? — A five-option single-choice (including “no review mechanism decided”) with a follow-up for the undecided case. This ensures accountability mechanisms are explicitly addressed.
Target date for the follow-up review of this incident and its actions — An optional date field that anchors the review commitment in time.
Is any additional investment, budget, or executive decision required to deliver these actions? — A yes/no gate with a descriptive follow-up. This surfaces resource needs early.
Should any findings or actions from this incident be shared more widely across the organization as a learning opportunity? — A yes/no gate with a five-option sharing-level follow-up. This encourages organizational learning while respecting sensitivity.
What is the single most important thing that must not be forgotten once the urgency of this incident fades? — This mandatory open-ended field is a powerful closing question. It captures the respondent’s deepest concern about institutional memory loss.
Any final comments, risks, or concerns you would like to add? — An open-ended catch-all for anything not covered elsewhere.
Confirmation checkbox — A statement of accuracy and identification of uncertainty. This is a lightweight attestation that supports data integrity.
Name of the person submitting this form and Date of submission — Standard closing fields that finalize the submission record. The name field is distinct from the earlier “person completing this form” field, which may serve different purposes (author vs. submitter).
Signature — An optional signature field that adds a layer of formal confirmation to the submission.
This form is a comprehensive and thoughtfully designed post-incident intake instrument. Its five-section structure covers the full arc from factual documentation through root-cause analysis, human impact, process evaluation, and forward-looking action planning. Key strengths include: extensive use of conditional follow-ups that collect detail only when relevant; a balanced mix of structured (single-choice, multiple-choice, matrix, rating) and open-ended fields; example rows and placeholder text that set clear expectations; and a strong emphasis on psychological safety and non-blame framing in the well-being section. The form also demonstrates good epistemic honesty by including confidence ratings and “too early to determine” options. Areas for potential refinement include: the form is quite long, which may challenge completion rates under time pressure; some respondents may benefit from the ability to save partial progress; and the distinction between “person completing this form” and “name of the person submitting this form” could be clarified to avoid confusion. Overall, this is a strong operational tool that balances depth with usability.
Mandatory Question Analysis for Post-Incident Intake & Recovery Assessment Form
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
Incident reference or tracking ID
Recommendation: Requiring this field supports record linkage and ensures each submission can be associated with an existing incident record in the organization’s tracking systems. It reduces administrative effort during review and prevents ambiguity when multiple incidents are being assessed concurrently. The necessity of this field depends on whether the organization maintains a formal incident tracking system; if not, an alternative reference scheme may be more appropriate.
Short incident title (as it is now referred to internally)
Recommendation: Requiring a concise title ensures that every submission is immediately identifiable and can be quickly referenced in summaries, dashboards, or review meetings. It supports efficient scanning and prioritization of submissions. The form creator may wish to provide guidance on maximum length to keep titles consistent.
Person completing this form
Recommendation: Requiring the respondent’s name supports follow-up communication and clarifies whose perspective is represented in the submission. It is operationally useful for scheduling debriefs or clarifying ambiguous answers. Depending on the organization’s data handling practices, consider whether a display name or a full name better serves the intended use.
Which category best describes this incident?
Recommendation: Requiring incident categorization supports structured aggregation and trend analysis across multiple incidents. It enables reviewers to filter and compare submissions by incident type. The conditional follow-ups already collect additional detail for specific categories, so requiring the initial selection does not create excessive burden.
When did the incident begin (best known start)?
Recommendation: Requiring a start timestamp provides the anchor point for all subsequent timing calculations and timeline reconstruction. Without this field, key metrics such as detection lag and total impact duration cannot be reliably computed. The qualifier “best known” appropriately acknowledges that exact times may be uncertain.
Total duration of customer or operational impact (in minutes)
Recommendation: Requiring a single impact-duration figure provides a headline metric that is easy to aggregate and compare across incidents. It supports prioritization and resource-allocation decisions. The form creator may wish to clarify whether this should reflect the widest scope of impact or the most severe affected segment.
What was the highest severity level reached during the event?
Recommendation: Requiring a severity classification supports consistent prioritization and ensures that submissions can be triaged appropriately. The inclusion of a “no formal severity scale” option makes this field inclusive for organizations without established frameworks. The necessity of this field depends on whether the organization uses severity levels in its operational processes.
Did the incident affect external customers, users, or the general public?
Recommendation: Requiring this yes/no determination ensures that external impact is explicitly assessed in every submission, which supports communication planning and stakeholder awareness. The conditional follow-ups on both branches collect relevant detail without overburdening respondents whose incidents were purely internal.
In two or three sentences, describe what happened in plain language…
Recommendation: Requiring a plain-language summary ensures that every submission includes an accessible narrative that can be shared with non-technical stakeholders. It also serves as a useful quality check: if the respondent cannot describe the incident clearly, the analysis may need further development. The placeholder example sets helpful expectations for tone and length.
What is the clearest statement of the problem that this analysis needs to explain?
Recommendation: Requiring a problem statement anchors the root-cause analysis and ensures the investigation stays focused. It prevents the analysis from drifting into tangential topics and provides a clear reference point for evaluating whether the final explanation is adequate. This is a strong foundational field for the analysis section.
Which single factor would you consider the primary root cause at this stage?
Recommendation: Requiring a single primary-cause selection encourages prioritization and prevents the analysis from remaining diffuse. The “too early to determine” option appropriately accommodates situations where evidence is still being gathered. This field supports decision-making about where to focus improvement efforts.
What evidence supports your current explanation?
Recommendation: Requiring evidence documentation grounds the analysis in verifiable data rather than speculation. It supports confidence in the findings and provides a basis for future review. This is one of the most important mandatory fields in the form, as it directly affects the reliability of the root-cause conclusions.
What is the most important single insight from this analysis that leadership should understand?
Recommendation: Requiring a single distilled insight ensures that the form produces a clear, actionable message for decision-makers. It prevents the analysis from being buried in detail and provides a concise summary that can be used in briefings or reports. The form creator may wish to provide a word-count guideline to encourage brevity.
If you could change one process or communication practice before the next incident, what would it be and why?
Recommendation: Requiring this single prioritized recommendation forces respondents to identify the highest-impact improvement, which supports focused action planning. It avoids the common problem of long wish lists without clear priorities. This field is well-placed near the end of the process-evaluation section, after respondents have reflected on gaps.
Which categories of preventive action are most needed? Select all that apply.
Recommendation: Requiring action-category selection ensures that the preventive action planning section is grounded in identified needs rather than generic improvements. It supports alignment between the root-cause findings and the proposed actions. The twelve-option list provides sufficient breadth without being overwhelming.
What is the single most important thing that must not be forgotten once the urgency of this incident fades?
Recommendation: Requiring this field captures the respondent’s deepest concern about institutional memory loss, which is a common risk after incidents. It provides a powerful closing statement that can be referenced in follow-up reviews. This is an emotionally resonant question that also serves a practical purpose.
Name of the person submitting this form
Recommendation: Requiring the submitter’s name finalizes the submission record and supports accountability. It may differ from the “person completing this form” field if the form is submitted on behalf of someone else. The form creator should clarify the intended distinction between these two fields to avoid confusion.
Date of submission
Recommendation: Requiring a submission date anchors the record in time and supports tracking of review timelines and action deadlines. It is a standard administrative field that supports record-keeping integrity.
The form currently designates approximately 18 fields as mandatory across its five sections. This is a proportionate distribution that covers identity, incident classification, key metrics, analytical rigor, and closing attestation without requiring every field to be completed. The mandatory fields are well-chosen: they ensure that every submission contains a clear identity, a categorized incident, core timing data, a plain-language summary, evidence-backed analysis, a prioritized recommendation, and a formal closing record.
Several observations and suggestions for balancing data depth with completion rates:
Overall, the mandatory field strategy is well-calibrated for a comprehensive post-incident intake tool. The form balances the need for structured, complete data with the practical reality that respondents may be under stress and time pressure. Minor refinements — particularly around the duplicate name fields and the optional status of key timing metrics — could further improve data consistency without significantly increasing respondent burden.
To configure an element, select it on the form.