Athletic Archive Digitization Acceptance Criteria Checklist: Verify Images, Metadata, and Deliverables

A recognition kiosk in a school trophy case draws directly from the digitized archive — acceptance criteria verification is what ensures every image, record, and label in that archive meets the standards the display requires

What Athletic Archive Digitization Acceptance Criteria Covers

An acceptance criteria checklist answers one question for each deliverable: does this meet the documented standard, or does it need to be corrected? Every item on the checklist has a binary outcome — pass or fail — so the acceptance decision is based on evidence rather than judgment.

The six areas covered by a complete athletic archive digitization acceptance criteria checklist are:

1. Scan quality — resolution, color accuracy, orientation, and absence of visible artifacts
2. Filename conventions — naming structure, character restrictions, uniqueness, and sortability
3. Metadata completeness — required fields present, correctly formatted, and populated with verified values
4. File counts — delivered count matches expected count, with no missing items and no unexplained extras
5. Rights and copyright documentation — rights status documented for every file, usage restrictions noted
6. Delivery media integrity — delivery package is intact, format matches specification, and checksums verify

Each area maps to a set of pass-fail criteria. The checklist runs through all six areas in order before a final acceptance decision is recorded. Items that fail are documented and returned to the vendor for correction before the project is approved — partial acceptance with an open correction list is a common and legitimate outcome when most deliverables pass but a subset requires remediation.

Building a digital history archive from athletic records is a long-term investment; the acceptance criteria checklist is the quality gate that determines whether the initial digitization project produces an archive that functions correctly across all the systems that will use it.

Master Pass-Fail Summary

The table below provides a single-page summary of all acceptance criteria organized by area. Use this as a cover sheet for your acceptance review — check each item pass or fail, note the count of failing items in the right column, and attach the detailed area checklists as supporting documentation.

Any “Fail” checkmark in this summary triggers the corresponding area’s detailed checklist and opens a correction item to be tracked until resolved. The project is not approved until every correction item is resolved or formally accepted as-is with documented rationale.

Area 1: Scan Quality Verification

Scan quality is the first and most foundational acceptance area because a low-quality scan cannot be improved after the fact without rescanning the original source material. If the original — a 1978 yearbook, a fragile game program, a faded photograph — is no longer accessible after the vendor returns it, a low-resolution or artifact-laden scan becomes the permanent record.

Minimum Resolution Standards

Resolution is specified in dots per inch (DPI) and measured against the intended use of the file, not the display size on a monitor.

How to verify resolution: Open a representative sample of delivered files in an image editing application (Adobe Photoshop, GIMP, or Preview on macOS) and check the image size and resolution settings without resampling. The DPI value reported in the file’s image properties reflects the actual scan resolution. A file that reports 72 DPI has been saved for screen display, not archival use, regardless of its pixel dimensions.

Common failure mode: Vendors sometimes deliver files that are large in pixel dimensions (e.g., 3000 × 4000 pixels) but saved at 72 DPI. The pixel count may seem adequate, but the metadata tag determines how the file behaves in professional publishing, large-format printing, and archival software. Verify both the pixel dimensions and the DPI setting.

Artifact and Quality Inspection

Artifact failures are among the most common scan quality issues in athletic archive digitization projects, particularly for materials that include halftone printing (game programs, newsletters) or materials scanned from bound volumes where the scanner bed cannot make full contact with the source page. These failures require vendor rescanning — there is no post-processing correction that restores missing detail or removes a deep moiré pattern from an archival master.

Schools preparing archives for alumni welcome area displays need photographic and program scans that render clearly at large display sizes — a scan that looks acceptable at thumbnail size often reveals artifacts when enlarged for a lobby or hallway display.

Recognition displays in school hallways and lobbies draw from digitized archives — scan quality acceptance criteria determine whether those images render correctly at the sizes and resolutions the display system requires

Area 2: Filename Convention Verification

Filenames are the addressing system for your archive. A filename that contains spaces breaks URL-based access in web-facing systems. A filename that uses inconsistent separators prevents automated sorting. A filename that lacks the sport and season context requires a human to open every file to understand what it contains. A filename that duplicates an existing file in the archive overwrites the original on import.

Approved Character Set and Naming Structure

The safest filename convention for athletic archive files uses:

• Lowercase letters only (a–z)
• Numerals (0–9)
• Hyphens as word separators (-)
• No spaces
• No special characters (@, #, &, %, (, ), ', ", commas, periods except the format extension)
• No underscores as primary separators (underscores are sometimes reserved for field separators in structured naming conventions)

A recommended filename structure for athletic archive deliverables:

[sport]-[level]-[season]-[asset-type]-[sequence-number].[extension]

Example: basketball-varsity-boys-2019-20-team-photo-001.tif

Why zero-padding matters: A sequence number of 1, 2, 10, 11 sorts as 1, 10, 11, 2 in alphabetical order — the standard sort used by most file systems. Zero-padding to 001, 002, 010, 011 produces the correct chronological sort.

How to run a bulk filename check: Most file systems allow you to list all filenames to a text file (dir /b on Windows; ls -1 on macOS/Linux). Paste that list into a spreadsheet and use formulas or a text editor’s find function to flag any row containing a space, uppercase letter, or prohibited character. For large deliveries (thousands of files), a short script that checks filenames against the pattern is more reliable than manual inspection.

Area 3: Metadata Completeness Verification

Metadata is what makes a digitized archive findable and usable. A scanned team photo with no sport, season, or athlete information is a JPEG file. The same photo with complete metadata is a searchable record that a student in 2040 can locate by filtering on “Boys Varsity Basketball, 2019-20.” Metadata completeness verification confirms that the vendor has populated every required field with verified, correctly formatted content — not left fields blank or filled them with placeholder values.

Required Metadata Fields for Athletic Archive Records

The fields listed below represent the minimum required metadata for athletic archive digitization projects. Your project contract should specify these fields explicitly; acceptance criteria verify that every delivered record includes them.

Checking for placeholder values: Search every metadata field for strings including “TBD,” “Unknown,” “N/A,” “To be confirmed,” “0,” and empty cells. Each instance is a failure that requires vendor follow-up to supply the correct value. Accepting a record with blank metadata fields means accepting a record that will not surface in filtered searches — the most common way school staff and alumni look for specific content.

Date format verification: Export all date field values to a spreadsheet column and apply a data validation rule requiring the YYYY-MM-DD format. Any value that fails the validation is a format inconsistency. Date format inconsistency is one of the most frequently failed criteria in athletic archive digitization deliveries because vendors often use the format native to their scanning software, which may differ from the format specified in the project contract.

Thorough metadata is what separates a searchable archive from a folder of files. Schools building recognition programs that serve alumni, donors, and award presentations need to locate specific athlete records quickly — a hall-of-fame presenter preparing remarks for an induction ceremony should not need to manually browse folders to find a championship photo from 1994.

Every athlete portrait card on a hall-of-fame touchscreen display requires a complete metadata record to display correctly — acceptance criteria verification confirms that the archive contains those records before the display is loaded

Area 4: File Count Verification

File count verification answers a simple question: did the vendor deliver everything they were supposed to deliver, and nothing they were not supposed to deliver? The expected file count comes from the source manifest — the inventory of physical materials the school handed over to the vendor for digitization. The actual delivered count is the number of files in the delivery package. These two numbers should match exactly.

Building and Using the Source Manifest

The source manifest should be created before any materials leave the school’s possession. It lists every item given to the vendor: every yearbook page, photograph, game program, certificate, and roster included in the digitization scope. Each item on the manifest gets a sequential ID, a brief description, and an expected file count (some physical items, like a multi-page program, produce multiple digital files).

If your school did not create a source manifest before sending materials to the vendor, request the vendor’s intake log — most vendors record what they receive for their own tracking purposes. Reconcile the vendor’s intake log against what your school sent before beginning file count verification.

Common reasons for count discrepancies:

• Missing files: Vendor’s scanner skipped a page in a multi-page document, missed a photo in a group, or delivered one file for a two-sided item that should be two files.
• Extras from vendor processing: Vendor delivered both archival master and display derivative, when the contract specified only the archival master — or included a metadata export file that was not on the expected list.
• Scope changes not reflected in the manifest: Materials were added or removed from the scope after the original manifest was created and the manifest was not updated.
• Naming collisions resolved by renaming: Vendor encountered two files with the same name and renamed one, creating a filename not on the expected list.

Document every discrepancy before contacting the vendor. A discrepancy list with item IDs and expected versus actual counts resolves faster than a general “some files are missing” communication.

Schools that include athletic archive digitization in a broader dedication ceremony or facility renovation often have a hard deadline tied to the event — catching count discrepancies during acceptance, while the vendor still has access to source materials, is significantly less disruptive than discovering them after the event.

Area 5: Rights and Copyright Documentation

Rights and copyright documentation determines what your school can do with the digitized materials after acceptance. A scanned photograph may be owned by the school, the photographer who took it, a local newspaper that published it, or a third party — and the answer affects whether the image can appear on a publicly accessible website, in a digital yearbook, in a donor newsletter, or on a lobby touchscreen.

Acceptance criteria for rights documentation do not require legal conclusions — they require that the rights status of every file is documented, clearly labeled, and that any files with restrictions are identified before they enter the archive and are used in programs without review.

Important: Rights determinations for specific materials — particularly photographs taken by third parties, materials from news publications, and records involving student likeness from specific eras — vary by jurisdiction and factual circumstances. Schools should establish their approach to rights documentation in consultation with their legal counsel before beginning a digitization project. The acceptance criteria checklist verifies that the documentation exists, not that the legal conclusions in that documentation are correct.

Rights Status Vocabulary

Rights documentation gaps discovered after acceptance are more difficult to resolve than gaps caught during acceptance. Once files are loaded into a recognition platform and used in a published display — a touchscreen in the lobby, a student honors display, or a printed donor acknowledgment — retroactive rights review creates the risk of having to remove or replace materials already visible to the public. The acceptance checklist is the point where these gaps are identified and resolved before that exposure occurs.

Every athlete image displayed on a public-facing touchscreen requires a rights status review before acceptance — a checklist that catches undocumented rights status prevents public display of materials that have not been cleared for use

Area 6: Delivery Media Verification

Delivery media verification confirms that the physical or digital package the vendor delivers can be fully opened, is formatted as specified, and contains files whose checksums match the values in the accompanying manifest. A delivery that cannot be opened — a corrupted hard drive, a broken archive file, an expired cloud share link — fails acceptance regardless of the quality of the files it may contain.

Delivery Format Verification

Checksum Verification

Every delivery should include a checksum manifest — a file that pairs each delivered filename with a hash value (typically SHA-256) generated at the time of delivery. Checksum verification confirms that each file arrived intact and was not altered in transit or during the transfer from vendor to school.

For schools that are building their first digitized archive or working with a vendor for the first time, delivery media verification may be the least familiar part of the acceptance process. A brief walkthrough with your school’s IT coordinator before acceptance day — confirming what tools are available for checksum verification and how to connect and read the delivery medium — prevents delays caused by technical setup on the day of delivery.

Who Runs This Checklist — Role Assignments

A complete acceptance review involves staff from several departments because the six verification areas require different expertise. The table below maps each area to the roles best positioned to complete it.

The acceptance review should be scheduled as a structured event — not a quick look at the delivery on the day it arrives. Allow two to four hours for the initial pass-through, plus additional time to run automated checksum verification on the full delivery set. For large digitization projects (hundreds or thousands of files), plan for a multi-day review before issuing a final acceptance decision.

Connecting an Accepted Archive to Recognition Programs

Passing acceptance criteria is the beginning, not the end, of a digitization project’s value. An accepted archive — with verified images, complete metadata, clean filenames, accurate file counts, documented rights, and confirmed integrity — can be connected to recognition programs that give the archived materials ongoing visibility and meaning.

Hall-of-fame and recognition displays. A touchscreen display or wall of honor in your school’s lobby or athletic corridor draws from the archive files your team just accepted. The scan quality criteria ensure images render correctly at display size. The metadata criteria ensure athlete names, seasons, and awards display accurately. The rights criteria ensure no image appears on a public display without clearance. Schools looking to expand their athletic corridor and display programs find that an accepted archive dramatically reduces the time needed to launch new content.

Donor and advancement programs. Development staff use digitized athletic history for campaign materials, naming-rights acknowledgments, and donor stewardship. An accepted archive with documented rights status eliminates the need for per-image rights review every time an image is requested for advancement use.

Digital yearbooks and retrospective publications. A digitized archive with complete metadata can be searched and filtered to identify content for specific publication projects — all women’s sports records from a specific decade, every championship team photo, every scholar-athlete award recipient. Schools building graduation ceremony programming and retrospective displays that draw on decades of athletic history need an accepted archive that is fully searchable.

Alumni engagement. Former athletes, coaches, and students who interact with a recognition display or digital yearbook expect to find accurate, complete records. An accepted archive is the foundation that makes those interactions trustworthy. Schools building their broader athletic history as a complement to recognition programs — connecting archived records to active alumni recognition channels — benefit from the metadata completeness that acceptance criteria require.

Facility events and ceremonies. When schools host athletic recognition programs, hall-of-fame induction ceremonies, or facility dedication events, materials from the accepted archive appear on screens, in printed programs, and in oral histories. The acceptance criteria that caught low-resolution scans and missing metadata before delivery are the invisible quality controls that make those materials display-ready on the day of the event.

A functional, trusted hall-of-fame touchscreen display is the downstream outcome of a rigorous acceptance review — every record that a visitor finds and trusts passed the criteria in this checklist before the display went live

Frequently Asked Questions

Q: Does our digitization contract need to specify acceptance criteria before the project starts?

Acceptance criteria should be established and agreed upon in the project contract before the vendor begins work. Criteria that are introduced at delivery — when the vendor has already completed scanning using different assumptions — are difficult to enforce and create disputes that delay the project. The practical approach is to include the scan resolution minimums, filename convention, required metadata fields, rights documentation requirements, and delivery format specification as appendices to the contract. The vendor agrees to these standards at the time of contract signature.

Q: What happens when some files pass and others fail?

Partial acceptance is a common and legitimate outcome of large digitization projects. Document every failing item by ID and the specific criteria it failed. Issue a correction list to the vendor with a reasonable timeline for remediation. Rescan or corrected files return for a second acceptance review against the same criteria before the failing items are marked passed. Avoid issuing full project approval until all correction items are resolved or formally accepted as-is with documented rationale.

Q: Our vendor delivered files on a hard drive but did not include a checksum manifest. Can we still accept the delivery?

You can run acceptance without a vendor-provided checksum manifest, but you should generate your own checksums for every delivered file immediately upon receipt and treat your self-generated manifest as the authoritative baseline going forward. Going forward, specify checksum manifest delivery as a contract requirement. A delivery without checksums cannot be verified for transit integrity — you are accepting on the assumption that no corruption occurred, which is an unverifiable assumption for archival materials.

Q: Do we need to verify rights status for materials the school already owns?

Yes. “The school owns this” is a conclusion that requires verification, not an assumption. School-created materials — produced by school staff in the course of employment, using school resources, in the school’s name — are generally owned by the school, but the specific circumstances matter. Photographs taken by a volunteer parent at a school event, game programs designed by a local print shop, or images sourced from a third-party stock library and included in a yearbook all have different rights implications regardless of whether the school paid for them. Documenting rights status for school-owned materials is straightforward; the documentation confirms the assumption and protects against future disputes. Your school’s legal counsel can help establish the framework for making these determinations.

Q: How do we handle metadata for items where the historical record is genuinely incomplete — we do not know the season or the athlete’s full name?

Document what is known and flag what is unknown explicitly. A metadata record that reads “Season: 1968-69 (estimated — source material undated)” is significantly more useful than a blank field or a placeholder. Estimated values should be marked as estimates; unknown values should use a flag value that your archive platform can filter on (such as “Unknown — Pending Research”) rather than a blank that is indistinguishable from a field that was never filled. Blanks in required fields are acceptance failures; documented unknowns with appropriate flags are acceptable if your acceptance criteria explicitly permit them with the flag convention.

Q: How often should we run acceptance criteria checks after the initial delivery?

The formal acceptance criteria checklist runs once per delivery — at handoff from vendor to school. After acceptance, ongoing archive integrity is maintained through periodic checksum verification (monthly to annually depending on collection activity), lightweight pre-publication quality checks before loading content into any new display or publication, and a field-level metadata audit before each major recognition event or hall-of-fame cycle. Consulting a broader digital history archive management approach for your ongoing archive governance helps establish how acceptance criteria connect to the long-term preservation practices your school will need to sustain the archive after the initial digitization project is complete.

Q: Can we use this checklist for donations of digital files — photos a community photographer submits electronically?

Yes, with modifications. Donated digital files do not require scan quality verification (they were not scanned), but they should be verified for file format, resolution, filename convention, metadata completeness, rights documentation, and checksum integrity. A simplified ingest checklist drawn from Areas 2, 3, 5, and 6 of this checklist applies to digital donations. The key addition for donations is provenance documentation — who submitted the file, when, and under what rights agreement — which is more critical for community submissions than for vendor deliveries.

An athletic honor wall in a school hallway represents years of athletic history — acceptance criteria verification is the quality gate that ensures every record behind those panels is accurate, complete, and cleared for public display