Initial thematic review · 1 September 2026

What contributors are telling us so far

Inside MECCA has completed an initial thematic review of the information submitted to the project. This records what is recurring within the material received. It is not a finding about MECCA, and a submission is not treated as proof.

Shares are of all accounts reviewed · submission volumes and counts are not published in this update
What we are doing now
Initial thematic review

Reading and coding the substantive accounts received so far.

Submission volumes
Not published

How many accounts sit behind these shares is held by the project and is not part of this update.

Last reviewed
1 September 2026

This page will be revised as accounts are followed up and clarified.

Thematic coding

Recurring themes

How often each theme appears, as a share of the accounts reviewed. Themes overlap — a single account can carry several — so the shares do not total 100%. The number of accounts behind these shares is not published, and the shares describe this material only, not the wider workforce.

Order
View

Where the material clusters

The strongest recurring signal

Most frequently raised
83%
of accounts reviewed — the most frequently recurring theme
Management conduct

Across the accounts, contributors commonly describe interconnected concerns involving perceived favouritism, access to development and promotion, bullying or belittling behaviour, limited responses to concerns raised internally, and impacts including anxiety, distress, resignation or loss of employment.

Reading the overlap
Themes are not mutually exclusive

A single account can be coded to several themes at once, which is why the shares add to well over 100% and cannot be added together.

The clustering visible here is a property of the material received, not a measurement of the workforce. A theme raised less often has not been ruled out or ranked as less serious — it has simply been described less often by the people who chose to submit.

Important context

Method and limitations

How this review was done
  • 01Submitted records were preserved in the state received.
  • 02Test, filler and other non-substantive entries were removed before analysis.
  • 03Each remaining account was read and coded to one or more recurring themes.
  • 04Counts were tallied per theme and expressed as a share of the accounts reviewed.
  • 05No account was quoted, attributed or identified in this update.
What this cannot show
Self-selected, and unverified unless stated

Contributors chose to come forward, so the material cannot be treated as a representative sample of the workforce. Nothing here has been verified unless expressly stated otherwise.

Submission volumes are not published at this stage, so the shares describe the accounts reviewed and nothing beyond them. Theme labels summarise what a code covers — they are not quotations, and they do not assert that any described event occurred.

Next

What happens next

Next stage
Follow-up and evidence review

Careful follow-up, evidence review and clarification with contributors who have given permission to be contacted.

Contributor control
Permissions remain separate

Contact permission, verification, consent and publication permission continue to be treated as four separate decisions. Giving one does not give the others, and any of them can be withdrawn.

No contributor has been identified or quoted in this update.

This section describes the contributor submissions received by the project. It is not a finding about any organisation or individual.