Exporting your data
Your data is yours. When you need it in a spreadsheet — for a report, your IR team, or a board paper — First Six exports it as CSV, and packages the headline support story as a ready-made evidence pack.
What you can export
The export area lets you download, per dataset:
- Cohort morale — the pulse data across all weeks.
- Help requests — category, priority, handler, week, status, assignee, and the student's details.
- Activity / audit trail — who did what, when.
- Weekly content — events, blocks, and to-dos by week.
- Library — quick links, help routes, and Ask Anything answers and questions.
There's a one-click "download everything" that chains them all, one CSV per table.
Help-request exports include student details and notes. Treat downloaded files as sensitive: store them where your institution's data-handling rules allow, and don't forward them casually. The export screen flags this for a reason.
The support-for-students evidence pack
Separately, you can download a support-for-students report — a 90-day snapshot of support activity designed for institutional reporting. It's the board-ready version of the story your day-to-day data tells. The institution-facing description is in the audit log and evidence pack.
Where the numbers come from
Exports reflect what you see in the console: the same pulse behind insights, the same engagement behind reach. Small groups are suppressed in aggregate views to protect individuals; raw operational exports (like your own cohort's help requests) are for the staff responsible for those students.
Common questions
What format are exports?
CSV — opens directly in Excel, Google Sheets, or whatever your IR team uses.
Can I schedule automatic exports?
Exports are on-demand from the console. For programmatic access, that's a developer integration conversation, not a self-serve schedule.
Does exporting change anything?
No — it's read-only. The export itself is recorded in the activity log for accountability.
Related
The fastest answer is usually one question away.