From a call to a brief without rewriting the notes.

Most briefs fail in the same place: they repeat the call in nicer prose and leave the hard choices implicit. The audience is vague, the constraint is softened, and the deliverables are a list someone will argue about on Thursday. Spark*form treats a brief as a contract with five fields: objective, audience, constraint, deliverables, and the source it came from, so a vague field cannot hide.

Start with the recording or the notes, whichever the client let you keep. Ask Spark to extract the five fields and flag the ambiguous ones. It will surface, for example, that the audience mixes trade buyers and end consumers, or that the constraint cites legal review without naming who signs off. Those flags are the review agenda. A senior who never joined the call can clear them in ten minutes, exactly as the call-to-brief playbook shows, with sources linked line by line.

The gate is explicit: no brief ships until every field has a check. Once it does, the deliverables carry acceptance criteria the reviewer already approved, so the studio does not interpret intent. The artefact is the checked brief itself, not an email summarizing it. That is the difference between handing off words and handing off a commitment your team can price, staff, and defend on first presentation.