> For the complete documentation index, see [llms.txt](https://changelog.visilean.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.visilean.com/changelog/release-7.0-2025/release-1.0-2026/daily-progress-reports-rebuilt-for-clarity.md).

# Daily Progress Reports, Rebuilt for Clarity

The Daily Progress Report is now available in the New UI, offering a modern, card-based experience designed to make daily site reviews faster and more productive. It carries forward the reporting logic teams already rely on, while presenting the information through a layout that reduces clutter and draws attention to what actually changed during the day. The DPR sits within the dashboard alongside existing project views, giving supervisory roles and project managers a dedicated screen for daily operational control.

### Why This Matters

Construction projects generate a high volume of daily activity — tasks starting, stopping, delays surfacing, and issues being raised. When this information is buried in dense tables or requires multiple screens to piece together, teams lose time and context. Progress meetings stall while someone explains what happened instead of deciding what to do next. A clear, well-organised daily view means fewer surprises, faster responses, and discussions grounded in the same shared picture.

### What’s New?

he DPR now uses a card-based design that highlights task movements, exceptions, and daily statistics at a glance. Teams can configure columns, apply local filters (including task type, Takt/Gantt, and delayed task filters), and save up to 11 view configurations to suit different review needs. Weather is shown for the selected day, and a downloadable report option supports offline sharing and record-keeping. A detail panel opens on click, giving quick access to task-level context without leaving the view. Key highlights include improved readability across desktop and tablet, structured task categories, and a cleaner path from overview to detail.

### How It Helps – Example Use Cases

A Project Manager opens the DPR before a daily coordination meeting, sees which tasks started and stopped, spots a flagged exception on a concrete pour, and walks into the meeting with a clear agenda — no preparation spreadsheet needed.

A Programme Manager reviews DPRs across multiple projects to identify patterns — which sites are logging repeated stoppages, where delays are clustering — and uses the downloadable reports to share findings with senior stakeholders.

A Site Supervisor checks the DPR on a tablet at the end of the day to confirm that all completed activities are reflected accurately, flags a missing update, and ensures the record is reliable before it reaches the wider team.

{% hint style="info" %}

### **Key Considerations & Caution Points**

The DPR view updates after a hard refresh rather than in real time, so recent changes may not appear until the page is reloaded.

The Zone filter is not available in this release and will be introduced as a future improvement.

Start Milestone and End Milestone task types are not included in the DPR filter options at present.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://changelog.visilean.com/changelog/release-7.0-2025/release-1.0-2026/daily-progress-reports-rebuilt-for-clarity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
