Hand off scanned materials without missing pages: register, review and reconcile three PDFs

01Fix the units: one member, three requirements, three files, four pages

The fictional member is 001 / Ada Example / Operations. The required materials are a two-page application, a one-page supporting memo and a one-page receipt. Each requires PDF files no larger than 1 MB. There are no waivers, optional requirements or due dates, keeping the completion denominator at 3. Four pages and three files measure different things from three fulfilled obligations.

After extracting the pack, separate working inputs, expected.json reference answers and actual tool exports. initial-project.json is an empty registration checklist. Do not import the answer file or mistake a reference answer for a real review record.

1. 1
   Read README and keep all three original PDFs and the initial JSON.
2. 2
   Open Material Tracker and use “Restore JSON backup as a new copy” to import initial-project.json.
3. 3
   Check member 001 and the three required rules. Fulfilled obligations should start at 0/3.
4. 4
   Register the files below, inspect the originals, then export the full checklist and backup.

02Choose the operation for this step

• Track required materials: Create a person-by-material checklist and distinguish uploaded files from items that a person has actually reviewed.
• Scan and proofread a batch: Review image-quality flags and OCR fields before saving a reusable recipe; a recipe repeats rules, not human acceptance.
• Classify scanned records: Check extracted naming fields and classification rules on exceptions before exporting an index.
• Organize receipts: Proofread date, merchant, currency and amount, flag possible duplicates and check totals before making a reimbursement package.
• Prepare Word-related outputs: Choose the supported conversion or generation route and inspect headings, tables and editable text in the downloaded result.
• Preview an Office file: Use the preview to inspect the visible content, then use the recipient’s application when exact rendering or editing behavior matters.
• Generate a document batch: Map each field explicitly, test a long name and a missing field, then inspect sample certificates, badges or quotes before the full run.
• Build a screenshot manual: Order the steps, verify arrows point at the intended controls and inspect the exported PDF or HTML for exposed private details.
• Compare document versions: Compare text-based PDFs or text with the selected baseline and confirm each reported change at its page location; scanned text needs recognition first.

03Register all three files: why does completion stay at 0/3?

In Material Tracker, select member 001. Choose each material in turn: register FORM-01.pdf for Application, PROOF-01.pdf for Supporting memo and RECEIPT-01.pdf for Receipt. Valid files should produce awaiting review 3, human accepted 0 and required obligations fulfilled 0/3. Selecting a file does not read or verify its body.

Open the three originals in a PDF viewer and inspect all four pages against the table. Both application pages must refer to the same member. The memo is explicitly a teaching record rather than an identity document. The receipt says USD 18.00. No OCR step occurs in this exercise; searchable text or a confirmation click does not demonstrate recognition accuracy.

After inspecting each material, return to it, check “I opened the original files myself…” and select “Confirm human acceptance”. Once all three are reviewed, expect human accepted 3, waived 0 and fulfilled 3/3. The tracker records the operator’s decision; it does not determine authenticity, signatures or institutional approval.

04Why counting pages or filenames is insufficient

FORM-01.pdf is one application with two distinct pages. A repeated first page cannot replace the second. Check FORM-01 / p1, FORM-01 / p2, PROOF-01 / p1 and RECEIPT-01 / p1 individually. The editor placed these markers inside the PDFs; the checklist does not generate or recognize them.

Actual scanned submissions might arrive as four images or one four-page PDF. Map business materials to files and page numbers, then inspect missing or repeated pages, mismatched members and readability. Retain provenance through OCR, renaming and merging. A count of four does not establish that the application is complete or that names and amounts are correct.

05Verify amount and currency before resolving duplicates

Suppose illustrative receipts A, B and C show USD 18.00, USD 7.50 and EUR 12.00. Reviewed totals should be USD 25.50 and EUR 12.00 separately. Without a defined currency-conversion rule, there is no combined 37.50 expense total. Receipt D with a blank amount is unresolved, not a zero-value receipt that can enter the reviewed count.

A second photograph of A has the same date, currency and amount and can become a duplicate candidate. A separate real purchase can share those values too. Compare images, merchant and receipt reference before excluding a row. The ledger does not delete candidates automatically; including and reviewing both copies of A could inflate the USD total to 43.50.

06Test recovery: replacing the receipt returns completion to 2/3

From 3/3, select Receipt, choose RECEIPT-01.pdf again and confirm metadata replacement. Even with the same filename, acceptance is cleared: expect awaiting review 1, human accepted 2 and fulfilled 2/3. Open the relevant original again and record acceptance only after review. A filename cannot carry an earlier approval forward.

Now replace the receipt registration with wrong-extension.txt. “Extension not allowed” should appear and human acceptance must be unavailable. This checks the filename extension, not whether a PDF is authentic. Restore the correct PDF, confirm replacement, inspect it and accept again. Renaming a text file to.pdf is not a repair.

In a real scanning workflow, changing an image, crop or recognized field also calls for downstream Word and expense-output review, with regeneration where needed. Existing downloads do not update themselves. Keep the original image, reviewed data and generated output as separate versions so the rerun scope is clear.

07Reconcile the handoff: a restorable ledger needs separate originals

Choose “Download full CSV”. Expect three material data rows plus the header. Check member 001, each requirement, filename, accepted status and review time. The missing/correction CSV is not a full ledger: after acceptance it can have no outstanding rows. Page filters do not narrow a full-checklist export.

Download the printable HTML report, open it in a browser and inspect the three records. Download the JSON backup too. JSON restores members, rules, statuses and attachment metadata, not PDF bytes. Deliver the three original PDFs alongside the full CSV, HTML and JSON, with a version note. Successfully importing a backup does not prove that the originals still exist.

MDN’s File API documentation describes browser access to user-selected files; this tool retains registration metadata such as filenames and sizes. For recognition work, continue with OCR proofreading; before generating documents, check a single output with the Word template guide.