AC
Family Division Scheduling
RiteTrack · Court of Common Pleas of Allegheny County · Prototype v1
Step 1 · Judicial chambers

Chambers request form

A page of its own, outside RiteTrack. Chambers staff open a link and fill it in — no application to learn, no licence to assign, nothing to install. It posts straight into the scheduling queue.

Session note · 16:52Today the 17 secretaries email Patty. If she takes a week off she returns to roughly 600 messages. This form is the replacement for that inbox — and keeping it outside RiteTrack means chambers never has to be onboarded to get it.
🔒 forms.alleghenycourts.us/family/listing-request
AC

Request a listing · Family Division

For judicial chambers. Submissions reach the scheduling office immediately.

No sign-in. The link is emailed once to each chambers and works from any county machine. Submissions are stamped with the chambers that sent them, and Patty sees them the moment they arrive.

New listing request

FD-REQ · draft
Mirrors the "schedule it after ___" line chambers writes today.
Session note · 36:42Counsel is a free-text field in FCSS today — it repeats whatever was typed last time, and there is no way back to a bar number. These fields read the participant table the custody module already populates.

What scheduling receives

Submitting writes one record. It lands in the queue, it counts toward the trend report, and the order travels with it. No re-keying anywhere.

This judge's rules

How it reaches the queue

The form is a static page on the county web server. It posts one JSON document to RiteTrack over the documented interface, and the reply carries the request number back to the person who submitted it. Nothing else is exposed.

HostingCounty web server. No RiteTrack licence consumed by chambers.
IdentityPer-chambers link. Every submission carries the sending chambers and a timestamp.
TransportSingle authenticated POST to the listings endpoint.
FailureIf RiteTrack is unreachable the form holds the request and retries, then emails scheduling as a fallback.
Step 2 · Scheduling desk

Scheduling queue

One list, sorted by age. It replaces the read/unread trick in Outlook and the Microsoft List that has to be typed up separately.

Session note · 20:43Three systems doing one job — email in, a hand-kept list for tracking, FCSS for the actual scheduling. This is all three.
—
Waiting to be completed
—
Oldest in queue (days)
—
Completed this month
—
Waiting on chambers

Find a case

FD number, party, counsel, or judge
Session note · 4:30"Trying to find something" was on her list of dislikes. This searches listings and open requests together, which is the thing FCSS and the tracking list can't do between them.

Open requests

Session note · 25:14She reads her backlog by judge, using unread mail as the counter. These are the same counts, kept for her.
AgeFD #Case nameJudgeType of proceeding LengthVenueNot before /
how far out
Referring party NoteOrderStatus
For the bench

My bench

Today’s listings, and one button: when the last matter wraps early, tell the scheduling desk the courtroom is clear. The room reads open everywhere the moment it’s tapped.

Judge McCrady · 9/30 email“Would it be possible to have a feature where a judge could notify Patti that the courtroom is vacant when they are done?”

—

—
External · Counsel self-service

Attorney date form

The county’s 48-hour date-response form, online. Counsel opens it from the email link — no RiteTrack sign-in — and the answer lands against the case, where the calendar can act on it.

From the paper form“Within 48 hours of receiving this form, please email the completed form and your scheduling documents… Your case will be scheduled without delay if this form is not returned timely.” Here the deadline, the reminder, and the filing all happen in one place.

Judicial Scheduling Request Form — Adult Section

48-hour response
The paper form lists seven judges plus “Other”; the portal offers the full bench.

4 · Contact information for all parties

5 · Bad dates for all parties

Every date in the current month and the next three months on which any party cannot attend a proceeding on this case.

Responses received

Scheduling-office view — counsel never sees this. Each response attaches to its case in the queue, and the calendar warns if a listing lands on a reported bad date.

FDCaseBad datesReturned
Scheduling · Events

Shift work

The recurring lists — motions, PFAs, exceptions, contempts — kept apart from the matters queue. A judge is put on the shift and it lands straight on the calendar.

Put a judge on a shift

No case numbers, no parties — the shift is the listing. The judge’s own rules still apply, Temporary-PFA Mondays included.

Scheduled shift work

Every upcoming shift across all seventeen judges. The month calendar’s All judges view draws the same picture.

DateTimeShiftJudgeRoom
Step 3 · Listing

Judge week

The judge's rules are drawn on the calendar, so an available slot is actually available. Hatched means a standing rule blocks it. Shaded means the judge would rather you didn't.

Session note · 26:49"Someone who doesn't know the system looks at this and asks why we can't put it at 11:30." Now the calendar answers that question itself.

—

Courtroom Teams Chambers Standing rule Judge prefers not Open

Standing rules in force

🔒 Visible to scheduling roles only
Step 4 · The question everyone calls about

Courtroom availability

Every courtroom, the whole day, one screen. An all-day matter reads as all day. Two judges can share a room at different hours — no chambers workaround required.

Session note · 10:08 & 49:43Two problems solved by the same picture: finding an open room took a dozen clicks through individual judges, and an all-day PFA listing displayed as morning-only — so a room looked free at 1:30 while the judge was on the bench in it.

—

In a courtroom Remote / chambers Protection from abuse Open

Open right now

When someone calls asking for a room this afternoon, this is the answer without opening a single judge's calendar.

RoomFloorOpen windowsTotal open
Step 5 · The request Patty gets weekly

Month at a glance

One judge, one month, everything on it — trials, conciliations, chambers days, time off. Print it or send it without editing a 300-page PDF.

Session note · 52:14The current workaround is printing every judge for the whole month, then deleting the other sixteen judges' pages one range at a time. Laura's version is a pen.

—

Step 6 · Public facing

Wayfinding board

The hallway screens read straight off the listings. Nothing is typed twice, hearing officers included.

Session note · 11:44Thirty minutes every morning, if uninterrupted, retyping into the television screen what was already entered in FCSS — plus the hearing officers, who sit in the same room every single day. This screen is generated, not entered.
AC
Family Division

—

3
—
—
Courtrooms on this floor Updated live from the court calendar

Standing assignments

Hearing officers keep the same room. Entered once, here, and the board carries them forward every day.

Hearing officerRoomDaysHours
Step 7 · Public website

Public motions calendar

The month builds itself from the listings. Publish pushes it to the county site through the feed — or hand it over as a file if the site team would rather paste it.

Session note · 55:35Every month, all thirty days of the motions calendar are typed into the website tool by hand, with the FCSS calendar open on the other half of the screen.

—

DateJudgeRoomTime

Publish

Site ownership sits with the communications team; IT holds the connection. Once it's pointed at the feed, nobody in the scheduling office touches it again.
Step 8 · Court IT

Exports & API

Pick the columns, pick the order, save it as a named layout. What comes out is already shaped the way the receiving system wants it, so nobody reformats anything downstream.

Session note · 1:04:44The ask wasn't "can you export to Excel" — it was "can the export already be in our columns," so that Patty isn't reformatting a file after the system produces it.

Column layout

—
Preview

Integration surface

RESTTwo-way, documented. Read and write on every scheduling object.
WebhookFires on list, continue, cancel, room change. JSON payload, your endpoint.
FeedRead-only URL per courtroom, per floor, per judge. What the screens consume.
iCalSubscription per judge for chambers calendars.
No private back door — everything the screens use is on the documented interface, which is what makes the four-network situation workable.
Configuration · Restricted

Judicial preferences

The scheduling matrix, held in the system instead of a spreadsheet. Rules the calendar can enforce are on the left; the ones that only a person can weigh are notes.

Session note · 33:20Judges will object if their preferences are visible to each other. Read access here is limited to the scheduling role — and it's the answer to what happens when the desk is covered by someone else.
🔒 Scheduling administrators only · every change is logged

Rules the calendar enforces

Unavailability

Hold a single day, a range of dates, or a range of hours. The scheduling calendars show what the time is held for; public screens never do.

Leave blank for a single day.
Shown on the scheduling calendars so the desk knows why; never on public screens, feeds, or exports.

Court-wide holidays

Session note · 2:03Holidays are added to every calendar by hand today. One import covers the court year for all seventeen judges.
Reporting

Reason for block out

Totals for held time over a period — how many bench days were blocked, and why. Partial-day holds count as half a day.

—

to
ReasonBench daysJudgesShare
Chambers self-service

Chambers block-out portal

Chambers signs in and holds their own Judge’s time directly — no email to the scheduling desk. It lands on the calendar the moment it is saved.

Hold time

—
In production this comes from the login — chambers only ever sees their own Judge.
Leave blank for a single day.
Shown on the scheduling calendars so the desk knows why; never on public screens, feeds, or exports.

Currently held for this Judge

Prototype for discussion on 20 August. Data is illustrative. Every screen here corresponds to something raised in the 28 July working session — turn on Session notes in the header to see which.