Onboard a New Client Into an Evidence-Led Writing Workflow

A new client sends a company deck, an old interview, a product note and an email about next week’s announcement. The agency’s onboarding questionnaire wants a full company profile before anyone writes. Now the account lead has two jobs, and only the announcement has a date.

Onboard through the first deliverable. Agree what must be written, for whom, by when and in whose voice. Take the documents in together and let the agency sort them, then ask the client only the questions this deliverable needs answered. The profile builds itself from accepted work.

Ask for what the first deliverable needs: the news, the audience, the deadline, the spokesperson and the documents that support it.

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.

Expect caution about what goes into AI tools. In Muck Rack’s State of AI in PR 2026↗, 77% of PR professionals said they avoid entering financial data into AI, and 69% avoid personally identifiable information and proprietary or strategic material¹. Clients often feel the same, so say plainly which tools will read their documents.

Personal data makes the arrangement a legal question as well as a courtesy. Where the EU GDPR applies and the agency processes personal data on the client's behalf, the European Commission's guidance↗ says the processor's duties to the controller must be set out in a contract or other binding legal act, including what happens to the data when the contract ends². The same guidance says a processor may sub-contract part of its task to another processor only with the controller's prior written authorization², and it gives cloud storage as a typical processor activity². A software tool that stores or processes client files containing personal data may therefore need the client's written agreement before anything goes into it. This is general guidance, not legal advice; check the rules that apply to your organization with counsel.

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.

Treat the brief as instructions about the assignment and the documents as evidence, and show the client which passage supports each sentence of the opening.

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.

Keep each request short and tied to the sentence it unblocks, as in asking a busy client for the evidence you need. QuoteIt works the same way: a pasted brief is kept as instructions for the draft, each claim is checked against the uploaded sources, and a nationwide launch that only the brief asserts is flagged, with a question about whether it belongs in the client's knowledge.

Three things: where open questions go, whose voice applies, and what each approval permits. Write the last one into the handoff that goes with each draft.

It leaves reusable items the client has accepted: a confirmed service description, a sourced availability record and voice guidance the spokesperson approved.

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, the same discipline that keeps approved facts current as the business changes.

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.

When the work ends, a closeout ledger carries the same facts, voice and open questions to whoever writes next.