A scoping call or a brief form: which comes first

The question is badly framed, which is what makes it hard. It is not one or the other: both earn their place, they do different jobs, and the order you put them in changes everything.

Most people do the call first and the form second. That is the natural order and it is the wrong one.

What a call hears that a form never will

Four things, and none of them can be written down.

Hesitation. "Yes... well, I would have to run it past my partner" appears in no form, because in a form that sentence becomes a ticked box. On the phone, the second and a half of silence before the "yes" is the information.

Contradiction. A client tells you they want something understated, then describes three elements that are not. In a form you get both answers with no idea which wins. On the phone you ask, and they settle it themselves.

What comes out at minute twenty-two. This is regular enough to count on: the project's real constraint arrives after twenty minutes, once the person has stopped presenting their project and started talking to you. "In any case it has to be ready before my colleague is back from leave, because otherwise she is going to want to review the lot."

That the project is not the one in the email. About one time in five. It only surfaces by talking.

What a form writes down that a call forgets

Three things, and they get paid for later.

Precision. Nobody dictates an exact material reference, a domain address or a panel's dimensions over the phone. You note it roughly and check later, except you do not check.

Completeness. A call follows the thread of the conversation, so it forgets. A form asks all twenty questions, including the five boring ones nobody wants to discuss and which are exactly what blocks the start.

A written trace. This is the expensive one. A call whose conclusions are written down nowhere is a call two people will remember differently in six weeks. And neither will be lying: you will both be honestly certain.

The order that works: the form first

Here is the counterintuitive part.

Why almost everybody does the opposite: calling first feels more courteous, more human, less bureaucratic. And it is. The trouble comes next, when you send the form: the client has just talked to you for an hour, and now they are being asked to write it all out again. They fill in half of it, answering "as discussed on the phone" to three questions, and you still have no usable record. Or they do not fill it in at all, which is fair enough of them.

The form first, the call second, and both get better:

• The form arrives before the client has worn themselves out narrating. They fill it in at their own pace, on their phone, going to fetch the actual files rather than describing them from memory.
• The call takes twenty minutes instead of an hour, because it is no longer there to discover the project.
• You arrive knowing something. You have read the answers, spotted the three that are vague, and the call is about exactly those three.
• And that is when the call finally hears what it is good at hearing: the hesitation, the contradiction, the thing not said. Against concrete answers, not against a project being pitched at you.

The sentence that sets this order without sounding cold: "I'll send you my questions, take your time over them, and we'll talk afterwards about anything that is not clear."

The case where the call does come first

There is one, and it needs naming or the rule above turns into dogma.

A stranger, on a large project. There, a short call before the form is justified, but it is not a scoping call: it is a qualifying call. Ten to fifteen minutes, five questions, and you know whether this project really exists. That is the subject of five questions to ask before writing a quote.

Which gives three moments rather than two, and is probably the only thing worth taking from this article:

1. Qualify. A short call, or three questions by email. Does this project exist.
2. Brief. The form. Everything you need to start, written down.
3. Clarify. A call, on the vague answers only.

Two and three are routinely confused, and that confusion is where the original question comes from.

What to write down after a call, always

Five lines, the same day, somewhere attached to the job rather than in your own notes.

What was decided, what is still open, and what you need from them. Not minutes: five lines. The point is not to archive, it is that a written version exists which you can both refer to without it being one person's word against another's.

And if the call changed something in the brief, the right answer is not to edit the answers already given: it is to ask the question again, properly. What a client answered should never be rewritten after the fact, including by you and including in good faith.

The shortcut

A call is for hearing. A form is for writing. In that order they do two different jobs; in the other, the form does the call's remembering for it, and does it badly.

For what goes in the form: the questions to ask, trade by trade.

Frequently asked questions

Do you need a scoping call or a brief form?

Both, and the form first. A call hears what cannot be written, the hesitation and the contradiction; a form writes down what a call forgets, the precision and the trace. In the wrong order the form is redundant and the client fills in half of it.

How long should a scoping call be?

Twenty minutes if it comes after the form, because it only covers the vague answers. An hour if it comes before, because then it is doing the whole job of discovering the project.

How do you propose a form without sounding cold?

By announcing the call in the same sentence: "I'll send you my questions, take your time over them, and we'll talk afterwards about anything that is not clear." The form stops being an administrative wall and becomes preparation for a conversation.

What should you do with what you learn on a call?

Write it down the same day, in five lines, somewhere attached to the job: what was decided, what is still open, what you need from the client. A call whose conclusions live nowhere is a call two people will remember differently.

The client answered a form question on the phone, now what?

Ask it again properly rather than filling in their answer for them. What a client answered should never be rewritten after the fact, even in good faith: it is the only version you can both refer to.