Findings and credibility templates
Inconclusive Investigation Outcome: Honesty Test, Next Steps, Monitoring
Last updated 2026-07-30
An inconclusive finding closes an allegation without deciding it, which is why it is the outcome investigators write worst. Written badly it reads to the complainant as a polite way of calling them a liar and to the respondent as an acquittal, and it is neither.
"Not substantiated" means the evidence was capable of being weighed and did not support the allegation. "Inconclusive" means the evidence does not permit a determination either way. Both fall short of the preponderance of the evidence and neither is a finding that the conduct did not occur; the vocabulary is set out at findings-of-fact and the reasoning that produces the deadlock at credibility-assessment. This page starts after that point, at the moment the word is about to be written.
Inconclusive is the outcome most easily abused, because it is equally available to an investigator who genuinely cannot resolve a conflict and to one who would rather not find against a senior respondent. Specificity separates them: name the single disputed fact, name the evidence that would have resolved it, and record what you did to obtain it and when. An inconclusive finding you cannot describe that precisely is an unfinished investigation wearing a finding's label.
What follows the finding is where most organizations improvise. An allegation nobody could substantiate still leaves an employer with knowledge it did not have before, interim measures running on no basis, and a workforce watching what happens to the people who complained.
Jurisdiction
Written primarily against US federal standards — EEOC guidance, NLRB decisions and Title VII case law — and against general investigative practice. State law, sector rules (public employers, education, regulated industries) and collective agreements impose additional requirements this page does not cover. Where a page borrows a concept from another jurisdiction it says so explicitly. Outside the US, treat the structure as transferable and the legal references as not.
Inconclusive Investigation Outcome: Honesty Test, Next Steps, Monitoring template
Free Word download, no email required. Or open it in Professional Drafter — it lands in your template library, ready to draft against.
When to use this document
- An allegation is in genuine evidential deadlock and you have to decide, before you sign, whether the deadlock is real or is work you stopped doing.
- The report is issued and the organization is asking what it may do about a respondent nobody could find against.
- Interim measures imposed during the investigation need a decision now that the matter has closed and cannot simply keep running.
- A party or witness has suffered an adverse change since the complaint and the organization needs a documented gate around further ones.
- A second complaint has arrived against a respondent whose earlier matter closed inconclusive.
Worked example
Fictional scenario, continuing the dispatch-team matter. Matter RW-2026-038: complainant Nadia Okafor (Dispatch Coordinator), respondent Sean Whelan (Team Lead), investigator R. Hall, HR Business Partner. Complaint dated 29 May 2026, received 30 May; report 14 July 2026. Allegations 1 and 2 substantiated; Allegation 3 (the corridor incident of approximately 17 April) inconclusive. The credibility reasoning behind that deadlock is written out at credibility-assessment and the two outcome letters at investigation-outcome-letter; neither is repeated here. This is the part nobody publishes: the checks R. Hall ran before signing, and the closure record of 16 July 2026 that tells the company what it may do next.
The honesty test: inconclusive, or unfinished?
Run 13 July 2026, before the report was signed.
The single disputed fact, in one sentence: whether Mr Whelan positioned himself so as to prevent Ms Okafor passing in the corridor outside the dispatch office in mid-April. It fits in a sentence, and everything else about that afternoon is either common ground or immaterial.
The evidence that would have resolved it: footage from the corridor camera; door access logs for the corridor between dispatch and the loading bay; a third person present.
Did I seek it, and when. This is the check I record in full, because it is the one that would be measured against me. Short-retention evidence was flagged in the investigation plan of 2 June. The request to Facilities went on 16 June; the answer came on 18 June — the corridor camera has been out of service since January 2026 and those doors are not access-controlled. Fourteen days passed between identifying the item and requesting it. It made no difference here, because there was never any footage to lose. It would have made every difference if the camera had been working: retention on that system was believed to be 30 days, an incident of 17 April was already marginal on 2 June, and by 16 June the window would have closed. The interval is recorded rather than smoothed over, because the reader's first question about a missing camera is which kind of gap it was.
Factors I was equipped to weigh and did not apply: none identified. The factors are set out and applied in the credibility assessment, and where they ran out I said so rather than stopping early.
The seniority check. Mr Whelan is Ms Okafor's team lead, which is exactly the configuration in which inconclusive findings are known to cluster, so I checked rather than asserted. Two of the three allegations against him are substantiated, which is some evidence that I was not deferring. Against my own caseload the answer was less comfortable: of eleven matters I have concluded in the last twelve months, two produced an inconclusive allegation, and in both the respondent held supervisory authority over the complainant. Two out of eleven is not a pattern I can draw a conclusion from, and I do not treat it as one. I have recorded it, disclosed it to the Director of HR with the report, and asked that the next matter of this kind go to an investigator outside the dispatch reporting chain.
Evidence sought, and the date you asked for it
Corridor CCTV — requested from Facilities 16 June; answered 18 June: camera out of service since January 2026, no footage of any date exists. Pre-existing coverage gap, not a closed retention window. Effect: removes the only source capable of resolving the disputed fact directly.
Door access logs, dispatch-to-loading-bay corridor — requested from Facilities 18 June; answered 19 June: those doors are not access-controlled and no logs are generated. Pre-existing gap. Effect: no independent means of placing either party in the corridor.
Third-party accounts — shift rota for 17 April obtained 10 June; four staff on the floor. Ms Anand interviewed 12 June: she saw Ms Okafor visibly upset near the dispatch office on a Friday afternoon in mid-April, saw nothing happen, and witnessed no physical contact at any time. Witness B interviewed 12 June: nothing relevant. The fourth was on the loading bay for the whole shift, was approached, and had no relevant account. Effect: the distress is corroborated; the incident is not.
What the report says about all three, in terms: two of these gaps existed before the complaint was made and would have existed whenever it was made. Nothing was lost to delay. That sentence is in the report because if it is absent the reader is entitled to assume the opposite.
Sorting what the organization does next
Closure record, 16 July 2026. Prepared by R. Hall for the Director of HR.
Prospective and universal — no finding required, each justified on its own facts. (a) Corridor camera repaired or replaced by 28 August; owner J. Reyes, Facilities. Raised as works order FM-4471 and worded as a standing coverage gap on a route between two operational areas, because that is what it is; RW-2026-038 is not referenced in the order. (b) Respectful-workplace concerns on the dispatch floor currently escalate through the Team Lead, which is the reason a February-to-May course of conduct did not reach HR until 29 May. Route changed to a named HR contact by 15 September; owner Director of HR. (c) Policy refresher to all dispatch staff in October on the standard annual cycle — not rescheduled, not re-scoped, and not delivered in any configuration that identifies Mr Whelan.
Terms-altering — must name its basis. The interim measure of 3 June (shift allocation for the dispatch team transferred to the Shift Supervisor with effect from 4 June) is made permanent from 16 July. Basis: Allegations 1 and 2, substantiated. The file says so in those words. It does not rest on Allegation 3 and must not be described as if it did. Note what is not happening: no change to Mr Whelan's pay, grade, title, duties or reporting line beyond the shift-allocation function, and no change at all to Ms Okafor's shift pattern, duties or reporting line — the burden of separation stays where the 3 June memo put it, and moving the complainant at closure is the same error as moving her at the start.
The legal note the Director asked for. The company is an at-will private employer, Mr Whelan has no collective bargaining agreement and no individual contract term touching this, and Loudermill does not apply outside public employment. As a matter of entitlement the company could change his terms without any of this. The reason to write the basis down anyway is that he is named in two matters within six weeks, and any change to his terms in the next year will be read against those dates by someone whose job is to argue that the stated reason was not the real one.
Do not. No reference to Allegation 3 at the disciplinary meeting on Allegations 1 and 2. Not recorded as a concern in his appraisal. Not counted in any promotion or redeployment decision. Each of those converts an outcome that decided nothing into a penalty, and each is discoverable.
The retaliation review gate
This gate is not precautionary. On 3 July Ms Anand — Witness A in this matter — raised a retaliation complaint about the July rota published on 30 June, and that complaint has been substantiated in a separate matter. The company already has a finding that someone in this matter suffered a detriment for participating in it. The gate is designed on the assumption that it can happen again, because it has.
Owner: Director of HR. Covered: Ms Okafor, Ms Anand, Witness B, and Mr Whelan. He is covered because he participated, and because a change to his terms with no recorded reason is the same evidentiary problem in reverse.
Check-ins with Ms Okafor and, separately, with Ms Anand on 14 August, 14 September and 14 October 2026, each recorded in the file whether or not anything is raised.
Gate: until 14 July 2027, any adverse change affecting a covered person — shift pattern, overtime, mentoring-rota supplement, appraisal rating, redeployment, or disciplinary action on an unrelated matter — is routed to HR and the reason recorded in writing before it takes effect, not after it is challenged. Under Burlington Northern the test is whether the change might dissuade a reasonable worker from complaining or supporting a charge, which is why appraisal ratings and rota supplements are on the list and not only pay.
The control failure this gate exists to close. The 3 June measure moved shift-allocation authority to the Shift Supervisor. It did not stop Mr Whelan asking the Shift Supervisor for changes, and the email of 26 June is what that looks like in practice. From 16 July the Shift Supervisor records the origin of any pattern change on the dispatch team and logs any request received from Mr Whelan. Moving an authority without addressing the ability to influence it is not a control.
And the outcome on Allegation 3 changes none of this. Protection attaches to complaining and to participating, not to being proved right, and the company can be entirely correct about Allegation 3 and still lose on what happens in September.
Retention, indexing, and a later complaint against the same respondent
The RW-2026-038 file is retained in full, indexed against Ms Okafor, against Mr Whelan and against the retaliation matter, and restricted to HR and counsel. Under 29 CFR 1602.14 personnel and employment records are preserved for at least one year, and where a charge is filed the relevant records are kept until final disposition — a preservation floor, not a filing rule, and it says nothing about what may sit in anyone's personnel file. The inconclusive finding is not on Mr Whelan's personnel file. What is on it is the outcome of the disciplinary process on Allegations 1 and 2.
If a second, similar complaint names him. The inconclusive finding on Allegation 3 is not evidence that the new allegation occurred; used that way it is propensity reasoning and it makes the second finding indefensible. It bears on two narrower questions. First, what the company knew and when — the notice date is 30 May 2026, the date the complaint was received, and it did not move when the report failed to resolve Allegation 3. Second, whether a general denial of the "I have never done anything like that" type remains sustainable. If it is to be considered at all, it is put to him in the second interview and he answers it. Whatever the second matter concludes, Allegation 3 in this matter stays inconclusive; it is not reopened and it is not retrospectively upgraded.
Disclosure of this matter to a future complainant is not the investigator's call and is not automatic in either direction. The default is no. Discovery, state personnel-record access statutes and the company's own position on notice can all displace it, so the question goes to counsel with the file, not to whoever picks up the second complaint.
Section-by-section guide
What each section is for, what a good one contains, and where they typically go wrong.
1.Matter details and the allegation at issue
This record sits alongside the report, not instead of it. Identify the allegation by the number it carries in the report and the allegation matrix. An allegation recorded inconclusive and an allegation nobody reached look identical to a reviewer scanning for orphans, and only one of them is defensible.
2.The honesty test: inconclusive, or unfinished?
Run these before the word goes in. If you cannot name the specific evidence that would have resolved the conflict, you have not finished investigating — you have stopped, and the file will read that way to anyone who checks the request dates against the interview dates. The uncomfortable check is the last one. Inconclusive findings cluster around senior respondents, no report says so, and the pattern is visible in an investigator's own caseload long before anyone else raises it. Run the check against your own file history, record that you ran it, and disclose the result to whoever commissioned you.
3.Disaggregate before you record inconclusive
Allegations recorded inconclusive are often allegations nobody split. Most have an undisputed core and a disputed edge: that there was an exchange may be common ground, while what was done during it is not. Find what can be found, record inconclusive on the residue only, and then ask whether the policy provision actually turns on the unresolved part. Frequently it does not — which converts an inconclusive allegation into a substantiated one with an unresolved detail. Where it does turn on the disputed part, say so expressly, because a reader who has seen part-substantiation elsewhere in the report will otherwise assume you failed to try it here.
4.Evidence sought, and the date you asked for it
Record what you asked for, who you asked, the date, the answer, and the date of the answer. Then set the request date against the date the complaint was received, because that interval is the first thing a reviewer measures when the missing evidence is CCTV, door logs, call recordings or messages on a company handset — all of them sitting inside retention windows measured in days or weeks. Say in terms which kind of gap you are dealing with: a coverage failure that predates the complaint is a fact about the building, while a window that closed while the file sat is a fact about the investigation. A deadlock created by your own delay is not a deadlock.
5.The wording, and the words the letters reuse
Write the determination and the express negatives once, in the report, and have the outcome letters reuse those words rather than paraphrase them. Two documents describing the same outcome in different words is the gap a party finds when the parties compare letters, which they do. For the complainant the negatives are that this is not a finding that the incident did not occur and not a finding that they were untruthful; for the respondent, that no adverse finding is recorded and that the report does not describe the outcome as an exoneration. Drafting the letters themselves — including how much each party is told about consequences — is at investigation-outcome-letter and is not repeated here.
6.Sorting what the organization does next
Sort every proposed step into prospective-and-universal or terms-altering before anyone acts. Prospective steps — repairing camera coverage, changing an escalation route that runs complaints through the person complained about, a refresher delivered to the whole team on the ordinary cycle — are justified on their own facts and need no finding. Terms-altering steps are a different problem, and the reason is evidentiary, not a right the respondent holds. In at-will private employment there is no general entitlement to a finding, to process, or to consent before pay, duties or reporting lines change. What supplies an entitlement is a contract, a just-cause clause in a collective bargaining agreement enforced through arbitration under the NLRA and LMRA, or, for public employees, the pre-deprivation hearing required by Cleveland Board of Education v. Loudermill. Absent one of those, the "no discipline without a finding" rule — the default position in UK ACAS practice and Canadian just-cause arbitration, and the frame most investigation training silently borrows — is not the US private-sector position, and stating it as law will get the page corrected by counsel. The operative risk is that an adverse change following a protected complaint, with no reason recorded before it took effect, is the raw material of a retaliation or pretext case; under Burlington Northern & Santa Fe Railway v. White the threshold is whether the change might have dissuaded a reasonable worker from complaining or supporting a charge, not whether it cost money. Record the rationale at the time. A rationale first articulated in a deposition reads as pretext.
7.What the team is told, and Section 7
Two constraints govern the announcement. Characterizing an unresolved allegation to colleagues is the shortest route to a defamation problem, so prospective measures are announced on their operational rationale and nothing else. The second constraint is one investigators routinely miss: a general instruction to employees not to discuss the matter, issued now that the investigation is over, is exposed under the NLRB's Stericycle standard. The investigative-integrity justification that supported a narrow, duration-limited confidentiality request during the process expires with the process, and a rule employees could reasonably read as chilling discussion of their working conditions is presumptively unlawful. Say what is changing and when. Do not tell the workforce what it may say about it.
8.Closing out the interim measures
Measures imposed during the investigation expire with the investigation, and they do not lapse quietly. Make an explicit decision on each one on the day the report issues: continued, modified or ended, with the basis and the date. A measure that continues because nobody revisited it becomes a sanction nobody imposed and nobody can point to a reason for. Tie each continuation to a finding that was reached, to the affected person's agreement, or to an operational reason that would exist anyway — and if the measure is being made permanent on the strength of substantiated allegations, the file has to say which ones, because the respondent's first argument will be that it rests on the allegation that failed. Where separation is being extended, the burden stays where the interim-measures memo put it; moving the complainant at closure is the same mistake as moving them at the start.
9.The retaliation review gate
This is the highest-risk window in the matter and the risk is indifferent to the outcome. A retaliation claim stands on its own facts and does not require the underlying allegation to have been substantiated. Under the opposition clause the employee's belief that the conduct was unlawful must be both sincerely held and objectively reasonable — Clark County School District v. Breeden polices the objective half — while participation in a charge process is protected without any reasonable-belief inquiry at all. Name an owner, fix the check-in dates before anyone leaves the room, and route adverse actions affecting either party or any witness through a written reason recorded before the action takes effect. Cover the respondent too: he participated, and a change to his terms needs the same recorded reason as anyone else's. Check where the authority for shift patterns, overtime and rota supplements actually sits, because a measure that moved an authority but left the ability to ask for a change is not a control.
10.What the organization knows now, whatever the finding
An inconclusive outcome does not return the employer to the position it was in before the complaint. Where harassment by a supervisor is alleged, the employer's affirmative defense under Faragher v. City of Boca Raton and Burlington Industries v. Ellerth turns on reasonable care to prevent and promptly correct — and reasonableness is judged on what the employer did with what it knew, from the date it knew it. That date is the date the complaint was received, not the date something was substantiated. The EEOC's 1999 vicarious-liability guidance, which remains operative, is the source to work from on what reasonable care looks like in practice. Record the notice date and what was done after closure; on a later complaint, that record is the only thing standing between the organization and the argument that it treated an unresolved allegation as a resolved one.
11.Retention, indexing, and a later complaint against the same respondent
Index the file by respondent as well as by complainant, or the organization will not know the first matter existed when the second arrives. On a second, similar complaint the rules are narrow. The earlier inconclusive finding is not evidence that the new allegation occurred — that is propensity reasoning and it makes the second finding indefensible. It is relevant to two narrower things: the organization's notice, which is a question about the organization rather than about the respondent, and whether a sweeping general denial of the "I have never done anything like that" type remains sustainable. If it is to be used at all it is put to the respondent and he answers it; reviving it silently is fatal. Whatever the second matter concludes, the first stays inconclusive — findings are not retrospectively upgraded. As a default the earlier matter is not disclosed to a new complainant, but state it as a default and not a rule: discovery, state personnel-record access statutes and the organization's own notice position all cut against a flat never, so route the question through counsel rather than answering it at the desk.
12.Sign-off and distribution
Record who this document goes to and who it does not. The organization's action note and the parties' letters are different documents for different audiences, and the commonest leak is a next-steps note written for the decision-maker being forwarded to a party, who reads the prospective measures as an admission.
Common mistakes
The failure modes that show up most often when this document is reviewed later.
Requesting perishable evidence only once the deadlock is obvious
CCTV overwrites in weeks, call recordings in months, and a returned company handset can be wiped in days. A report showing a complaint received on the 30th and footage requested seven weeks later lets the reader see the deadlock was manufactured by the timeline. Request perishable items in the first 48 hours, before you know whether you will need them, and put the request date in the report.
Recording inconclusive when one account is contradicted by a document you already have
A deadlock means the factors do not separate the accounts. Where a rota, a message or an access log does separate them, the honest outcome is substantiated or not substantiated, and choosing the neutral-sounding third term to avoid saying so is visible in how thin the reasoning is. Genuinely unresolved is defensible; unresolved-by-preference is the finding most often overturned on review.
Recording inconclusive on an allegation that was never fully put to the respondent
An allegation the respondent was not asked about produces two accounts only because one of them was never taken. That is a procedural defect, not an evidential deadlock, and it is fatal in a way a real deadlock is not — the fix is a further interview and a dated record of it, not a label.
Letting the inconclusive allegation into the room at the disciplinary meeting on the substantiated ones
The decision-maker reads the whole report and sanctions on the total impression unless someone stops them. It surfaces in the meeting notes — a reference to "the pattern of behavior" or "the corridor matter" — and it converts an outcome that decided nothing into an aggravating factor, which is the single most quotable line in a later claim.
Answering the complainant's "so what happens to him?" with "nothing, it wasn't proven"
It is usually said by a line manager, not the investigator, and it is wrong twice over: it treats an unresolved allegation as a rejected one, and it ignores the allegations that were substantiated. Brief whoever will be asked, in writing, on the two sentences they are to use.
Closing a withdrawn complaint as inconclusive
A withdrawal is not an evidential deadlock. It is a decision point about whether the organization continues on what it already knows, and recording it as inconclusive both misdescribes the file and hides the fact that the organization was on notice. Record the withdrawal, its date, and the decision taken on it.
Letting the case-management system record a different outcome from the report
Most HR case systems offer two outcome values. Whoever closes the record picks the nearest one, and "not substantiated" lands in the field. Discovery produces the report and the system export together, and the discrepancy reads as the organization deciding against the complainant while telling her something softer. Check the closed record against the report before the file is archived.
Questions
- Can we discipline the respondent after an inconclusive finding?
- Not on that allegation, as a matter of practicality — there is no finding to point to, and discipline for conduct you did not find has no stated basis, which is precisely what a pretext argument needs. The framing to avoid is that he has a right to a finding: in at-will private employment he generally does not, and the "no discipline without process" rule is a just-cause frame imported from UK ACAS practice and Canadian arbitration. It becomes a genuine entitlement only through a contract, a collective bargaining agreement's just-cause clause, or Loudermill due process for public employees. So act on the allegations that were substantiated, name them in the record, and treat prospective, universal measures as separately justified.
- Our policy only allows "substantiated" or "not substantiated". What do I record?
- Use the label the policy provides and make the reasoning carry the distinction expressly: state that the evidence did not permit a determination either way and that this is not a finding that the conduct did not occur. Then flag the two-term vocabulary for the next policy review. A policy that forces every unresolved allegation into a bucket the complainant reads as "we decided against you" generates appeals and agency charges that a third term would have prevented.
- Does an inconclusive outcome affect the complainant's right to file an EEOC charge?
- No — no internal outcome does. The deadline runs from the discriminatory act: 180 days, or 300 where a state or local fair employment practices agency has jurisdiction. For a hostile work environment the flat rule misleads. Under National Railroad Passenger Corp. v. Morgan a hostile-environment charge is timely if any act contributing to the environment falls inside the filing period, and the whole course of conduct can then be considered — exactly the position where the conduct alleged runs over several months. Discrete acts are different; each starts its own clock. Federal-sector employees are on a separate track and must contact an EEO counselor within 45 days. An internal investigation pauses none of these clocks.
- A second complaint has been made against the same respondent. Can I rely on the first?
- Not as evidence that the second allegation occurred — that is propensity reasoning and it will not survive review. It is relevant to two narrower questions: what the organization knew and when, which goes to the organization's own response rather than to his conduct; and whether a sweeping general denial remains sustainable. If you are going to consider it at all, put it to him and let him answer. Whether the earlier matter is disclosed to the new complainant is a question for counsel, not a default you apply at the desk.
- Should the inconclusive finding go in the respondent's personnel file?
- Keep it with the investigation file rather than the personnel file, indexed by respondent so a later complaint surfaces it, and restricted to HR and counsel. The reason is not a legal prohibition on what a personnel file may contain — it is that anything sitting in the file becomes available as a reason for a later decision, and a decision drawing on an allegation nobody substantiated is a pretext argument waiting to be made. In several states employees have a statutory right to inspect their personnel file, which is another reason to know exactly what is in it. Retention is a separate obligation: 29 CFR 1602.14 requires personnel and employment records to be preserved for at least a year, and until final disposition where a charge has been filed.
- The complainant says an inconclusive outcome means the company did nothing. What does the company actually owe her?
- A response that is reasonable on what it knows, which is not the same as a response that follows a finding. Where harassment by a supervisor is alleged, the Faragher and Ellerth affirmative defense turns on reasonable care to prevent and promptly correct, and reasonableness is judged from the date the employer had notice — the date the complaint arrived, not the date something was substantiated. So the answer is: the allegations that were substantiated have been acted on, the prospective measures are being taken on their own justification, monitoring is in place with named dates, and all of it is recorded. "We could not resolve it, so we stopped" is the position that loses.
- How long should the retaliation review gate run?
- Twelve months is a workable default, and the reason is that the events most useful to a retaliating manager are annual: the appraisal cycle, the promotion round, the shift-pattern reset, the bonus or supplement decision. A gate that expires at 90 days closes before any of them. Set the end date explicitly rather than letting it lapse, and diarize the review of the gate itself — an indefinite gate around one employee is its own detriment.
The blank template
Exactly what is in the Word download, so you can see the structure before deciding whether you want it.
Matter details and the allegation at issue
The honesty test: inconclusive, or unfinished?
- [State the single disputed fact in one sentence — if it takes a paragraph, it is more than one fact]
- [Name the evidence that would have resolved it, and why it is unavailable]
- [Did you seek it, and is the request documented with a date and a named recipient?]
- [Are there factors you were equipped to weigh — a contemporaneous record, a document, a rota — that you listed and then did not apply?]
- [Would you record the same outcome if the respondent held a different position? Check the pattern across your own recent matters, not just this one]
Disaggregate before you record inconclusive
- [Components accepted by the respondent or established by a document]
- [The single component genuinely in conflict]
- [Whether the policy provision can be engaged on the components that are established, and if not, why not]
Evidence sought, and the date you asked for it
The wording, and the words the letters reuse
Sorting what the organization does next
- [Prospective, universal measures and the standing operational reason each rests on]
- [Any terms-altering measure — and the substantiated finding, contractual basis or agreement it rests on, named]
- [Whether a CBA, contract or public-sector due-process obligation applies to this respondent]
- [Targeting check: is any measure scheduled or scoped so that it identifies the respondent to the team?]
- [Do-not list: where the inconclusive allegation must not appear — appraisal, promotion packs, the sanction decision on other allegations]
What the team is told, and Section 7
Closing out the interim measures
The retaliation review gate
What the organization knows now, whatever the finding
Retention, indexing, and a later complaint against the same respondent
Sign-off and distribution
Download this template
Free Word download, no email required. Or open it in Professional Drafter — it lands in your template library, ready to draft against.
Sources
- EEOC — Enforcement Guidance: Vicarious Liability for Unlawful Harassment by Supervisors (1999, still operative)
- EEOC — Enforcement Guidance on Retaliation and Related Issues (2016)
- EEOC — Harassment (overview and employer obligations)
- Faragher v. City of Boca Raton, 524 U.S. 775 (1998) — reasonable care to prevent and correct
- Burlington Industries, Inc. v. Ellerth, 524 U.S. 742 (1998) — employer liability for supervisor harassment
- National Railroad Passenger Corp. v. Morgan, 536 U.S. 101 (2002) — timeliness of hostile-environment charges
- Burlington Northern & Santa Fe Railway Co. v. White, 548 U.S. 53 (2006) — materially adverse action (U.S. Reports, Library of Congress)
- Clark County School District v. Breeden, 532 U.S. 268 (2001) — objectively reasonable belief under the opposition clause (U.S. Reports, Library of Congress)
- Cleveland Board of Education v. Loudermill, 470 U.S. 532 (1985) — pre-deprivation process, public employees only
- NLRB — Board Adopts New Standard for Assessing Lawfulness of Work Rules (Stericycle, 2023)
- NLRB — National Labor Relations Act (Section 7 rights)
- 29 CFR 1602.14 — Preservation of records made or kept (eCFR)
- EEOC — Time Limits for Filing a Charge
Related templates
Credibility Assessment Template & Example (Workplace Investigation)
A structured credibility assessment template using objective factors — plausibility, corroboration, consistency and motive — with a filled-in worked example showing the reasoning written out.
Findings of Fact Template: Substantiated, Not Substantiated, Inconclusive
A findings-of-fact worksheet that ties each allegation to the evidence relied on, the standard applied, and a clear substantiated / not substantiated / inconclusive outcome.
Investigation Outcome Letter Templates & Samples
Outcome letter templates for both parties, with guidance on the hardest judgment in the process: how much detail each party receives about the findings.
Suspension Pending Investigation & Interim Measures Memo
A memo recording interim measures during an investigation — the risk addressed, why the measure is not punitive, who decided, and when it will be reviewed.
This page is a documentation aid, not legal advice. Workplace investigation requirements vary by jurisdiction, sector and policy, and a template cannot tell you what your matter requires. The worked example describes a fictional scenario.