Fieldnotes.scot

The Participation Accountability Project

A public enquiry into lived experience, quiet extraction, and institutional ethical accountability.

A developing project on whether systems that claim ethics, trauma-informed change, and fairer human conditions are willing to learn from what their own processes expose.

Developing public enquiry · organisation anonymised · Stage 2 response received

Participation is not ethical just because it is invited.

This page is a public learning route, not an exposure exercise. It grows out of a live complaint process, but it does not name the organisation involved, identify people unnecessarily, or ask readers to take sides in a private dispute.

The organisation does not need to be named because the pattern is the subject. The concern is how lived experience can be welcomed, recognised, interpreted, learned from, and then made difficult to account for once boundary, authorship, credit, withdrawal, or accountability questions are raised.

The wider test is simple: can participation projects build the ethical architecture required to receive lived experience safely before that experience enters institutional interpretation?

If a project asks people to bring the truth of fragmented systems, it must not fragment accountability when truth arrives.
Read the opening fieldnote Read redacted email timeline Shared material evidence note Return to index
StatusStage 2 response received; external oversight route being prepared; central Participation Accountability concerns remain unresolved.
BoundaryNo naming, no shaming, no reputational punishment. The pattern is the subject.
DirectionField learning: better conditions for the next person invited to bring lived experience.

Update after Stage Two response

The response closes one part of the formal route, but it does not close the participation-accountability question.

18 June 2026 · anonymised process update

The response partially accepts confusion, but does not answer the live ethical sequence.

A Stage Two complaint response has now been received. It partially upheld limited issues around perceived similarities, perceived encouragement in relation to personal work, and problems with communication and contact information.

However, it did not uphold the central concerns around recognition, influence, prior engagement, assurances, withdrawal, participation processes, project development, framing, or language.

The important learning point is not simply whether a formal agreement existed, or whether external work was formally incorporated into a project output. The deeper issue is how live participation was handled: what was said, what was encouraged, what was recognised, what expectations were created, how concern was responded to, and who carried the consequences when ambiguity appeared.

The absence of formal incorporation is not the same thing as ethical clarity.

A project may be able to say that no formal use took place while still failing to examine whether its live conduct created reasonable expectation, recognitive dependence, authorship ambiguity, or harm through withdrawal and narrowing of contact.

This is why Participation Accountability cannot be reduced to paperwork. A signed form may describe participation rights, but the ethical field is created through conduct, timing, speech, access, role clarity, and the way a project responds when a participant brings more than the structure expected.

The concern now is not only what happened inside one project. It is what the response itself reveals about a wider pattern: systems may answer the safer formal question while leaving the lived sequence unanswered.

A separate redacted extract page has been prepared to show that use, non-use, protection, credit, agreement, verbal assurance, management contact, and practice change were raised before the Stage Two outcome. The extracts remove names and identifying details so that the pattern remains the subject.

A supporting shared material evidence note has also been prepared. It explains why the curated material folder is being made public: not as proof of formal organisational use, but as evidence of seriousness, scope, emotional significance, access over time, and the need for clear boundaries around recognition, use, non-use, protection, and project context.

Open shared material evidence note

The most serious unresolved question

Whether live practice changed after participant knowledge was recognised, and why that change was not made accountable.

Live sequence · practice change · accountability

No written record of influence is not the same as no influence.

The central concern is not only whether any written material was formally incorporated into a project output. The more serious issue is whether live participant knowledge, spoken concerns, and management-level engagement changed practice in the field, and whether that change was later treated as if it had not happened.

The participant account is that management-level conversations took place about treating service users with respect and understanding. After that, the practical field changed: contact roles changed, who appeared to be leading the work changed, and the participant was told more than once that they would be worked with and credited.

The credit point matters because the participant account is not that credit was later demanded after the fact. The account is that credit was raised at the point of recognition itself, within a very short period of the work being recognised as relevant to what the project was trying to do. The participant says they immediately distanced themselves from credit and made clear that the priority was not personal recognition, but seeing the work help people and improve conditions.

That sequence should not be collapsed into a later dispute about whether the participant wanted status or ownership. It raises a sharper ethical question: if there was no intention to use, adapt, carry, credit, or work with the material in any meaningful way, why was that not made clear when credit, use, non-use, protection, and agreement were already live matters?

Those statements matter. Not because they automatically create a formal contract, and not because they require a project to use a participant's work. They matter because they create expectation, ethical significance, and a duty to clarify what is happening before the participant is left carrying the ambiguity alone.

A project cannot avoid accountability for informal influence simply by failing to record the informal route through which influence occurred.

If practice changes after lived knowledge enters the room, the project needs to account for that change even if no formal output later quotes or names the participant's work. Influence is not only a line in a report. It can also be a shift in method, tone, role, conduct, framing, or the way workers begin to understand the people in front of them.

A further accountability question remains where local activity appears to have stopped or changed after concerns were raised. If there were no serious issues with practice, what explains the project no longer continuing in the same form? A responsible answer would not need to admit wrongdoing automatically, but it would need to account for the change rather than treating the concern as unrelated to what then happened in the field.

The question therefore remains: did participant knowledge alter practice? If so, who was responsible for recognising, bounding, crediting, declining, documenting, or ethically distancing from that change?

Where a response relies mainly on the absence of records and internal confirmation, it risks missing the very problem being raised: ethically significant participation may have happened in the live field without being given the governance route it needed.

Live sequence

The order matters.

Recognition, credit being raised, immediate distancing from credit, encouragement, practice change, assurance, concern, withdrawal, and denial are not separate fragments. They form a sequence, and the ethical meaning sits in the sequence.

Management

Authority cannot become invisible.

If management-level engagement changes the field, management remains part of the accountability field. Procedure cannot later erase the authority that shaped what participants experienced.

Dhalarmacological caution

Unrecorded is not unreal.

The pot may insist there is no written record of seasoning. The person eating the dhal may still reasonably ask why everything suddenly tastes different.

Core boundary

The pattern can be named without naming the organisation.

This project is not about revenge, exposure, or humiliation. If lived experience is to be treated with respect, then even critique must remain answerable to the conditions of respect.

That does not mean the account becomes soft. It means the criticism must be precise enough to protect learning from becoming spectacle.

The working principle: the organisation does not need to be named because the pattern is the subject.

What is being tested

Kindness without structure is not enough.

People inside a project may be sincere, careful, warm, frightened, constrained, or genuinely trying to do better. That matters. It prevents the story becoming a cartoon.

But good intentions do not replace ethical architecture. A project that invites lived experience needs structures capable of receiving, protecting, crediting, challenging, withdrawing from, and answering that experience without leaving the participant to carry the ambiguity alone.

The question is not whether everyone meant well. The question is whether the structure can carry what good faith opens.

What the Stage One response exposed

The response is treated here as evidence of process failure, not as an occasion for attack.

Narrow answer

Formal request is not the whole issue.

A response can answer whether work was formally requested or formally used while leaving unanswered how it was received, recognised, accessed, understood, discussed, or left ambiguous.

Alignment

Aligned work needs a route.

If work aligns with a project's concerns, the ethical question becomes sharper, not weaker: what route existed to discuss, assess, credit, bound, formalise, or respectfully distance from it?

Confusion

Confusion is not a conclusion.

Where a participant repeatedly asked for clarity, later confusion does not resolve the concern. It confirms why role, boundary, contribution, and accountability needed to be clear from the beginning.

Dhalarmacological note

Processing is not nourishment.

A system does not understand lived experience because it has processed it. A pot does not become lunch because it has held the lentils. The digestion has to remain answerable to the food.

Structural failure

The structure created conditions in which one person's conduct could carry disproportionate consequence.

The failure should be understood structurally first. The conditions were not built for a worker to gather, hold, translate, protect, credit, and remain accountable to lived knowledge safely and fairly.

That does not erase individual conduct. Conduct still matters. But the larger failure is that the structure allowed one person's interpretation, gatekeeping, or response to carry disproportionate consequence without enough ethical architecture to prevent, interrupt, or repair harm.

Canonical formulation: the structure created the conditions in which one person's behaviour could carry disproportionate consequence, and there was not enough ethical architecture to prevent, interrupt, or repair that harm.

Management and answerability

Authority cannot hide inside procedure.

Management matters because management controls routes, boundaries, access, framing, and what is later treated as official. Where managerial response narrows the issue, removes human access, or treats unresolved ethical questions as administrative inconvenience, it becomes part of the field evidence.

This is not a call to shame a manager. It is a call to stop pretending that management is neutral when it is the layer deciding what can be acknowledged, who can speak, and how the participant is made legible.

A little Dhalarmacology may help: the pot has responsibilities. If the pot clamps the lid down and then announces the lentils were always confused, the problem may not be the lentils.

The human cost of recognition being severed

This is not a minor relational side-effect. It is why the ethical architecture matters.

When lived experience is properly recognised, the person is not only being listened to in a general sense. Something deeper may be happening. A person who has lived for years without being understood may, for the first time in a very long time, feel that the shape of their life, work, pressure, and responsibility has become legible to another human being.

That is not a small event. It is especially not small when the person's life is already shaped by isolation, formal processes, care concerns, and the pain of trying to remain clear around a child they love while systems hold power over the record.

In this case, the human cost was not only that work became ambiguous. It was that the one route through which the work, the lived experience, and the wider situation appeared to be understood was removed after ground had been set and concerns had been repeatedly raised.

This should not be reduced to blame against the person who recognised the work. The point is not that the worker caused the harm. The point is that the structure did not protect the human significance of the recognition it had helped make possible.

There is a real difference between someone understanding, someone caring, someone being free to act, someone being structurally able to remain in contact, and a project having the ethical architecture to carry what recognition opens.

Where someone has not felt properly understood for many years, the sudden removal of the one person who appeared to understand them, their work, and their situation with their child is not a minor communication adjustment. It can intensify loneliness, destabilise recovery, and make a complaint process feel not only unresolved, but personally severing.

The ethical issue is not that any worker owed personal rescue. The ethical issue is that the project created conditions in which one person's recognition became profoundly important, then did not appear to have a safe, clear, accountable way to hold the consequences when that recognition became structurally difficult.

The ambiguity is the issue

This is not an attempt to personalise blame. It is a record of why clearer ethical boundaries were needed.

Boundary failure

Where project interest, individual interest, encouragement, credit, and possible use blur, the participant should not be left carrying the ambiguity.

This account should not be read as an attempt to blame one worker for the whole situation. The concern has always been the ambiguity created after the participant had been clear about the work, the conditions of use, and what collaboration would need to look like in practice.

The difficulty was not simply that encouragement was given. The difficulty was that encouragement, recognition, discussion of being worked with and credited, individual professional interest, possible separate use, and project participation were not clearly distinguished at the time they needed to be.

Where a participant explains the contents and conditions of their work before sharing it, later comments about working with the participant, crediting them, or recognising the value of the work cannot safely be treated as ordinary encouragement unless that boundary is made clear.

The ethical question is therefore not whether every comment by an individual project member was automatically a formal project commitment. The ethical question is why the participant was left in a field where the difference between project interest, individual professional interest, personal encouragement, possible use, non-use, credit, and collaboration was not made clear.

That uncertainty matters because participation takes place under unequal conditions. The project holds the route, the language, the record, and the power to later define what did or did not count. The participant should not be expected to absorb the consequences of ambiguity that the structure was responsible for clarifying.

Working line: this is not about blaming a person for ambiguity. It is about asking why the structure allowed ambiguity to become consequential after clarity had already been given.

Answerability theorem

No serious knowledge can be sustained where the interpreting layer stops answering to the living field.

A system does not understand lived experience because it has processed it. It understands only when the processing remains answerable to the life it has received.

Here, lived experience entered the project; institutional interpretation gained authority over it; the participant-source became vulnerable to that interpretation; and the response appeared to process the issue without metabolising the harm.

Primary material

The source is not inferior to the analysis.

A participant's lived experience is not raw material waiting to be made intelligent by a project, professional, researcher, manager, or institutional frame.

Primary material is the nourishment. Interpretation is digestion. Distortion occurs when digestion mistakes itself for the food.

What this project will not do, and what it will ask

The aim is field learning, not reputational punishment.

This project will not

No naming. No shaming. No revenge.

  • It will not name the organisation or identify people unnecessarily.
  • It will not flatten sincere workers into villains.
  • It will not treat humour as permission to humiliate.
  • It will not replace formal process with public accusation.
  • It will not reproduce extraction in reverse.
This project asks

What ethical architecture must exist before invitation?

  • How are role, boundary, and contact routes defined before lived experience is invited?
  • How is contribution recognised before formal use is decided?
  • How are authorship, influence, credit, withdrawal, and non-use discussed without ambiguity?
  • How are human-AI collaborative works handled without treating AI involvement as ownerlessness?
  • How does a project protect both workers and participants when recognition becomes ethically significant?
  • How does management remain answerable without turning concern into defensiveness?

What participatory projects must learn

The constructive direction is practice change: not better slogans, but better conditions.

Before participation

Define contact routes, complaint routes, withdrawal, authorship, AI collaboration, credit, non-use, and how participant influence will be recognised before contribution is invited. If named routes are provided, keep them live, accurate, and intelligible.

During participation

Do not let warmth, access, or recognition become informal extraction. If a person's thinking shapes the room, the project needs a way to account for that without turning the person into a problem when they ask for clarity.

After concern is raised

Do not retreat into hierarchy. Do not make the participant carry the ambiguity alone. Answer the process questions with enough honesty for practice to change.

Final working line: participation without answerability is extraction risk. A Stage 2 response does not close the learning question where the lived ethical sequence remains unanswered, especially where live practice change, verbal assurance, credit being raised and immediately deprioritised, participant expectation, and later changes to the practical field are treated as if they can disappear because they were not properly recorded. The repair is not shame. The repair is sequence, responsibility, protection from repeated harm, external accountability where needed, and better conditions for the next person.