Corrections and Updates

Corrections and Update Policy

This page explains how Azrested handles page-level correction concerns, documentation-based update requests, and the important difference between an official source changing over time and a site page needing review.

What This Policy Clarifies

When to verify with an official source first

When a page-level concern belongs in the review workflow

When formal legal communications should use the legal contact channel

Public-record pages can age in two different ways. Sometimes the source record itself changes because a jail, court, clerk, or agency posts later developments. Other times a visitor believes the page raises a page-specific issue that can be reviewed with documentation. This policy exists to separate those situations clearly.

Official Source Changes

If the concern is about current custody, release, court activity, case disposition, or another later development, the first step is usually to verify the current official record rather than assume the site page is independently controlling that fact.

Page-Level Review Issues

If the concern is mistaken identity, a documented factual mismatch, a qualifying legal order, or another issue that can be assessed at the page level, the review workflow is the more appropriate route.

Formal Legal Communications

Attorneys, courts, and government agencies acting in an official capacity should use the legal contact route so formal notices are not mixed into the ordinary visitor request queue.

What Helps a Review Request Move Faster

  • The exact page URL and a clear description of the issue.
  • Supporting documents that explain why the concern is a page-level review issue.
  • Confirmation that current official-source questions have already been checked when relevant.
  • A clear distinction between a later official update and a claim that the page itself needs review.

1. Verify Current Facts

Make sure the question is not really about a later update controlled by a jail, clerk, court, agency, or corrections source.

2. Gather Documentation

If the concern is page-specific, gather the records, order, or factual support needed to explain the issue clearly.

3. Use the Right Channel

Use the review form for structured documentation-based concerns and the legal contact route for formal official communications.

How This Policy Connects to the Rest of the Site

A Good Corrections Policy Starts by Separating Two Kinds of Problems

One kind of problem belongs with the official public office because the underlying fact changed over time. The other belongs with the site because the page presentation or documentation raises a review issue. This policy is built to help visitors tell those apart before they lose time.