record-span docket · clerk's docket sheet

Map Missing Numbered Pages and Overlaps in a Delivered Record Packet

Three attachments can add up to the expected page count and still repeat one page while omitting another. Map the actual numbered spans before sending a precise, privacy-conscious follow-up to the records custodian.

1 · Attachment code | first numbered page | last numbered page

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The record-span docket processes Attachment code | first numbered page | last numbered page locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: attachment lengths seemed to prove a complete packet. After: distinct numbered coverage, overlaps and exact missing ranges are separate facts.

2 · Read the record-span docket

Pagination arithmetic only: this does not inspect medical files, certify record completeness or give legal or clinical advice. Ask the medical-records custodian to explain numbering and missing ranges, and a qualified clinician to review clinical completeness.

Paid layer: record-span docket filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked record-span docket run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent record-span docket app calculations after a local convenience signal
print the record-span docket with visible assumptions and its safety boundary
CSV of the displayed pages missing and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the record-span docket, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the record-span docket

Use one stable numbering system supplied by the custodian or created locally for one packet. PDF viewer position, printed page number and attachment-local numbering are not interchangeable. If each attachment starts again at page 1, ask how it should be indexed or build a verified packet index outside this tool before entry. The expected count is a source assertion, not something inferred from the largest entered page. Labels can be anonymous attachment codes, with the code-to-file map kept privately. Spans are inclusive and may overlap. New coverage is attributed in entered order so the duplicate arithmetic is reproducible, while the final union and missing ranges do not depend on row order.

Boundary and sources

Method: Count a numbered page once even if several attachments include it. Each row shows its inclusive length and how much coverage it adds after earlier rows. The docket then merges overlapping and adjacent spans, subtracts their union from the expected count, and lists absent intervals. Repeated page appearances are reported separately from missing numbers.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this record-span docket for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a record-span docket. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Attachment code | first numbered page | last numbered page; the setting is Expected numbered page count for this one packet. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.