Scope Map
Creates a structured description of the proposed search universe: question, timeframe, custodians, systems, terminology, exclusions, assumptions, and unresolved issues.
Public Records QCPUBLIC RECORDS SEARCH QUALITY
Better scope.Stronger searches.
Public Records QC develops evidence-linked methods for defining, documenting, and reviewing the scope of complex public-record searches. The objective is to make critical search decisions more visible, reproducible, and ready for informed human review.
THE PROBLEM
More records. More systems. More ways to miss what matters.
As public records accumulate across email, messaging platforms, databases, document repositories, archived systems, and individual custodians, retrospective searches become increasingly complex. The challenge is not simply running a search—it is defining and documenting the right search.
THE SOLUTION
Quality control for search scope.
Public Records QC brings a structured, evidence-linked method to search-scope review. It makes gaps, inconsistencies, assumptions, and unresolved questions visible before the scope reaches human approval.
Better scope supports stronger searches.
WHAT SHAPES A SEARCH
Search terms are only one part of search quality.
Each dimension can affect what a search is capable of finding. Making those decisions explicit creates a record that can be examined, revised, and explained.
- 01Search objective
- 02Date range
- 03Custodian universe
- 04Systems and repositories
- 05Search terminology
- 06Known exclusions
- 07Supporting evidence
- 08Assumptions and uncertainties
- 09Review and revision history
THE FRAMEWORK
A visible chain from search question to review.
Four connected records organize what is proposed, what supports it, what remains uncertain, and how the scope changes over time.
Evidence Trail
Connects material scope decisions to a public source, policy, authorized input, or documented reasoning. Unsupported assumptions remain visible rather than becoming facts.
Quality Review
Examines completeness, internal consistency, traceability, reproducibility, and unresolved uncertainty before the documented scope proceeds to human review.
Change Record
Preserves what changed, why it changed, who authorized the change, and which downstream parts of the proposed scope may be affected.
HYPOTHETICAL WORKED EXAMPLE
One request can contain dozens of scope decisions.
Consider a retrospective request for communications concerning a multiyear public construction project. Before any search begins, the proposed scope may need to address formal and informal project names, relevant departments, employee roles, date ranges, email and document systems, predecessor systems, archived accounts, known exclusions, and unresolved custody questions.
This illustration is hypothetical and does not use agency records or case materials.
- 01Define the question
Record the objective, timeframe, known context, and explicit boundaries of the proposed search.
- 02Map likely coverage
Organize people, roles, systems, terminology, aliases, exclusions, and unresolved locations.
- 03Link evidence and uncertainty
Show what supports each material decision and clearly mark what remains unknown.
- 04Review and preserve changes
Examine consistency and traceability, then record authorized revisions and their effects.
TANGIBLE EXAMPLE
See what a Scope Map can make visible.
This downloadable two-page example turns the framework into a concrete review artifact. It uses a fully fictional municipal project and contains no agency records, case materials, or live search instructions.
Download the Hypothetical Scope MapHYPOTHETICAL SCOPE MAPRiver Crossing Municipal Center Modernization
Example 01 · v0.3Communications and planning records for a fictional municipal modernization project.
Jan 1, 2021 - Dec 31, 2023
Five role-based custodians, with former accounts still under review.
Email, shared drive, project workspace, messaging, and a predecessor system.
Formal name, acronyms, informal names, and an illustrative contractor.
Automated alerts, public newsletters, duplicates, and unrelated facilities work.
Illustrative project page, agenda, organization chart, and project roster.
Archive coverage, former accounts, text messages, aliases, and exclusion approval.
Three versions showing the initial map, terminology review, and coverage questions.
Illustrative only · Not a live request · No agency data
QUALITY-CONTROL PRINCIPLES
A disciplined method needs clear operating principles.
Evidence before assertion
Material scope decisions should be connected to a source, an authorized input, or documented reasoning.
Visible uncertainty
Unknowns remain visible until resolved. They are not silently converted into facts.
Reproducible decisions
A reviewer should be able to understand how the proposed scope was assembled.
Human accountability
The framework organizes information for judgment; it does not replace accountable human decisions.
Controlled change
Revisions should preserve what changed, why it changed, and what else may be affected.
Minimum necessary information
Early analysis should use the least sensitive information needed to examine the scope question.
Clear role boundaries
Methodology remains separate from legal, policy, compliance, and records-management judgment.
RESEARCH & VALIDATION
Progress should be stated with the same precision as the method.
Development status is separated from the company's purpose so visitors can understand both what is being built and what the available evidence can support today.
Conceptual foundation
The problem statement, primary scope dimensions, four-part framework, and quality-control principles have been documented.
Method specification
Decision records, evidence-linking rules, review criteria, change controls, and illustrative use cases are being developed.
Operational evaluation
Usability, reproducibility, workflow fit, and performance measurement require controlled future evaluation.
Outcomes not yet established
No claims are made regarding savings, completeness, accuracy, legal sufficiency, compliance, or operational performance.
ABOUT PUBLIC RECORDS QC
Founded from a quality-control perspective.
Robert Miller founded Public Records QC to apply established quality-control disciplines—documented assumptions, traceable evidence, controlled change, and accountable review—to complex public-record search scope.
The work focuses on making proposed scope decisions, supporting evidence, unresolved questions, and revision history easier to see and evaluate. Public Records QC is privately operated and independent.
Public Records QC is not a government agency, regulator, law firm, records-request service, or endorsement by any public body. The framework does not provide legal advice or replace authorized legal, policy, compliance, or records-management judgment.
CONTACT
Start a professional conversation.
Public Records QC welcomes inquiries from records professionals, researchers, public-sector organizations, legal and compliance teams, and others interested in public-record search quality.
Robert MillerFounder
robertmillerjr@publicrecordsqc.orgInitial inquiries should not include records, case materials, credentials, confidential information, attachments, or system details.