Connect WeKare to your private database
Enter the two details you saved in Notes. Only use your publishable key – never a secret or service-role key. They remain in this browser.
Not connected yet.
Registered Manager sign-in
Learning themes
Reviews and actions needing attention
Briefings are assembled from existing record fields – not generated or verified by external AI. Check the original record before decisions.
LLSI register
Themes & trends
Each LLSI counts once by its primary learning theme. Secondary themes are tracked separately and are not added to the pie chart.
Primary learning themes
Top 5 recurring themes
Monthly LLSI volume
All learning themes – including secondary areas
One Jason may appear in several areas. Bars show the number of different LLSIs linked to each theme, so totals may exceed the number of records.
Meeting themes over time
Stacked columns count learning-theme mentions across recorded meeting updates. A meeting can contribute to multiple themes. Historic meetings only appear after they are entered.
Open versus closed Jasons
Two lines show the number of open and closed records at each reporting period end, using preserved status changes. “Open” includes Monitoring and Embedded into Practice. History begins when versioning was enabled; earlier statuses cannot be reconstructed.
New LLSI
Meeting updates & record history
Meeting updates are saved separately from this LLSI. Original reports and earlier revisions stay in the history table.
Privacy checks
Our convention is ClientJH, StaffJ, FamilyMS and ProfessionalJB. Initials are still pseudonymous data. Automatic checks flag possible identifiers but cannot guarantee anonymity.
This checker identifies possible names, email addresses, phone numbers and postcodes. A manager must review the narrative and indirect identifiers (rare incidents, dates, locations and family relationships) before considering cloud storage.
📥 Import an LLSI report
Adding a report we’ve prepared together? Select its AI draft JSON file below. The report opens for your review before anything is saved.
This adds one LLSI; it does not replace the rest of your register. You'll check the details and privacy before saving.
Governance exports
Export all cloud-loaded Jasons, even when the register has filters applied. Excel and CSV contain detailed data for internal management; the meeting handout contains only aggregate learning.
For disaster recovery, continue to use the separate complete JSON backup below – neither the spreadsheet nor handout replaces it. Review exported information before circulating it.
Backups & maintenance
WeKare schedule: export on the last working day of a month in which records changed, and after major imports or changes. Save the dated file to the restricted WeKare OneDrive backup folder. Printed reports are an independent contingency, not a replacement for the JSON register.
Cloud backups: A V5.2 JSON export captures both current records and the separate historical timeline retrieved from Supabase in the current signed-in session. Always check the record count before relying on the export. Keep dated copies in your WeKare OneDrive. The check below is PREVIEW ONLY: it does not restore, import, delete, overwrite, or change any cloud records.
After downloading, open the JSON file, check the backup preview below, place it in OneDrive, then confirm. The reminder is recorded only in this browser; it does not verify OneDrive storage or synchronise to your phone.
Restoring into the live Supabase database is intentionally disabled. A fictional record has been restored to a separate recovery project, but full system restoration and permissions still require documented verification.
Demo records are only added when the register is empty.