Record the business need, accountable owner, intended use, asset class, and target date. Confirm this run covers one asset or one tightly governed asset package; split unrelated assets into separate runs so rights, versions, and disposition remain traceable.
1
Image or graphic
2
Video or animation
3
Audio recording
4
Document or publication
5
Web or interactive content
6
Data or software package
Identify source and establish custody
Identify the authoritative source and document how custody will transfer. Prefer an original or highest-quality source; retain transfer evidence and avoid treating an uncontrolled download as authoritative when provenance cannot be established.
1
Internal creator handoff
2
External vendor delivery
3
Licensed repository download
4
Public domain source
5
Legacy system migration
6
Physical media digitization
Document rights and usage restrictions
Establish the legal basis for storing, transforming, publishing, and retaining the asset. Capture the rights holder, license terms, expiry, and restrictions; do not proceed on assumptions when ownership or permitted uses are unclear.
1
Organization owned
2
Licensed for intended use
3
Public domain
4
Permission pending
5
Restricted or disputed
Resolve rights and intake exception
Resolve pending, restricted, or disputed rights before intake approval. Obtain a documented decision from an authorized owner, record any conditions, and stop the run if the asset cannot be lawfully acquired or used.
1
Approved without conditions
2
Approved with conditions
3
Alternative asset required
4
Escalated for legal review
5
Intake declined
Approval: Intake owner
Will be submitted for approval:
Capture asset request and ownership
Will be submitted
Identify source and establish custody
Will be submitted
Document rights and usage restrictions
Will be submitted
Resolve rights and intake exception
Will be submitted
Acquire preservation master file
Acquire the highest-quality authorized master and preserve it unchanged as the source of truth. Keep the original filename, record the format family and source-provided checksum, and never overwrite the master with an edited derivative.
1
Raster image
2
Vector image
3
Video
4
Audio
5
Document
6
Dataset or archive
7
Software or interactive
Validate file safety and integrity
Scan the acquired file, calculate and compare a checksum when one is available, and confirm that the master renders or opens as expected. Quarantine failures, reacquire from the authoritative source, and document any accepted limitation.
1
Passed
2
Failed and quarantined
3
Reacquisition required
4
Approved exception
5
Not technically available
1
Matched source checksum
2
Checksum created at ingest
3
Mismatch under investigation
4
Reacquisition completed
5
Not technically available
1
Passed without issue
2
Passed with minor issue
3
Failed to render
4
Required software unavailable
5
Reacquisition required
Capture descriptive discovery metadata
Describe the asset so users can find and understand it without opening the file. Use the organization's controlled vocabulary where available and distinguish the asset creator from the person performing intake.
Record technical and provenance metadata
Capture the identifiers and technical history needed to authenticate, manage, and reproduce the asset. Record transformations as a chain of events rather than silently replacing prior versions.
Classify sensitivity and access
Classify the asset using the organization's information-handling policy and define the minimum audience needed for the intended use. Flag personal, confidential, contractual, or embargoed content before derivatives or publication are created.
1
Public
2
Internal
3
Confidential
4
Restricted
5
Embargoed
1
General public
2
All employees
3
Named departments
4
Approved partners
5
Named individuals
6
Records or legal staff
1
No personal data identified
2
Consent documented
3
Redaction required
4
Privacy review required
5
Processing prohibited
Produce accessible use derivatives
Create working or delivery copies from the preserved master without altering it. Test the derivative appropriate to its medium, including text alternatives, captions or transcripts, readable structure, and other applicable accessibility requirements; record remediation still needed.
1
Text alternative provided
2
Captions or transcript provided
3
Document structure verified
4
Color and contrast checked
5
Keyboard access checked
6
Flashing content checked
7
Not applicable to asset type
1
Meets applicable requirements
2
Meets requirements with exception
3
Remediation required before release
4
External specialist review required
5
Not applicable with rationale
Approval: Asset steward
Will be submitted for approval:
Acquire preservation master file
Will be submitted
Validate file safety and integrity
Will be submitted
Capture descriptive discovery metadata
Will be submitted
Record technical and provenance metadata
Will be submitted
Classify sensitivity and access
Will be submitted
Produce accessible use derivatives
Will be submitted
Publish the controlled asset version
Release only the approved derivative or controlled master to the authorized destination. Record the exact released version and location, confirm the release date, and preserve a concise change note so later users can distinguish versions.
Configure permissions and recovery controls
Apply least-privilege access to the repository and published location, confirm protected copies exist, and record recovery evidence. Access controls must match the approved classification and should be tested rather than inferred from folder names.
1
Passed
2
Passed with time-limited exception
3
Remediation completed
4
Escalated for security review
5
Release suspended
1
Primary and separate copy verified
2
Primary copy verified only
3
Backup job pending
4
Recovery test failed
5
External archive confirmed
Set retention and review controls
Map the asset to an approved record class and express retention from a clear date or business event. Set the next review and intended disposition; do not use vague 'keep until no longer needed' language when a measurable trigger is available.
1
Asset creation date
2
Asset release date
3
License expiration
4
Asset superseded
5
Project or campaign closure
6
Contract termination
1
Retain and review
2
Archive permanently
3
Transfer to records repository
4
Delete after authorization
5
Return to rights holder
Hand off ownership and close intake
Confirm who owns ongoing stewardship, where the authoritative registry record lives, and how users report problems. Close only when residual risks and follow-up actions are visible to the owner; recurring monitoring and later disposition belong in separate scheduled runs.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.