A records request comes in, and the file lives in a box at an offsite facility. Someone has to pull it and ship it, or get it scanned and sent back as a PDF. That choice repeats itself often in most hybrid records programs, and it’s rarely made with a consistent policy behind it.
This guide lays out scan on demand’s role next to backfile conversion and day-forward scanning, and the contract checklist: turnaround, custody, format, and cost.
“Scan on demand” is a retrieval service. A provider pulls a stored file from storage, scans it, and delivers a digital copy rather than a shipped physical box. That usually happens within a committed window measured in hours, well under the days a physical shipment takes. It’s one of three ways organizations generally approach digitization, alongside backfile conversion of an existing archive and day-forward scanning of newly created documents going into a scanning program. Scan on demand covers a narrower case. It gets one stored paper file to a requester fast, without touching the rest of the archive.
A records team member logs a request through FileBRIDGE, identifying the specific file or box. The provider retrieves the physical item at the storage facility, scans it on-site, and uploads the resulting file to the requester’s portal for secure download, usually as a PDF. Because the request runs through the same system used for inventory visibility and chain-of-custody reporting, the digitization event becomes part of the same audit trail as the physical retrieval.
Some boxes don’t belong in a scan-on-demand queue; others don’t justify a full backfile conversion project. Retrieval frequency decides it.
A useful triage splits records into a few buckets:
Scan on demand sits in the middle of that spectrum. It’s the right fit when retrieval frequency is high enough to matter, but not so constant that paying per-scan stops making financial sense.
Once scan on demand is the right fit for part of an archive, the comparison across vendors or service tiers turns on four practical questions.
Ask for a specific, written turnaround commitment stated in hours or days. Access has, for example, offered turnaround windows as tight as four hours or less under a flat monthly arrangement. Confirm current terms directly with any vendor; they vary by record type. Pair that commitment with proof of barcode-tracked fulfillment, so a missed SLA shows up in the record.
“Chain of custody” is the documented record naming each custodian who held a physical file from pickup through return or destruction. It’s a compliance requirement for regulated or compliance-sensitive record types. Before buying, confirm the provider’s custody-logging method for the retrieval-scan-return cycle, and the quality checks that catch a missed page or a misfiled document before it reaches the requester.
A scanned file can come back as a plain image or as a searchable document. “OCR,” or optical character recognition, adds a machine-readable text layer to a scanned page, so names, dates, and account numbers become searchable text rather than pixels in a page image. Decide upfront on an output format: image-only, or searchable text if someone needs to search inside the document.
There’s no standard per-page rate across the industry. Volume, media type, physical condition, and indexing depth all affect the quoted price for a given project. Ask any vendor to walk through the cost drivers behind their number for a specific archive. A flat per-page figure may not hold once the condition of the records is assessed.
Scan on demand works best as one piece of a larger digitization plan, alongside backfile conversion and day-forward scanning.
Most records programs eventually need both backfile conversion for the existing archive and day-forward scanning for new documents coming in. Many organizations start with day-forward capture to stop the backlog from growing, then phase in backfile work and scan on demand for the records that get requested along the way. A platform approach such as Access Unify lets a records program modernize gradually, without one disruptive conversion event. That phased approach is easier to budget and staff than a single large conversion project.
Digitizing a file doesn’t settle the paper original’s disposition, and skipping that decision is the usual path to maintaining two archives instead of one. Every scan-on-demand request should trigger a retention check: does the original get retained per schedule, or is it now eligible for defensible destruction? Building that decision into the workflow keeps the digital and physical records in sync, instead of deferring it to a later cleanup project.
Before signing, get specific answers to the following:
Scan on demand earns its place when a records program can point to records that get requested often enough to justify per-file digitization. That case gets stronger with a documented SLA, clear custody tracking, and an honest answer on format and cost. Pair it with day-forward scanning, backfile conversion where it pays off, and a retention decision for every digitized original.
Scan on demand digitizes individual files as they’re requested, leaving the rest of the archive in physical storage. Backfile conversion digitizes an existing archive systematically, box by box, regardless of whether any single file has been requested. Most hybrid records programs use both: backfile conversion for records that justify bulk digitization, scan on demand for everything else that still gets occasional retrieval requests.
There’s no industry-wide standard, which is why a written commitment matters more than a general promise of speed. Access has, for example, offered windows as tight as four hours or less for digitized documents under a flat monthly arrangement. Confirm current terms directly with any vendor; they vary by record type. Ask for the specific commitment in writing and ask for barcode-tracked fulfillment behind it, so a missed SLA shows up in the record rather than getting lost.
No. Scan on demand creates a digital copy for delivery. The physical original isn’t automatically retired. The paper file’s disposition after scanning (retained per schedule, returned to storage, or flagged for defensible destruction) is a separate governance decision that should be built into the request workflow.
That depends on the organization’s retention schedule. Some originals stay in storage because the schedule still requires it; others become eligible for destruction once a digital copy satisfies the business need. Digitization should trigger the retention review. Without a retention check, organizations end up maintaining both the physical file and the digital copy indefinitely.
It varies by provider and should be confirmed before the project starts. “OCR,” or optical character recognition, adds a machine-readable text layer to a scanned page so names, dates, and account numbers can be searched as text instead of sitting inside an image. Image-only output is sometimes acceptable, but only if no one on the team needs to search inside the document.
Volume, media type, physical condition, and the depth of indexing required all move the price for a given project. Vendors quote per project instead of publishing a flat per-page rate. Ask any vendor to walk through the cost drivers behind their number for the specific archive in question. A rate that looks competitive on paper can shift once the condition of the records is assessed.
Chain of custody should be tracked continuously from pickup through return or destruction. Requests placed through a system like FileBRIDGE tie the digitization event to the same inventory and audit trail used for physical retrieval, so the documentation exists as part of the normal workflow. Before buying, confirm the documentation’s audit-readiness, beyond an internal log.
Records that get requested often enough to matter, but not so constantly that per-file scanning becomes more expensive than converting the whole set upfront, are the best fit. Dormant boxes with no retrieval activity are usually better left in storage, or indexed first so a decision can be made with real usage data. Records in continuous, active use typically justify a targeted full-digitization project instead.
If you’re weighing scan on demand against a backfile project, or deciding where to draw the line between the two for your archive, a conversation will get you there faster. Request a demo to walk through turnaround commitments, chain-of-custody documentation, and output options for your specific records.
Share