Gold Standard Practical Case Study 03 | An Archive Request and an Unaccepted Handoff

In a fictional local-history reading room, visitor Rowan requests a scan of a public event programme. Volunteer Ada finds the catalogue entry but cannot confirm whether the requested page is included. The next step is to inspect the item and report what can be supplied. The exercise concerns request ownership, not permission to reproduce real collection material.

The room’s local handoff rule H0 says the outgoing volunteer retains ownership until a receiving volunteer explicitly accepts the request identity, current state and next action. If acceptance cannot be arranged before departure, the shift lead must decide the cover route. Naming a recipient in a message is not the acceptance event.

The useful outcome is a supported answer to the visitor, including a limitation where appropriate. Sending a scan request internally does not complete that outcome. This scope begins with the accepted enquiry and ends with the visitor’s answer or an agreed alternative; it excludes any assumed entitlement to access or reuse restricted material.

Contents · Next chapter

H1 records enquiry AR-09 and Ada’s partial search. H2 records her message to Ben with the catalogue entry and unresolved page check. H3 records Ada marking the request transferred and ending her shift. H4 records that Ben did not accept the request before that shift ended. These are explicit simulated facts, not inferences from a silent inbox.

H5 records the next morning’s queue review. The request is marked transferred, no active owner is shown, and no item inspection has occurred. H6 records the shift lead, Mei, identifying the open case and assigning it back to Ada temporarily. H7 records Ben later accepting AR-09, its current state and the next inspection action.

If H4 instead said only that an acknowledgement could not be found, the historical event might remain Unknown. In this exercise H4 states that acceptance did not occur. The reviewer must use that fact without weakening it into uncertainty or strengthening an absent record into a fact it does not contain.

Contents · Previous chapter · Next chapter

Under H0, the handoff in H2–H4 is Not met. Ada transmitted information but did not obtain the acceptance required for transfer. H5 shows the resulting operational gap. Mei’s later intervention restores a named route; it does not make the earlier handoff compliant.

The case also shows why a status field matters. Transferred sounded like completed work, while the next action remained unowned. A useful status should describe the actual state: awaiting acceptance, owned by Ada, inspection pending. The wording is helpful only if the work system uses it to retain responsibility.

Do not conclude that every archive request is lost or that Ben deliberately ignored Rowan. The record set contains one request and no evidence of motive. The appropriate finding is bounded to this handoff and its local condition. Clear boundaries keep a serious observation from becoming an unsupported accusation.

Contents · Previous chapter · Next chapter

In H8, Ben inspects the item and records that the requested page is present. Mei checks that the fictional room’s access conditions permit the supplied response. H9 records Ben sending Rowan the agreed answer through the enquiry channel and retaining the response identity. H10 records Rowan’s acknowledgement. The current request is now resolved within the exercise’s stated conditions.

This is more than changing the owner field. The receiver needs enough information to continue, the authority to act within the permitted route, and a concrete next action. H7 contains those acceptance elements; H8–H10 connect them to the visitor’s outcome.

An apology could be appropriate in a live service, but its wording is not the evidence of resolution. The case’s closure depends on the supported response and acknowledgement. Communication can be courteous and operationally precise at the same time.

Evidence-to-decision register

Contents · Previous chapter · Next chapter

The lead proposes action HC1: a transferred status becomes available only after the receiver’s acceptance is recorded. Until then, the outgoing owner remains visible. The shift lead receives unresolved acceptance requests before the outgoing volunteer departs and decides whether to cover, defer or reassign them.

That design must fit the actual volunteer arrangement. If nobody can accept at the boundary, the service needs an honest limited mode. The visitor may receive a later response commitment accepted by an authorised owner. The organisation should not promise uninterrupted processing merely because the rota lists a name.

No trial of HC1 is supplied. Its effectiveness is Unknown under GS-R10. GS-R11 continuity also cannot be declared Met from the proposed cover route alone. Demonstration would need to show whether the lead or deputy can find the case, access the needed records and carry out the assigned next step under the relevant conditions.

Contents · Previous chapter · Next chapter

Consider an alternative exercise in which Ben accepts the request identity but the message omits which page Rowan wants. Acceptance alone would not make the information usable. The reviewer would examine the local requirement for the request’s current state and next action rather than checking only whether an acknowledgement exists.

Another variation has all information present, but Ben is authorised only to catalogue items. He cannot decide access. The handoff needs an accessible authority route as well as a recipient. These variations explain why GS-R07 concerns usable communication and responsibility, not a ritual reply.

Keep these alternative facts outside the original finding register. A case study becomes difficult to reason about when hypothetical changes quietly enter the supplied history. State the variation, solve it on its own terms, and then compare the management function that remained necessary.

Contents · Previous chapter · Next chapter

Write a receiving note for AR-09 that identifies the case, current state and next action. Add who holds ownership until acceptance and where a permission question goes. Keep the note short enough for a volunteer to use during a shift change.

A defensible answer says: AR-09 seeks a specified page; the catalogue entry is located but the item still needs inspection; Ben accepts inspection and response preparation; Ada retains ownership until that acceptance; Mei decides any access limitation outside Ben’s remit. The original facts support the sequence, not a universal policy for real archives.

Use the manual’s handoff reasoning to review an actual authorised process, with its own information rights and conditions. The aim is continuity for the person waiting, supported by a record another worker can understand. A forwarded message becomes valuable when it connects to an accepted next action.

Contents · Previous chapter · Gold Standard hub