Babel can generate a PDF report for any project with a single click. The report captures a point-in-time snapshot of the project’s tasks, traceability records, and health indicators — making it suitable for milestone reviews, sprint retrospectives, and stakeholder deliverables.
Generating a report
Open the project
Navigate to the project you want to report on. You must have access to the project to generate its report.
Click Reporte
In the project details view, click the Reporte button. Babel fetches the latest project data from the server — tasks, datasets, experiments, decisions, and stalled task detection results — and renders the report as a visual HTML preview.
Review the preview
A modal or panel displays the rendered report. Review the content to confirm it reflects the current state of the project before downloading.
Export the PDF
Click Exportar PDF in the report modal toolbar. Babel uses html2canvas to capture the rendered report as an image and jspdf to package it as a PDF file. The filename includes the project name (e.g. reporte-mi-proyecto.pdf). The file downloads automatically to your browser’s default download location.
The report is a point-in-time snapshot. The data captured in the PDF reflects the state of the project at the moment you clicked Reporte. If tasks are updated after you open the report preview, those changes will not appear in the downloaded PDF unless you close and regenerate the report.
What the report contains
The generated PDF includes the following sections:
Project summary
The project name and overall metadata appear at the top of the report, giving context to anyone reading it outside of Babel.
Tasks by phase and status
All tasks in the project are listed, grouped by their CRISP-DM phase. For each task, the report shows:
- Task name and description
- Current status (
pending, onHold, inProgress, underReview, completed)
- Priority level
- Deadline (if set)
- Estimated hours (if set)
- Assigned user (if set)
This section gives a complete view of work progress across all six CRISP-DM phases.
Traceability records
The report includes all traceability records attached to the project, organized by type:
| Record type | What it captures |
|---|
| Datasets | Data sources used in the project, with lineage and quality notes |
| Experiments | Model training runs with parameters and evaluation metrics |
| Decisions | Key decisions made during the project with rationale and phase context |
Stalled task warnings
Any task identified as stalled — meaning it has not changed status for a configurable period — is listed in a dedicated warnings section. This draws the reader’s attention to potential blockers that need follow-up.
If your project has no tasks, the report body will be empty. Create tasks and assign them to CRISP-DM phases before generating a report, otherwise the PDF will contain only the project header with no meaningful content.
Data source
The report data is fetched from:
This endpoint returns a consolidated payload:
type ReportData = {
tasks: any[]
datasets: any[]
experiments: any[]
decisions: any[]
stalledTasks: any[]
}
When to generate reports
Generate a report at the end of each CRISP-DM phase gate review. This creates a permanent record of what was completed, what traceability artifacts exist, and whether any tasks were stalled at the time of the gate. This is especially useful if the project has external stakeholders or must meet documentation standards.
Generate a report before starting a new sprint or iteration cycle. A report at the beginning of a sprint captures the baseline state — the snapshot can then be compared to the next report at sprint end to quantify progress.
Generate a report before any major team change, such as a new member joining, a team member leaving, or a handoff to operations. The traceability records and task history in the PDF serve as onboarding material and institutional memory.
