Registry Metrics Supervisors Should Track Weekly and Monthly

Most registry supervisors know when the unit is falling behind. The overdue list gets longer, officers mention they cannot get to everyone, and reported changes sit in a queue. What is often missing is a clear, consistent set of numbers that shows the problem, tracks whether fixes are working, and makes the case to command staff and budget officials.

This article describes six registry metrics supervisors should track, how to define each one so it stays consistent, how to review them on a weekly and monthly rhythm, and how to use them in budget requests. It does not offer benchmark targets. The most useful baseline is your own agency's data, measured the same way over time.

Why consistent definitions matter more than the numbers

A metric is only useful if it means the same thing every time you report it. If one month "overdue" means one day past due and the next month it means 30 days past due, the trend is meaningless.

Before you start reporting, write a one-page definitions sheet that answers:

• What exactly is being counted, and what is excluded?
• What is the time period (week, month, quarter)?
• Which system or report is the source?
• Who pulls the number, and on what day?

Keep the definitions stable. If you must change one, note the change and the date in your reports so readers can interpret the trend.

The six core metrics

The table below gives a starting definition for each metric. Adjust the details to match your state statute, agency policy, and records system.

Notes on each metric

Compliance rate is the headline number, but it can hide problems. Report it alongside the overdue and absconder counts so readers see what is driving it. Under SORNA (34 U.S.C. § 20901 et seq.), federal minimum verification frequencies are every year for Tier I, every 6 months for Tier II, and every 3 months for Tier III. State law may be stricter, so calculate "current" using the rules that actually apply to your registrants.

Overdue verifications are most useful grouped into aging buckets, such as 1 to 7 days, 8 to 30 days, and more than 30 days, using whatever intervals your policy sets. A long tail of very old items usually signals a process gap, not just a busy week.

Time to process reported changes matters because registrants must report changes of name, residence, employment, or student status in person within 3 business days under federal minimums. If the registry takes much longer to record the change, the public and partner agencies see stale information.

Absconder count should be tracked as a flow, not just a total. A stable total can hide many new cases offset by many located cases.

Verification attempts per officer is a workload measure, not a performance score. Read it alongside caseload size, geography, and the share of high-risk or transient registrants assigned to each officer.

Data quality issues include missing photos, invalid addresses, missing vehicle information, mismatched dates, and incomplete offense details. These issues affect public website accuracy and submissions to national systems.

Weekly review: keep the work moving

The weekly review is operational. Keep it short, ideally a standing 15-minute check with the people who do the work.

1. Review overdue verifications by aging bucket and assign the oldest items first.
2. Check the queue of reported changes and anything waiting longer than your policy target.
3. Review new and located absconder cases and confirm next steps for each open case.
4. Note any obstacles, such as vacancies, vehicle issues, or system problems.

The goal is action, not reporting. Each item should end with a name and a date.

Monthly review: look for trends

The monthly review is about direction. Pull all six metrics, compare them with the previous months, and ask:

• Is the compliance rate moving, and which metric explains the change?
• Are overdue items aging, or are they cleared quickly?
• Is processing time for reported changes stable or growing?
• Are verification attempts rising while completions stay flat? That can point to more "not home" outcomes or routing problems.
• Which data quality issues recur, and can they be fixed at intake?

Keep a simple running chart for each metric. Six to twelve months of consistent data tells a much clearer story than any single month.

Using metrics in budget requests

Budget officials respond to documented need. Registry metrics let you show the gap between workload and capacity in your agency's own numbers rather than general claims.

• Show the trend. A chart of overdue verifications growing over a year is more persuasive than a single snapshot.
• Connect workload to staffing. Use attempts per officer and active caseload to show what current staff can realistically complete each month.
• Quantify time spent. Measure how long common tasks take, such as processing a change or preparing a submission, then multiply by volume to estimate staff hours.
• Tie it to obligations. Jurisdictions that do not substantially implement SORNA face a 10% reduction in Byrne JAG funds. Explain how better tracking supports your state's compliance posture.
• Propose a measurable outcome. State which metric you expect to improve if the request is funded, and commit to reporting on it.

For help building the full justification, see funding registry modernization grants and the grant funding page.

Next steps

Start with the definitions sheet, then run the weekly review for a month before adding the monthly trend report. Many units find that the act of measuring reveals problems that were invisible before, such as old overdue items or recurring data errors.

Justice Compliance provides reports and dashboards built on registrant records with a complete, time-stamped audit trail, which makes metrics easier to pull and defend. To estimate how process changes could affect staff time in your agency, try the ROI calculator.