> 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-2.0-2026/daily-quantity-logger.md). # Daily Quantity Logger Construction schedules track whether tasks start and finish on time but they rarely show whether the right amount of work is being completed each day. A task can be marked "in progress" for a week while actual output quietly falls short of what was planned, and nobody notices until the totals are reconciled at the end. By then, the overrun is baked in and recovery options are limited. #### Why This Matters When quantity tracking lives only at the task level as a single total, the daily reality on site becomes invisible to anyone not standing there. Concrete pours, steel erection, finishing works all of these involve daily output that can vary significantly from plan. Without a day-level breakdown, project managers spot problems too late, procurement adjustments lag behind actual consumption, and progress claims are based on estimates rather than recorded data. The gap between "what should have happened today" and "what actually happened today" is where cost overruns and schedule drift hide. #### What's New? * **Daily Quantity tab on every leaf-level activity** - A new tab sits alongside your existing task details, showing a scrollable date-by-date timeline of planned and actual quantities. * **Automatic planned distribution** - Total planned quantities flow in from the main Quantities tab and distribute evenly across working days. If the total or the task dates change upstream, the daily figures recalculate automatically. * **Actual quantity logging per day** - Your team enters actual quantities against each date as work is completed. * **Non-working day handling** - Weekends and holidays are excluded from the automatic planned distribution but remain available for manual actual entry when overtime or weekend work happens. Weekend output shows as bonus progress without distorting the weekday plan-versus-actual picture. * **Automatic variance calculation** - The system calculates the variance between total planned and total actual quantities, giving you a clear measure of over- or under-delivery. * **Legacy sync** - The percentage progress recorded in the Daily Quantity tab can be synced back to the main Quantities tab, keeping both views aligned without double entry. #### How It Helps A *Site Engineer* overseeing a ten-day concrete pour checks the Daily Quantity tab on day four and sees actual quantities consistently exceeding the planned distribution. The early signal triggers an investigation formwork dimensions are off and the team corrects course before the overrun compounds across the remaining six days. Procurement adjusts the next delivery accordingly. A *Planner* managing a structural steel erection task notices the crew mobilised three days early. The Daily Quantity tab adds the extra date columns automatically, and the engineer logs actual tonnage from day one. By the time the original planned start arrives, three days of progress data are already captured giving the planner a precise picture of how far ahead the task is running and whether resources can shift to other critical-path activities. A *Project Manager* authorises weekend work on a time-critical finishing activity. The supervisor enters actual quantities on Saturday and Sunday days that carry no planned allocation so the weekend output shows up as clear schedule recovery without distorting the weekday comparisons. The progress claim for that week reflects exactly what was delivered, day by day. #### Key Considerations & Caution Points **Leaf-level activities only.** The Daily Quantity tab is available on leaf-level tasks. Summary or parent tasks do not display daily quantity breakdowns. **Planned distribution is even.** Planned quantities are distributed equally across working days. Weighted or custom daily distributions are not supported in this release. --- # 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-2.0-2026/daily-quantity-logger.md?ask= ``` 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.