# Choosing PDF remediation: honest guides for school districts

Canonical page: https://districtproof.io/compare

Compare the workflow, cost and evidence behind a PDF remediation offer. These three guides help district teams ask specific questions, recognize useful automation and purchase the review coverage they need.

## Start with the decision in front of your district

A remediation quote can describe very different work: running a tool, checking a sample, or having a person review every delivered file. Before comparing prices, identify which output and review coverage your district is buying. These three guides address separate decisions, so you can begin with the question holding up your project.

Comparison guide

## [Is automated PDF remediation enough for ADA Title II?](https://districtproof.io/compare/automated-vs-human-pdf-remediation)

Compare automated processing, sampled review and human-verified PDF remediation, with district examples, scope questions and primary sources.

[Read the guide ↗](https://districtproof.io/compare/automated-vs-human-pdf-remediation)

Comparison guide

## [How much does PDF remediation cost for a school district in 2026?](https://districtproof.io/compare/cost-of-pdf-remediation)

Understand PDF remediation price drivers, published rates, a clearly hypothetical triage example, purchasing questions and the costs to confirm.

[Read the guide ↗](https://districtproof.io/compare/cost-of-pdf-remediation)

Comparison guide

## [How should a school district evaluate a PDF remediation vendor?](https://districtproof.io/compare/how-to-evaluate-pdf-remediation-vendor)

Use twelve practical vendor questions, DistrictProof’s factual answers, primary sources and a printable tagged PDF purchasing checklist.

[Read the guide ↗](https://districtproof.io/compare/how-to-evaluate-pdf-remediation-vendor)

## What changes between the three approaches?

Use the same document sample and intended tasks when comparing providers. The labels below describe review coverage to confirm in an agreement; a product name alone does not tell you which files a person will check. An automated processing service may offer additional review, so ask what its particular quote includes.

| Ask about | Automated processing | Processing with sampled review | Human-verified delivery |
| --- | --- | --- | --- |
| Returned output | A processed PDF or an alternative format; inspect what actually changed | Processed files plus findings for the selected sample | Agreed remediated files plus a record of the human review |
| Human coverage | Confirm whether any human review is included | Named pages, files and tasks within the sample | Every delivered file, with the agreed methods and coverage recorded |
| Tables, forms and scans | Inspect header meaning, field behavior, OCR accuracy and reading sequence | Check whether difficult document types are represented in the sample | Confirm those tasks are included in the file-by-file review |
| Evidence to request | Changed output and supported tool results | Sample selection, reviewed versions, tasks and remaining findings | File manifest, versions, methods, review dates and open actions |
| Question before acceptance | What has been verified beyond the processing step? | What happens when the sample reveals a recurring failure? | How are corrections and the published version checked? |

A sample is useful for identifying patterns and estimating work. It does not establish the behavior of the files outside that sample. A tool result, a human review and verification of the published version answer different questions; ask the provider to identify each one in the handoff.

## Choose a guide by the work you need to do

### Technology and accessibility teams: examine the output

Start with [automated versus human PDF remediation](https://districtproof.io/compare/automated-vs-human-pdf-remediation) if you already use a tool or need to decide what to add after processing. The guide walks through budgets, fillable forms, newsletters and image descriptions. Use those examples to choose meaningful review tasks, rather than relying on a single scanner result.

### Business offices and project owners: define the budget

Use the [cost guide](https://districtproof.io/compare/cost-of-pdf-remediation) to separate page quantity, complexity, review coverage and turnaround. It explains the published DistrictProof rates and a clearly hypothetical triage example. Carry the final production list, package allowance, annual Care total and retained district work into your budget discussion; headline rates alone leave those decisions unresolved.

### Purchasing teams: compare written commitments

Use the [vendor evaluation guide](https://districtproof.io/compare/how-to-evaluate-pdf-remediation-vendor) when gathering proposals or preparing a purchasing record. Its twelve questions cover testing, evidence, corrections, intake, data handling and the contracting entity. The downloadable checklist helps you record which answers are backed by a proposal clause, a sample deliverable or a named process.

## Compare quotes using one shared sample

Choose a short notice, a table-heavy report, an active form and a document assembled from several sources. Keep the versions and page counts fixed for every provider. Ask each one to describe the output it would return, the tasks a person would test, and the findings your team would receive. Include the editable source where it is available and appropriate to share.

Then record what your district still owns: approving content meaning, deciding archive or removal actions, providing descriptions, publishing returned files and keeping replacements connected to their review record. Compare the total price and delivery calendar after those responsibilities are clear. A quote that leaves substantial work with staff should make that work visible.

For example, if a processed form still has unnamed controls, ask who repairs the labels, who checks keyboard completion, whether that work is in the quote, and what evidence identifies the corrected version. That conversation is more useful than asking whether the service includes a generic accessibility check.

## Leave the comparison with a usable handoff

Your purchasing record should connect the proposal, agreed file list, accepted sample, delivery milestones and review method. Name the person who approves the content and the person who posts the final files. Define the correction period and what happens when a source changes or a replacement is exported.

Use the [sample evidence report](https://districtproof.io/resources/sample-evidence-report) to discuss the record you expect, then confirm it in the agreement. The [quality process](https://districtproof.io/how-we-work/quality) explains how technical checks, human review and publication verification remain identifiable. For vendor onboarding and district purchasing documents, see [procurement](https://districtproof.io/procurement).

If the size of the backlog is still unclear, begin with the [free Backlog Report](https://districtproof.io/backlog-report). If you already have processed files, [send 25 auto-fixed pages for a sample review](https://districtproof.io/contact?topic=sample-review). Both are starting points for defining the work; the final production scope and price are confirmed separately.