Site Execution
The day-to-day heartbeat of a jobsite — daily logs, subcontractor tasks, milestone progress, and the weather conditions that constrain all three.
What this group does
These four screens are how a construction jobsite tracks its own pulse day by day. A daily site log captures what actually happened on a given date; subcontractor tasks carry the granular work items to completion; milestones roll individual tasks up into the project's big-picture schedule; and weather conditions are logged as an independent factor that can slow or stop work on either a task or a milestone. Unlike a strictly linear pipeline, this group is a hub-and-spoke: the daily log and the weather log both cross-reference tasks and milestones, rather than handing off to a single "next" screen.
Daily Site Logs, Subcontractor Tasks, Project Milestones, and Weather & Site Conditions share a common data model, and every cross-screen computation described below runs automatically — not a simulated hand-off.
1. Daily Site Logs
Purpose: A per-date, per-site record of what happened on the ground — work performed, issues encountered, crew headcount, equipment status, and which tasks were closed out that day.
Key features
- Structured daily entry — date, site name, recorded-by, free-text work performed and issues encountered, an equipment status field (
operational/idle/under_repair), and a crew headcount. - Milestone linkage — each log can optionally reference a milestone, tying the day's narrative to the broader schedule.
- Completed-task roll-up — a log records which Subcontractor Tasks were finished that day, and can resolve those back to full task records for display.
- Free-text notes for anything that doesn't fit the structured fields — other screens append to this same notes field when they push data in (see the Site Materials group's delivery-receipt sync).
Integration triggers
| Action | What it does |
|---|---|
| Mark tasks completed | Adding a task to the day's completed-tasks list makes it resolvable back to the full task record — the same lookup Milestone Progress uses to sanity-check its own derived progress percentage. |
| Link a milestone | Linking a milestone associates the day's narrative with that milestone, so the milestone's story can be reconstructed from its linked daily logs. |
2. Subcontractor Tasks
Purpose: The granular unit of work — a named task assigned to a subcontractor, with a priority, a due date, and an optional link up to a project milestone.
Key features
- Priority and status tracking — priority (
low/medium/high) and status (pending→in_progress→done). - Blocker flag — a blocked toggle plus a free-text blocker reason, so a stalled task is visible in the list without having to read every note.
- Milestone linkage — each task can link to a milestone, and that link is what lets Milestone Progress resolve the full set of tasks that roll up into a given milestone.
- Weather-risk flag — a task that is not yet
doneis checked against every logged weather condition whose date falls inside the task's start-to-due-date window; if any of those weather logs recorded a work impact ofslowedorstopped, that log is surfaced (preferring astoppedentry over aslowedone) as the task's active weather risk.
Integration triggers
| Action | What it does |
|---|---|
| Mark task done | Once status becomes done, the task drops out of the weather-risk consideration set and is counted as a completed task in its milestone's derived progress. |
| Assign to a milestone | Linking a milestone makes the task visible to Milestone Progress's derived-progress calculation, and to the Site Materials group's Consumption Requests screen as a valid requisition target. |
3. Milestone Progress
Purpose: The project-level schedule view — each milestone's own target date and status, with its completion percentage derived automatically from the tasks linked to it wherever possible.
Key features
- Four-state status —
not_started/on_track/at_risk/completed. - Derived progress percentage — the screen looks up every Subcontractor Task linked to the milestone. If the milestone has no linked tasks at all, its manually-entered progress percentage is treated as authoritative and shown unchanged; otherwise the percentage is recomputed as done task count ÷ linked task count, rounded to the nearest whole percent.
- Weather-risk flag — the same severe-weather matching logic used on tasks is applied to the milestone's own start-to-target-date window, but only while the milestone is not yet
completed.
Integration triggers
| Action | What it does |
|---|---|
| Recompute progress | Any change to a linked Subcontractor Task's status is reflected automatically the next time the milestone's progress is displayed — there is no separate "sync" action to trigger, the derivation is live off the current task list. |
| Mark milestone completed | Once status is completed, the milestone is excluded from the active weather-risk set, and from the Field Maintenance screen's critical-path check in Heavy Machinery & Fleet (a maintenance work order tied to a completed milestone is no longer considered a downtime risk). |
4. Weather & Site Conditions
Purpose: An independent log of daily site weather — temperature, wind, precipitation, a categorized condition, and its impact on work — that other screens read against, rather than a screen anything writes into.
Key features
- Seven-way condition taxonomy —
clear/cloudy/rain/storm/snow/extreme_heat/high_wind. - Work-impact classification —
no_impact/slowed/stopped. Onlyslowedandstoppedentries count as "severe" for the purposes of risk-matching; arainentry logged withno_impactis informational only and never flags a task or milestone. - Cross-reference counts — for a severe weather entry, the screen counts how many currently-open tasks and not-yet-completed milestones fall inside that weather log's date, giving the screen an at-a-glance sense of blast radius without opening every task.
Integration triggers
| Action | What it does |
|---|---|
| Log a severe weather day | A new entry with workImpact: 'slowed' or 'stopped' is immediately eligible to surface as a risk flag on Subcontractor Tasks and Milestone Progress for any task/milestone whose date window includes that day — no separate propagation step is needed since the matching is computed live. |
End-to-end data flow
| Source screen | Action | Target screen / record |
|---|---|---|
| Subcontractor Tasks | Task assigned to a milestone | Now included in that milestone's linked tasks → Milestone Progress's derived progress percentage |
| Subcontractor Tasks | Task marked done | Counted the next time the milestone's derived progress is displayed |
| Weather & Site Conditions | Severe entry logged (slowed/stopped) | Surfaces automatically as a risk flag on any open task/milestone in its date window |
| Daily Site Logs | Task added to the day's completed-tasks list | Resolvable back to the full Subcontractor Task record |
| Subcontractor Tasks | Task assigned to a milestone | Becomes a valid requisition target in Site Materials' Consumption Requests screen |
AI Assistant on every screen in this group
Daily Site Logs, Subcontractor Tasks, Milestone Progress, and Weather & Site Conditions each carry an embedded AI Assistant — the same right-edge panel used across TotalApp, opened from the vertical AI Assistant tab. Every panel reads the live rows on screen (or your current selection), can summarize, flag data gaps, and answer natural-language questions in Markdown (Turkish or English), and ships with Save as Report and Add Knowledge.
Pages in this section
Frequently Asked Questions
workImpact: 'stopped' or workImpact: 'slowed'. A logged condition with workImpact: 'no_impact' — even a storm entry — never triggers a risk flag on any task or milestone.stopped entry takes priority. The weather-risk check for both tasks and milestones always prefers a stopped match over a slowed one when both exist in range.done task and a completed milestone are both excluded from weather-risk matching before the date-range check is even attempted.