FREELANCE FIELD
Client workflow

Run a Focused Creative Discovery Call and Write Useful Notes

A discovery call should establish whether the project is understandable and suitable for the way you work. It is not a performance in which you must instantly solve every creative problem. A clear agenda lets you listen, ask specific questions and identify the information needed for a brief or quote. This guide offers an original structure for a modest creative assignment. Adapt its timing to the conversation and get consent before recording any call.

Planner, tablet and stationery on a dark desk.

Photo: Ann H · License. Illustrative stock photography.

Send a small agenda before the call

Explain that you will discuss the intended output, available inputs, decision process and schedule. Ask the client to bring one example of the problem and any existing materials they are comfortable sharing. Do not demand a long homework questionnaire before an exploratory conversation. Set an expected duration and leave room for questions. If the project involves sensitive information, agree an appropriate sharing method in advance. A simple agenda helps both people arrive with the same understanding of what the call is meant to accomplish.

Ask about the situation before the solution

Start with what prompted the enquiry: what is happening now, what is difficult and what should the finished material help someone do? For a workshop deck, ask who attends, where the deck is shown and which information participants need afterward. Listen for a mismatch between the requested output and the underlying task. The client may ask for more slides when a shorter handout would be more useful. Present such an observation as a question to explore, not as a diagnosis based on two minutes of conversation.

Explore inputs, approvals and constraints

Ask what already exists, who can approve facts and which materials are still missing. A deadline may be tied to an event, but production also depends on receiving usable copy and feedback. Ask who will review drafts and whether other stakeholders need to be involved. Clarify practical constraints such as printing, language, accessibility and the receiving software. Record unknown answers honestly. It is better to write venue details pending than to fill the note with a confident assumption that later becomes an expensive design change.

Take notes in decisions rather than a transcript

Use four columns or headings: confirmed information, open question, owner and next step. Capture exact quantities and dates carefully, but do not write every conversational aside. Example: confirmed: one four-page PDF; open: whether an editable file is needed; owner: event manager; due: before quote. If you want to record audio, ask first and explain the purpose, access and retention. A plain written note is often sufficient for a small project and avoids collecting more personal material than you actually need.

Explain your process and test the fit

Describe how you move from brief to draft, consolidated review and handoff. Mention the type of input required and the limits of the service. If the project needs skills you do not offer, say so clearly rather than accepting work on an unsupported promise. Ask whether the client can meet the approval and input responsibilities. Discuss resource constraints respectfully without pushing for a commitment during the call. A useful outcome may be a smaller project, a separate discovery stage or a polite decision that the assignment is not suitable.

Send a recap with one next action

After the call, write a concise summary of purpose, proposed outputs, dependencies and unresolved questions. Distinguish agreed facts from your suggested approach. End with one next action, such as the client sending approved text so you can prepare a scope. Avoid writing a recap that quietly treats an exploratory idea as a confirmed purchase. Keep the note in the project folder with its date. If the client corrects a detail, update the working version so future production does not rely on the first imperfect summary.

Your working checklist

Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.

Put it into practice

  1. Share the agenda and expected duration, then prepare a few questions about the audience, immediate task and existing materials rather than a generic sales script.
  2. During the call, clarify purpose, quantities, inputs, approvals and dependencies. Capture missing information with an owner instead of filling gaps with guesses.
  3. Explain your process and limits in practical terms. Check that the client can provide the required input and that the assignment fits your demonstrable skills.
  4. Send a dated recap separating confirmed information from proposals. Give one clear next action and request correction of any factual misunderstanding before preparing the scope.

Before you finish

  • The call's purpose and expected duration are clear.
  • Notes identify decisions rather than collecting irrelevant personal details.
  • Every unresolved production question has an owner.
  • No exploratory suggestion is presented as confirmed work.
  • The recap gives a single understandable next action.

Common questions

Do I have to record the conversation?

No. Decision notes are often enough. If recording would be useful, obtain appropriate consent and agree the purpose, access and handling before recording begins.

Should I give a final quote during the call?

Only if the project is clear enough for you to do so responsibly. It is reasonable to confirm the inputs and prepare a considered quote afterward.

What if the client does not know the deliverable yet?

Discuss the task and available information first. You may propose a bounded discovery stage, but do not promise a final package before the missing decisions are understood.

Open the toolkit ↗

Find a guide