TYLER TECHNOLOGIES / eFILEMAINE PUBLIC ACCOUNTABILITY RECORD
Gmail notice audit: March 30 through August 17, 2026

COUNTING RULE
Counts are Gmail-message counts. They are not counts of unique envelopes, filing packets, rejected filings, independent defects, or judicial decisions. Duplicate notices are normalized by envelope for case studies.

VERIFIED MESSAGE COUNTS
879 Tyler-domain emails total; 878 filing-system notices and 1 account/password message.
196 submission notices; 343 service notices; 91 primary rejection notices; 143 File & Serve rejection/return notices; 103 entry confirmations; 2 failed-submission notices.
Combined rejection/return email count: 234. This is not a count of unique rejected filings.

NORMALIZED CASE STUDIES
2026-03-30 to 2026-03-31 | Envelope 199174 | First documented Region 1 filing cycle in the audit window
Submitted March 30 at 3:06 p.m. ET; rejected March 31.
Source Gmail message ID(s): 19d4025e273fff0b, 19d43ee416e33d05

2026-04-27 | Envelope 210756 / 210987 | Authorized service contact
Rejected under M.R.E.C.S. 36(B) for an authorized service contact not being provided for/by a party.
Source Gmail message ID(s): 19dcfaa26fdc7a8f, 19dd02d733359495

2026-05-14 | Envelope 220333 | Mandatory form and relation-back clock
Motion for Interim Implementation Order and Expedited Status Conference rejected because FM-218 was required. The notice imposed a four-business-day M.R.E.C.S. 35(E) correction path and exact language in Comments to Court.
Source Gmail message ID(s): 19e27e5ddd186eaf

2026-06-30 | Envelope 240279 | Comments to Court were not court-presented content
The rejection notice stated that the Filing Comments section was visible only to File & Serve reviewers and that language intended for the court had to be submitted as a proper filing.
Source Gmail message ID(s): 19f191f7217e05ba

2026-07-19 | Envelope 249014 | Failed filing submission
The system issued a failed-submission notice rather than a clerk acceptance or rejection notice.
Source Gmail message ID(s): 19f7a8689b4c35a5

2026-07-25 to 2026-07-26 | Envelope 252039 | Proposed order requirement
Submitted and served, then rejected because a proposed order was not included when required under M.R. Civ. P. 7; promptly resubmitted as envelope 252093.
Source Gmail message ID(s): 19f9a713a8260ad4, 19fa09d873cae9d3, 19fa0ba09ecddcc6

2026-08-04 to 2026-08-06 | Envelope 257090 | One envelope produced thirty automated emails
Five submission notices and ten service notices were followed by five primary rejection notices and ten File & Serve rejection notices. The fifteen rejection/return messages arrived between 10:13:18 and 10:13:31 a.m. ET—a thirteen-second burst. The rejection included separate-document requirements for attachments/exhibits.
Source Gmail message ID(s): 19fcf1fe636c1095, 19fcf1fe9136d0a9, 19fd76be06960c15, 19fd76c11117257f

2026-08-17 | Envelope 262592 | Entry and rejection notices appeared for the same envelope
The Gmail record contains repeated rejection/return notices and a confirmation of entry for envelope 262592 within minutes. Component-level docket status controls; the message pattern illustrates why a filer needs one authoritative envelope-and-document status view.
Source Gmail message ID(s): 1a01137db7debe2b, 1a01138f79c25f95

RESPONSIBILITY MAP
Tyler Technologies / eFileMaine: Portal usability, notification generation, duplicate-message behavior, system-failure messaging, status presentation, and technical-support routing.
Maine Judicial Branch: Procurement, configuration, M.R.E.C.S. rules, mandatory forms, operational policy, and whether the digital workflow is accessible to self-represented litigants.
Clerk review: The substantive acceptance/rejection decision, corrective comments, filing-code treatment, document separation, and entry into Odyssey.
Filer: Document content, signatures, filing codes, service contacts, forms, proposed orders, exhibits, and timely correction of defects.

LIMITATIONS
- A Tyler-domain email proves that a notice was generated and transmitted; it does not by itself establish that every clerk instruction was erroneous.
- Rejection reasons shown in automated notices are identified as clerk-office reasons transmitted through the platform, not automatically as Tyler policy.
- An envelope can contain multiple filing components and recipients, generating multiple notices from one submission event.
- The official docket, accepted filing, clerk record, and native system audit logs control the final status of any filing component.
- The audit does not publish confidential filing documents, private service links, or unnecessary minor-identifying information.

PUBLIC-ACCOUNTABILITY POSITION
The central question is not whether electronic filing should have rules. It is whether the combined platform, configuration, review, correction, service, and notice architecture creates unnecessary process before a filing reaches meaningful judicial consideration.