Directory/Working togetherP/02 Define the material.
Agree the handover.
A commission should make its purpose, boundaries, and review criteria legible before production begins. This page describes the working documents that support that agreement.
The work is not only the screen. It is also the explanation that makes the screen possible to review and maintain.
Different starting points require different working material. A content-model exercise may need representative entries and editorial interviews. An interface prototype may need an existing route, a proposed behavior, and a clear account of what is being simulated.
Bluff Vista’s operational approach organizes a commission around reviewable artifacts. Scope, schedule, commercial terms, and responsibilities are discussed directly; this website does not offer an automatic booking or a fixed package.
WORKING DOCUMENTS
01The brief
The brief identifies the intended audience, the body of content, and the difficulty the work is meant to address. It includes the existing environment and the people who will contribute material or make decisions.
It also names exclusions. A prototype may omit accounts and persistent data; a content model may stop before migration. Recording those limits helps prevent a convincing visual example from being mistaken for an operational commitment.
Review questionCould a new reader describe the assignment without guessing what is included?
The working set
The working set contains the representative material used to develop the design: sample entries, route sketches, screen states, or an annotated interface. It should be broad enough to expose meaningful differences without pretending to represent every possible case.
Versions need names and dates that reviewers can distinguish. Comments are easier to act on when they refer to a specific artifact and explain the visitor or editorial difficulty, rather than a preference detached from context.
Review questionCan each observation be traced to the version and state it describes?
The decision record
The record explains which direction was selected, what evidence informed it, and which questions remain unresolved. It distinguishes an agreed decision from an idea that is still being examined.
A useful review also identifies who owns the next action. Some issues require content, some require design, and others require a decision from the implementation team. The record should not leave those responsibilities hidden inside a long conversation.
Review questionIs it clear what has been accepted, what needs another pass, and who is responsible?
The handover
The handover brings together the approved material, the instructions needed to use it, and the limitations that still matter. For an interface, that may include component behavior, content examples, and an explanation of unusual states.
Implementation and ongoing care need explicit ownership. Access to source files, content systems, hosting, and third-party services should be arranged through the appropriate authorized channels, rather than embedded in a public document.
Review questionCan the receiving team understand and use the material without recreating the original discussions?
Decide who
carries each part.
A commission should identify the people responsible for content accuracy, review decisions, implementation, and post-launch updates. These may be different people or organizations.
Before starting, agree how new requests will be evaluated and how a change in scope will be recorded. Clear ownership makes the handover more useful than a folder of unexplained files.