Project Log: Your Comprehensive Guide

Last updated: August 7, 2025

View Video Overview Here.

Overview

The Project Log is a dynamic and essential feature designed to provide a comprehensive, chronological record of all activities, communications, and changes associated with a specific project. Its primary purpose is to serve as a centralized hub where team members can track a project's entire lifecycle, from inception to completion.

The scope of the Project Log is extensive. It automatically captures key system-generated events, such as:

  • Project creation and initial assignment.

  • Changes in project status (e.g., moving from Lead to Estimating).

  • Reassignments of the project to different users.

  • Uploading of documents to the Documents tab.

  • Sending of invoices (if integrated with systems like QuickBooks Online).

  • Submission of actuals via the Actuals tab.

Beyond these automated entries, the Project Log facilitates manual user interactions, allowing team members to post comments, share updates, attach relevant files (like photos or documents), and use @mentions to notify specific colleagues. Each entry is timestamped and attributes the action or comment to the responsible user.

The benefits of utilizing the Project Log are manifold:

  • Complete Audit Trail: Offers an immutable history, crucial for accountability and review.

  • Enhanced Collaboration: Keeps all stakeholders informed by centralizing project-related discussions and updates.

  • Single Source of Truth: Minimizes confusion by consolidating diverse project information in one accessible location.

  • Improved Transparency: Clearly shows who performed which action and when, fostering a clear understanding of project progression.

Insight: The Project Log transforms a series of discrete events and conversations into a cohesive project narrative, providing invaluable clarity and context at any point in the project's lifecycle.

Pro Tip: Use @mentions strategically to direct attention where it's needed most. While it's great for ensuring key individuals see a message, overusing mentions for general updates can lead to notification fatigue.

Configuration

The Project Log itself doesn't require extensive setup, as it's an integral part of each project. However, users can configure how they interact with it and what information is displayed.

Adding Entries to the Log

At the bottom of the Project Log, you'll find the Write a comment... field. This is your primary tool for adding new information:

  1. Text Messages: Simply type your message or update into the field.

  2. Attachments:

    • Click the Upload button.

    • A file dialog will appear, allowing you to select one or more files (images, documents, etc.) from your computer.

    • Once selected, thumbnails of images or file names will appear below the comment box.

    • These attachments will be sent with your message and will also be automatically added to the Documents tab for the project.

  3. Mentions:

    • Click the Mention button or type the "@" symbol directly in the comment field.

    • A list of users will appear. Start typing a name to filter the list, then select the desired user.

    • The mentioned user will receive a notification about your message.

  4. Sending: Once your message (with any attachments or mentions) is ready, click the Send button or use the keyboard shortcut (e.g., CMD+Enter or CTRL+Enter).

Filtering Log Entries

On the right-hand side of the Project Log, a Filters pane allows you to refine the displayed entries, which is especially useful for long or active projects:

  • See All: This is the default view. It displays all log entries—both system-generated actions and user-written messages—in chronological order.

  • Actions: Selecting this filter will show only the system-generated entries. This is ideal for getting a clear, objective history of the project, such as when it was created, when its status changed, who uploaded specific files, or when an invoice was recorded.

  • Messages: This filter isolates all user-generated content. It shows only the comments, replies, and associated attachments posted by team members. This view is useful when you want to focus specifically on the communications and discussions that have taken place.

Insight: Filtering the Project Log allows you to switch perspectives effortlessly – from a high-level audit of key project milestones to a detailed review of team conversations, ensuring you find the information you need quickly.

Use Cases

The Project Log is a versatile tool that supports various project management activities. Here are some common scenarios where it adds significant value:

  • Tracking Project Lifecycle Milestones: Automatically captures and displays critical project events. For instance, when a project is created, its status is updated (e.g., from "Lead" to "Estimating"), or it's assigned to a new team member, an entry is logged, providing a clear timeline of progress.

  • Centralized Team Communication: Serves as a dedicated message board for the project. Team members can post updates, ask questions, discuss challenges, and record decisions directly within the project's context, ensuring all communication is logged and easily accessible.

  • Documenting On-Site Progress and Issues: Particularly useful for field teams. For example, a technician can take "before" and "after" photos of a job site, or document an unexpected issue, and then post these images as attachments to a message in the Project Log (e.g., "Before photos attached"). These uploaded files are also conveniently stored in the project's Documents tab.

  • Targeted Stakeholder Updates with Mentions: When a specific team member needs to be alerted or involved in a discussion, users can type "@" followed by the person's name (e.g., "@Max Kostow") or use the Mention button. This sends a notification to the tagged individual, ensuring they see the relevant message promptly.

  • Historical Review and Information Retrieval: When questions arise about past actions, decisions, or communications, the Project Log provides a searchable history. Whether it's to understand the evolution of a project phase or to recall a specific instruction, the log is an invaluable resource.

Examples

Here are some real-world examples illustrating how the Project Log can be used to solve problems and add value throughout a project's lifecycle:

Example 1: Daily Progress Update and Task Assignment

Scenario: A project manager needs to provide a daily update to the team and assign a follow-up task.

Action:

  1. The Project Manager navigates to the relevant project and opens the Log tab.

  2. In the Write a comment... field, they type: "Daily Update: Phase 1 completed ahead of schedule. Excellent work, team! @SarahMiller, please begin compiling the requirements for Phase 2. Let me know if you have any questions."

  3. They click Send.

Outcome:

  • The update is logged for all team members with access to the project to see.

  • Sarah Miller receives a specific notification because she was mentioned, ensuring she sees her new task assignment.

  • The communication is documented and timestamped.

Example 2: Field Technician Reporting an On-Site Issue

Scenario: A field technician encounters an unexpected problem at a job site that requires immediate attention or documentation.

Action:

  1. The technician opens the project on their mobile device and accesses the Log.

  2. They type a message: "Site Inspection - Unit 12B: Found significant water damage in the subfloor, not noted in initial assessment. See attached photos. Recommend immediate remediation assessment. Before photos:"

  3. They click the Upload button, select several photos of the damage from their device's gallery, and confirm the upload.

  4. They click Send.

Outcome:

  • The critical issue is immediately communicated to the project team.

  • The photographic evidence is logged directly with the comment, providing clear visual context.

  • The uploaded photos are also automatically available in the project's Documents tab for future reference and inclusion in reports.

Example 3: Verifying Project Milestone Achievement

Scenario: A stakeholder asks for confirmation of when a key project milestone, like "Estimating Complete," was achieved.

Action:

  1. A team member opens the Project Log.

  2. They use the Filters on the right and select Actions.

  3. They scroll through the filtered log or use their browser's find function (Ctrl+F or Cmd+F) to search for keywords like "status" or "Estimating."

  4. They quickly locate an entry similar to: "September 13, 2022, 16:28 - Ari changed the project status from Lead to Estimating."

Outcome:

  • The team member can confidently and accurately provide the date and time the milestone was achieved.

  • The Project Log serves as a reliable record, preventing disputes or misinformation.

Pro Tip: For recurring updates, such as weekly progress reports or site visit summaries, consider establishing a consistent message format or template. This makes it easier for team members to quickly scan and digest the information in the Project Log.