Behaviour Incident Spreadsheet Imports
Bringing incident data in, and rolling a batch back.
Purpose
This workflow imports school behaviour incident spreadsheets and converts valid rows into student observations and non-diagnostic reasoning reports.
Where to go
- Sign in.
- Open
/dashboard/imports. - Use
Import incident login the top-right of the cohort import dashboard to open the importer dialog.
/dashboard?tab=imports redirects straight to /dashboard/imports, so users do not need to click through an intermediate dashboard card.
Preview an import
- Choose a student.
- Upload or paste spreadsheet rows through the importer.
- Map columns:
- Date/time.
- Severity.
- Behaviour/category.
- Narrative.
- Assignee if present.
- Click preview.
- Review validation outcomes.
Duplicate detection
senco checks duplicate risk using incident date/category/text patterns and existing observations.
Rows may be:
- Valid.
- Invalid.
- Duplicate.
- Skipped.
Commit an import
- Review the preview.
- Confirm valid rows.
- Commit the import.
- Valid imported rows become observations and reasoning reports.
- Escalation tasks are created if a report indicates SENCO review or urgent safeguarding risk.
Import history
- Open
/dashboard/imports. - Review cohort outcomes and duplicate queues immediately.
- Use
Import incident logonly when you need to upload a new file. - Open a batch detail page at
/dashboard/imports/[id].
Row-level review
On the batch detail page:
- Review each row.
- Correct editable row text where needed.
- Override duplicate status where appropriate.
- Skip rows that should not be imported.
- Reprocess rows after ontology updates.
Rollback
- Open the import batch.
- Use rollback/undo for recently imported rows.
- Confirm the action.
- Imported observations and reports from that batch are rolled back where supported.
Outcome summaries and cohort dashboard
Use import outcome analytics to review imported rows, duplicate rows, skipped rows, escalation rows, and cohort-level patterns for SENCO review.
Product phase note
The Excel import workflow is complete for the current product phase. Future work should prioritise core reasoning, review, reporting, and governance unless a real import gap is found.