
No Way Pro Se: Why the IDPQ Is the Asserted Causal Connection
Outpost 422 examines how a disability-accommodation questionnaire entered an employment record—and why the resulting chronology deserves examination before Wisconsin’s Equal Rights Division.
By Bradley J. Burt
Outpost 422® | Journalism eDiscovery
Publication notice: This article concerns pending administrative proceedings. The allegations described below remain disputed unless established by a final agency or judicial ruling. Quotations should be evaluated against the underlying record.
The questionnaire is not background evidence
At the center of my pending Wisconsin Fair Employment Act dispute is an Interactive Dialogue Process Questionnaire, identified throughout my filings as the IDPQ.
The IDPQ is not merely another document in the case file. It is the asserted causal connection between my protected disability disclosures and the termination decision that followed.
My theory can be stated in four steps:
IDPQ disclosure → accommodation dialogue → “viewed as a threat” → termination
The legal question is not whether those four events occurred near one another by coincidence. The question is whether information introduced through the IDPQ materially influenced how the employer interpreted my conduct and ultimately decided to terminate my employment.
That question requires examination of the complete chronology.
What the IDPQ introduced
The IDPQ placed information about my service-connected disabilities, workplace limitations, and requested accommodations before the employer’s human-resources and management personnel.
Once that information entered the decision-making process, the employer possessed more than generalized knowledge that I was a veteran. It possessed information concerning the functional effects of documented disabilities and the workplace adjustments being requested.
The IDPQ therefore performs at least three evidentiary functions:
- It establishes the employer’s knowledge of the asserted limitations.
- It fixes the date when protected disability information entered the employment record.
- It identifies the decision-making channel through which that information reached human resources and management.
The subsequent statement that I was “viewed as a threat” cannot be examined in isolation from that record. The Tribunal must determine who formed that perception, what information influenced it, what specific conduct supposedly supported it, and whether the employer conducted an individualized assessment before relying upon it.
From accommodation to threat perception
Employers have a legitimate responsibility to address actual workplace threats. An accommodation request does not immunize an employee from neutral conduct rules, and disability law does not require an employer to ignore proven violent or threatening behavior.
But that principle does not answer the disputed question here.
The issue is whether an actual threat was documented—or whether disability and veteran-related information was converted into an ambiguous perception of dangerousness without an adequate factual foundation.
A proper examination should identify:
- The exact words or actions characterized as threatening;
- The original source of the characterization;
- Whether that person directly observed the alleged conduct;
- Whether the account was recorded contemporaneously;
- Whether witness descriptions remained consistent;
- Whether available video or other objective evidence was preserved;
- Whether the termination decisionmaker relied on firsthand evidence or hearsay;
- Whether medical or accommodation information influenced the interpretation; and
- Whether less adverse accommodations or workplace interventions were considered.
Where “threat” becomes a conclusion without a clearly identified factual predicate, the label itself requires scrutiny.

Wisconsin requires an individualized evaluation
Wisconsin disability law does not permit an employer to substitute generalized assumptions for an individualized evaluation of a particular employee’s ability to perform a particular job.
In Szleszinski v. LIRC, the Wisconsin Supreme Court addressed the statutory requirement for an individualized assessment. Wisconsin authorities also require an employer asserting a future safety hazard to establish a reasonable probability of substantial harm rather than a speculative possibility.
Similarly, Wingra Redi-Mix, Inc. v. LIRC confirms that a refusal-to-accommodate claim does not depend upon proving an independent violation called a “bad-faith interactive process.” The legally operative question is whether the employer refused an available reasonable accommodation without establishing the required defense.
That distinction matters.
My allegation is not simply that the conversation was unpleasant or procedurally imperfect. It is that the IDPQ introduced protected information into the decision-making chain; the employer then communicated a threat perception; and termination followed without an adequately documented accommodation or individualized safety analysis.
The probable-cause question
A probable-cause hearing is not a final determination of liability.
Under Wis. Admin. Code § DWD 218.02(8), probable cause exists when facts and circumstances provide reasonable grounds for a prudent person to believe that discrimination probably occurred or is occurring.
The standard is lower than the preponderance-of-the-evidence standard applicable at a hearing on the merits, but it requires more than speculation. The complainant must connect the evidence into a coherent factual theory.
My asserted connection is the IDPQ.
The evidentiary presentation should therefore focus on:
- The condition of the employment relationship before the IDPQ;
- The disability information disclosed through it;
- The personnel who received or discussed that information;
- The accommodations requested or reportedly implemented;
- The origin and timing of the “threat” characterization;
- The evidence used to support that characterization;
- The termination decision and stated reasons; and
- Any subsequent changes, omissions, or contradictions in the employer’s explanation.
This is a documentary causation theory. It does not depend on name-calling, speculation about private motives, or social-media popularity. It depends on the record.
Why Outpost 422 is publishing the process
Outpost 422 operates as a convergent-media reporting system.
The Bob Cobb reporting post collects raw footage, tips, leads, and preliminary source material. OP422 State Street organizes and distributes developing reports through the #OP422 public-discovery label. Outpost422.com serves as the reporting, evidence-examination, and Journalism eDiscovery archive.
ChatGPT assists with chronology development, document comparison, drafting, and issue identification. It does not replace the original evidence, independently verify disputed facts, or exercise final editorial judgment. The human publisher remains responsible for source selection, attribution, accuracy, corrections, and publication.
The purpose of this reporting is not to ask the public to decide a pending case. It is to document how a self-represented litigant identifies disputed facts, preserves objections, examines administrative standards, and builds a reviewable record.
Why “all blogs and social media” is overbroad
The existence of this reporting system does not make every post, private message, unpublished draft, unrelated article, or source communication relevant to an employment case.
A request for “all blogs and social media” collapses materially different categories:
- Raw and unverified leads;
- Unrelated journalism;
- Personal communications;
- Educational work;
- Posts concerning other employers or proceedings;
- Published articles addressing the respondent;
- Drafts and editorial analysis; and
- Private source material.
A properly limited request should identify the respondent, relevant subject matter, platforms, date range, claims, defenses, and damages issues involved.
I do not contend that relevant public statements are categorically immune from discovery. I object to converting a targeted employment proceeding into a wholesale inspection of an independent journalistic archive.
The reasonable scope is the nonprivileged material directly concerning the respondent, the IDPQ, the relevant employment events, the termination, the allegations presented to the agency, or damages claimed in that proceeding.
The record is the foundation
“No Way Pro Se” documents the difficult work of building an administrative record without counsel.
The project follows a basic rule:
Preserve the record. Analyze with integrity. Inform the public. Build accountability.
That requires disciplined language. A filed allegation is not a finding. A disputed exhibit is not automatically true. A respondent’s position statement is advocacy, not an adjudication. A probable-cause determination is not a final merits decision.
But an unresolved allegation does not become unreportable merely because it is disputed.
The responsible approach is to identify the source, disclose the procedural posture, distinguish allegation from finding, provide material context, and correct demonstrated errors.
That is the publication standard Outpost 422 will apply as the Tribunal examines the asserted causal chain:
IDPQ disclosure → accommodation dialogue → “viewed as a threat” → termination
The IDPQ is where protected information entered the record. Whether that information improperly influenced the termination decision is the question the evidence—and ultimately the Tribunal—must resolve.
Editorial disclosure: This report was developed through a human-controlled Journalism eDiscovery workflow using source records and AI-assisted drafting. Bradley J. Burt retains responsibility for factual attribution, legal characterization, editing, and publication.
Case-status notice: The matters discussed remain pending. Nothing in this article should be understood as reporting that discrimination has been finally established.
#OP422 · #JournalismeDiscovery · #ProSeRecord · #VeteranEmployment










