{
  "title": "Tyler Technologies / eFileMaine Gmail Notice Audit",
  "generated": "2026-08-18",
  "review_window": {
    "start": "2026-03-30",
    "end": "2026-08-17",
    "elapsed_days": 140
  },
  "gmail_query": "from:(no-reply@efilingmail.tylertech.cloud) after:2026/03/29 before:2026/08/19 -in:spam -in:trash",
  "counts": {
    "tyler_domain_total": 879,
    "filing_system_notices": 878,
    "account_password_messages": 1,
    "submitted_filing": 196,
    "service": 343,
    "primary_rejection": 91,
    "file_serve_rejection": 143,
    "entry_confirmation": 103,
    "failed_submission": 2,
    "rejection_return_total": 234
  },
  "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.",
  "case_studies": [
    {
      "envelope": "199174",
      "date": "2026-03-30 to 2026-03-31",
      "issue": "First documented Region 1 filing cycle in the audit window",
      "record": "Submitted March 30 at 3:06 p.m. ET; rejected March 31.",
      "source_message_ids": [
        "19d4025e273fff0b",
        "19d43ee416e33d05"
      ],
      "classification": "submission and rejection notices"
    },
    {
      "envelope": "210756 / 210987",
      "date": "2026-04-27",
      "issue": "Authorized service contact",
      "record": "Rejected under M.R.E.C.S. 36(B) for an authorized service contact not being provided for/by a party.",
      "source_message_ids": [
        "19dcfaa26fdc7a8f",
        "19dd02d733359495"
      ],
      "classification": "clerk rejection reason transmitted by Tyler"
    },
    {
      "envelope": "220333",
      "date": "2026-05-14",
      "issue": "Mandatory form and relation-back clock",
      "record": "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_message_ids": [
        "19e27e5ddd186eaf"
      ],
      "classification": "clerk rule/form instruction transmitted by Tyler"
    },
    {
      "envelope": "240279",
      "date": "2026-06-30",
      "issue": "Comments to Court were not court-presented content",
      "record": "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_message_ids": [
        "19f191f7217e05ba"
      ],
      "classification": "workflow and presentment instruction"
    },
    {
      "envelope": "249014",
      "date": "2026-07-19",
      "issue": "Failed filing submission",
      "record": "The system issued a failed-submission notice rather than a clerk acceptance or rejection notice.",
      "source_message_ids": [
        "19f7a8689b4c35a5"
      ],
      "classification": "system submission failure"
    },
    {
      "envelope": "252039",
      "date": "2026-07-25 to 2026-07-26",
      "issue": "Proposed order requirement",
      "record": "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_message_ids": [
        "19f9a713a8260ad4",
        "19fa09d873cae9d3",
        "19fa0ba09ecddcc6"
      ],
      "classification": "submission, rejection, and relation-back resubmission"
    },
    {
      "envelope": "257090",
      "date": "2026-08-04 to 2026-08-06",
      "issue": "One envelope produced thirty automated emails",
      "record": "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\u2014a thirteen-second burst. The rejection included separate-document requirements for attachments/exhibits.",
      "source_message_ids": [
        "19fcf1fe636c1095",
        "19fcf1fe9136d0a9",
        "19fd76be06960c15",
        "19fd76c11117257f"
      ],
      "classification": "single-envelope notification multiplication",
      "message_counts": {
        "submission": 5,
        "service": 10,
        "primary_rejection": 5,
        "file_serve_rejection": 10,
        "total": 30,
        "rejection_burst_seconds": 13
      }
    },
    {
      "envelope": "262592",
      "date": "2026-08-17",
      "issue": "Entry and rejection notices appeared for the same envelope",
      "record": "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_message_ids": [
        "1a01137db7debe2b",
        "1a01138f79c25f95"
      ],
      "classification": "mixed component/status messaging"
    }
  ],
  "responsibility_map": [
    {
      "lane": "Tyler Technologies / eFileMaine",
      "scope": "Portal usability, notification generation, duplicate-message behavior, system-failure messaging, status presentation, and technical-support routing."
    },
    {
      "lane": "Maine Judicial Branch",
      "scope": "Procurement, configuration, M.R.E.C.S. rules, mandatory forms, operational policy, and whether the digital workflow is accessible to self-represented litigants."
    },
    {
      "lane": "Clerk review",
      "scope": "The substantive acceptance/rejection decision, corrective comments, filing-code treatment, document separation, and entry into Odyssey."
    },
    {
      "lane": "Filer",
      "scope": "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."
  ]
}