The work card brings together the full context of one construction task: site and contractor, assignee, local budget line and resource, unit of measurement, status, planned dates, and budgeted volume. Separate blocks show plan vs. actual since the start of construction and the gap between them, the monthly target, planned dates, remaining budgeted volume, and resource indicators.

For one work item, a user records physical volume and worker count by day. Planned values and confirmed actuals are shown together, so new entries are made in the context of existing data.

For updating several work items at once, there's a separate flow: the user works with a tree of sites and work items, expands the levels they need, and enters actual values right in the list. Unlike the single-item card, the priority here is speed — processing many work items for a chosen period quickly.

The first version of this flow was simpler. After testing, it turned out users needed a clearer link between resources and the work hierarchy, plus more detail over time — so I reworked it to show resources in the context of work items, by day and by week. For equipment: assignee, equipment type, quantity, and hours worked are recorded; for engineering staff: assignee and headcount. This was one of the key iterations in the product — testing changed not just the visual layout, but the underlying information structure.

One of the hardest parts of the product was combining a deep data hierarchy (company → project → event → site → work item) with a calendar view on a small mobile screen, without losing the connections between levels. A user needed to see, at the same time, where a work item sits in the structure and its dates on the timeline. The solution went through several rounds of testing and feedback until the registry tree and the Gantt view worked as one consistent data model.

If a needed work item wasn't in the current structure, a user could create an unplanned one directly from the registry with a quick action. The form asked for the site, local budget line, work item, remaining budget, unit of measurement, and the progress date — and the user could record physical volume, worker count, and resources used at the same time. After submission, the new work item went through review and was only added to the main registry once approved.

Main actions are available directly from the registry: add unplanned work, enter bulk progress data, log equipment and staff, or take a photo. For photos: states for "no photos" and "photos added", a full-screen view, deleting a photo, and a limit on how many photos can be attached.

Without a network connection, a user can still view available work items and enter progress data for them — so work on site doesn't have to wait for a signal, which matters most in areas with no coverage (underground, basements).

Operational analytics for construction work and resources: completed physical volumes, labor metrics, resource mobilization, and other production indicators — each analytics screen has its own filters and system states (loading, no data, error).