Skip to content
ArumSoft Learning
KO
    Word templateOperations and safety

    Workplace Incident and Near-Miss Investigation Report Template for Word

    A near miss is a free lesson: the same causes that almost hurt someone today will hurt someone later if nothing changes. This report is built to turn an incident into fixes. It is a finished four-page example of a falling-pallet near miss in a fictional plant, moving from facts (what happened, who saw it, what evidence exists) to causes (five whys and contributing factors) to dated, owned actions that close the report.

    Pages:
    4
    Works with:
    Word for Microsoft 365, Word 2016 or later, Word for Mac (Word for the web can fill in fields)
    Updated:

    Workplace Incident Investigation Report.docx

    Word document (.docx) · 17 KB · 4 pages

    Download template

    Free to download. No sign-up needed. No macros.

    What you can do with it

    • Incident block with type, severity and OSHA recordable dropdowns and date pickers
    • What happened, immediate actions, people involved, and a block per witness statement
    • Evidence checklist, five whys numbered steps, root cause callout and contributing factor checkboxes
    • Corrective and preventive actions with type and status dropdowns, due dates and four-way sign-off
    First two pages of the workplace incident report Word template: incident details table with type and severity, what happened, immediate actions, people involved, witness statement blocks, evidence checklist and five whys
    Pages 1 and 2 of the four-page sample, a near miss in a fictional plant.

    What's inside

    The document has 4 pages. Each part below is a heading in the file, so you can jump to it from the Navigation Pane (View > Navigation Pane).

    PartWhat it coversWhat you write
    Incident blockWhat, when, where, how seriousNumber, type, date, time, location, severity, reporter, investigator, recordable
    1–2. What happened and whoThe facts in orderNarrative, immediate actions, people involved
    3–4. Witnesses and evidenceFirst-hand accounts and what was keptOne statement block per witness; evidence checklist
    5. Root cause analysisWhy it happenedFive whys, root cause, contributing factor categories
    6–7. Actions and sign-offWhat will change and who confirms itAction, type, owner, due date, status; four signatures

    Before you start

    • Make the area safe and preserve the scene: photos before anything is moved.
    • Take witness statements separately and as soon as possible, in the witness’s own words.
    • Know your reporting duties: serious injuries may have to be reported to a regulator within hours.

    Step-by-step guide

    1. Fill in the incident block

      Type the incident number, location, reporter and investigator, pick the type, severity and recordable status, and pick the dates.

    2. Describe what happened

      Write the events in time order with measurements, without blame or guesses. List immediate actions taken to make the area safe.

    3. Record each witness

      Use one statement block per witness (copy the table for more). Write the statement in their words and have them sign it.

    4. Tick the evidence

      Tick each type of evidence collected and say where it is stored.

    5. Find the root cause

      Ask why five times (more or fewer if needed) until you reach a system cause. Put it in the Root cause callout and tick the contributing factor categories.

    6. Assign actions and close

      Each action gets a type, owner, due date and status. EHS closes the report once every action is done and verified.

    Field and control map

    Every content control and field in the document, in the order they appear. Gray-boxed fields in Word are the content controls.

    NameTypeWhereValue in the sample
    Incident numberTextHeaderINC-2026-0147
    Incident numberTextBodyINC-2026-0147
    Incident typeDropdownBodyNear miss (Injury / Near miss / Property damage / Environmental release / Security / Vehicle)
    Incident dateDate pickerBodyOctober 28, 2026
    Incident timeTextBody2:40 p.m.
    LocationTextBodyBuilding 2, aisle 14, rack C
    SeverityDropdownBodyHigh potential (Low / Medium / High potential / Serious / Critical)
    Reported byTextBodyTyler Brooks, forklift operator
    Reported dateDate pickerBodyOctober 28, 2026
    InvestigatorTextBodyRosa Alvarez, EHS Coordinator
    RecordableDropdownBodyNo (Yes / No / To be determined)
    Witness nameTextBody2 fields: Ana Silva, Marcus Hill
    Statement dateDate pickerBody2 fields: October 29, 2026
    Statement taken byTextBody2 fields: R. Alvarez
    Evidence photosCheckboxBodychecked
    Evidence videoCheckboxBodychecked
    Evidence wmsCheckboxBodychecked
    Evidence trainingCheckboxBodyunchecked
    Evidence equipmentCheckboxBodyunchecked
    Cause peopleCheckboxBodyunchecked
    Cause procedureCheckboxBodychecked
    Cause equipmentCheckboxBodyunchecked
    Cause environmentCheckboxBodychecked
    Cause materialsCheckboxBodyunchecked
    Cause managementCheckboxBodychecked
    Action typeDropdownBody4 fields: Corrective, Preventive (Corrective / Preventive)
    Action dueDate pickerBody4 fields: November 20, 2026, November 6, 2026, December 15, 2026 …
    Action statusDropdownBody4 fields: In progress, Done, Open (Open / In progress / Done / Verified)
    Investigator signerTextBodyRosa Alvarez
    Signed dateDate pickerBody3 fields: Click or tap to enter a date.
    Supervisor signerTextBodyMarcus Hill
    Plant managerTextBodyType a name
    EHS managerTextBodyType a name
    Closed dateDate pickerBodyClick or tap to enter a date.
    CompanyTextFooterRidgeline Manufacturing
    { PAGE }FieldFooter1
    { NUMPAGES }FieldFooter4
    { SEQ Table \* ARABIC }FieldBody1

    Every field, control and style, explained

    The code in each card is read straight from the .docx file (the XML Word stores, or the field code you see with Alt+F9), so it is exactly what the template contains.

    Numbered headingsHeading 1 and Heading 2 styles
    <w:lvl w:ilvl="0">
      <w:start w:val="1"/>
      <w:numFmt w:val="decimal"/>
      <w:pStyle w:val="Heading1"/>
      <w:lvlText w:val="%1."/>
      <w:lvlJc w:val="left"/>
      <w:pPr>
        <w:ind w:left="440" w:hanging="440"/>
      </w:pPr>
    </w:lvl>
    <w:lvl w:ilvl="1">
      <w:start w:val="1"/>
      <w:numFmt w:val="decimal"/>
      <w:pStyle w:val="Heading2"/>
      <w:lvlText w:val="%1.%2"/>
      <w:lvlJc w:val="left"/>
      <w:pPr>
        <w:ind w:left="660" w:hanging="660"/>
      </w:pPr>
    </w:lvl>

    The section numbers (1., 2., 6.1 …) are not typed. A multilevel list is linked to the Heading 1 and Heading 2 styles, so any paragraph you set to Heading 1 gets the next number and the table of contents picks it up.

    Piece by piece

    <w:pStyle w:val="Heading1"/>
    Links list level 1 to the Heading 1 style (level 2 to Heading 2).
    <w:lvlText w:val="%1."/>
    Level 1 shows its counter and a period: 1., 2., 3.
    <w:lvlText w:val="%1.%2"/>
    Level 2 shows the parent number, a period and its own counter: 6.1, 6.2.
    <w:ind w:left="440" w:hanging="440"/>
    Hanging indent so wrapped heading text lines up after the number.

    In the sample: 1. What happened, 1.1 Immediate actions taken, 2. People involved … (10 headings)

    How it is used: To add a section, type the heading, then pick Heading 1 (Ctrl+Alt+1) or Heading 2 (Ctrl+Alt+2) on the Home tab. Numbers after it update by themselves.

    How to change it: Home > Multilevel List > Define New Multilevel List to change the format (for example "Section 1"). Keep "Link level to style" set to Heading 1 and Heading 2.

    Learn this: How to Plan and Structure Long Documents in Word: Outline View and Multilevel Numbering →
    Page X of YFooter
    Page { PAGE } of { NUMPAGES }

    The footer counts pages with two fields: PAGE is the current page and NUMPAGES is the total. Both recalculate when the document is printed, saved as PDF or scrolled in Print Layout.

    Piece by piece

    PAGE
    The number of the page the field sits on.
    NUMPAGES
    The total number of pages in the document.

    In the sample: Page 1 of 4 on the first page

    How it is used: Nothing to do: add or delete pages and the numbers follow.

    How to change it: Double-click the footer to edit the text around the fields. Insert > Page Number > Format Page Numbers sets the starting number.

    Learn this: How to Set Up Pages in Word: Margins, Breaks, Headers, Footers, and Page Numbers →
    Numbered table captionsCaptions above tables
    { SEQ Table \* ARABIC }

    Each table caption uses a SEQ field that counts tables in order. Insert a new captioned table in the middle and every later caption renumbers.

    Piece by piece

    SEQ Table
    A counter named "Table". Every SEQ Table field adds 1.
    \* ARABIC
    Show the counter as 1, 2, 3.

    In the sample: 1 caption(s): Table 1

    How it is used: Captions are what a "see Table 2" cross-reference points to (References > Cross-reference).

    How to change it: References > Insert Caption adds a new one. If numbers look stale, press Ctrl+A then F9 to update all fields.

    Learn this: How to Add a Table of Contents, Captions, and Cross-References in Word →
    Fill-in fields (plain text content controls)Gray-boxed fields
    <w:sdtPr>
      <w:alias w:val="Incident number"/>
      <w:tag w:val="incident_number"/>
      <w:text/>
    </w:sdtPr>

    Names, numbers and other details people change every time are plain text content controls. Click one and type: the text replaces the sample, keeps the formatting, and the field still shows its name when selected.

    Piece by piece

    <w:alias w:val="…"/>
    The title shown on the control’s tab when you click it.
    <w:tag w:val="…"/>
    A machine-readable name, useful for mail merge or code.
    <w:text/>
    Plain text: one line, one format, so pasted text cannot break the layout.
    <w:showingPlcHdr/>
    Present when the field shows gray placeholder text instead of a value.

    In the sample: Incident number = INC-2026-0147

    How it is used: 15 in this template: Incident number, Incident time, Location, Reported by, Investigator, Witness name, Statement taken by, Investigator signer, Supervisor signer, Plant manager, EHS manager, Company. Use Developer > Design Mode to see every control at once, or the Selection Pane to jump between them.

    How to change it: Developer > Properties changes the title, tag and placeholder. To show the Developer tab: File > Options > Customize Ribbon > Developer.

    Learn this: How to Create Fillable Forms with Content Controls in Word →
    Date pickersDate fields
    <w:sdtPr>
      <w:alias w:val="Incident date"/>
      <w:tag w:val="incident_date"/>
      <w:date w:fullDate="2026-10-28T00:00:00Z">
        <w:dateFormat w:val="MMMM d, yyyy"/>
        <w:lid w:val="en-US"/>
        <w:storeMappedDataAs w:val="dateTime"/>
        <w:calendar w:val="gregorian"/>
      </w:date>
    </w:sdtPr>

    Dates are date picker content controls: click the arrow to pick from a calendar, or type a date in any format and Word shows it as "November 2, 2026".

    Piece by piece

    w:fullDate
    The stored date, independent of how it is shown.
    <w:dateFormat w:val="MMMM d, yyyy"/>
    Display format: full month name, day, four-digit year.
    <w:lid w:val="en-US"/>
    Language used for month names.
    <w:storeMappedDataAs w:val="dateTime"/>
    Stores a real date value if the control is mapped to data.

    In the sample: Incident date = October 28, 2026

    How it is used: 12 in this template: Incident date, Reported date, Statement date, Action due, Signed date, Closed date. Pick the date from the calendar so every date in the document has the same format.

    How to change it: Developer > Properties > Display the date like this, for example d MMMM yyyy or yyyy-MM-dd.

    Learn this: How to Create Fillable Forms with Content Controls in Word →
    Dropdown listsStatus and choice fields
    <w:sdtPr>
      <w:alias w:val="Incident type"/>
      <w:tag w:val="incident_type"/>
      <w:dropDownList>
        <w:listItem w:displayText="Injury" w:value="Injury"/>
        <w:listItem w:displayText="Near miss" w:value="Near miss"/>
        <w:listItem w:displayText="Property damage" w:value="Property damage"/>
        <w:listItem w:displayText="Environmental release" w:value="Environmental release"/>
        <w:listItem w:displayText="Security" w:value="Security"/>
        <w:listItem w:displayText="Vehicle" w:value="Vehicle"/>
      </w:dropDownList>
    </w:sdtPr>

    Fields with a fixed set of answers are dropdown list content controls, so everyone uses the same words (useful when you search or count documents later).

    Piece by piece

    <w:dropDownList>
    A list the reader must pick from (no free typing).
    <w:listItem w:displayText="…" w:value="…"/>
    One choice: the text shown and the value stored.

    In the sample: Incident type = Near miss (Injury / Near miss / Property damage / Environmental release / Security / Vehicle)

    How it is used: 11 in this template: Incident type, Severity, Recordable, Action type, Action status. Click the field and choose from the list.

    How to change it: Developer > Properties > Add, Modify or Remove choices. Use a Combo Box instead if people need to type their own answer.

    Learn this: How to Create Fillable Forms with Content Controls in Word →
    CheckboxesChecklists
    <w:sdtPr>
      <w:alias w:val="Evidence photos"/>
      <w:tag w:val="evidence_photos"/>
      <w14:checkbox>
        <w14:checked w14:val="1"/>
        <w14:checkedState w14:val="2612" w14:font="MS Gothic"/>
        <w14:uncheckedState w14:val="2610" w14:font="MS Gothic"/>
      </w14:checkbox>
    </w:sdtPr>

    Checklist boxes are checkbox content controls: click to tick or untick. They print as ☒ and ☐.

    Piece by piece

    <w14:checked w14:val="…"/>
    1 when ticked, 0 when not.
    <w14:checkedState w14:val="2612"/>
    Symbol for ticked: U+2612 ☒.
    <w14:uncheckedState w14:val="2610"/>
    Symbol for unticked: U+2610 ☐.

    In the sample: 6 of 11 ticked in the sample

    How it is used: 11 in this template: Evidence photos, Evidence video, Evidence wms, Evidence training, Evidence equipment, Cause people, Cause procedure, Cause equipment, Cause environment, Cause materials, Cause management. Click the box. Checkboxes need Word 2010 or later; very old versions show a static symbol.

    How to change it: Developer > Properties > Checked symbol > Change, for example to ✓ (Wingdings 2).

    Learn this: How to Create Fillable Forms with Content Controls in Word →
    Callout styleNotes, tips and warnings
    <w:style w:type="paragraph" w:styleId="Callout">
      <w:name w:val="Callout"/>
      <w:basedOn w:val="Normal"/>
      <w:pPr>
        <w:pBdr>
          <w:left w:val="single" w:color="F2A93B" w:sz="24" w:space="8"/>
        </w:pBdr>
        <w:shd w:fill="EEF2F8" w:color="auto" w:val="clear"/>
        <w:spacing w:after="160" w:before="120"/>
        <w:ind w:left="180" w:right="180"/>
      </w:pPr>
      <w:rPr>
        <w:sz w:val="21"/>
      </w:rPr>
    </w:style>

    Notes and warnings use a paragraph style named Callout: tinted background, amber bar on the left, indented on both sides. Because it is a style, every callout matches and you can restyle them all at once.

    Piece by piece

    <w:shd w:fill="EEF2F8"/>
    Light blue-gray background.
    <w:left w:val="single" w:sz="24" w:color="F2A93B"/>
    Amber bar, 3 pt wide, on the left edge.
    <w:ind w:left="180" w:right="180"/>
    Indented 1/8 inch on each side.

    In the sample: Used for the notes, tips and warnings in the body.

    How it is used: Put the cursor in a paragraph and pick Callout in the Styles gallery.

    How to change it: Right-click Callout in the Styles gallery > Modify > Format > Border or Shading. All callouts change together.

    Learn this: How to Use Styles and the Navigation Pane in Word →
    Repeating table headersEvery table with a dark header row
    <w:trPr>
      <w:cantSplit/>
      <w:tblHeader/>
    </w:trPr>

    Header rows are marked to repeat at the top of each page when a table breaks, and rows are set not to split across pages, so a long table stays readable when printed.

    Piece by piece

    <w:tblHeader/>
    Repeat this row at the top of each page.
    <w:cantSplit/>
    Keep each row on one page.

    In the sample: 2 of 8 tables repeat their header row

    How it is used: Add rows with Tab in the last cell; the header keeps repeating.

    How to change it: Click in the header row > Table Layout > Repeat Header Rows. Short tables are also set to keep with the next paragraph so they do not split.

    Learn this: How to Build and Format Tables That Read Well in Word →
    Guidance notesGray italic notes
    <w:style w:type="paragraph" w:styleId="Guidance">
      <w:name w:val="Guidance"/>
      <w:basedOn w:val="Normal"/>
      <w:pPr>
        <w:spacing w:after="100"/>
      </w:pPr>
      <w:rPr>
        <w:i/>
        <w:iCs/>
        <w:color w:val="6B7280"/>
        <w:sz w:val="19"/>
      </w:rPr>
    </w:style>

    Instructions for whoever fills in the template use a Guidance style (gray italics). Delete them before you send the document; with a style, Find and Replace can remove them all at once.

    Piece by piece

    <w:i/>
    Italic.
    <w:color w:val="6B7280"/>
    Gray text.

    In the sample: One note under the title block.

    How it is used: Home > Replace > More > Format > Style > Guidance finds every note.

    How to change it: Right-click Guidance in the Styles gallery > Modify.

    Learn this: How to Use Styles and the Navigation Pane in Word →

    Tips and limits

    • Near misses deserve the same investigation as injuries; they are cheaper to learn from.
    • A root cause is a system or process gap. If your last "why" is a person’s name, keep asking.
    • Corrective actions fix this case; preventive actions stop it elsewhere. Aim for at least one of each.
    • The OSHA recordable dropdown applies to US employers; replace it with your country’s reporting category if needed.
    • Keep injury details and medical information in a separate confidential file.

    Learn the skills behind this template

    Was this guide helpful? Spot a mistake? Send feedback · admin@arumsoft.com