Daily Logs (Dailies)
Daily Logs (Dailies) - Construxion Pro User Guide
Daily logs are field reports filled out at the end of each workday. They record who worked, what they did, weather conditions, equipment used, and any issues encountered. Accessible to Owner, Manager, Administrative, and Foreman roles.
Accessing Daily Logs
Daily logs appear on the Daily Logs tab (labeled "Dailies") within each job. The tab's visibility is controlled by a company-level setting:
- Off — Dailies tab never shown
- On (Default On) — Shown on all jobs unless disabled per-job
- On (Default Off) — Hidden unless enabled per-job
Creating a Daily Log
- Go to a job's Dailies tab
- Click New Daily Log or select a date
- The daily log editor opens as a side sheet (full-screen panel on desktop, bottom sheet on mobile)
There is one daily log per job per day — you can't create duplicates for the same date.
Copy from Previous
When creating a new log, you can Copy from Previous Log to pre-fill the crew roster, tasks, trucking, subcontractors, and equipment from the last daily log. This copies the structure but not day-specific values (times, hours, quantities).
Daily Log Sections
Weather
Weather fields include high/low temperature, conditions, and wind.
Auto-fetch: Click the weather button to automatically pull weather data from the Open-Meteo API using the job's coordinates. The data source is tracked:
auto— Fetched automaticallymanual— Entered by handauto_modified— Fetched then manually adjusted
Work Performed
Tag which job tasks were worked on during the day:
- Click Add Task to open the task picker
- Select tasks from the job's task list (inspections are excluded — they have their own section)
- Add "Other Work" entries for tasks not in the system (free-text)
- Use Additional Notes for general observations
- Use Problems / Issues to flag anything that went wrong
Labor
Record employee hours for the day:
- Click Add Employee or Add from Crew Assignments (pre-populates from the day's crew schedule)
- For each employee, enter:
- Name — Autocomplete from company users
- Position — Dropdown of company-configured position types (e.g., Operator, Laborer, Flagger)
- Time In / Time Out — Start and end times
- Lunch — Lunch duration (deducted from hours)
- Hours — Auto-calculated from times, or manual entry
- Equipment Operated — List of equipment used (links to company equipment; "Save to company equipment" option for new items)
Position Types: These are company-configurable. The first time you use the labor section, default positions are seeded. Manage them in the daily log settings.
Inspections
Record inspections performed on the job:
- Shows scheduled inspection items for the date in a blue banner
- Inspector — Autocomplete from the company's inspector list; "Save as inspector" option for new entries
- Links to inspection items from the job's schedule
Trucking
Record trucking activity:
- Driver/truck name
- Type of truck
- Hours
- Material hauled
- Hauled from / hauled to
Subcontractors
Record which subcontractors were on site:
- Select from company's subcontractor list
- Add notes per subcontractor
Rental Equipment
Record any rented equipment used:
- Equipment description
- Vendor/company
- Hours used
Status Workflow
Daily logs follow a three-step status workflow:
| Status | Who Can Edit | How to Advance |
|---|---|---|
| Draft | Anyone with dailies access | Click Submit |
| Submitted | Only Owner and Manager | Click Approve |
| Approved | No one (locked) | Must Revert to Draft first (with confirmation dialog) |
- Foremen typically create and submit logs
- Managers review and approve
- Reverting an approved log back to draft requires confirmation, since it unlocks all fields for editing
PDF Export
Daily logs can be exported to PDF from the side sheet. The PDF includes:
- Company branding — Logo, accent color, company address
- All sections formatted with tables
- Signature line on the last page
- Page numbers and accent bar
Auto-Save
Fields save automatically on blur (when you click away from a field). Child sections (labor entries, trucking records, etc.) use debounced batch saves to avoid excessive API calls.