What clients ask for is not always what they need

A client contacts you and says they need a translation into Portuguese. Or they ask whether you can “just proofread” a patient leaflet. Or they say they need a short article, a report, a review, an adaptation for Portugal, or a quick check before something is sent to the local team.

At first sight, these requests sound clear enough. Translation, proofreading, writing, review, adaptation, reporting. We know those services. We can quote them. We can deliver them.

And sometimes, of course, the client has described exactly what they need.

But not always.

Sometimes the words clients use are simply the closest label they have for the problem they are trying to solve. They ask for translation, but the project may require localisation or adaptation. They ask for proofreading, but the text may need editing. They ask for a report, but what they really need is a document that supports decisions after a meeting. They ask for a “quick check”, but the material may need a more careful review because of where and how it will be used.

If we respond only to the surface request, we may deliver the service the client asked for, but not the support the project actually needed.

The first request is not the full brief

When a client asks for a translation, it is natural to move straight into the practical details: word count, deadline, file format, reference materials, glossary, rate.

Those questions are necessary. We need them to quote, plan and deliver properly. But they are not enough to understand the work.

A 5,000-word document is not just a 5,000-word document. It could be an informed consent form, a patient leaflet, an HCP brochure, a disease awareness text, a training document, a manuscript abstract, a lay summary, a slide deck, a regulatory response, or website copy for a medical device company.

The word count may be similar, but the work is not. The audience may be different. The level of review may be different. The level of adaptation may be different. The consequences of unclear wording may be different.

So the first request is only the starting point. The real brief begins when we understand what the content needs to do.

When “translation” means alignment with what already exists

Let’s take a clinical trial example.

A client sends an informed consent form and asks whether you can translate it into Portuguese. If we look only at the request, the job seems simple: translate the English file.

But before quoting, I would want to know whether there are any previously approved related documents in Portuguese. That could include the protocol synopsis, consent forms for other patient populations, assent forms, recruitment materials, patient-facing study documents, or previously approved site or sponsor wording.

That one question can change the scope.

If there are already approved Portuguese materials, the work is not simply “translate this file from scratch”. The client may need the new document to stay aligned with wording that has already been reviewed, especially around the study purpose, procedures, risks, benefits, visit schedule, participant responsibilities, data use, withdrawal, or safety information.

If we translate the document in isolation, we may introduce differences in terminology or phrasing across related study materials. Not because the translation is wrong, but because it was not aligned with what already existed.

That can create unnecessary inconsistencies, extra review questions, and avoidable back-and-forth.

So instead of only replying with a rate, we can say:

“Before I confirm the quote, could you let me know whether there are any previously approved Portuguese documents for this study or related patient populations, such as the protocol synopsis, consent forms, assent forms, or recruitment materials? If there are, I’ll need to align the wording where appropriate so the Portuguese materials remain consistent across the study package.”

That is not a sales pitch. It is a practical scope question.

When “proofreading” means the text is not working yet

Proofreading is another common example. Clients often use “proofreading” to mean “please make this better”. But proofreading, editing and rewriting are not the same service.

A client may send a patient-facing text and ask for proofreading. When you open the file, you see that the problem is not mainly typos or small language errors. The terminology is inconsistent, the structure is hard to follow, the sentences are too close to the source, the reading level is too high, or the tone does not fit the audience.

If you accept the project as proofreading, you create a problem for yourself and for the client. If you only proofread, the text may still not work. If you edit or rewrite it properly, you may end up doing a much larger job than the one you quoted.

This is where scope needs to be clarified before the work starts. You could say:

“I can review this, but based on the sample, this looks more like editing than proofreading. The main issue is not only surface errors, but clarity, structure and audience suitability. Would you like me to quote for that level of review?”

This protects the client from expecting too much from the wrong service. It also protects you from unpaid scope creep. Most importantly, it helps both sides agree on what the text actually needs.

When “a report” can mean several different outputs

A client may say, “We need a report.” But that can mean many things. Do they need a chronological summary of what was said? A structured synthesis of the discussion? A list of key takeaways? A document with recommendations? A consensus-style document? A publication-oriented summary? An internal document to support next steps?

These are different outputs. They require different levels of detail, structure and judgment.

So before quoting, I would not only ask how many pages the client expects. I would ask what the report will be used for after the meeting.

If the report is for internal documentation, a straightforward summary may be enough. If it will support a publication plan, the structure and level of detail need to be different. If it will help a cross-functional team decide what to do next, the report may need to highlight key themes, points of agreement, open questions and possible next steps.

The client asked for a report. But the real need may be a document that helps them use the meeting output.

When “patient-friendly” is too broad

Patient-facing content for newly diagnosed patients is not the same as content for people who have been living with a condition for years. Content for caregivers is not the same as content for clinical trial participants. A text for people considering screening is not the same as instructions for using a medical device.

The purpose also matters. Should the content help readers understand a diagnosis, prepare for a medical appointment, decide whether to join a clinical trial, use a device correctly, understand study results, recognise when to seek help, or talk to a healthcare professional?

The same topic can require a different approach depending on the audience, context and purpose. A text can be accurate and still not be useful. It can be simple and still not answer the reader’s real questions. It can be readable and still miss important context.

So when a client asks for patient-friendly content, we need to go beyond the label. We need to clarify who the content is for, what the audience can be expected to know, what readers should understand after reading, what they should do next, where they will encounter the content, and whether any claims, references or approved wording need to be followed.

This helps us avoid treating “patient-friendly” as a style preference. It is not just about using simpler words. It is about making content usable for a specific audience in a specific situation.

When “adapt this for Portugal” needs a clearer scope

Adaptation is another word that can cover very different things.

Sometimes it means changing spelling, units, terminology and local references. Sometimes it means making the text sound more natural in Portuguese. Sometimes it means checking whether examples, healthcare system references, professional roles or patient pathways make sense in Portugal. Sometimes it means translating and adding comments for the local team. Sometimes it means rewriting the content because the source text does not work well for the new context.

For example, a global team may have an English HCP brochure and want to use it in Portugal. The request may be “Can you translate this for Portugal?” But the project may require more than translation.

Do the references to healthcare pathways make sense locally? Are the professional roles described in a way that fits Portugal? Does the tone sound credible for Portuguese HCPs? Are product or regulatory constraints relevant? Are there terms that should follow local usage rather than the source structure?

The answer may still be translation. But it may also be translation plus localisation comments, adaptation, editing or rewriting. The right service depends on what the client needs the content to do.

This is not about making every project bigger

Saying that clients do not always ask for what they need does not mean we should turn every enquiry into a large consulting process. Not every project needs a discovery call. Not every text needs a strategic review. Not every “quick check” is secretly a complex editing project.

Sometimes the client asks for a translation and they do need a translation. Sometimes they ask for proofreading and proofreading is enough. Sometimes the project is straightforward.

The point is not to make everything more complicated. The point is to notice when the requested service and the actual need may not match.

That requires judgment, but it also requires restraint. For a simple project, two or three questions may be enough. For a complex, regulated or high-risk project, you may need more context before you can quote responsibly.

The goal is not to sound more strategic. The goal is to scope the work properly.

Why should we do this?

When we accept the client’s label without checking what sits behind it, several things can happen.

We may underquote because the project is more complex than it first appeared. We may overdeliver because we end up doing work that was not included in the original scope. We may deliver exactly what the client asked for, but not what they expected. We may miss context that would have helped us do better work. We may create confusion around revisions, review rounds and responsibilities.

Most of these problems do not happen because the client is difficult. They happen because the label was too vague.

“Review” can mean many things. “Adaptation” can mean many things. “Report” can mean many things. “Patient-friendly” can mean many things.

Our job is to clarify what the label means in that specific project.

How to shift the conversation without making it awkward

Many freelancers worry that asking questions will make them sound difficult. But this does not need to be a long explanation. You can keep it simple and practical.

For example:

“Before I confirm the quote, can I just check how this document will be used? I’m asking because the level of review will be different if this is for internal use, publication, submission or patient-facing communication.”

Or:

“Are there any previously approved Portuguese materials I should align with, such as a protocol synopsis, consent form, patient leaflet or recruitment material?”

Or:

“Do you need a language check, or would you like me to comment on clarity and structure as well?”

Or:

“If this will go back into design after translation, I can also flag any non-editable text or layout issues that may need attention.”

This kind of language works because it connects the question to the project. You are not giving a lecture about quality. You are explaining why the answer matters.

A simple way to think about it

When a new request comes in, ask yourself what service the client is asking for, what outcome they are probably trying to achieve, what could go wrong if the scope is defined too narrowly, and what you need to know before you can quote responsibly.

This does not need to become a complicated process. Even a short reply can help shift the conversation:

“Thanks for sending this. I can help. Before I confirm the quote, could you let me know who the final audience is and where the text will be used? That will help me confirm whether a straightforward translation is enough or whether the text needs light adaptation for the Portuguese context.”

This paragraph confirms that you can help, asks for relevant context, explains why that context matters and opens the door to a better scope.

Your experience is part of the answer

One reason we can spot these issues is that we have seen similar situations before.

Even if the work came through agencies, the experience still counts. You may have seen clinical trial documents delayed because materials were not aligned across the study package. You may have seen patient materials that were accurate but too hard to understand. You may have seen HCP materials that sounded translated rather than credible. You may have seen slide decks with untranslated text hidden in images. You may have seen reports that captured what was said but did not help the client move forward.

You do not need to name clients or share confidential details. You can simply say:

“In similar projects, it is usually useful to check whether there are previous approved materials to follow.”

Or:

“For patient-facing content, I normally clarify the audience and intended use before quoting because that affects the level of adaptation.”

Or:

“For meeting reports, it helps to know how the document will be used afterwards so the structure supports that purpose.”

This shows experience without turning the conversation into a sales pitch.

A practical exercise

Look at one recent enquiry or project and write down the exact words the client used when they first contacted you. Then ask yourself what they asked for, what they actually needed, which questions helped clarify the scope, and which questions you would ask earlier next time.

Also look at whether the proposal was clear enough. Did it explain what was included? Did it make your process visible? Did the client understand why those steps mattered?

Then turn that reflection into a short note you can reuse.

These small explanations can be used in emails, proposals, LinkedIn posts, website copy or client calls. They help clients understand your process before there is a misunderstanding.

Change your narrative

“What clients ask for is not always what they need” is not a criticism of clients.

Clients are using the words they know. They are trying to move a project forward. They may not know the difference between proofreading and editing, translation and localisation, review and rewriting, a meeting summary and a strategic report.

That is fine.

Our role is not to correct them. Our role is to understand the request, ask the right questions and help define the right scope.

Sometimes that means saying: “Yes, I can help.” OR “Yes, and I would suggest including this step.” OR “Yes, but that is a different level of review.” OR “I don’t think proofreading alone will solve the issue here.” OR “The best approach depends on what you need this content to do.”

That is where we move beyond simply accepting tasks. Not by making the project sound more complex, but by making the need clearer. And when the need is clearer, the value of our work becomes easier to understand.