Skip to content
JTforMEFAMILIES · PUBLIC SERVICE · ACCOUNTABILITY

PUBLIC DOLLARS / ACCOUNTABILITY

Public Money Evidence Chain: Contract, Deliverable, Payment and Performance

Follow the money. Follow the deliverable. Measure whether the public received what it paid for.

A strong public claim should survive hostile reading.

For each claimed failure or success, create an event ledger that lets another person reproduce the conclusion.

LayerQuestionEvidence
NeedWhat problem was the project supposed to solve?Procurement justification, assessment, project plan.
DeliverableWhat exact product, support task or service was required?Contract/SOW, authorization order, change order.
DeliveryWhat work was actually performed?Ticket, release note, work log, deliverable register.
AcceptanceWho accepted, rejected or conditionally accepted it?Acceptance memo, signoff, deficiency/cure record.
MoneyWhat was invoiced and paid?Invoice, voucher, ledger, credit/refund.
User outcomeDid the intended public-facing measure improve?First-pass acceptance, handling time, support resolution, access data.
CorrectionWhat happened after failure?Remediation, credit, revised requirement, policy change.

Measure outcomes that a family can actually experience.

First-pass acceptance

Eligible first submissions accepted ÷ eligible first submissions.

Review amplification

Total human processing reviews ÷ logical filings. More than one review may be legitimate; classify why.

Correction completeness

Returned filings where reasonably discoverable defects were identified together rather than serially.

Support resolution

Tickets where the question was substantively answered before closure.

Time to substantive action

Elapsed time from a procedurally usable request to a meaningful decision or responsible next step.

Implementation completion

Orders/services that reached a workable real-world outcome, not merely a docket event.

Do not blame the vendor for the court. Do not blame the filer for the system. Audit the event.

Classify each event as a necessary safeguard, preventable filer defect, system/vendor defect, court-process inconsistency, third-party availability problem, or indeterminate/mixed. A rejection notice alone does not establish which category applies.

That discipline permits severe criticism when the evidence supports it—and prevents a public-interest project from manufacturing certainty when it does not.

Inspect the record before drawing the conclusion.

  1. Maine Procurement Services — Service Contract Search — Official portal for current and archived service contracts, including Judicial Branch service contracts.
  2. Tyler Technologies Procurement Justification Form — NOI 0320240229 — $600,000 amendment request; $525,000 cap for additional professional services; $75,000 TAM cap; stated hourly ceiling of $210 for custom development; expressly not a guarantee of funds.
  3. Maine Judicial Branch — 2022 State of the Judiciary — States that BerryDunn was hired to assess Maine eCourts after implementation problems caused a pause.
  4. Maine Judicial Branch — 2024 State of the Judiciary — States that the Branch paused, obtained an independent assessment, reorganized, and later resumed rollout.
  5. Maine Judicial Branch — Maine eCourts — Current public rollout information and listed features of eCourts/eFileMaine.
  6. Maine Judicial Branch — eCourts access — Current public explanation of electronic-record access and limitations.
  7. Administrative Order JB-20-03 (A. 11-26) — Current implementation order governing MRECS during the continuing statewide rollout.
  8. JTforME fiscal accountability briefing — Public briefing with stated assumptions, workload model, fiscal sensitivity analysis and explicit limitations.
  9. JTforME public records tracker — Tracks selected DAFS and Judicial Branch requests and distinguishes acknowledgement, denial and unverified production status.

This is public-interest analysis, not an audit finding, legal opinion, procurement determination, or individualized legal advice. Contract ceilings are not the same as amounts paid. An observed problem is not automatically attributable to a vendor. A modeled capacity value is not cash recovered by the State.

PUBLIC ACCOUNTABILITY / SHARE THE RECORD

Share this public accountability record.

Help another reader reach the source directly. These controls open the selected platform; nothing posts automatically.

Facebook LinkedIn X Bluesky Email

Sharing a page does not endorse every claim. Read the sources, preserve context, and submit specific corrections through JTforME’s published correction process.