Onboard a New Client Into an Evidence-Led Writing Workflow

The new client has sent a company deck, an old interview, a product note and an email explaining next week's announcement. Your onboarding questionnaire asks for a completed company knowledge profile before writing can begin. The account lead now has two jobs: prepare the announcement and translate the client's material into the questionnaire.

Start with the announcement instead. Agree what must be written, for whom, by when and in whose voice. Accept the documents together through the team's approved channel. The agency can make the first pass at organizing them, then ask the client to resolve the uncertainties that matter to this deliverable.

For a press release, establish the news, availability and proposed spokesperson. For an authored article, establish the argument, publication brief and author's contribution. For journalist Q&A, retain the exact questions, deadline and attribution request. These starting points produce different information gaps, so avoid sending the same long form for every format.

Ask for relevant factual material, approved writing examples and any existing guidance the client wants considered. Explain where the files will be stored and which people or tools may process them under the agreed arrangement. If tool permission is unresolved, keep the material out of that tool while continuing permitted manual work.

A pasted brief supplies instructions about the assignment. It does not establish that every requested claim is true or that every attached document may be quoted publicly. Record any actual sharing restrictions and ask targeted questions about uncertain source use. Never invent a rights confirmation because the client submitted an email.

Consider a hypothetical client introducing an employee scheduling service. The brief asks for a launch across the country. The product note confirms availability to existing customers in two regions. Last year's founder interview includes the phrase built for every workplace. The phrase sounds useful, but it neither establishes this launch's reach nor supplies permission for a new attributed quote.

Show the client the proposed opening beside the supporting passages. Mark the national scope as an open question. Explain that the product note supports a narrower availability statement and that the interview can inform the founder's expression, subject to approval. This gives the client a concrete decision instead of an abstract request to complete missing profile fields.

Ask product to confirm eligibility and timing. Ask the communications contact to decide what can be disclosed. Ask the founder or their authorized approver to accept any proposed quote. The same person may hold several responsibilities, but write down what each answer settles. A factual confirmation should not silently become authorization to release the whole announcement.

After the first review, propose a small set of reusable items: the confirmed service description, a source-backed availability record, and accepted voice guidance for the founder. Show the client exactly what would be retained and for which uses. If an existing record would change, show the old and new versions and preserve the decision history.

There is a tradeoff between early structure and early delivery. A complex client may need more agreement about restricted material or decision authority before drafting can proceed. Keep that work tied to the actual sources and people involved. A large blank profile does little to resolve a specific permission or ownership question.

The first-assignment walkthrough should leave a draftable brief, a short owned question list and a route to release. Those concrete artifacts form a more useful foundation for later work than a large profile whose uncertain fields have no connection to the current deliverable.