What review speed should I assume?

Manual redaction throughput varies widely with complexity. Simple documents with light redactions may run 40 to 60 pages per hour, while dense, heavily-PII or privilege-laden material can drop to 10 to 20 pages per hour. Use your team's actual measured rate where possible rather than a generic figure.

How does technology-assisted redaction change the cost?

Tools that auto-detect names, account numbers, and other patterns can multiply throughput several times over, especially on structured PII, with a human only verifying. This tool applies a speed multiplier when technology assistance is enabled, lowering the hours and cost, though a quality-control pass is still needed.

Why does redaction density matter?

Pages with no redactable content still take time to read and clear, but pages requiring many redactions take far longer. Estimating the share of pages that actually need redactions lets the tool weight the effort more realistically than treating every page identically.

Should I include a quality-control pass?

Yes — a second-pass QC review to catch missed or failed redactions is standard, since a single leaked Social Security number or privileged passage can be costly. Add a QC percentage so the estimate reflects the verification effort, not just the first pass.

Is hourly the right model?

Many vendors quote per-page or flat-project rates instead. You can convert: divide your target per-page price into the hourly rate and review speed to check consistency. This tool estimates from hours and rate, which is useful for staffing and comparing against a vendor's per-page quote.

Document Redaction Cost Estimator

Redacting a document set before production is a labour-intensive, high-stakes task — a single missed redaction can leak privileged or personal data. This estimator projects the review hours and cost for a redaction project from page count, redaction density, reviewer speed, and rate, with an optional boost for technology-assisted review.

How it works

The tool weights pages by how many actually need redactions, converts to hours at your review speed, applies a technology multiplier and a QC pass, then costs it:

effective_pages = total × (1 + density_weight × redactable_share)
base_hours      = effective_pages / pages_per_hour
adj_hours       = base_hours / tech_multiplier
total_hours     = adj_hours × (1 + qc_percent)
cost            = total_hours × hourly_rate

Pages with redactions count for more effort than blank ones, technology assistance divides the hours, and the QC pass adds a verification margin on top.

Tips and notes

Use your team’s measured throughput rather than a generic page rate, since complexity swings it dramatically — dense PII or privilege review can be three to five times slower than light redactions. Technology-assisted redaction genuinely cuts hours on structured data, but always keep a human QC pass, because automated detection misses context-dependent privilege and can over- or under-redact. If a vendor quotes per page or a flat project fee, convert it against this hourly estimate to check the two are consistent before signing. The figures here are a budgeting aid; actual effort depends on document quality, native vs image formats, and the redaction standard required.