An editorial coverage and distribution audit of a community-focused publication
Publication: 11 November 2026 | Type: Editorial coverage audit | Status: Descriptive learning paper, not peer-reviewed research.
Executive summary
The Tees exists to make local stories, activities and achievements more visible. That is a meaningful editorial ambition, but its evidence needs to distinguish the availability of journalism from what the journalism changes.
An audit of the publication database identified 763 story records, of which 722 were marked published, 39 archived and two drafts. The published records span dates from 2020 to 2026, including 430 dated 2026. They cover Middlesbrough, Stockton-on-Tees, Hartlepool, Redcar & Cleveland, Darlington and stories labelled Tees Valley-wide.
The largest subject categories in the published archive are transport (189), arts and culture (123), community (99), education (89), health (69) and business (45). These counts reveal a broad editorial remit, while also showing that coverage is not evenly distributed across geography or subject.
The central conclusion is constructive: The Tees can already account for a substantial body of local publishing. A second measurement layer is required to understand who encounters that work and whether it helps people discover events, support, opportunities or positive community activity.
Purpose and research question
What places and subjects are represented in The Tees' published story database, and which additional measures would turn a publishing activity report into an evidence-based account of public value?
Data and method
The Tees' Base44 Story entity was queried in two paginated batches, retrieving all 763 stored story records as at 11 November 2026. Records were grouped by their publication_status, area, category and year derived from published_date. Only 722 records marked published were included in the main geographic and topical breakdowns.
The SocialQueue entity was separately reviewed for workflow status, with 204 stored queue records counted. A PageView event log also exists, but raw events were deliberately not used as a unique-reader measure: automated traffic, duplicate views, retention and user identification were not sufficiently validated in this audit.
No article body text, contributor identities, contact information or reader tracking data were transferred. Categories were reported as actually stored rather than silently reclassified; some near-duplicate category names therefore remain a metadata issue.
Findings
Place coverage
Among 722 published story records, area labels are:
- Middlesbrough: 216
- Stockton-on-Tees: 174
- Hartlepool: 113
- Redcar & Cleveland: 104
- Darlington: 71
- Tees Valley-wide: 41
- Missing area: 3
These figures show the distribution of recorded stories, not the relative quality of local reporting. Fairness cannot be judged without comparing these figures with community need, population, event volume and other relevant benchmarks.
Subject coverage
The six largest unnormalised category labels are transport (189), arts_culture (123), community (99), education (89), health (69) and business (45). Transport's prominence reflects a particular archive mix and should not automatically determine future priorities. Category variants such as culture, arts-culture and capitalised names appear elsewhere in the data and require normalisation.
Publication and distribution
Of 763 total story records, 722 are marked published. 430 published records carry a 2026 publication year. All 722 published records have a source URL recorded and a verified flag, but the meaning and consistency of that verification have not been independently inspected. There are 721 non-empty image URL fields, which do not guarantee that every image loads or has reusable rights.
The social queue contains 204 items: 27 published, 26 partially published, 41 ready and 110 draft. These are workflow states, not independently confirmed social impressions or reach.
What these findings mean
The geographic and topical picture can now inform editorial decisions. It can reveal underrepresented places, help avoid over-reliance on one type of story and invite community organisations to suggest positive news that would otherwise remain invisible.
A publication also contributes to public life through accuracy and trust. That requires more than a high content count: clear provenance, image rights, corrections, accessibility and proof that the material is being seen and used. The next phase should pair editorial output data with reliable reader and community-feedback indicators, without turning the site into a surveillance exercise.
Limitations and safeguards
The database audit does not review every story for accuracy, fairness, public benefit or originality. Published records may include historic archive imports, updated content and duplicate slugs. In fact, 722 published records correspond to 721 distinct stored slug values, requiring a metadata check. Stored verification flags are internal states, not independent fact-checking certificates.
Article counts are not unique readers, reading time, reach, changed behaviour or community outcomes. SocialQueue statuses are not the same as verified posts on each platform. PageView event counts cannot safely be converted into actual human visitors without traffic-quality controls. Area labels and categories are editorial metadata that may change over time.
Practical recommendations
- Publish an annual editorial coverage dashboard showing local authority area, topic, new-versus-archive content and corrections.
- Normalise category names and investigate any duplicate or missing slugs.
- Track successful page loads and human-readable engagement in an aggregate, privacy-conscious way; distinguish automated traffic and repeated visits.
- Use opt-in reader feedback to record whether articles helped people find an event, service, business or community project.
- Maintain image licensing and featured-image checks separately from the mere presence of an image URL.
- Report platform distribution only from confirmed provider receipts, not queue intentions.
- Invite story leads from underrepresented communities and review representation rather than simply maximising article volume.
Reproducibility and next review
Source: The Tees Story and SocialQueue entities, snapshot 11 November 2026. The published-story total is a status count, with 2026 determined by the first four characters of published_date. Geographic and category counts use the raw stored labels. Any future version must disclose whether historic imports, revised stories and duplicates are counted separately.
Source and privacy note
Aggregated data from The Tees Story and SocialQueue entities, queried 11 November 2026. PageView metadata was inspected but not treated as verified unique reach. No reader or contributor personal information was exported.