EDUKATE SINGAPORE · GOLD STANDARD REFERENCE PROGRAM · VOLUME 17
Turn the twelve requirements into a local agreement that people can use, test and maintain.
Choose a reading route, consult the chapter index, or begin with Chapter 1.
Full chapter index · Practical exercise · Reference-programme reading sequence
An organisation can agree that work should be dependable and still disagree about what a colleague should do on Monday morning. A useful operating standard closes that distance. It turns a worthwhile promise into conditions, responsibilities, decisions and evidence that people can use together.
This workbook produces a local operating agreement: a controlled description of one piece of work. It applies the existing twelve requirements of the Gold Standard Reference Program. Its worksheets are optional implementation tools, not additional requirements or a substitute for the full Core Requirements and Evidence. Completing a form does not establish conformance.
The worked example is a fictional community workshop that lends reusable learning kits to adult participants. All names, quantities and decision rules are illustrative. Readers should set their own conditions from the work and the consequences involved. The intended output is a usable agreement, a tested example and a clear decision about release.
Chapter index
Chapters 1–2: Define the agreement
Chapters 3–4: Make decisions usable
Chapters 5–6: Prepare connected work
Chapters 7–8: Record and test
Chapters 9–10: Release and practise
Start with a promise that someone can recognise as fulfilled. “Deliver excellent service” is too broad to organise a shift. “Provide the agreed kit at collection, with its contents verified and its return arrangements understood” describes an outcome that can be examined.
Name the beneficiary, the start event, the finish event and the important exclusions. For the fictional workshop, the process starts when a booking is accepted and ends when the returned kit is reconciled or an unresolved item is assigned for follow-up. Equipment repair is a connected process with a separate owner. Leaving repair outside this scope does not remove the obligation to pass a damaged item to that owner.
Write a one-paragraph scope statement before designing a checklist. Ask an operator to identify a real case that fits, a case that does not, and a case near the boundary. If the answers differ, resolve the boundary before adding detail. Otherwise the form will look precise while its population remains uncertain.
Workbook entry: Record the promise, beneficiary, start, finish, exclusions and receiving process for each excluded activity that can affect the promise. Name the person authorised to resolve a disputed boundary.
CHAPTER 2 OF 10 · Define the agreement
2. Separate the requirement from the local method
A programme requirement explains what the management system must achieve. A local criterion explains what acceptable performance means in this setting. A method explains how people intend to achieve it. Evidence shows what happened. Keeping these layers separate makes adaptation possible without quietly weakening the requirement.
For example, GS-R07 concerns handoffs and communication. The kit workshop's local criterion is that the receiving custodian acknowledges responsibility for each unresolved item. The method may be an electronic queue or a signed handover sheet. The evidence is the acknowledgement linked to the item, time and receiving role. Replacing the queue with a sheet changes the method; removing acceptance changes the control.
| Layer | Worked entry | Question to test it |
|---|---|---|
| Programme requirement | GS-R07 Handoffs and communication | Is the full requirement being addressed? |
| Local criterion | Each unresolved item has an accepting custodian | Can two reviewers apply it consistently? |
| Operating method | Outgoing and incoming custodians reconcile the queue | Can people do it during a busy handover? |
| Evidence | Item ID, status, sender, receiver and acceptance time | Can a later reviewer reconstruct responsibility? |
Use the full requirement text when making the connection. A short label is a retrieval aid. It cannot carry every condition in the governing requirement. See Definitions and Reference Vocabulary when the team is using the same word in different ways.
CHAPTER 3 OF 10 · Make decisions usable
3. Write criteria that survive a difficult case
Test each proposed criterion against normal work, an exception and an incomplete record. “Kit ready” might mean that a box is present to one person and that its contents have been checked to another. The agreement should state what ready means, how it is checked and what prevents release.
In the worked example, readiness includes an identifiable kit, the agreed contents, a condition check and confirmed collection arrangements. A missing essential component prevents release under the original promise. An alternative kit may be offered only if the participant understands the difference and the authorised coordinator accepts the substitution. A silent substitution would change the promise without the beneficiary's knowledge.
Avoid adopting a numerical target because it looks professional. A time limit needs a reason, a starting event, an ending event and a response when exceeded. If the workshop needs a handover completed before the next custodian begins issuing kits, that operational dependency is more useful than an unexplained target of five minutes.
Workbook entry: For each criterion, record its purpose, observable acceptance condition, prohibited shortcut, treatment of uncertainty and exception authority. Then write one borderline example and the intended decision. Resolve disagreements before release.
CHAPTER 4 OF 10 · Make decisions usable
4. Put decisions beside the work they control
An operating agreement should tell people where a decision belongs. A long list of responsibilities at the end of a document often leaves the critical moment unclear. Place the decision rule beside the step it governs: accept a booking, release a kit, receive a return, escalate a discrepancy or close a case.
Distinguish performing, deciding and checking. One person may hold several roles in a small team, but the agreement should explain how an important self-check is challenged. A second person might review unusual substitutions or periodically examine completed cases. Do not imply that independent review exists when the same person made and approved the decision without another safeguard.
Name roles with current holders in a separate roster if personnel change frequently. This keeps the method stable while allowing responsibility to remain current. The roster must still be available where work occurs; an unnamed role with no reachable holder provides little help.
Workbook entry: For each material decision, record the decision-maker, required information, limits of authority, substitute and escalation route. Ask the substitute to explain one difficult case. An authority table is incomplete until its intended users can act from it.
Readiness concerns the conditions needed before a commitment is made. It includes people, equipment, information, capacity and connected services. A checklist should lead to a decision, not merely produce ticks.
The fictional workshop checks whether the assigned custodian can verify contents, whether the current booking list is accessible, whether the kits are identifiable and whether returns can be reconciled. An unavailable printer may be manageable if an approved record method exists. An untraceable kit identity is more fundamental because it breaks issue and return evidence.
| Readiness question | Evidence at the point of work | If the condition is absent |
|---|---|---|
| Can the custodian perform the release check? | Relevant demonstration and current assignment | Provide qualified supervision or defer release |
| Are kit identity and contents known? | Kit record and physical comparison | Isolate the kit until reconciled |
| Can the agreed demand be handled? | Available kits, booking commitments and return workload | Limit acceptance or change the promise openly |
| Can the next handoff be completed? | Reachable receiver and working record route | Establish an approved alternative before proceeding |
These are example questions, not universal release criteria. Use Process Design and Readiness to examine dependencies before deciding what your own release gate must contain.
CHAPTER 6 OF 10 · Prepare connected work
6. Design the handoff as an agreement between two people
A handoff is complete when the next responsible person can continue the work with the necessary meaning intact. Sending a message is only one event within that exchange. The operating agreement should define what is transferred, what acceptance means and who remains responsible if acceptance does not occur.
For a kit with a missing component, the outgoing custodian records the item identity, the discrepancy, the temporary action, the next decision and the time by which that decision matters. The incoming custodian checks that the record matches the physical kit. If it does not, the difference is resolved or escalated; it is not hidden by a receipt confirmation.
An operating agreement also needs a route for absence. A message to an unavailable colleague can leave responsibility suspended. Specify an alternate receiver and a clear limit on what may continue while the handoff remains open. See Handoffs, Communication and Continuity for the wider design.
Workbook entry: Write the minimum handoff information, acceptance test, rejection response and temporary owner. Test the arrangement with an incomplete record and an absent receiver. Both cases should produce a clear next action.
CHAPTER 7 OF 10 · Record and test
7. Collect the evidence needed for the next decision
Begin with the decisions the record must support. A custodian needs to know whether a kit can be issued. A reviewer needs to know whether release controls operated. A manager needs to know whether repeated discrepancies reveal a capacity or design problem. One record may support all three, but each field should have a purpose.
The workshop's basic case record contains kit and booking identities, method version, responsible person, release result, exceptions, handoff acceptance and closure. Sensitive or irrelevant information should not be copied simply because a form has spare space. Decide who needs access and how records remain usable for the required review period. Applicable external obligations must be checked separately for the actual setting.
A blank field needs an interpretation. It may mean not done, not applicable, not recorded or not yet known. Define the permitted entries so absence does not become a convenient substitute for evidence. Where a record is corrected, preserve what was changed, by whom and why in proportion to the importance of the decision.
Workbook entry: For every field, name its decision use, source, recorder and reviewer. Remove fields with no defensible use. Add missing fields where the next responsible person otherwise has to guess.
Read the draft while following one kit from booking to closure. A desk review can identify missing words; a connected trial identifies missing work. Observe whether the custodian can find the current instruction, apply the readiness rule, complete the record and obtain handoff acceptance.
Include at least one case chosen to challenge an important assumption. This is a design suggestion, not a fixed sample size. The workshop might use a kit returned near the next collection time with one disputed component. The trial should reveal who can decide whether the kit remains available and how the booking promise is protected.
Record assistance supplied during the trial. If the document's author repeatedly explains what the instruction means, the result does not yet demonstrate that the agreement works independently. Revise the confusing point and repeat the affected part under the intended operating conditions.
Workbook entry: Record the test conditions, cases chosen, observations, assistance, failures and changes. Distinguish a successful trial from permission to claim dependable performance across conditions that were never examined. The agreement's release scope should match what its evidence supports.
CHAPTER 9 OF 10 · Release and practise
9. Release a version people can actually use
A controlled release needs an owner, a version identity, an effective point and a method for withdrawing superseded instructions. It also needs a clear decision about cases already in progress. Without that transition rule, one custodian may start a case under the old method while another closes it under an incompatible new one.
The workshop chooses a changeover between sessions, briefs the custodians and identifies open discrepancies before the new agreement takes effect. If a necessary urgent correction cannot wait, the coordinator records the temporary rule, communicates it to affected people and sets its review point. A temporary exception must not disappear into an undocumented permanent practice.
Check usability at the actual point of work. A carefully approved document behind an inaccessible account is not an available instruction. Where printed copies are needed, the agreement should say how their currency is checked. Where the electronic system fails, the fallback must preserve the decisions and evidence that still matter.
Workbook entry: Record approval, effective conditions, briefing evidence, locations of controlled copies, treatment of open work and rollback or suspension authority. Schedule review around material changes and evidence of difficulty, as well as any chosen periodic review.
CHAPTER 10 OF 10 · Release and practise
10. Complete and challenge your operating agreement
Transfer test: a learner-feedback routine
Fictional contrast: a tutor promises to help a learner understand an earlier algebra error and attempt a suitable fresh task. This is a learning routine, so returning a marked worksheet is an output; useful completion concerns the learner’s explanation and recorded application.
Local scope: one identified misconception, one correction conversation and one later check. The tutor owns preparation and feedback; a receiving tutor explicitly accepts any unresolved next step. Record the task, help provided, the learner’s explanation and the next review. Never describe a prompted response as independent.
Normal case: the learner explains the correction and attempts the fresh task under the agreed assistance conditions. Changed case: the explanation remains uncertain or a prerequisite is missing. Record that limit, choose a manageable teaching response and retain the next owner. The case can be transferred responsibly while mastery remains unestablished.
Use GS-R02 to specify what an acceptable explanation would show, GS-R07 to protect the next teaching handoff and GS-R08 to separate observation from inference. A later independent task would add evidence; one successful response does not guarantee retention or an examination grade. Compare this routine with kit issue: the framework persists, but the beneficiary’s outcome, evidence and completion event must change.
For a connected set of source records and a finding register, use the worked portfolio in Volume 31. Its simulated records let you check each conclusion against what was actually supplied.
Bring the workbook entries together into a concise agreement with supporting records where needed. The table below is an assembly guide. It does not require one large form; the information may live in connected documents if people can reliably find the current parts.
| Agreement component | Minimum question answered | Worked example output |
|---|---|---|
| Promise and scope | What outcome are we responsible for? | Correct kit issued and return reconciled within the agreed boundary |
| Criteria | What counts as acceptable? | Identified kit, verified contents and understood arrangements |
| Roles and decisions | Who acts, decides and substitutes? | Custodian, coordinator and alternate receiver |
| Readiness and method | What must exist before and during work? | Release check linked to actual capacity and kit condition |
| Handoffs and exceptions | What happens when work changes hands or fails? | Accepted discrepancy record and temporary ownership |
| Evidence and review | How will we know and improve? | Traceable case records, review questions and effectiveness checks |
| Version and transition | Which method applies to which work? | Effective version, treatment of open cases and withdrawn copies |
Practice: A custodian proposes removing receiver acknowledgement because most handoffs are uncomplicated. Decide what question must be answered before changing the agreement. Write the evidence you would examine and a trial that could test an alternative.
Reasoned response: First identify the purpose of acknowledgement: preserving responsibility and detecting mismatches. Examine unresolved cases and failed or delayed handoffs, not only routine completions. An alternative may be acceptable if it preserves those functions under relevant conditions. Faster transfer alone is insufficient evidence. Record the decision, test the alternative and use Assessment and Conformance Handbook when evaluating the wider management system. A well-written local agreement is one part of that system.
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
- 17. The Gold Standard Reference | Local Operating Standards Workbook — you are here.
- 18. The Gold Standard Reference | Diagnostic Review and Improvement Planning Workbook
- 19. The Gold Standard Reference | Casebook and Decision Practice
- 20. The Gold Standard Reference | Reference Index and Programme Maintenance
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. Version 1.0 was prepared 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.