SOP Maker Complaints procedure
← Back to SOP Maker

Complaints procedure

PCRA wants SOPMaker to be useful and trustworthy. If you are unhappy with the service, the quality of a generated pack, or how your data has been handled, please tell us — we treat complaints as a way to improve.

Last updated: 25 June 2026 · Provider: Primary Care Research Alliance (PCRA) · Contact: daphne@pcralliance.uk

1. What you can complain about

2. How to raise a complaint

Email daphne@pcralliance.uk with:

If you would rather not email, ask your PCRA contact to pass the complaint to the data protection lead.

What we can investigate, honestly stated: the tool deletes your session data automatically within 24 hours, so for most complaints the session itself no longer exists by the time we receive them. What remains available: the generated pack you downloaded (please attach the relevant documents), the Build Manifest inside your pack's audit records (which records the generator version, the checks that ran and your organisation's access-code label), and — for up to ~30 days — our AI sub-processor's (Anthropic's) API logs, which we can ask to be checked under our agreement with them. We will always tell you which of these we used.

3. What happens next

StageWhat we doTimescale
AcknowledgeWe confirm we have received your complaint and give it a reference.Within 5 working days
InvestigateWe look into what happened, involving the relevant people and our processors (Anthropic, Render) if needed.
RespondWe give you a written response — what we found, what we have done or will do, and any lessons learned.Within 20 working days of acknowledgement; if longer, we tell you why and give a revised date.

4. If your complaint is about your data

5. If you are still not satisfied

6. About the AI-generated content

SOPMaker produces AI-assisted draft SOPs that your organisation must review and approve before use (see the Terms of Use). A complaint that a draft contained an error will be taken seriously and used to improve the tool, but please remember that catching such errors before adoption is exactly what the required local review is for — the responsibility for an SOP you have signed into use rests with your organisation.