Scoping a freelance job without ten rounds of back and forth

Where the back and forth comes from, how to group it into two or three rounds, and what to write down before you start.

Published on August 14, 2026Written by Kalepio5 minute read

The time lost on a job is almost never production time. It is waiting time: you asked a question, the client answered two days later, you moved forward for an hour, and then you hit the next question.

Ten rounds of one day each is two weeks of calendar for six hours of work. The client thinks it took a long time, so do you, and nobody did anything wrong.

Where the back and forth comes from

Three causes, and only one of them is the client's fault.

You asked the questions as you went. This is the most common one. Every time you get stuck, you write. The client answers one question, not five, because you only asked one. The next day you have another.

You started without something you thought you had. The logo was on the client's website, small, so you made do. Three hours later the whole thing has to be redone from a vector file.

The client changed their mind. That one happens, and it is legitimate: they discover what they want by seeing what they do not. It is not a problem to eliminate, it is a problem to organise.

The rule: group it, do not scatter it

A well-scoped job does not have zero rounds of back and forth. It has two or three, planned.

  • Round 1, the brief. Everything you need in order to start, asked in one go, before the first hour of work.
  • Round 2, what gets decided by looking. The final copy, the choice between two directions, the partner logos nobody knew about at the start. You ask for those once the first proposal is in front of them, because before that the client cannot answer.
  • Round 3, sign-off. The green light, with a precise list of what still changes.

Each of these rounds is a moment when you wait. Three planned waits beat ten unplanned ones, and above all: you can tell the client in advance. "I am going to need you three times" is a sentence that reassures people.

What to write down before you start

Three lines, in the quote or in your first reply. They cost nothing and they head off the most unpleasant conversation in the trade.

What is included. The number of proposals, the number of revisions, the formats delivered. Not "a few rounds of feedback": a number.

What is not. This is not suspicion, it is information. A client who knows the third creative direction is billed does not ask for it absent-mindedly.

What blocks you. "Without the final copy I cannot start the layout." A sentence like that turns your waiting into an action on the client's side, rather than a silence they read as you being late.

Tracking is worth as much as scoping

Half of all client chasing is not a request: it is anxiety. "Where are we?" means "I have not seen anything happen for eight days".

Somewhere the client can look, without writing to you, removes that half. Not a weekly report to write: a page where they see where their job stands, what they answered, what is left, and what you are waiting on from them.

That is the second thing Kalepio does, after the brief: your client keeps one link, from the first form to the delivery, and looks instead of writing.

In short

Ask everything at once, plan two or three rounds rather than ten, write down what is included, and give the client somewhere to look.

If you want a starting point for the round-one questions, there is one per trade: here, to cut down as you see fit. And if you want the long version of what makes a good brief, it is here.

Frequently asked questions

How do you scope a freelance job?

By asking everything in one go before you start, then planning two or three moments when you will need the client again, rather than reaching out every time you get stuck.

How many rounds of revisions should be included?

A number, written in the quote, rather than "a few rounds of feedback". Two or three depending on the job, and anything after that is billed. It is not suspicion: a client who knows what is included does not ask for a fourth version absent-mindedly.

What do you do when a client changes their mind mid-project?

Treat it as planned rather than as an incident. Clients discover what they want by seeing what they do not, so a round of questions after the first proposal costs less than building on what was said at the start.

How do you avoid back and forth with a client?

You do not avoid it, you group it. Three planned waits beat ten unplanned ones, and telling the client in advance turns your silence into a step rather than a delay.

Kalepio asks these questions for you

You send one link, your client answers once, and you start with everything you need.

Read next