Source bounded review protocol · Course systems

Course Reserve Access Recertification Review

A protocol for checking whether each course reserve item still has a valid access basis, a working link, and a documented takedown date at the end of a term.

Education operations diagram for Course Reserve Access Recertification Review

Protocol status

A reserve list is trustworthy when each item shows its access basis, its current link or location, its audience, and its expiry; a list that only shows a title cannot distinguish a licensed copy from an unlicensed scan.

This page describes a review design and its proposed controls. It does not report an executed sample, measured outcomes, or evidence that the controls improved performance.

Review protocol

Planned review sequence

  1. Define the population as every active reserve item for a fixed term, including physical items, licensed electronic copies, open access links, and instructor-provided files. Record the term, the extract date, the courses, and the count.
  2. List the fields required for each item
  3. Name the source for the access basis. A library catalog record supports ownership; a license record supports concurrent access; a permission letter supports a specific use. A file in a shared drive does not establish permission by itself.
  4. Sample across formats, course sizes, and request channels. Include items added late, items with a personal copy, and items that were renewed from a prior term.
  5. Classify exceptions as missing access basis, expired permission, broken link, wrong edition, over-broad audience, inaccessible file, missing loan rule, or overdue takedown. Assign an owner and a correction date.
  6. Report the population, sample, exceptions, and limits. Retain the list version, the access evidence, and the takedown log. The protocol does not decide whether a particular use is fair use.

Operational implications

Ownership, licensing, and permission are different access bases.

A working link does not prove that the use is permitted.

Expiry dates belong beside the item, not only in a calendar reminder.

Accessibility is part of readiness, not a separate project.

Takedown should be recorded with a date and a disposition.

The review tests the record, not the legal conclusion.

Limitations

The protocol has not been presented here as a completed empirical study. Its steps and implications require local validation before use.

Sources

  1. Fair use index, U.S. Copyright Office. Access checked
  2. Privacy Framework, National Institute of Standards and Technology. Access checked
  3. Records Management Policy and Guidance, National Archives and Records Administration. Access checked
  4. Section 508 accessibility guidance, U.S. General Services Administration. Access checked

Apply the brief carefully

Map the control to a real workflow

We can help define the preparation lane, accountable owner, evidence requirements, and escalation point without treating a brief as proof.

Discuss your workflow