Map Missing Numbered Pages and Overlaps in a Delivered Record Packet — Free
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.
The proof surface
Records-request forms identify who holds a report. This docket works after delivery: it unions inclusive page spans, exposes overlaps, and names absent page numbers under one packet's pagination. It never judges clinical completeness or reads an uploaded medical file.
InputAttachment code | first numbered page | last numbered page; expected numbered page count for this one packet
Rare deviceRecords-request forms identify who holds a report. This docket works after delivery: it unions inclusive page spans, exposes overlaps, and names absent page numbers under one packet's pagination. It never judges clinical completeness or reads an uploaded medical file.
Output artifactAbsent numbers in the expected packet with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Lab packet | 1 | 5; Visit extract | 5 | 10; Appendix | 13 | 16. Expected numbered page count for this one packet = 16. Absent numbers in the expected packet: 2 pages missing. All records are invented.
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.
Why the flat version breaks
Adding attachment lengths without removing overlaps
Pages 1–5 and 5–10 contain eleven page appearances but only ten distinct numbers. A duplicate can offset a missing page in a simple length total. The union count and repeated-appearance count answer different questions; keep both when describing the packet to its custodian.
Bridging an internal hole with one range
A first page of 1 and last page of 10 do not establish that page 6 was delivered. A span means every number between the endpoints was observed. Enter two runs when a hole exists, and retain the source files for checking. The app does not inspect PDFs to confirm your range assertion.
Calling continuous pagination complete medical history
A packet can be numbered 1–16 and still lack a relevant report, patient context or legible content. The tool checks number coverage only. Ask the custodian and clinician about clinical completeness separately; do not turn a zero-page gap into a diagnosis, a legal conclusion or an assurance of disclosure compliance.
How to work the record-span docket
Verify the numbering universe
Confirm whether the expected packet has pages 1 through a stated total with no alternate prefixes. Preserve the custodian's explanation, especially for supplements and intentionally omitted blank pages. This tool has no concept of sections such as A-12 or repeated attachment-local page 1; do not strip those prefixes and silently create a different numbering system.
Enter observed inclusive spans
For each delivered attachment or uninterrupted run, enter its first and last number. Both must be whole numbers from 1 through the expected count, and last cannot precede first. Split an attachment with an internal gap into separate observed runs. A range entry asserts that every number between its endpoints is present, so it must not bridge an unverified hole.
Union spans before counting the gap
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.
Send a narrowly scoped follow-up
Ask the medical-records custodian about the named missing page ranges and any repeated numbers. Include only the packet reference and the minimum necessary attachment codes through an appropriate private channel. Do not describe a pagination gap as proof that a clinical report was withheld. The content, attribution and completeness of the record still need qualified review.
What the record-span docket separates
Question
Before
Inspect this instead
Adding attachment lengths without removing overlaps
Pages 1–5 and 5–10 contain eleven page appearances but only ten distinct numbers. A duplicate can offset a missing page in a simple length total. The union count and repeated-appearance count answer different questions; keep both when describing the packet to its custodian.
Enter observed inclusive spans
Bridging an internal hole with one range
A first page of 1 and last page of 10 do not establish that page 6 was delivered. A span means every number between the endpoints was observed. Enter two runs when a hole exists, and retain the source files for checking. The app does not inspect PDFs to confirm your range assertion.
Union spans before counting the gap
Calling continuous pagination complete medical history
A packet can be numbered 1–16 and still lack a relevant report, patient context or legible content. The tool checks number coverage only. Ask the custodian and clinician about clinical completeness separately; do not turn a zero-page gap into a diagnosis, a legal conclusion or an assurance of disclosure compliance.
Send a narrowly scoped follow-up
This record-span docket replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
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.
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.
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.
Go deeper: the companion app files the same reading as a clerk's docket sheet
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the record-span docket reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The record-span docket answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
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.
What this is built on
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.
Before: attachment lengths seemed to prove a complete packet. After: distinct numbered coverage, overlaps and exact missing ranges are separate facts.
Setting: Expected numbered page count for this one packet = 16. Expected summary: 2 pages missing.
The first attachment covers pages 1–5. The second adds 6–10 and repeats page 5; the appendix covers 13–16. Fourteen distinct pages out of sixteen are represented, leaving 11–12 missing. Summing the three inclusive span lengths gives fifteen appearances, which would hide the duplicate. The docket shows both the union and the exact missing range rather than treating every appearance as a new page.
Sample B — changed plan
Scan A | 1 | 7
Scan B | 9 | 16
Setting: Expected numbered page count for this one packet = 16. Expected summary: 1 pages missing.
Seven pages in Scan A and eight in Scan B cover fifteen distinct numbers. Page 8 is the single gap between them. This boundary is about numbering, not clinical content: Scan B might contain a blank page with a correct number, and the tool cannot inspect it. Keep the delivered files and the custodian's pagination explanation alongside the gap list.
Sample C — boundary convention
Complete-numbered scan | 1 | 16
Setting: Expected numbered page count for this one packet = 16. Expected summary: 0 pages missing.
An inclusive span from 1 through 16 covers all sixteen expected numbers, so the pagination gap is zero. It does not establish that every relevant report was supplied or that the document is readable and correctly attributed. A custodian may number an incomplete packet continuously. A zero therefore supports only the narrow statement that no number is absent from the entered spans.
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.