Reports
The plan tells you what should happen. Reports tell you what is actually happening.
Once your BEP is in execution and workflow instances are running, the state of the project is constantly changing: some instances are active, others are waiting on a specific person, others have completed. Remote resources connected to the BEP reflect the current state of work in external tools. Reports are how you capture all of that at a specific point in time and communicate it in a clear, presentable format.
A report is a snapshot. It reflects the state of the project at the moment it was generated, not the current state. This makes reports useful not just for sharing with stakeholders, but for building a record of how the project evolved over time.
Workflow instance reports
The most direct use of a report is to summarize what is happening across your workflow instances: which are active, where they are in the process, and whether anything is blocked or overdue.
Generate a report with the current state of all active workflow instances. For each one, show which step it is on, who is responsible for the next action, and how long it has been in the current step.Generate a report summarizing the coordination workflow instances. Group them by status: completed, active, and blocked. For the blocked ones, identify who needs to act.Generate a progress report for the [workflow name] workflow. Show a timeline of transitions for each active instance and highlight any that have been idle for more than [number] days.Remote data reports
If your BEP has remote data connected (clash reports, model statuses, platform dashboards), you can ask for a report that reflects the current state of those resources at the time of generation.
Generate a report with the current state of all remote data sources in this BEP. For each one, show what it contains and flag anything that looks out of date or requires attention.Generate a snapshot of the clash detection data for this BEP. Summarize the open clashes by discipline and by priority.Combined reports
The most powerful use of reports is crossing workflow instance states with remote data. This gives you a single document that connects what the process says should be happening with what the data shows is actually happening.
Generate an execution summary report for this BEP. Combine the current state of workflow instances with the remote data sources to give a full picture of where the project stands today.Generate a coordination report that crosses the active clash detection workflow instances with the current clash data. For each open clash, show which workflow instance is tracking it and what step that instance is on.Generate a weekly status report for this BEP. Summarize the workflow instances that advanced this week, any that are blocked, and the current state of the remote data sources. Format it for a project meeting.dotBEP Flavored Markdown
Reports are Markdown documents. You can use standard Markdown: headings, lists, tables, blockquotes, bold, italic, inline code, and code blocks. dotBEP extends this with visual block elements using the :::token syntax. Each block opens with :::token-name, contains one item per line with fields separated by |, and closes with :::.
Stats
Displays a row of stat cards. Each line: value | label | color (color is optional, accepts any CSS color value).
:::stats
47 | Open clashes | #ef4444
12 | Resolved this week
3 | Pending approval
:::Progress
Displays labeled progress bars. Each line: label | value | total.
:::progress
Structural | 34 | 40
MEP | 18 | 40
Architecture | 40 | 40
:::Pie chart
Displays a pie chart. Each line: label | value.
:::pie-chart
Completed | 58
In progress | 27
Not started | 15
:::Area chart
Displays an area chart. Each line: label | value.
:::area-chart
Week 1 | 4
Week 2 | 11
Week 3 | 19
Week 4 | 31
:::Timeline
Displays a milestone timeline. Each line: name | date | status. Status values: completed, active, upcoming (default).
:::timeline
Design freeze | 2025-03-15 | completed
Coordination | 2025-05-01 | active
Construction issue | 2025-07-30 | upcoming
:::Matrix
Displays a data matrix. The first line defines column headers; each subsequent line is a row. Fields separated by |.
:::matrix
Discipline | Open | Resolved | Critical
Structural | 12 | 34 | 3
MEP | 8 | 21 | 1
Architecture | 5 | 18 | 0
:::Callouts
Highlights a message with a colored border. Three variants: warning, danger, success. The title after the variant name is optional.
:::callout-warning Coordination deadline at risk
The MEP coordination workflow has 3 instances blocked for more than 5 days with no action taken.
::::::callout-success
All clash detection instances for the structural package have been resolved.
:::Where reports live
Reports are saved to your BEP automatically once the AI generates them. Open your BEP in app.dotbep.com and go to the Reports tab to find them. Each report shows the date it was generated and can be viewed directly in the platform or deleted when it is no longer needed.