Selective Scepticism: How Attribution Shapes War Reporting

I read a lot of news. Probably more than is healthy.

And lately, I keep tripping over the same problem. Not outright errors. Not fake facts. But something subtler, and in some ways more troubling: uneven precision.

Here’s a short example from a BBC article reflecting on global conflicts in 2025: (You can read the whole piece here.)

“There is Ukraine of course, where the UN says 14,000 civilians have died. In Gaza, where Israel’s prime minister, Benjamin Netanyahu promised ‘mighty vengeance’ after about 1,200 people were killed when Hamas attacked Israel on 7 October 2023…”

A few sentences later:

“Since then, more than 70,000 Palestinians have been killed by Israeli military action, including more than 30,000 women and children according to Gaza’s Hamas-run health ministry – figures the UN considers reliable.”

Nothing here is obviously false. But the way it’s written does a lot of quiet work.

Let’s start with attribution

In Ukraine, we’re told:

“the UN says 14,000 civilians have died”

That number is presented as stable, authoritative, and uncontested.

In Gaza, the number is framed very differently:

• It’s attributed to a “Hamas-run health ministry”

• The governance of Hamas is explicitly named

• Only then are we told the UN considers the figures reliable

If the UN considers the figures reliable, why not lead with the UN in both cases?

This kind of layered attribution introduces doubt even while claiming reassurance. It’s not wrong, but it feels different. And as a reader, I couldn't help but notice that feeling. Something seemed off.

Then there’s the flashback problem

Notice what context we’re given.

For Gaza, the article pauses to remind us:

• Hamas attacked Israel on 7 October 2023

• About 1,200 people were killed

• Hostages were taken

For Ukraine, we get:

“Ukraine of course…”

No mention of:

• Russia’s invasion

• How or when the war began

• Why civilians are dying

One conflict is given a clear origin story. The other is treated as background noise.

That matters.

Why this shapes how we read

When coverage consistently:

• Explains why one war began

• But assumes the causes of another are already understood

…it subtly assigns responsibility differently.

This isn’t about telling readers what to think.

It’s about what information is front-loaded, what is backgrounded, and what is questioned.

Bias doesn’t always shout. Often, it simply whispers.

Is this intentional? Probably not. More likely, it’s habit.

Editors know Gaza coverage is heavily scrutinised, so they over-attribute. Ukraine feels settled in the public mind, so context gets trimmed or just ignored.

Risk management replaces consistency.

But good journalism isn’t about managing risk. It’s about managing clarity.

What better looks like

This isn’t a call to drop attribution or context. It’s a call to apply them evenly.

• If casualty figures need caveats, give them everywhere

• If a conflict needs a flashback, give it consistently

• If the UN is your authority, let it be the authority

Precision isn’t pedantry. It’s fairness.

Why I’m writing this

I’m a technical writer by trade. My job is to notice when language does more than it says it’s doing.

And I’m convinced I’m not the only reader who feels uneasy when stories technically say the right thing, but structurally lean one way or another.

That’s what Write Right is about. Not gotchas. Not outrage. Just slowing down and asking: does this say what it means to say?

If it doesn’t, we can do better.

https://www.bbc.com/news/articles/cj4qp17e1lqo