Adverse filing messages reported
The July 21 preservation notice recorded the sender’s Gmail count—not an official statewide Tyler statistic.
Page sections
Vendor accountability · electronic court access · public record
Maine eCourts and Tyler Technologies Accountability Record
A documentary record of repeated eFileMaine rejection cycles, public-facing interface defects, legislative notice, preservation demands, and the administrative labor shifted onto a self-represented court user.
Record boundary: This page combines sent-email records, linked public documents, first-person observations, and public-policy criticism. It does not claim that every rejection was improper, that every message reflects a unique software defect, that any particular defect changed a court result, or that a tribunal has found misconduct by Tyler Technologies or the Maine Judicial Branch. The question presented is whether the documented burden, notice, response, and correction history warrant transparent public review.
Record at a glance
The public did not buy an automated rejection factory.
Distinct rejected envelopes reported
The related July 22 article reported at least 40 distinct envelopes across 32 calendar dates.
Messages on July 20–21
The article reported a two-day burst of rejection, return, or failed-submission traffic.
Visible interface defect
The July 26 service record stated that the CSS/login-card bleed was finally corrected after months of notice.
Notice and correction timeline
The defect was reported. The filing burden was documented. The record kept growing.
This sequence distinguishes what the source records establish from what remains a question for Tyler Technologies, Maine Judicial Branch leadership, court administration, and public oversight.
Public email record on Tyler and eFileMaine access barriers
An earlier outreach record placed electronic-filing barriers into the public documentary lane and distributed the concern beyond a private support exchange.
Legislators and newsrooms receive a public notice on eCourts cost, access, and record accuracy
The notice used a court-audio and registry-accuracy request as a concrete example of the burden placed on a public user, then asked for an independent accounting of procurement, configuration, continuing support costs, and the product Maine actually received.
Professional Courtesy Notice to Tyler, Maine eCourts, the Judicial Branch, legislators, and newsrooms
The notice described months of opaque rejections, repeated resubmissions, fragmented routing, delayed action, and a visible defect on Tyler’s public-facing login experience. It requested a substantive response and escalation reference.
Formal preservation notice documents 174 rejection and failure messages
The preservation notice asked that support tickets, logs, rejection records, routing history, configuration and change records, screenshots, and internal communications be preserved. It identified representative envelopes and expressly told the Legislature that the request concerned public systems—not adjudication of a private family dispute.
“The Two-Headed Snake Coin of Maine Justice” publishes the filing metrics
The related commentary reported 71 “Rejected Filing Notification” messages, 101 “File & Serve Filing Rejected Notification” messages, and 2 failed-submission notices in the author’s mailbox review. It framed the issue as public-money, access-to-justice, and accountability—not proof that every rejection was erroneous.
Read the original LinkedIn article · Open the record extract
The login-card defect was reportedly still visible
Justin Tahai reports that the defect remained present on Friday. This page does not present a separate Friday screenshot as independent verification; it preserves the observation with that limitation.
Rule 5 service email documents the corrected interface
A current screenshot was served with a relation-back filing record. The email stated: “Four months later, the CSS bleed is finally fixed,” while expressly declining to claim that the sender’s emails caused the change.
Legislative and public notice
The Legislature was not asked to decide a private case. It was asked to account for a public system.
The notices repeatedly separated the merits of a family matter from the State's responsibility for procurement, filing access, support workflows, record accuracy, administrative duplication, relation-back protection, and whether delay destroys rights before a judge reaches the substance.
Tyler / eFileMaine access barriers
Public preservation notice describing technical rejections, packaging rules, portal friction, and the mismatch between modern document-processing capabilities and the workflow experienced by a self-represented litigant.
Open the email PDFCost, configuration, and record accuracy
A public notice to legislators and newsrooms asking what Maine purchased, what was configured, what remains unavailable, and why an ordinary audio/record request still required a specialized chain of forms, categories, portals, and correction risk.
Open the public extractMonths of rejection and support failure
Direct notice to Tyler, Maine eCourts, Judicial Branch leadership, legislators, and newsrooms describing repeated rejection cycles and requesting a substantive response and escalation reference.
Open the public extractFormal preservation notice
Notice requesting preservation of support tickets, rejection records, routing history, configuration changes, screenshots, and internal communications while documenting the sender's 174-message archive count.
Open the preservation extractSee who received the public notice.
Open email PDF + recipient listThe July 17 email PDF preserves the broad distribution record—including Maine legislators, Judicial Branch and bar-oversight recipients, counsel, parties, and news organizations—so readers can inspect the contact list rather than accept a vague claim of “notice.”
Public documents and commentary
Open the records. Test the characterization.
The strongest accountability page is not the loudest one. It is the one that lets readers inspect the sequence, see the limits of each source, and decide whether the public received the court-access system it paid for.
Multimillion-Dollar eCourts Failures — July 15
A public notice tying a specific audio/record-accuracy problem to procurement, configuration, support workflow, and continuing taxpayer-cost questions.
“The Legislature and the press should require an independent accounting of what was promised, what was delivered, what remains unavailable, how much the State continues to pay...”
Tyler / eFileMaine Access Barriers — July 6
An original public outreach email record documenting electronic-filing and access concerns before the later preservation sequence.
Earlier notice matters because a corrected defect should not erase how long it remained public or how often the concern was raised.
When Professionals Become More Troubled by Documentation Than by Harm
The July 17 notice addresses the institutional inversion in which record volume becomes the complaint while the unresolved failure that generated the record receives less scrutiny.
The paper trail is not the original harm. It is the footprint left by a failure that continued.
The Two-Headed Snake Coin of Maine Justice
A sharp public-accountability article connecting the court-access vendor lane with the professional-regulation lane while preserving separate responsibility for each.
“Every rejection manufactures more litigation labor.”
Email notice and correction extracts
Four privacy-conscious public extracts identify dates, subjects, recipient groups, requested action, key exact excerpts, and the boundary of what each source proves.
They are public summaries, not raw MIME exports and not a substitute for native records in a formal investigation.
Who received public notice?
Technology and court administration
Tyler Technologies filing support, Maine eCourts help, Maine Judicial Branch technical and leadership channels, and Judicial Branch public-information recipients.
State oversight and elected officials
The Office of the Maine Attorney General, state executive recipients, and broad distribution to members of the 132nd Maine Legislature.
Press and public accountability
Maine and regional newsrooms, investigative desks, public-interest outlets, professional-regulation recipients, counsel, and parties.
The source emails preserve the detailed recipient fields. This page groups them by public function so the accountability record remains readable and does not become an indiscriminate address dump.
Proof boundary
What the record establishes—and what it does not.
The published record establishes
- Repeated written notice to Tyler Technologies, Maine eCourts, Judicial Branch recipients, legislators, and newsrooms.
- A sender-documented archive count of 174 rejection or failure messages, with the count methodology and limitations stated publicly.
- A publicly visible login-card/CSS defect documented before its later correction.
- A July 26 email and current screenshot documenting that the interface had changed.
- Requests for preservation, audit, escalation, and assurance that filing barriers would not prejudice access to judicial review.
The published record does not establish
- That all 174 messages represented unique defects or improper rejections.
- That Tyler Technologies alone controlled every rejection, routing decision, support response, or court delay.
- That the public notices caused the interface correction.
- That a specific filing-system event caused a particular judicial outcome.
- That a court, regulator, auditor, or procurement authority has made a misconduct finding.
The public-accountability request
A correction is welcome. An explanation is still owed.
Preserve the native record
Support tickets, rejection logs, envelope events, configuration changes, notices, screenshots, and internal communications should be retained under ordinary legal and public-record obligations.
Audit rejection and duplication workflows
Separate unique filer errors from duplicate automated messages, platform validation failures, routing problems, and avoidable clerk-review rework.
Publish meaningful performance measures
Report rejection rates, repeat rejections, correction time, support escalation, urgent-filing handling, and time from submission to merits review.
Protect relation-back and access rights
Promptly corrected technical defects should not erase the original attempted-filing date or prejudice a litigant before a judge reaches the substance.
Explain the interface correction
Identify when the CSS/login-card defect was corrected, who owned the fix, and whether related interface-quality checks were added.
Answer the public, not just the ticket
A taxpayer-funded justice platform should provide a substantive accountability response when documented failure patterns reach legislators, oversight recipients, and newsrooms.
The point is not that every filing should be accepted. The point is that a modern court-access system should identify defects clearly, prevent avoidable rework, preserve timely attempts, escalate repeated failures, and let a human being reach the merits before procedural time becomes the outcome.
The public paid for a digital courthouse.The public is entitled to receipts.