# Reporting — Web app

Generated reports that can be exported, scheduled, and shared — structured summaries of data for stakeholders.

Source: https://www.checklist.design/web-app/reporting

## Items

### Report selection and parameters
A way to choose the type of report and configure its inputs — date range, segments, filters.

_Tip: Users who run the same report every week should not have to rebuild the configuration each time — saved presets remove significant recurring friction._

### Scheduled or on-demand generation
The option to run a report immediately or schedule it to be generated and delivered automatically.

_Tip: Email delivery is the most common use case for scheduled reports — format should be selectable per report rather than a global setting._

### Export options
Download the report in PDF, CSV, or spreadsheet format.

_Tip: PDFs work for sharing with stakeholders, CSVs are better for further analysis — when only one format is possible, CSV is more useful to more users._

### Report title and generation date
Clear labelling of what the report covers and when it was created.

_Tip: A report without its parameter context — date range, active segments — is difficult to interpret when shared outside the platform._

### Summary or key findings section
A brief narrative or highlights section at the top of the report.

_Tip: An auto-generated summary adds value for users who share reports with people who will not read the full data._

### Historical archive of past reports
A list of previously generated reports that can be downloaded or re-opened.

_Tip: Finding a quarterly report from six months ago should take one click — organising by report type and date is what makes that possible._

### Share or distribute options
A way to send or share the report with colleagues or external stakeholders.

_Tip: Shareable links with expiry work well for external recipients — requiring an account to view a shared report is a significant barrier._

## License for the Checklist Design collection

Checklist Design collection: https://github.com/Checklist-Design/skills
Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12
Republished under the MIT License. Original checklist text belongs to Checklist Design.

MIT License

Copyright (c) 2026 Checklist Design

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.