Client
A UK prisoner escort and custody services contractor providing prison-to-court transport and courtroom video-link facilities under contract across several regional prison estates
Sector
Justice & Public Safety
Engagement
Prisoner movement and court video-link scheduling platform linking prison wing movement schedules, escort officer rostering and court listing office bookings into one shared operational view - multi-quarter programme.
What the client needed
A prisoner appearing at a hearing by video link depends on three separate organisations agreeing on the same slot: the prison, which has to move the right prisoner from their wing to a video suite at the right time without disrupting the rest of the day's regime; the escort contractor, which staffs and supervises that suite; and the court's own listing office, which sets hearing times independently and reschedules them without much notice. Before this engagement, those three parties coordinated by phone and email, each keeping its own version of the day's schedule, and the client's own incident logs showed hearings being delayed or collapsed entirely - what court staff call a "cracked" hearing - several times a week across the estate, most often because a prisoner wasn't in the suite when the court connected, or because a late court reschedule never reached the wing in time to move anyone.
How we worked
- Built a single shared schedule view combining court listing times, wing movement plans and escort officer rosters, so a change on any one side was visible to the other two the moment it was made rather than discovered at the suite door.
- Integrated with the court video-link booking system used by listing offices, so a confirmed or rescheduled hearing slot fed directly into wing movement planning instead of arriving as a phone call to whoever happened to answer.
- Built an automatic movement-readiness countdown for wing staff, flagging which prisoners needed to be moving to a suite in the next thirty minutes, rather than relying on a paper movement sheet checked at fixed points in the day.
- Added an explicit late-reschedule alert path, so a court changing a hearing time inside the two-hour window that previously caused most missed connections triggered an immediate flag to both the wing and the escort supervisor.
- Ran the platform alongside the existing paper and phone process for a full term of court sittings, comparing collapsed-hearing rates before treating it as the primary process.
- Trained wing staff, escort officers and suite supervisors across every site in the contract on the shared view, since the benefit only holds if every site is working from the same schedule rather than some still relying on the phone.
Measured results
All figures verified with the client. Specific site, personnel and prisoner detail withheld in line with our standard confidentiality terms and criminal justice data-handling requirements.
- Hearings collapsed due to a prisoner not being ready when the court connected fell from several a week across the estate to close to zero in a full term of sittings.
- The late-reschedule alert path materially cut the number of movements started for a hearing time that had already changed, once courts' own last-minute reschedules were reaching the wing in real time.
- Escort supervisors report far less time spent chasing wing staff and listing offices by phone to confirm a schedule that should already have matched across all three parties.
- The shared schedule surfaced a specific gap at one site where wing movement plans and escort rosters had been running to slightly different daily cut-off times for months without anyone noticing - now aligned rather than silently worked around.
- The contractor is extending the same shared-schedule approach to prisoner transfers between sites, where the coordination problem is similar but the parties involved are different.
"Every one of those cracked hearings meant a victim, a witness or a defendant turning up to nothing, and a court slot that could have gone to someone else sitting empty instead. Nobody involved was being careless - the prison, the escort staff and the court were all doing their own job properly. What none of us had was one version of the day that all three could see at the same time, so a late change on one side kept arriving too late for the other two to act on it. That's the part this fixed."
Working on something similar?
If this engagement looks like the kind of problem you are facing, we would be glad to compare notes by email.
Context and constraints
Coordinating a prisoner's appearance at a court hearing by video link sits across an organisational boundary that most scheduling problems don't have to deal with: three separate organisations, each with its own systems, its own priorities and its own legitimate reasons for changing a plan at short notice, all needing to agree on the same fifteen-minute window. The brief was explicit that the platform had to work with the prison's existing wing management systems and the court's own video-link booking system rather than replace either, since both were established, audited systems with their own governance, and the actual problem was that the information inside them wasn't reaching the other two parties fast enough to act on.
Criminal justice data-handling requirements shaped the build from the outset. Prisoner movement schedules and hearing details are sensitive by nature, and the platform was built so that each party could see only the fields relevant to its own role - a court listing office needed hearing times and suite availability, not a prisoner's wing location or security categorisation, and wing staff needed a movement countdown, not case details. Getting that access boundary right took longer than the scheduling logic itself, but it was not a step the client would have accepted skipping.
Building an alert that arrived before the movement, not after
The hardest design problem wasn't the shared schedule view itself - once all three parties agreed to work from one source, that part was comparatively straightforward - it was making sure a late court reschedule reached wing staff before, not after, an escort officer had already started walking a prisoner to a suite for a hearing time that no longer existed. We worked with wing staff and escort supervisors to define exactly how much notice a reschedule needed to trigger an audible alert rather than a passive update on a screen nobody was currently looking at, since the two-hour window before a hearing was when most of the previously collapsed hearings had actually gone wrong.
A full term before removing the phone as a fallback
We ran the platform alongside the existing phone-and-paper process for a full term of court sittings before treating it as the primary schedule, deliberately comparing collapsed-hearing counts against the client's own historical records rather than against a shorter and more favourable sample window. That longer comparison period is what surfaced a specific and previously invisible gap: one site's wing movement plans and its escort rostering had been working to slightly different daily cut-off times for months, a mismatch that the phone-based process had been silently absorbing through informal workarounds nobody had ever written down or flagged as a problem.
Lessons learned
The first lesson was that a scheduling problem spanning three separate organisations needs one shared source of truth with role-appropriate visibility, not three separate systems kept in sync by phone calls between people who each have their own day job to be doing at the same time.
The second lesson was that an alert is only useful if its timing matches how the underlying process actually breaks - a schedule change flagged after a movement has started is not meaningfully better than no flag at all, and getting the two-hour window right took real input from the staff who deal with a collapsed hearing when the alert comes too late.
The third lesson was that running a full term as a comparison period, rather than a shorter pilot chosen for convenience, is what it took to catch a cut-off time mismatch that had been quietly absorbed by informal workarounds for months - the same pattern we've seen surface in other cross-organisational coordination programmes we've delivered.
If your organisation coordinates a time-critical process across more than one organisational boundary, we would be glad to discuss what a programme like this might look like for you. Email sales@halfteck.com.