A brief usually describes the book with real precision — tone, audience, comparable titles, sometimes a moodboard of exactly the feeling a cover should have. What it's rarely designed to describe is the project underneath: who signs off on what, how many rounds of feedback are built in, and what happens if the manuscript changes shape halfway through. That's not a flaw in how briefs get written. A brief exists to describe an object. It was never really built to describe a working relationship.
That gap doesn't show up on day one. It shows up in week six, when a decision that should have taken an afternoon takes a week because nobody quite agreed whose call it was.
We've worked with a dozen publishing houses across trade and education lists, delivering hundreds of books between them, and the pattern holds regardless of list size or genre: the projects that run smoothly almost always have more than a brief behind them. They have alignment — a shared understanding, agreed early, of how the project itself will work, not just what it will produce.
Before work starts on a new project, our editorial, design and project management team builds its own shared picture of it internally — reconciling everything that's arrived in fragments across a proposal, a kick-off conversation, an email thread, a decision made on a call nobody wrote down — before a single word is written or page designed. That step exists so the genuinely useful questions surface early, while they're still cheap to answer, rather than three weeks in, when they cost a rewrite or a redesign.
What we're checking for matters more than exactly how we check it. Is this book standalone or the start of a series? What's already fixed — a printer's template, a house style, a series rule inherited from an earlier title — and what's genuinely open? Who actually has final sign-off, and is that the same person who's been giving feedback along the way? Questions like these sound obvious written down. They're rarely all answered by the time a project like this begins, simply because it was never anyone's job on the brief to ask them.
For a commissioning editor bringing in a new publishing partner, this is usually the quiet question underneath the visible one: not whether the book will come together well, but whether the relationship itself will generate more friction than it saves. That's really what this groundwork is for. It's not a formality before the ‘real’ work starts — it's where most of a project’s actual risk gets found, while it's still inexpensive to deal with.
A brief tells you what a book should look like. What determines whether a project runs the way everyone expects is everything around it — the editorial, the design and the management of both together — and the strongest partnerships treat that as work worth doing properly, in week one, rather than a gap that gets discovered in week six.