Judiciary Websites

We build court websites organized around the tasks people arrive to complete.

What we usually find

Most court websites are organized around the institution: divisions, departments, and PDFs. People arrive with a task and a court date, and leave with a phone call to your clerk.

The first question we ask is whether something your agency already owns can be made to do this. Where the answer is yes, that is the recommendation, and it is a smaller and cheaper engagement than the one described below.

What follows is what the work looks like when the answer is no: the reference scope for a typical engagement, the variables that move what it costs, and what your agency holds at the end of it. Scoping is done by the engineers who will do the build, which is usually why the scope comes back smaller than an agency expects.

What a typical engagement includes

Content and information architecture built around what people arrive to do
Accessible templates meeting WCAG 2.2 AA, tested with assistive technology
Plain-language rewrite of the pages that generate the most counter traffic
A content system your staff can maintain without a developer
Language access included from the start
Migration of existing content, with the dead pages retired rather than moved

This is a reference scope, written in full before the work starts and adjusted to your agency during scoping. Anything included is written down, and anything left out is written down too.

What moves the price

Two agencies buying the same offering will pay differently, and these are the reasons why. We publish them because they are the questions we would ask in the first scoping session, and you can work out most of your own answers before that session happens.

How many pages survive the content audit
Whether translation is human, machine assisted, or both
How many systems the site has to link into
Whether you keep your current content system or move

What happens when scope changes

Scope changes on nearly every project. We manage changes through a documented approval process, so your agency sees the cost of a change before any work happens.

The change is documented: Anything outside the written scope is raised as a change request, in writing, as soon as we identify it.
The change is priced: You receive the cost and the schedule impact in writing before any work on the change starts.
Your agency decides: You can approve, defer, or decline the change. Declining does not affect the rest of the engagement.
No work proceeds without approval: No change is built or billed without your written approval.

What your agency owns at the end

The source code is yours, in your own repository from the first commit. Host it yourself, keep us on support, or move it later: all three options are priced in advance.

How Custom Digital Solutions runs, phase by phase

What it costs, and how it is bought

This offering is bought through the Build engagement, against a scope written and agreed before any work starts. We publish a price only once it is a commitment, so the band for this engagement is not on the page yet. Everything else about it is.

Builds usually depend on services such as hosting, email, messaging, identity, or payments. Your existing services are the starting point.

See engagements and pricing

Judiciary Websites

Price: From $60,000
Timeline: 10 to 16 weeks
Bought through: Build

What we need from your team

A decision maker who can approve scope in one meeting
Access to the systems it must integrate with
Staff time for research and review, about 3 hours every two weeks

The safe first step

The readiness assessment is free, takes about 20 minutes, and returns a scored report you keep. It creates no obligation, no call, and no follow-up.

Start a conversation Take the readiness assessment See engagements and pricing