Is reliability scoring a background check or a consumer report?

No. It is an internal operational tool built only from your agency’s own records of how work was delivered. It does not pull outside information about a person, it is not sold or shared as a report about an individual, and it is not used to determine anyone’s eligibility to work.

What data does a reliability score use?

Typically first-party facts you already track: whether transcripts were delivered by the agreed due date, whether the reporter arrived on time for proceedings, and whether confirmed jobs were given back late. Strong tools show these factors so you can see how a score was formed.

Can a reliability score be wrong?

A score reflects the data behind it, so gaps or unusual circumstances can skew it, especially for reporters with very few past jobs. That is why explainability and human judgment matter. A manager should be able to see the factors, account for context, and make the final call.

All guides

Operations

What Court Reporter Reliability Scoring Is, and What It Is Not

Reliability scoring turns your agency's own delivery history into a simple, explainable signal for staffing time-sensitive work. Here is what it measures, what it does not, and how to use it responsibly.

Key takeaways

Reliability scoring is built from your agency's own operational data: past on-time delivery, on-time arrival at proceedings, and late give-backs.
It is an internal, advisory staffing aid. It is not a background check, a consumer report, or a credit score, and it does not decide who is eligible to work.
Explainability is essential. A staffer should always be able to see the factors behind a score and override it with good reason.
A person makes the final staffing decision. The score informs and speeds up the call; it does not replace human judgment.

What reliability scoring actually measures

Reliability scoring is an internal, advisory way to summarize how dependably a court reporter delivers, based entirely on your agency's own records of past work. It is a staffing aid, not a report, rating, or judgment about a person, and it does not reach outside your agency for information. It looks at the operational facts you already track every time you staff a job. From those facts, the tool produces a single, at-a-glance signal, often a number or a band, that helps you compare how reliably different reporters have delivered in the past. The signal is a summary of work history, nothing more.

On-time transcript delivery: did the finished transcript arrive by the agreed due date?
On-time arrival at proceedings: was the reporter present and ready at the scheduled start?
Late give-backs: was a confirmed job handed back close to the proceeding date, leaving little time to re-staff?

What reliability scoring is not

This is the part worth being precise about. Reliability scoring in this operational sense is an internal, advisory staffing aid. It is built from first-party data about how work was delivered, and it is meant to inform a human decision, never to replace one. Drawing the boundaries clearly protects your agency and the reporters you work with. A person always makes the final staffing decision. The score is one input among many, and a good manager weighs it alongside context that the data cannot see.

It is not a background check. It does not pull criminal, credit, or public-record information about anyone.
It is not a consumer report, and it is not governed or handled as one. It is not sold or shared as a product about an individual.
It is not a credit score. The signal reflects delivery history at your agency, not creditworthiness or financial standing.
It is not an eligibility determination. It does not decide whether a person may work, hold a license, or be hired. It informs which of your available reporters to assign to a given job.
It is not a judgment of character. A low signal can reflect a rough stretch, a scheduling conflict, or a thin data history, not a person’s worth or professionalism.

Why explainability matters

A reliability signal is only useful if the person reading it can see why it says what it says. A bare number with no context invites two failure modes: blind trust and blind dismissal. When a staffer can see the factors behind a score, they can judge whether it even applies to the job in front of them, and they stay in charge of the outcome. Explainability is what keeps a reliability signal an aid rather than a verdict. It lets a manager override the signal for good reason, correct bad data, and explain a staffing choice to a colleague or a client with confidence.

The factors are visible: on-time delivery rate, arrival record, and recent late give-backs, each shown plainly.
Recent events are distinguishable from older ones, so a reporter is not defined forever by a single bad month.
Thin histories are flagged. A reporter with only one or two past jobs does not have enough of a record to score confidently, and the tool should say so rather than imply false precision.

How to use it to staff time-sensitive work

The practical value shows up on jobs where a late transcript or a no-show carries real consequences: an expedite, a rush daily, a high-stakes deposition, or a matter with a firm court deadline. For routine work, most reporters on your roster will do fine. For time-sensitive work, a reliability signal helps you place your most dependable available reporters where the timing matters most. Used this way, the score does not make decisions. It helps you make faster, better-informed ones, and it gives your team a consistent way to talk about dependability.

Start with availability and fit, such as location, specialty, and rate, then use the reliability signal to choose among qualified options.
Reserve your strongest delivery records for the jobs with the least room for slippage.
Treat a low or thin signal as a prompt to confirm details, not as an automatic no.
Keep notes. When context explains a score, record it so the next staffer benefits from what you already know.

Bringing reliability scoring into your workflow

Most agencies already hold this information. It sits in emails, calendars, and spreadsheets, scattered across jobs and hard to see as a pattern. The value of a reliability feature is that it gathers those first-party facts in one place and presents them as a clear, explainable signal at the moment you are staffing. Falcyn offers this through a feature called Eyespan, which builds a reliability view from your agency’s own delivery and scheduling history and shows the factors behind it, so a person can make the final call with better information. Whatever tool you choose, the principles hold: keep it built from your own operational data, keep it explainable, and keep a human in the decision.

Frequently asked questions

Is reliability scoring a background check or a consumer report?: No. It is an internal operational tool built only from your agency’s own records of how work was delivered. It does not pull outside information about a person, it is not sold or shared as a report about an individual, and it is not used to determine anyone’s eligibility to work.
What data does a reliability score use?: Typically first-party facts you already track: whether transcripts were delivered by the agreed due date, whether the reporter arrived on time for proceedings, and whether confirmed jobs were given back late. Strong tools show these factors so you can see how a score was formed.
Can a reliability score be wrong?: A score reflects the data behind it, so gaps or unusual circumstances can skew it, especially for reporters with very few past jobs. That is why explainability and human judgment matter. A manager should be able to see the factors, account for context, and make the final call.