The problem
Policy documents, review dates and staff acknowledgements can be scattered across Word files, spreadsheets and email, making the current approved version difficult to follow.
AccordPolicy
In developmentA policy-management platform I’m building for independent homecare providers in England, bringing documents, reviews, approvals and staff acknowledgements into one workflow.
An active product in development, with a public launch list. The platform is not yet generally available.
- My role
- Founder, designer and developer
- Platform
- Web application
- Built with
- Next.js, TypeScript, Supabase, Tiptap
My approach
Build around the policy’s journey from draft to review, approval and staff use, with clear version history and a manager responsible for each decision.
The result
A working product preview, an original draft template library and a live launch website. Development and preparation for early access are ongoing.
The decisions
behind the product.
My experience in care operations shapes this project: policy work needs to connect the wording of a document with the people who review, approve and use it.
Start with one care setting
Focus the language, templates and workflow on independent homecare providers in England so the product has a clear starting audience.
Make the approved version clear
Design around explicit draft, review and approval states, with the document’s history kept close to the current wording.
Support different starting points
Let providers begin with an original draft template, import a document they have permission to use or write a policy from scratch.
Keep managers in control
Build optional AI help around explanations and suggested wording. Review, approval and responsibility stay with the provider.
From thinking to making.
A workspace around the document
The Next.js and Supabase application brings together the policy library, a Tiptap editor, document imports and review decisions. The product preview makes that workflow tangible while development continues.
An original draft library
Prepared 60 original draft policies and 60 matching forms, with a route for providers to adapt, review and approve each document for their own service.
A clear introduction before launch
Designed and built the public website around the care team’s work, with illustrative product walkthroughs, clear availability messaging and a consent-based launch list.
What came out of it.
Working product preview
A concrete policy-management workflow to develop and evaluate ahead of general availability.
Original draft templates
60 policy drafts and 60 matching forms prepared as starting points for provider review and customisation.
Public launch website
A live introduction to the product with a launch list for interested homecare providers.
Constraints, lessons and next steps
The constraints
- The product is in development; customer adoption and operational outcomes have not yet been established.
- Templates need provider customisation and review before use. The platform does not guarantee regulatory compliance.
- AI suggestions must remain reviewable and separate from a manager’s approval.
What I learnt
- Next steps include evaluating the workflow with providers and preparing the product for early access.
- Care-sector experience helps frame the problem, but the product still needs validation through use.
- Clear approval boundaries are part of the user experience, particularly when AI assistance is involved.