Care Logging App Development
Budget: £250 – £750 GBP
Project Brief: SafeCareLogs
Overview
SafeCareLogs is a UK-focused safeguarding and record-keeping web application designed primarily for foster carers, with future expansion to homecare and residential care.
The system allows carers to record daily logs, incidents, medication administration, and observations in a way that is secure, time-stamped, non-editable, and suitable for scrutiny during reviews, inspections, or allegations.
This is not positioned as a productivity app, but as safeguarding evidence of good practice.
Core Design Principles
Safeguarding-first (records must be defensible)
Non-technical users (carers, families)
Low friction (quick logging, drafts allowed)
Accountability (clear authorship, timestamps, audit trail)
UK compliance mindset (GDPR, inspections, social worker expectations)
User Roles
1. Family Admin (Primary Account Holder)
Created at signup
Manages:
Carers (add / edit / disable)
Children / placements
Household settings
Can also act as a carer and log entries
Has access to the admin dashboard
2. Carer
Logs daily interactions, incidents, medication
Has a PIN + password for login
Logs show the carer’s name (not PIN)
Cannot delete logs (only void/archive where permitted)
3. Global Admin (System Owner)
Manages tenants (households)
Sees subscription/trial status
Can enable/disable accounts
No access to tenant content unless explicitly designed
Authentication Model
Tenant-based system
Each household has:
A unique 8-digit account number
Login flow: (can be changed to whatever you feel best)
Account number
Carer PIN (4 digits)
Password
Per-carer passwords
Sessions are server-side
Tenancy & Subscriptions
One tenant = one household
Subscription applies to the household, not per child
Initial model:
30-day free trial
Monthly or yearly paid plan
Account states:
Trial
Active
Read-only (expired)
Disabled
Read-only accounts can view/export but not add logs
Core Features
Logging
Log types:
Daily logs
Incidents / concerns
Medication administration
Logs include:
Event date/time
Entry creation timestamp
Author (carer)
Target (child or household)
Logs cannot be edited after saving
Drafts are supported
Drafts
Carers can save unfinished logs
Drafts are private to the author
Drafts can be discarded or finalised
Supports medication drafts
Late Entries
If a log is entered after the event time:
Automatically flagged as Late Entry
Requires a reason for late entry
Late reason is visible when viewing logs
Offline / Resilience
System is designed to tolerate:
Page refresh
Double submission
Slow or intermittent connectivity
Duplicate submissions are prevented via client submit IDs
Children / Placements
Each child has:
Basic profile
Additional notes (e.g. known triggers, health conditions)
Child information can be viewed separately from editing
Logs link to children where applicable
Medication Logs
Medication logs capture:
Medication name
Dose and unit
Route (oral, topical, etc.)
Outcome (given / refused / missed)
PRN flag
Reason if not given
Medication data is attached to a log entry
Attachments
Logs can include file uploads (e.g. photos)
Stored securely
Can be:
Viewed inline (thumbnails)
Opened fullscreen on mobile
Downloaded when authorised
Reporting & Export
Logs can be:
Viewed chronologically
Filtered
Exported (PDF/CSV planned)
Designed for:
Social worker review
Inspection
Allegation timelines
UI / UX
Desktop-first, but mobile-usable
Clean, minimal interface
No clutter or unnecessary options
Professional tone (not “techy”)
Language avoids “subscription” and focuses on cover / safeguarding
Tec Expectations (High Level)
Web-based (PHP + MySQL or equivalent)
Server-side validation
Secure session handling
Prepared statements
GDPR-aware data handling
Clear separation of:
Routing
Auth
Business logic
Views
Non-Goals (Explicit)
No real-time monitoring
No automatic sharing of data
No AI interpretation of logs
No deletion of historical records by carers
Success Criteria
A foster carer should be able to:
Log daily care in under 60 seconds
Prove what happened, when, and by whom
Defend themselves with clear records if questioned months later
Feel protected, not monitored
Overview
SafeCareLogs is a UK-focused safeguarding and record-keeping web application designed primarily for foster carers, with future expansion to homecare and residential care.
The system allows carers to record daily logs, incidents, medication administration, and observations in a way that is secure, time-stamped, non-editable, and suitable for scrutiny during reviews, inspections, or allegations.
This is not positioned as a productivity app, but as safeguarding evidence of good practice.
Core Design Principles
Safeguarding-first (records must be defensible)
Non-technical users (carers, families)
Low friction (quick logging, drafts allowed)
Accountability (clear authorship, timestamps, audit trail)
UK compliance mindset (GDPR, inspections, social worker expectations)
User Roles
1. Family Admin (Primary Account Holder)
Created at signup
Manages:
Carers (add / edit / disable)
Children / placements
Household settings
Can also act as a carer and log entries
Has access to the admin dashboard
2. Carer
Logs daily interactions, incidents, medication
Has a PIN + password for login
Logs show the carer’s name (not PIN)
Cannot delete logs (only void/archive where permitted)
3. Global Admin (System Owner)
Manages tenants (households)
Sees subscription/trial status
Can enable/disable accounts
No access to tenant content unless explicitly designed
Authentication Model
Tenant-based system
Each household has:
A unique 8-digit account number
Login flow: (can be changed to whatever you feel best)
Account number
Carer PIN (4 digits)
Password
Per-carer passwords
Sessions are server-side
Tenancy & Subscriptions
One tenant = one household
Subscription applies to the household, not per child
Initial model:
30-day free trial
Monthly or yearly paid plan
Account states:
Trial
Active
Read-only (expired)
Disabled
Read-only accounts can view/export but not add logs
Core Features
Logging
Log types:
Daily logs
Incidents / concerns
Medication administration
Logs include:
Event date/time
Entry creation timestamp
Author (carer)
Target (child or household)
Logs cannot be edited after saving
Drafts are supported
Drafts
Carers can save unfinished logs
Drafts are private to the author
Drafts can be discarded or finalised
Supports medication drafts
Late Entries
If a log is entered after the event time:
Automatically flagged as Late Entry
Requires a reason for late entry
Late reason is visible when viewing logs
Offline / Resilience
System is designed to tolerate:
Page refresh
Double submission
Slow or intermittent connectivity
Duplicate submissions are prevented via client submit IDs
Children / Placements
Each child has:
Basic profile
Additional notes (e.g. known triggers, health conditions)
Child information can be viewed separately from editing
Logs link to children where applicable
Medication Logs
Medication logs capture:
Medication name
Dose and unit
Route (oral, topical, etc.)
Outcome (given / refused / missed)
PRN flag
Reason if not given
Medication data is attached to a log entry
Attachments
Logs can include file uploads (e.g. photos)
Stored securely
Can be:
Viewed inline (thumbnails)
Opened fullscreen on mobile
Downloaded when authorised
Reporting & Export
Logs can be:
Viewed chronologically
Filtered
Exported (PDF/CSV planned)
Designed for:
Social worker review
Inspection
Allegation timelines
UI / UX
Desktop-first, but mobile-usable
Clean, minimal interface
No clutter or unnecessary options
Professional tone (not “techy”)
Language avoids “subscription” and focuses on cover / safeguarding
Tec Expectations (High Level)
Web-based (PHP + MySQL or equivalent)
Server-side validation
Secure session handling
Prepared statements
GDPR-aware data handling
Clear separation of:
Routing
Auth
Business logic
Views
Non-Goals (Explicit)
No real-time monitoring
No automatic sharing of data
No AI interpretation of logs
No deletion of historical records by carers
Success Criteria
A foster carer should be able to:
Log daily care in under 60 seconds
Prove what happened, when, and by whom
Defend themselves with clear records if questioned months later
Feel protected, not monitored