Service and creative work: events, films, documents, training and delivered services

Load when the output is delivered by people rather than shipped as a product: an event, a film or video, a publication, a translation, a course, a consultation, a campaign, a service performed for a client. The same loop applies (../SKILL.md §2. The control loop); what changes is the form of the procedures and the evidence.

Brief and acceptance

• A written brief, agreed with the client or owner: the purpose and audience; the deliverables (the film at its length and formats, the event on its date for its number of people, the document in its languages); constraints (budget, dates, venue, brand, legal and accessibility requirements); who approves at each stage; and the acceptance criteria for the final result.
• Acceptance criteria are concrete: “a 3-minute cut in 16:9 and 9:16, captioned, with licensed music, approved by the marketing lead”, not “a great video”.
• Rights and permissions are part of the brief: releases from people filmed or photographed, licences for music, footage, fonts and images, venue and location permissions, and who owns the result.
• A deliverable derived from a source (a translation, a cut-down, a revised edition) records the version of the source it was made from, so it can be told when the source moves on (software.md §Translations for the method).
• Plan the work and its dependencies like any other project (planning.md): venues, crews, suppliers, talent and approvals are resources and dependencies with dates, and their confirmed bookings are records.

Rehearsals and reviews

• Rehearse what will happen live (the run of show, the talk, the handover, the demo) with the people and equipment that will do it, and record what went wrong and what changed.
• Review drafts at the stages the brief names (script, rough cut, draft, proof), with the approver named. Each review records what was approved, what must change, and by when.
• A review is of the actual draft, in its real format and on the devices or in the room it will be experienced in, not a description of it.

Observed delivery

• Delivery is observed and recorded: the event ran to its schedule with its numbers counted; the film was delivered in each format and played on the target platforms; the document was published and its links work; the training was held and attendance recorded.
• What was planned is not what happened until someone saw it happen. A booking confirmation is not the caterer arriving; a scheduled post is not a published one.
• Problems on the day are handled and recorded (what happened, what was done, who was affected), and anyone affected is put right afterwards.

Closure and archive

• The client or owner accepts the delivery against the brief’s criteria, in writing.
• Obligations are settled: suppliers and crew paid, deposits returned, licences and releases filed, promises to attendees or audiences kept.
• Materials are archived where the owner can find them: masters and source files, project files, releases and licences, the brief and approvals, contact lists handled under the privacy rules.
• A finite piece of work closes here. It does not acquire a recurring operations loop. If anything must keep running (a website, a recurring event, a published course), hand it to a named operator (../templates/handover.md).