The Tiny Ask That Ate Tuesday: Putting a Fence Around 'Can You Just...'

Every freelance writer knows the sentence. It arrives on a Tuesday morning, just as you are finally getting into the work that actually pays. 'Can you just...' The request is small. The implication is that saying no would be unreasonable. And somehow, by Friday, the brief has grown a tail and your week has disappeared into a series of tiny, unpaid yeses.

I have nothing against small requests. Some of the best client relationships are built on goodwill, quick fixes, and the occasional favour. But there is a difference between a genuine two-minute tweak and a request that quietly redraws the boundaries of the project. The trouble is that clients rarely know which one they are sending. Often, neither do we until we are halfway through.

The word 'just' is doing a lot of work

'Just' is a minimiser. It tells you the request is small before you have had a chance to assess it. 'Can you just rework the intro?' 'Can you just make it sound more premium?' 'Can you just add a section on sustainability?' The word softens the ask, but it does not shrink the work.

A two-minute tweak is rarely two minutes by the time you have found the file, reopened the brief, checked the style sheet, made the change, exported the document, written a cheerful reply, and updated your project notes. Then there is the context switching. You were in the middle of something else. Now you are not. That cost does not appear on an invoice, but it is real.

In the UK, politeness makes this trickier. Clients often phrase requests as gentle questions: 'Would you mind just...', 'While you are in there...', 'Sorry to be a pain, but...' The tone is friendly. The scope creep is still scope creep.

A scope check that takes four minutes

Before you say yes, run a quick check. Ask three questions, either in your head or in a reply: What exactly is changing? Who has asked for it, and who approves it? When is it needed, and what should it replace?

If the answers are fuzzy, do not start. A vague request is not a small request; it is an unfinished one. 'Make it punchier' could mean a new headline, a new structure, or a completely different tone. 'Add a quick paragraph' could mean 50 words or 500. You need enough detail to judge whether the work fits the brief.

The third question is the one freelancers forget. If something is added, something else usually has to move. That might be another task, another deadline, or another part of the draft. If the client wants more words, ask what should come out. If they want a new section, ask which existing section it replaces. If they want it today, ask which deadline moves. This is not being difficult. It is being honest about capacity.

Use a fifteen-minute rule, but do not let it become a habit

One useful habit is the fifteen-minute rule. If a request is clearly within the original brief, takes less than fifteen minutes, and does not disturb a deadline, absorb it. Say yes, do it, and move on. Goodwill has value.

But log it. A simple change log with the date, the request, the time spent, and whether it was in or out of scope will tell you a lot after a month. If the same client is sending three 'tiny' requests a week, the pattern is the problem, not any single request. That is when you need a process, a retainer, or a rate that reflects the admin.

Email scripts that keep you warm and firm

You do not need to write a legal treatise every time the phone pings. A short, friendly reply is usually enough. The key is to name the scope without making the client feel accused.

For a small in-scope request: 'Yes, I can fold that in. It will replace the [X] section rather than add to it, so the word count stays put. I will send it with the next draft on [date].'

For a small out-of-scope request: 'I can do that. It sits outside the agreed brief, so it will be [fee] and add [time] to the schedule. Want me to go ahead?'

For a vague request: 'Happy to look. Can you confirm which pages you mean and what outcome you want? Once I have that, I will tell you whether it fits the current scope or needs a change request.'

For an urgent request: 'I can prioritise this today if we move [other task] to [date]. Which would you prefer?'

For the classic 'while you are in there': 'I can make that change. To keep the revision round clean, I will log it separately so we can see what is included and what is extra.'

Notice what these scripts do. They do not say 'no'. They say 'yes, and here is what it means'. That is a much easier conversation.

Say yes to the relationship, no to the scope

Boundary language works best when it is warm and specific. Try: 'I want to keep this simple.' 'Let us put it in writing.' 'I can do that as a separate small piece of work.' 'That is a change to the brief, so I will quote it.' 'I would rather flag it now than surprise you later.'

Avoid apologising for having a process. You are not being precious. You are running a business. A clear boundary is kinder than a resentful yes followed by a late delivery or a sloppy final draft.

Put it in the contract before you need it

If you have a contract, make scope visible. List the deliverables, the number of revision rounds, the window for feedback, what counts as a revision, and how change requests are handled. Add a line about small requests if that is a recurring issue. If you work on a retainer, state the monthly hours and what happens when they run out.

If you do not have a contract, a polite email confirming the scope is better than nothing. 'Just to confirm: this covers X, Y, and Z, with two rounds of revisions. Anything beyond that I will quote separately.' Keep it in the thread. Future you will be grateful.

When the client is lovely but chaotic

Most clients are not trying to exploit you. They are busy, they do not see your other projects, and they think in outcomes rather than hours. A short explanation of your process can change the relationship. 'I batch small changes on Wednesdays' is often more useful than a lecture about scope creep.

If they keep ignoring the process, you have options. Raise your rate to cover the admin. Move to a retainer with a clear monthly allowance. Or, if the relationship has run its course, part ways politely. A client who respects your process is a better client. A client who does not is a warning sign.

The bottom line

'Can you just' is not a command. It is an opening. Answer it with clarity, a little warmth, and a clear sense of what the work actually involves. Protect your week. The relationship will survive a clear boundary far better than it will survive resentment.