← All engine journeys

Small-Claims Court Journey

E-filed claim in a sixth domain, SAME engine. LOOP: first service failed then completed by an alternate method (history preserved). JOIN: 3 of 4 hearing prerequisites converge — the serviceable-party proof still active; "Ready for hearing" stays locked until all four meet. Exits fan out to plaintiff judgment (which launches collection), dismissal (which launches appeal), default, settlement, and withdrawal.

Entrance: e_onlineProgress controlled by: serverMost-likely exit: —

You are here (2 active)

  • activeClaim filedstate
    Where am I?
    Claim filed — active
    What just happened?
    —
    What happens next?
    —
    What could stop me?
    —
    How long?
    —

    Routes to Court e-filing portal (court) — official link not yet published

  • activeAwaiting service of processwaiting
    Where am I?
    Awaiting service of process — active
    What just happened?
    —
    What happens next?
    —
    What could stop me?
    —
    How long?
    1–4 weeks

    Routes to Sheriff / process server (court) — official link not yet published

Completed ✓ (6)

  • E-file the claim
  • Filing fee paid or waived
  • Evidence & documentation assembled
  • Serve the defendant
  • Service outcome
  • Proof of service on file

Waiting on (1)

  • Awaiting service of process — server · 1–4 weeks

Possible next (3)

  • Defendant identified with a serviceable address via enables
  • Settled before hearing via branches_to
  • Withdrawn / unable to serve via branches_to