Progress overview
Filter pupils and cohorts to surface patterns, concerns and changes without rebuilding the same spreadsheet for each review.
Planned feature set
DAS Board is planned as a single working view for staff responsible for pupil progress and additional provision. It brings progress, intervention and access-arrangement records into one pupil context, so the next action does not disappear between spreadsheets, inboxes and meetings.
Filter pupils and cohorts to surface patterns, concerns and changes without rebuilding the same spreadsheet for each review.
Record an intervention, assign an owner, set a review point and keep the outcome attached to the original concern.
Give authorised staff a clear reference for approved arrangements, evidence status and review dates. The system supports the process; it does not decide entitlement.
Show actions awaiting review, overdue follow-up and the information another colleague needs to pick up a case responsibly.
Why it earns a place
A product should do more than put a polished skin over the same institutional friction.
Progress, interventions and access arrangements are connected around the pupil instead of being treated as unrelated admin.
The useful unit is not an amber box. It is a named action, an owner, a review point and an outcome.
Staff remain responsible for interpretation and decisions; the product provides evidence, workflow and an accountable record.
Expected impact
The intended impact is earlier follow-up and clearer ownership, with less staff time lost reconciling separate records before useful work can begin.
No invented stopwatch claims. Numeric time savings will be published only after pilot schools have established a baseline and measured the same task using the product.
Security · UK GDPR
These are requirements for the planned service, not a claim that an unfinished product is certified or that software makes a school automatically compliant.
Define the minimum fields needed for each job, validate imports and avoid copying wider MIS records into the product without a clear purpose.
Use role-based permissions, least-privilege defaults and auditable administrative actions for data that should not be visible to every member of staff.
Treat encryption in transit and at rest, tested backups, retention controls and reliable deletion as baseline technical requirements.
Prepare a clear data map, processing agreement, subprocessor list, retention schedule, technical-measures summary and practical DPIA support before contracting.