Sorry, Just, Perhaps: Trimming the Hedge Words Out of UK Business Copy

UK business writing has a politeness reflex. We apologise before we ask, soften before we state, and put a little bracket around the point so nobody feels cornered. Usually this is a feature, not a bug. A well-placed sorry can keep a client relationship intact; a just can take the edge off a chase. But when every request arrives wrapped in three layers of apology, the reader has to dig for the actual ask. That is not manners. It is fog.

Manners or fog? Try the removal test

Take out the softener. Read the sentence again. Did it become rude? If yes, put something back. Did it become clearer? Leave it out.

That is the whole editorial test. It works on emails, reports, proposals and client-facing web copy. It also stops you from performing the opposite mistake: stripping every please and sorry until your writing sounds like a parking fine.

The bracketed apology is a good example. (Sorry!) in a Teams message to a colleague is fine. (Sorry to chase!) in a formal proposal is not. Brackets are for asides, not for asking permission to exist.

The usual suspects

Just

Just is not always a hedge. In I just need the final figure, it means only. In I’m just checking in, it means please do not be annoyed with me.

Before: I’m just checking in on the report — sorry to chase, I know you’re busy. Just wondered if you’d had a chance to look?

After: Checking in on the report. Have you had a chance to look? I need your comments by Thursday so I can brief the designer.

The second version still has a friendly opening. It also has a deadline and a reason. One softener is plenty.

Sorry

Apologise for actual inconvenience. Do not apologise for the act of communicating.

Before: Sorry to bother you, sorry for the short notice, and sorry the deck is late. I just wanted to check you got it.

After: Apologies for the late deck. I have flagged the two slides that changed. Could you review by 11am?

One specific apology does more work than three vague ones. It tells the reader what went wrong and what happens next. If nothing has gone wrong, you probably do not need sorry at all.

I might be wrong, but

This is the hedge that hides a useful point. Sometimes it is genuine humility. Often it is a request for permission to have noticed something.

Before: I might be wrong, but I think the figures in section 3 don’t match the appendix.

After: Section 3 and the appendix don’t match. Can you confirm which figure is correct before we send this to the client?

If you are genuinely unsure, say so precisely: I am not sure the figures match. Can you check? That is honest. I might be wrong, but makes the reader reassure you before they answer the question.

Three edits for real work

The email chase

Before: Sorry to bother you — just a quick one. I might be wrong, but I think the invoice hasn’t been paid? No worries if not, just wondered.

After: Quick check on invoice 1042, due 24 October. Has it been scheduled? I can resend the PDF if helpful.

Quick check is a small softener, but it carries information: this will not take long. The second version also includes the invoice number, the due date and a useful next step. The client does not have to guess what you need.

The report recommendation

Before: It might just be worth considering whether there is perhaps a slight case for reviewing the timeline.

After: We recommend reviewing the timeline at the end of Q1.

Four hedges in one sentence is not caution. It is a decision someone is avoiding. If the recommendation is tentative, say why: We recommend a limited review of the timeline at the end of Q1, once the new data is in. That is still careful, but it is readable.

The client-facing update

Before: We’re sorry if this sounds confusing — we just wanted to let you know that prices may possibly change.

After: Prices change on 1 April 2026. Here’s what is changing and what you need to do.

If the news is genuinely unwelcome, keep one human line before the detail: We know price changes are never welcome. Here is what is changing and what you need to do. That is not hedging. It is acknowledgement.

When the softener stays

Keep a softener when it carries information or does a real social job:

• A first approach to a new client: I hope you are well is not a crime.
• A genuine apology for a missed deadline or a mistake.
• A bad-news message where you need to acknowledge the impact before the explanation.
• A correction where you are genuinely unsure of your ground.
• An internal message where brevity would read as panic or aggression.

Cut it when it only asks permission to exist. If the sentence works better without it, it was not politeness. It was padding.

A style-sheet rule you can paste

Keep a softener when it carries information: a real apology, a genuine first approach, a bad-news cushion. Cut it when it only asks permission to exist. One softener per request. No just and sorry in the same sentence unless something has actually gone wrong.

Add one more line for reports: No stacked hedges. One qualifier per sentence. That gives you a rule you can apply without turning every edit into a debate about tone.

Editing without sounding terse

Direct writing is not the same as blunt writing. The fix is usually not to add another apology. It is to add a next step, a reason or a specific thank you.

Try these swaps:

• I might be wrong, but can you check this? becomes Can you check this before Thursday?
• Sorry to chase becomes Following up on the deadline we agreed for 24 October.
• Just wondering if you had any thoughts becomes What are your thoughts on the two options?
• Sorry for the short notice becomes This is short notice: can you confirm by 3pm?

Read the result aloud. If it sounds like you are issuing instructions from a high chair, add one warm sentence at the start or end. If it sounds like you are apologising for having a job, cut again.

Good UK business copy does not need to grovel. It needs to be clear about who is doing what, by when, and why. Keep the manners. Lose the fog.