EDUKATE SINGAPORE · GOLD STANDARD REFERENCE PROGRAM · VOLUME 22
Preserve the identity, meaning and history that allow records to support trustworthy decisions.
Choose a reading route, consult the chapter index, or begin with Chapter 1.
Full chapter index · Practical exercise · Reference-programme reading sequence
A record is useful because someone can make a better decision from it. A full database can still leave that person uncertain about which case it describes, whether it is current, what its status means or who changed it. Information integrity concerns preserving the identity, meaning and trustworthy history needed for the intended use.
This volume follows a record from creation through transfer, correction, recovery and review. It applies the Gold Standard's existing requirements, especially evidence, handoffs, controlled execution and continuity. It is not a technical security specification or a statement of legal compliance. Local owners must establish the actual access, retention and technical controls appropriate to their work.
The worked example is a fictional community equipment desk that records reservations, issues, returns and unresolved discrepancies. The case is deliberately ordinary: dependable information management matters long before a system becomes large or technically sophisticated. A spreadsheet, paper register or application can be assessed through the same underlying questions.
Chapter index
Chapters 1–2: Define and identify
Chapters 3–4: Preserve meaning
Chapters 5–6: Correct and validate
Chapters 7–8: Transfer and recover
Chapters 9–10: Trace and practise
CHAPTER 1 OF 10 · Define and identify
1. Define the decision before designing the record
Ask what the next responsible person needs to decide. The equipment custodian needs to know whether a particular kit can be issued to a particular reservation. The reviewer needs to understand why it was released. The manager needs to know whether repeated discrepancies affect the next commitment. These uses overlap, but they are not identical.
List the facts needed for each decision and where those facts come from. A field should not be collected merely because it might be interesting later. Equally, a record that omits the criterion version may make a historical decision impossible to interpret. The appropriate detail depends on the importance and consequences of the decision.
Distinguish a working instruction, a case record and a summary measure. An instruction says what should happen. A case record documents what happened. A summary combines selected records according to a definition. Treating any one of these as a substitute for the others can produce a convincing account with no traceable basis.
Design entry: For each record, state its purpose, users, decision, source, owner and necessary review period. Identify the fields whose absence would prevent the decision. This gives later validation and access choices a clear reason.
CHAPTER 2 OF 10 · Define and identify
2. Preserve identity across people and systems
A case identifier should keep the same case recognisable as it moves. Names alone may be ambiguous, and a position in a spreadsheet can change when rows are sorted. Choose identifiers and matching checks appropriate to the work, then verify that transfers preserve the relationship between the identifier and the thing it represents.
The equipment desk uses a reservation identity and a kit identity. They answer different questions. A reservation may be moved to another kit, but that change should not erase the history of the original allocation. A kit may serve many reservations over time without those reservations becoming one case.
When duplicate records are suspected, investigate before merging them. Two similar entries may describe separate events. Two differently named entries may describe the same case. Record the basis for a merge or separation and preserve any information needed to understand earlier actions.
Identity check: Choose one live reservation and follow it through the booking list, physical kit, issue record and return queue. Then repeat with a changed allocation. The test succeeds when the same case remains understandable through the change, not merely when all systems display a matching name.
Define the meaning of important fields, including units, timing and permitted values. “Completed” may mean packed, issued, received or returned. A date may refer to the event, the entry or the later correction. If these meanings are mixed, even accurately copied values can support the wrong decision.
The equipment desk distinguishes Reserved, Prepared, Issued, Returned and Reconciled. These are example local workflow states, not new Gold Standard assessment findings. Each state has an entry condition and an owner. A returned kit with missing contents is not yet reconciled merely because it has arrived at the desk.
| Information element | Definition to preserve | Ambiguity to prevent |
|---|---|---|
| Event time | When the described event occurred, with necessary time context | Confusing late entry with late performance |
| Record time | When information was entered or amended | Treating an amendment as the original observation |
| Status | The decision condition represented by the label | Using one label for several unfinished stages |
| Quantity | The item and unit being counted | Combining kits, components and reservations |
| Missing value | Why information is absent or unavailable | Treating a blank as zero, success or not applicable |
Test the definitions with a difficult case. Ask two users to classify it independently, then resolve differences in interpretation. A short field guide can prevent repeated arguments and make later measurement more reliable.
An observation describes what was seen, measured or reported. An interpretation explains what the observation may mean. A decision states what someone will do. A useful record connects these layers without presenting them as the same fact.
For example, “component missing from the box at return check” is an observation. “The participant lost it” is a possible explanation that the observation alone does not prove. The component may have been absent at issue or moved during handling. Record the immediate decision to isolate the kit separately from the investigation of cause.
Preserve the source and its limitations. A direct check, a participant's account and a copied note each have a different evidential position. Several reports copied from the same original are not necessarily independent confirmation. A summary should retain enough connection to the underlying cases for a reviewer to examine that dependence.
Evidence chain: Link requirement, observation, interpretation, decision and follow-up. The Evidence, Claims and Verification volume explains the wider method. Recording a confident conclusion cannot repair an absent observation.
CHAPTER 5 OF 10 · Correct and validate
5. Control changes without making correction impossible
People need to correct mistakes. Integrity does not mean pretending a record has never changed; it means preserving the history necessary to understand and trust the change. Decide who can amend important fields, what basis is required and how affected users learn that the earlier value should no longer guide their work.
The equipment desk discovers that a return was assigned to the wrong reservation. The correction records the affected identities, the reason, the responsible person and the evidence supporting reassignment. It also identifies decisions that used the wrong association, such as an unresolved-return reminder, so they can be reconsidered.
Distinguish correcting an entry from changing the underlying criterion. If the acceptance rule changes, old records should not be edited to make them appear compliant with the new rule. Preserve which criterion applied and, where needed, perform a separately identified reassessment.
Correction record: Keep the original value or an appropriate trace of it, the replacement, reason, authority and downstream action. The exact mechanism can vary with the setting. The test is whether an authorised reviewer can reconstruct the material change without relying solely on the editor's memory.
CHAPTER 6 OF 10 · Correct and validate
6. Validate information at the point where it can fail
A validation check should address a plausible error and lead to a useful response. Some checks examine format, such as whether an identifier is present. Others examine relationships, such as whether an issued kit is already assigned elsewhere. A record can pass a format check while describing the wrong real-world situation.
At the equipment desk, the issue decision compares the reservation, physical kit identity and readiness status. A later review reconciles issues and returns. These checks act at different points and answer different questions. Removing the first because the second exists may allow an avoidable wrong issue to reach the participant.
| Check type | Example question | Limit |
|---|---|---|
| Presence and format | Is the required identity recorded in the accepted form? | A valid-looking identity can still be wrong |
| Internal consistency | Can this state follow the recorded earlier state? | Consistency does not prove the events occurred |
| Cross-record reconciliation | Do issue and return records refer to the same kit and case? | Two systems can share the same copied error |
| Direct comparison | Does the record match the observed kit and event? | Coverage is limited to the conditions examined |
Record rejected or uncertain entries in a controlled route. Silently discarding them can improve apparent data quality while hiding work that still needs a decision.
CHAPTER 7 OF 10 · Transfer and recover
7. Preserve meaning during transfer and transformation
Copying data is not always copying meaning. A receiving system may use a different status vocabulary, date convention or treatment of empty values. A report may combine rows, filter exceptions or calculate a measure. Each transformation needs enough explanation for its output to be interpreted correctly.
Before moving the equipment register to a new application, map important fields and states. Test ordinary cases, unresolved discrepancies, corrected entries and changed allocations. Compare the resulting decisions, not only the number of rows transferred. Equal record counts do not prove that the relationships survived.
Where a value is derived, retain its definition and the source population. A percentage of reconciled returns needs the cases included, the period and the treatment of cases still open. If the calculation changes, explain the effect on comparisons with earlier results.
Transfer record: Identify the source version, destination, transformation rules, excluded records, reconciliation results and unresolved exceptions. Use a controlled cutover so users know which record governs current work. The Change, Scaling and Renewal volume develops the transition decision.
CHAPTER 8 OF 10 · Transfer and recover
8. Make access and recovery serve the operating purpose
Information should be available to the people who need it and protected from uses that are not authorised. Assign access by actual responsibility, including substitutes and reviewers. A shared account that makes every amendment indistinguishable can weaken accountability; an inaccessible record can stop legitimate work. The design needs to address both problems.
Plan for unavailability before relying on a record system. The fallback may be a controlled temporary register with limited operations. Specify how new entries receive identities, who can act from the fallback and how differences are reconciled when the usual system returns.
Test recovery by reconstructing a meaningful case, not merely by confirming that a file opens. Can the desk identify current reservations, unresolved returns, the applicable criteria and changes made during the interruption? A restored file that omits the most recent accepted commitments may require a restricted operating decision.
Recovery check: Record what was restored, the latest trustworthy point, missing or conflicting work and the basis for resuming. Choose technical safeguards and retention arrangements with appropriate expertise for the actual system; this chapter does not prescribe a complete security architecture.
CHAPTER 9 OF 10 · Trace and practise
9. Follow a damaged record into its consequences
When an information problem is found, examine which decisions relied on it. Correcting the source may not repair a report already issued, an allocation already made or a message already sent. Trace the affected uses and assign the necessary reconsideration or communication.
The equipment desk finds that “Returned” entries were counted as “Reconciled” in a performance report. The correction should distinguish the underlying state error from the report's interpretation. Recalculate the affected measure, identify any capacity decision based on it and state the remaining limitations. Do not simply replace the number without explaining a material change in meaning.
Preserve proportionality. Not every spelling correction requires a full investigation. The depth of response should reflect the effect on identity, meaning, authority or outcome. This judgement should itself be explainable, especially when the decision is to take no further action.
Source context: The W3C PROV overview describes provenance through the things, activities and responsible agents involved in producing information. That perspective helps explain why origin and transformation matter. This volume uses a plain-language operating method; it does not claim that the records described implement the PROV technical specifications.
CHAPTER 10 OF 10 · Trace and practise
10. Practise an information-integrity decision
Case: A fictional desk moves fifty reservations into a new application. Both systems show fifty rows, so the migration is declared complete. Later, a custodian finds that an empty return date became today's date and that two corrected allocations display only their original kit identities. No one has yet examined the other unresolved cases.
Pause and decide: What does the equal row count establish? What should be restricted immediately? Which cases should be examined next, and which earlier decisions might need review? Write a scoped conclusion without assuming that every record is wrong or that only the three noticed entries are affected.
Reasoned response: Equal counts establish a limited numerical match, not preserved meaning. The return-date transformation and lost allocation corrections can affect release and reconciliation decisions. Identify the affected data rules, prevent uncertain records from silently authorising work and compare cases exposed to those rules. Preserve a controlled source of truth while the discrepancies are resolved.
A successful repair includes corrected transformation rules, reconciled affected cases, review of decisions already made and evidence that the revised transfer preserves relevant meaning. Connect findings to the applicable requirements, retaining Unknown where coverage remains insufficient. Information integrity is demonstrated when the record can support the right decision through change, not when its fields merely look complete.
Contents · Previous chapter · Continue through the reference program
The Gold Standard reference program · 32 volumes
Begin with the four foundation volumes, then choose the evidence, operating, assessment or study guides that match your task. These reading routes extend the manual without changing its twelve core requirements.
Volumes 1–4 · Foundations
Volumes 5–8 · Evidence and governance
Volumes 9–12 · People and operating systems
Volumes 13–16 · Assurance and assessment
Volumes 17–20 · Workbooks and reference tools
Volumes 21–24 · Advanced applications
Volumes 25–28 · Everyday management controls
Volumes 29–32 · Study and teaching guides
Return to The Gold Standard master hub
Apply the framework to a specialist field
- Education Management — connect the parts of a learning system.
- Learning Assessment — examine what learning evidence can establish.
- Operations Management — follow plans into everyday delivery.
- Business Continuity — examine continuity under disruption.
Edition, sources and interpretation
The definitions, GS-R01 to GS-R12, assessment findings, teaching loops, templates and worked cases are the original editorial synthesis of the eduKate Gold Standard Reference Program. Examples do not report audited organisational results. This volume was prepared on 14 October 2026 and applies programme Edition 1.0, established on 13 October 2026. A future change to requirements should identify the affected edition and preserve the interpretation of earlier evidence.
The working definitions and requirements in this volume are program-specific. For an externally governed task, consult its applicable authoritative vocabulary and technical requirements directly. No numbered clause here is presented as a quotation or reproduction of an external standard.