Construction Daily Log Checklist for Supervisors

Purpose and limits of the daily record

A daily construction record serves as a factual account of site activity.

According to the NCDOT Construction Manual, this report should be used to give a daily detailed account of all activities occurring during the life of the project ( NCDOT). The manual specifies that a minimum of one report should be completed for each day, beginning with the date work begins and carried to the date that the project is completed and accepted, whether or not work is performed on the project ( NCDOT). This requirement ensures that the record remains unbroken, even during periods of inactivity. If no work was completed on the project site today, the manual instructs you to create a Daily Diary_No Work diary to document that situation and explain why ( NCDOT). This practice prevents gaps in the timeline that could later complicate the understanding of project sequencing.

In digital field management systems, the permanence of these records is a critical operational constraint. For example, Autodesk BIM 360 Daily Logs documentation states that daily logs cannot be deleted ( Autodesk). Only the current and past dates can be edited, and users can update a log ( Autodesk). Consequently, the value of the daily log lies in its accuracy at the time of entry, not in its ability to be edited later to fit a narrative.

Blank site daily-log checklist

Use the following worksheet to structure your daily entry. This worksheet separates raw observations from interpretations, ensuring that the record remains a factual account of the day's activities. Each field below corresponds to a specific data point required for a complete site record.

The project and date field anchors the entry to a specific timeline. Without this, the record lacks temporal context for later review. The contributor field identifies who is entering the data. This is distinct from the crew members working on site; it names the person responsible for the accuracy of the entry.

For the work and location field, document the specific task and its physical position. The SiteManager Daily Work Report (DWR) documentation specifies that this section should capture who performed the work, what was performed, whether it was inspected or not inspected, and where the work was being performed using station numbers and offsets ( TXDOT). Record the task description and the specific station or offset. Do not add narrative about why the work was done; stick to the factual description of the activity and its location.

The crew observation field tracks the personnel present. The Manpower section of the Daily Log Overview - Procore tracks the people on site who have completed work on the project for that day ( Procore). Enter the names or identifiers of the workers who performed tasks. This is a record of presence and labor contribution, not a performance evaluation.

In the conditions field, record the weather data. Chapter 5: Contract Administration, Section 0: Conduct of the Work | Caltrans lists weather conditions such as maximum and minimum temperatures and precipitation, among other items ( Caltrans). Enter the high and low temperatures and any precipitation. If the weather is exceptional, expand on the details in this field. Otherwise, keep the entry concise with the standard metrics.

For the delivery or delay field, log any shipments received. The Deliveries section of the Daily Log Overview - Procore tracks when shipments or packages are delivered, allowing you to include who the delivery was from, the tracking number associated with the delivery, and the contents of the package ( Procore). Record the sender, tracking number, and contents. If a delivery is delayed, note the expected arrival time and the reason for the delay if known. This field is for factual tracking of material movement, not for negotiating delivery terms.

The attachment reference field links to visual or documentary evidence. Enter the file name or ID of any photos, drawings, or documents attached to this entry. This ensures that the written record can be cross-referenced with visual proof. Do not describe the photo in this field; the attachment itself serves as the record.

Illustrative example

An illustrative one-day worksheet shows day 1, a curb pour at station 210 with offset 10, 8 workers for 8 hours, a high of 85, a low of 65, precipitation of 0, and 2 loads, plus 1 attached photo. A note records a wet north edge and leaves the cause unrecorded, and the reviewer line names a second person, separate from the person who entered the row. These round figures are illustrative only.

Separating observation from interpretation

Keep the clock time, the observed event, and your explanation in separate fields. In the Procore daily log, the Delays section allows you to track any delays that might occur or exist during the day, as documented in the Daily Log Overview. When you create a specific delay entry, select the delay start time using the hour and minute dropdown menus, as described in the Create Delay Entries tutorial ( Procore). This structure forces the timestamp to stand apart from the written comment. Do not merge the start time into a narrative sentence. The time is a data point; the narrative is the context.

Record discussions and agreements on the day they happen. The Caltrans construction manual states: "Important discussions and agreements with the contractor. Record these on the day discussed. Give the names of specific persons to whom instructions were given or with whom agreements were made." Record the names of those specific persons with the discussion entry, and keep the contributor line for the person entering the data. Name the specific individuals involved. Do not use generic titles like "foreman" or "subcontractor rep" if you know the name. The entry belongs on the date the talk occurred, not the date you remember it.

Use actual quotations for significant discussion points. The Caltrans manual notes that "Actual quotations on significant discussion points can be useful. Through letters to the contractor, confirm important verbal instructions." Keep the quoted words in the log. Send the confirmation in a letter. Caltrans advises confirming important verbal instructions through letters to the contractor. The log records what was said; the letter confirms the instruction. Do not assume the log entry carries the weight of a formal directive.

This separation protects the record. The observation is the fact. The interpretation is your view. Both are useful. Neither replaces the other. The time is the anchor. The name is the witness. The quote is the evidence. Keep them distinct.

Carry-forward review and missing inputs

When you copy a daily log to start the next day, the system does not transfer every piece of data. Understanding what carries over and what resets is the first step in a reliable carry-forward review. In Procore’s Daily Log Overview, you can configure your Manpower section so that the 'Hours' and 'Workers' values on a copied manpower entry are set to zero (0) ( Procore). This specific setting ensures that labor data does not accidentally duplicate from the previous day. If you do not enable this zeroing behavior, you must manually verify that hours and worker counts reflect the current day’s actual presence, not the prior day’s record.

Weather and photos never copy over. Procore’s Copy a Daily Log documentation states that weather data is pulled from the Dark Sky service for a specific day, and photos are tied to a specific point and time, so neither is copied to a new day’s entry ( Procore). Check the weather pulled for the new day, and supply new photos, since photos are not copied to that day. Do not assume yesterday’s weather conditions or site photos apply to today. Similarly, attachments will only copy from Notes log entries; all other logs do not copy attachments ( Procore). If you attached a delivery ticket to a Materials log yesterday, it will not appear in today’s Materials log. You must re-attach any documents that remain relevant to the current day’s activities.

Missing subcontractor data requires a distinct review step. When you use the Missing Companies page in Procore, only the company names are copied to the new pending entries; the remaining fields must be filled out after the entries are created ( Procore). These new entries are automatically labeled 'Copied' to distinguish them from manually created collaborator logs ( Procore). The newly created pending entries initially require their remaining fields to be completed. If you treat a 'Copied' entry as a confirmed observation, you risk recording unverified information. Your review process should flag every 'Copied' entry for manual verification before the log is finalized.

Attaching photos and notes without inventing context

Photos and notes serve as visual evidence for the daily record. In Autodesk BIM 360, the system allows you to upload photos and add notes to daily logs ( Autodesk). This capability supports the goal of capturing site conditions exactly as they appear. When attaching media, avoid adding speculative context in the filename or caption that is not visible in the image. The record should reflect what the photo shows, not what the supervisor believes it means.

Notes can be categorized to track unresolved matters. In Procore, you can mark specific notes as issues to generate dedicated reports on them ( Procore). This distinction helps separate general observations from items requiring follow-up. This workflow ensures that critical problems are not buried in general site notes.

Be mindful of how data is entered relative to system imports. In Autodesk BIM 360, manual entries may be overwritten at the time of an import, so the documentation advises using the automatic entry first and editing any fields manually afterwards ( Autodesk). This rule applies specifically to fields that the system populates automatically. If you enter data manually before an import occurs, that data may be lost. To preserve your specific observations, wait until after the automatic import completes before adding manual notes or editing fields.

Keep the original observation distinct from your interpretation. A photo of a wet floor is a fact; a note claiming the floor was wet due to a broken pipe is an interpretation. If the cause is unknown, record the condition as "wet floor, cause unknown." This approach prevents the daily log from becoming a narrative of blame or speculation. The record should remain a factual account of the day's events.

Review, publish, and export rules

The final phase of the daily log workflow involves verifying permissions, confirming publication status, and generating required reports. These steps ensure the record is accessible to authorized parties and meets specific administrative requirements.

Permission boundaries Access to daily logs is controlled by system permissions. Note: Viewing and editing daily logs requires permission ( Autodesk). This applies to the Daily Logs feature within Autodesk BIM 360. You must confirm that your team members have the correct access levels before expecting them to view or modify entries. Do not assume that all project staff can edit the log; verify their specific permission status within the platform.

Publication status In Autodesk BIM 360, the daily log stays in progress until it is published. The daily log will retain its in-progress status until you publish it ( Autodesk). This distinction is critical for record-keeping. Check the status indicator in your software to ensure the log has moved from in-progress to published before closing out the day’s administrative tasks.

Report generation and distribution Different systems offer different export capabilities. In Raken, the Daily report generates a PDF of the completed daily report for a specific date and project ( Raken). Reports for unsigned or incomplete days may not contain all sections ( Raken). If you need to consolidate multiple inputs, the Super daily report combines your company's daily report with all collaborator (subcontractor) reports for a given date into a single PDF ( Raken). This combination is useful for creating a unified view of all site activities for a particular date.

Key takeaways and daily-log FAQ

A daily construction record serves as the primary written account of site activity, crew presence, and conditions. Do not rely on the log alone for contract notices, fault determinations, or payment. Its value lies in capturing details while they are fresh and maintaining a clear distinction between observed facts and later interpretations. Supervisors should treat the log as a factual baseline, not a legal argument. Under the NCDOT Daily Diary workflow, create an additional entry for each contractor after the first. In Autodesk BIM 360, users can create, update, and publish multiple logs for each day if necessary ( Autodesk). This flexibility allows for granular tracking without forcing unrelated activities into a single entry. However, editing capabilities are limited; only current and past dates can be edited in daily logs, while future dates allow only general notes ( Autodesk). For audit purposes, change history features in systems like Procore list all changes made to the daily log during that day, including who made the modifications ( Procore). This transparency supports reviewer trust. Finally, reports generated from daily log data, such as those in Raken, may not contain all sections if the underlying daily log is unsigned or incomplete ( Raken).

Do I need a log entry for a day with no work?

Yes, create a marked no-work entry explaining why. This practice aligns with NCDOT guidance, which requires documentation even when no physical work occurs. The entry should specify the reason for the stoppage, such as weather or material delays, to maintain a continuous record of the project timeline.

Can I edit a past daily log?

In Autodesk BIM 360, only the current and past dates can be edited in the daily logs ( Autodesk). General Notes can be added to future dates. Past dates can be edited, and corrections should follow the project's applicable review process.

What happens to copied manpower data?

Pending entries created from the Missing Companies page are labeled 'Copied', while a copied manpower entry can have Hours and Workers set to zero (0). If you copy data from a previous day, verify that the crew and hours reflect the current day's reality.

How do I handle multiple subcontractors on site?

Create a separate entry for each additional contractor under NCDOT Daily Diary guidance. If there is more than one contractor (prime or sub) on the project site today, create a Daily Diary_Addtn'l Subs entry for each contractor after the first ( NCDOT). This ensures that each subcontractor's work, crew, and conditions are recorded distinctly, preventing confusion in later reviews or disputes.

Can I delete an incorrect daily log entry?

No, daily logs cannot be deleted in Autodesk BIM 360. Instead, use change history to track corrections. In systems that support this, such as Procore, Change History lists all changes that have been made to the Daily Log during that day, as well as who made the modifications ( Procore). This approach preserves the audit trail while allowing you to correct errors transparently.