Public record

Earlier SSEN correspondence and formal questions

A public-safe audit summary of the main emails, formal questions and feedback routes Save the Deveron Valley used before and after the first SSEN Strathbogie Hub feedback deadline.

Audit summary prepared: 30 June 2026

What this audit shows

This page does not publish raw emails. It gives a public-safe summary so residents can see that the campaign had already put substantial local evidence, process concerns and technical questions on record before the main public submission package was shared.

37outgoing emails found to direct SSEN project contacts between 23 May and 30 June 2026
1confirmed completed SSEN online feedback form submission
50formal written questions submitted by 3 June 2026

The main public-facing submission materials published on this website cover the formal 22 June response and 26 June supplementary response. This page fills the gap by summarising the earlier correspondence trail.

Public-safe audit table

This table summarises the main issues raised. It is not a full legal archive and does not include every email sent to councils, agencies, MSPs, MPs, charities or support organisations.

DateTypeMain issue raisedStatus / public note
23 May 2026Supplementary representationRiver Deveron and Atlantic salmonSubmitted to SSEN by email before the main consultation deadline.
25 May 2026Supplementary representationB9022 red squirrel zone and native black honeybee apiarySubmitted to SSEN by email.
26 May 2026Consolidated supplementary representationsProject Deveron / salmon, pearl mussel eDNA questions, B9022, black honeybee, Coachford context, and overlapping local pressuresSubmitted to SSEN by email.
26–27 May 2026Consultation reach concernHuntly resident notification and session awarenessSSEN replied and said the point was useful for improving future event advertising.
29 May 2026Forgue follow-upRegistration process concerns, maps running out, local knowledge briefing offer, and further questions to followSubmitted to SSEN by email.
29 May 2026Consolidated formal written questionsQuestions 1–25Submitted to SSEN by email and later acknowledged as part of the wider question set.
29 May 2026Additional questionsQuestions 26–27 on fire risk, wildfire capacity, Scottish Fire and Rescue Service, and private water suppliesSubmitted to SSEN by email.
29 May 2026Additional questionQuestion 28 on BESS, emerging risk and fire/emergency contextSubmitted to SSEN by email.
1 June 2026Additional questions and requestQuestions 29–40, including land rights, consultation record preservation, whole-project environmental assessment, local cumulative pressures, and linked infrastructure questionsSubmitted as separate emails to SSEN.
3 June 2026Additional questionsQuestions 41–50, including cable/landfall, consultation form equality, acknowledgement, 3D visualisation, connection routing, AI use in feedback analysis, hydrology, roads and ornithologySubmitted as separate emails to SSEN.
4 June 2026Community engagement requestRequest for Rothiemay engagement before the 26 June feedback deadlineSubmitted to SSEN by email.
5 June 2026SSEN acknowledgementSSEN acknowledged the various questions, said responses would be prepared in due course, and stated the project was still at site selection with no preferred siteUseful written status point for the public record.
8 June 2026Further questionsWhole-system options, demand modelling and consultation adequacySubmitted to SSEN by email.
22 June 2026Main formal campaign submissionMain formal response and addenda package, with public-facing evidence and questionsSubmitted by email with attachments. A separate SSEN online feedback form was also completed.
23 June 2026Receipt / online-form follow-upFeedback form clearing problem and request to confirm that online feedback, email response and attachments would be considered togetherSSEN had confirmed receipt of the email, attachments and online feedback.
24 June 2026Follow-up submissionScottish Fire and Rescue Service engagement and emergency resilienceSSEN acknowledged receipt and passed it to the project team.
25 June 2026Ground-investigation questionsGround investigation scope, equal comparison, safeguards, access basis, reinstatement, reporting and public transparencySubmitted to SSEN by email before the deadline.
26 June 2026Final supplementary feedbackNational planning guidance, cumulative infrastructure, BESS, fire resilience, rural legacy and catchment assessmentSSEN confirmed it was passed to the project team and would form part of the consultation.
30 June 2026Post-deadline transparency requestExtended feedback window, Rothiemay consultation, 3D modelling, ZTV explanation and environmental informationSubmitted to SSEN, councils, elected representatives and support organisations.

Why this matters

The early correspondence shows a consistent pattern: the community was already asking for clear answers on cumulative assessment, landscape and visual information, roads, water, wildlife, emergency resilience, feedback handling, fair comparison of shortlisted locations, and meaningful participation.

The first feedback deadline has passed, but the scrutiny has not. Local knowledge remains evidence, and a clear paper trail matters.

Confirmed online feedback record

Save the Deveron Valley completed one SSEN online feedback form submission alongside the main formal email submission of 22 June 2026.

SSEN subsequently confirmed receipt of the online feedback, email and attachments, and said they would be passed to the project team and recorded as part of the consultation process.

Because an online-form clearing problem was experienced during submission, the campaign also asked SSEN to confirm how it would prevent public feedback being lost and to make clear that feedback could also be sent by email.

Our position

Save the Deveron Valley is not against clean energy or grid reinforcement in principle.

We are asking for proper scrutiny, fair process, clear information, meaningful public participation and full cumulative assessment before decisions are made.

The deadline has passed. The scrutiny has not.