The Service That Kept Its Promise

At 13:10 on Friday, Mira has six PDFs in a folder and a message ready to send. At 13:20, her client can use four. One link does not allow access. Another file is an older version. The deadline is 15:00. There is still time, but there is not yet a complete delivery.

Mira, her colleague Tomas and their client Eden are fictional. The six-document project is an original worked case, not a testimonial or a report of real business performance. Its times and quantities let us examine what a handoff means without pretending that every service works like a small document job.

The agreed promise is specific: six named, review-ready PDFs in the agreed private folder by Friday at 15:00. Review-ready means the correct versions are available to the named reviewer and pass the agreed formatting checks. It does not mean approved for printing, accepted as final content or published for the public. The client review is scheduled separately for Monday.

This handbook follows the gap between making something and leaving it usable with the next person. It covers scope, evidence, a proportionate response when a check fails, customer communication and the distinction between delivery and final acceptance. The worksheets are editorial tools, not legal contract templates or guarantees of reliability, earnings or customer satisfaction.

Start with one handoff in your own work. Ask what the next person must actually be able to do. If the answer is only receive my email, look again. They may need to open the file, identify its version, use an agreed format or know what remains unapproved. The useful promise lives at that point of use, not solely at the moment you press send.

An internal activity is easier to promise than a customer result. We will export the files describes your action. The named reviewer can open the six specified current PDFs in the agreed location describes a handoff. Neither sentence alone defines every responsibility; it gives you a place to begin the conversation.

The UK Service Standard connects defined success measures with user research. [S3]

That is public-service guidance, not a law binding every reader's business. The practical adaptation here is to ask the receiving person what usable means before selecting your completion measure. Do not choose a metric merely because your own dashboard can produce it.

Mira and Eden agree the six document names, the source version for each, the expected page order and the private folder. Content is supplied by Eden. The team is responsible for the specified formatting and export checks; it is not claiming specialist review of the subject matter. If a known content problem becomes visible, it will be flagged, not concealed behind that division of responsibility.

They agree a source freeze on Wednesday at noon. A later request is recorded and assessed, rather than silently added to the original promise. The original deadline is not automatically moved by the team's inconvenience, nor does a client request automatically create an unpriced or unreviewed obligation. A changed arrangement needs an explicit agreement suitable for the actual contract and context.

Your promise card should identify the deliverable, receiving person, location, relevant version, checks, deadline and exclusions. Write exclusions as clear boundaries, not traps. If the recipient believes printing is included while your card says review-ready only, the disagreement should be resolved before work begins.

Created, checked, shared, opened and accepted should not be five decorative ways to say done. For this case, each word has a distinct observable meaning.

Created: the file exists. Checked: the specified inspection was completed on that version. Shared: it is placed in the agreed location with the intended sharing arrangement. Opened: the authorised reviewer confirms access to that version. Accepted: the reviewer confirms the agreed deliverable after the separate review. An invoice and a payment remain separate records.

Google's SRE guidance distinguishes reliability measurements from their target levels. [S1]

This document project is not a technical SLO implementation. The useful analogy is that an observation and a target are different things. Six exports observed is not the same statement as six usable handoffs by the agreed time. A target does not become evidence just because it appears on a plan.

Choose your own words with the receiving person. A different service may need different stages. Avoid copying this vocabulary into a field where it conceals an essential safety, regulatory or contractual gate. A medical, financial or safety-critical service requires its own qualified process.

At 13:10 Mira may truthfully say that all six exports exist. She cannot yet say all six are usable for Eden. At 13:20 the record changes: four meet the current recipient check, two do not. That is a useful state, even though it is less impressive than complete.

Write the test beside each progress word. If no one can explain how a state is established, use a more modest label. A message should help the next person decide what they may rely on.

A manifest is a list connecting each promised item to the version and location you intend to hand over. It does not need to be elaborate. It does need to distinguish six documents from six copies of an uncertain bundle.

Mira's fictional list uses letters A through F. A, B, C, D and E require version1. F requires version2 because a correction was agreed before the source freeze. Each line names the intended PDF and the person who checks it. The manifest is stored with the job record, not published as a customer list.

Before sharing, Tomas compares the output against that list. He checks the agreed page order and whether the export opens. The recipient access check is still distinct: opening a file while signed in as its creator does not establish that Eden can open it.

At 13:20 Eden reports that E is inaccessible and F is version1. The team keeps those two issues separate. Fixing E's access will not update F. Exporting F again will not grant access to E. A vague instruction to fix the folder would make the record harder to test.

Keep the earlier version in its authorised archive if the agreement requires it, but do not leave two indistinguishable current files in the delivery list. Use a clear current location and an explicit version reference. Do not permanently delete records or expose private material merely to make a folder look tidy.

For your own service, the manifest may list pages, packages, appointments or reports. Retain only information you are authorised to hold. The purpose is to make the promise inspectable, not to collect every detail about the person receiving it.

Work time is not exhausted when production ends. A service promise may need checking, communication and a response to something unexpected. If those activities are absent from the plan, they do not become free when the deadline approaches.

The fictional team reserves ten hours: six for formatting, two for checks, one for communication and one for contingency. Six plus two plus one plus one equals ten. These are illustrative allocations, not prices, standard productivity rates or advice about wages.

For Friday, the team has reserved 12:00 to 15:00 for checking and contingency. The access and version problems are found at 13:20, while there is still time in that window. The story does not claim that a buffer always saves a project. A larger problem could exceed it, and a different service could require a much longer preparation period.

Separate work that can proceed from work that depends on another person. Mira can regenerate F from the agreed source. Only the authorised folder owner can make the needed sharing correction for E. Calling the dependency early matters more than pretending the team controls it.

Do not borrow unagreed labour from colleagues to preserve an attractive plan. If the work no longer fits, describe the tradeoff and obtain a legitimate decision. It may be necessary to revise scope or timing, provide an agreed alternative or acknowledge a miss. Do not silently redefine the original promise after discovering you cannot keep it.

Your capacity page needs time for production, checks, communication and identified dependencies. Give each estimate a basis and keep uncertainty visible. A plan is an estimate of work, not a certificate that the future will comply.