Activating theRecords & Archivesfunction
A proposed scope in two phases: a foundation by 31 December 2026, then scale-up across Tasama.
Records, archives, and the function that manages them
The function that controls, systematically, how records are created, captured, kept, used and disposed of, so they stay reliable evidence that can be found when needed.
Information created or received in the course of business, and kept as evidence of what was done and as a reference for later.
contracts · project files · decisions & minutes · correspondence · emails · system outputs — on paper or electronic
Records no longer in active use that are still kept: for their approved retention period, or permanently when they hold lasting value.
The record's life cycle, in operation
Tasama's records at a glance: types, subjects and how we describe them
Products and Operations share service names, so their records are told apart by activity: developing a service, or delivering it.
What every record carries: its codes and its level
Identifies the record for its whole life. It stays the same when the record moves or is reclassified.
Business function, activity and record type.
Recorded on its own, apart from the codes.
A code dictionary sets each code's meaning, its limits and who updates it. The unified classification and coding plan in the National Center for Documents and Archives guide is a reference when the scheme is developed.
One library for Tasama's records, and how it is run
- One placeElectronic records and the register of paper originals, linked to source systems
- Search & filtersBy type, subject, owner, project, date and status
- Record cardContent or link, data, versions, paper location, retention rule, audit log
- VersionsThe approved version is kept; later changes become a new version or annex
- Work awaiting actionCompleting data, review, approval, access requests, retention review
- Access controlOn everything shown, search results, titles and previews included
- Permissions by roleGrant, change and revoke access, with the least each role needs
- Classification & codesKeep the scheme and the code dictionary up to date
- Retention rules & holdsLink rules to groups of records; place and lift holds
- DispositionReview eligibility, then carry out approved transfers or destruction, on record
- Data qualityCheck entries are complete and linked to their source and owner
- Audit trailReview what was done, by whom, to which records
Running the repository stays apart from reading what is in it. Backup and restore sit with IT.
Scope, plan and estimated cost
The dates firm up with the volume of records, the platform's readiness and the stakeholders' availability.