Editing5 min read

How to tell which hedging words to keep in a work draft

Hedging words in professional writing are not clutter by default. Some report genuine uncertainty; others are habit that softens a point you are certain of. Read each hedge as a claim about your own confidence. If you would stand behind the sentence without it, cut it. If removing it promises more than you can deliver, keep it. The two examples below show each case.

Treat every hedge as a confidence claim

A hedge does one of two jobs. It either tells the reader how sure you are, or it hides that you have not decided. The first is information; the second is noise. The test is simple: ask what you would say if a colleague across the desk asked the same question. If you would state it plainly, the hedge is habit. If you would still qualify, the qualification belongs in the draft.

This matters because hedges stack. A sentence with might, possibly, and I think in it does not sound three times as careful; it sounds as if the writer has not checked. Editors often cut all three on reflex, which creates the opposite problem: a promise the writer never meant to make. The skill is knowing which hedge carries the uncertainty and which only pads it.

Keep this guide separate from decisions about vague deadlines. The question here is not which date to name but whether the qualifier in front of a claim is doing honest work.

Find the hedge that has to stay

Some hedges protect a real limit. If you do not control the outcome, removing the qualifier turns a report into a guarantee. That is the risk in optimistic editing: the sentence reads tighter, and the writer has now committed to something they cannot control.

The clearest case is the estimate that depends on someone else. The word should is doing real work here because the timeline rests on a dependency, not on the writer's own schedule.

Before

The migration should be finished by Friday. The database team is still checking the export, and we have not heard back from them. If their check finds a problem, the work may run into the following week.

After

The migration should be finished by Friday, but it depends on the database team's export check. We have not heard back from them yet; if their check finds a problem, the work may run into the following week.
The hedge stays because removing should would promise Friday while the writer is still waiting on the database team. The edit keeps the uncertainty and moves it next to the reason, so the reader sees why the date is not fixed.

Cut the hedge that only repeats your own confidence

The opposite error is the hedge on something you have already checked. If you reviewed the figures yourself and found the error, the phrase I think adds nothing except a suggestion that you did not really look.

Here the writer has the facts in hand: the totals were checked and the discrepancy was found. Removing the softening phrase does not overclaim, because the writer is describing their own completed work.

Before

I think there may possibly be an error in the Q3 totals. I checked them twice and the discrepancy is in the second column. I just wanted to flag it in case it matters.

After

There is an error in the Q3 totals. I checked them twice and the discrepancy is in the second column.
The writer did the work: the totals were checked twice and the error was located. Cutting the stacked hedges and the just-wanted-to-flag phrase leaves a claim the writer can defend, with the evidence still attached.

Keep negations and conditions attached to their hedges

When you cut a hedge, check what else leaves with it. A hedge often sits beside a negation or a condition, and removing the wrong word flips the meaning. The sentence does not guarantee the outcome is different from the sentence that does not promise it, but they read very differently to a reader scanning for a commitment.

The safe edit keeps the clause whole. If the qualifying phrase and its condition belong together, move them as a unit rather than trimming inside them.

Before

If the vendor confirms receipt before Thursday, we can probably still meet the 15 March handover. This is not guaranteed, because the final check is on their side.

After

If the vendor confirms receipt before Thursday, we can probably still meet the 15 March handover. This is not guaranteed, since the final check is theirs.
The hedge and the negation both stay because together they carry the real uncertainty about 15 March. The edit only tightens the reason clause, so the reader gets the dependency without losing the qualification.

Run a four-question check before you cut

Work through each hedge in the draft with the same short list. It takes less time than rereading the whole message and catches both the empty hedges and the load-bearing ones.

If you use a rewrite action such as Retone in Lightphrase to tighten a paragraph, compare the result against the original before accepting it. Names, numbers, dates, and commitments are exactly what a tidying pass is most likely to shift.

  • Do I control the outcome? If not, keep the qualifier.
  • Have I already verified the claim? If yes, the hedge is probably filler.
  • Does the hedge sit beside a negation or a condition? Move it as a unit.
  • Would I say this plainly to a colleague at my desk? If so, the draft can say it plainly too.

Take it into your next draft

Before you send, read the draft once looking only for hedges. For each one, ask whether it reports a real limit on what you know or control. Keep the ones that protect a genuine uncertainty, especially where a dependency or a negation is involved. Cut the ones that pad a claim you have already checked. Then reread the sentence to confirm the meaning still matches what you intended to promise.