Latest Update: 6-12-2026

Planera's Table view is divided into tabs: Build, Resources, Codes, Updates, CPM Data, and Variance. Each tab surfaces columns relevant to a specific workflow. The sections below follow that same order. For help adding, hiding, or rearranging columns, see Project Table Basics.

The Build tab is where you enter and edit your schedule. It includes the core fields for defining activities, their durations, constraints, and relationships.

The label for the schedule element, such as "Install Conduit" or "Foundation Pour." Rename by double clicking the Name cell and typing.

A unique alphanumeric identifier for each element (for example, A0010 or A0020). Auto-generated but editable. Used to reference specific activities, milestones, or groups throughout the schedule.

If a scheduling constraint is applied to the element (such as Start On, Finish On, or As Late As Possible), it appears here. Constraints override CPM-calculated dates for that element. Use the drop down to apply constraints on activities and milestones.

The total planned working days for the element from start to finish. Edit by double clicking the duration cell and entering a number.

Lists the number of relationships (predecessors and successors) tied to the current activity or milestone.

The calendar assigned to the element. Defines work days vs non-work days used in scheduling calculations.

A free-text field for notes attached to the element. Commonly used for URL links to project documents, checklists, field context, RFI references, notes on impacts or coordination details.

The element's start date, which is linked to its status. For Not Started elements this is the planned start; for In Progress elements it is the Actual Start; for Completed elements it is the Actual Start.

The element's finish date, which is linked to its status. For Not Started elements this is the planned finish; for In Progress elements it is the Expected Finish; for Completed elements it is the Actual Finish.

The Resources tab is where you assign labor and equipment to schedule activities to resource-load your schedule.

Where you add labor to your schedule activities to resource-load your schedule. This column is used to calculate Total Labor Hours.

The total labor hours allocated to the element. This is calculated from the duration, assigned labor and work hours.

Where you add equipment to resource-load your schedule. This column is used to calculate Total Equipment Hours.

The total equipment hours allocated to the element. This is calculated from the duration, assigned equipment and work hours.

Determines the work hours in a day. This column is used to calculate Total Labor Hours.

The Codes tab is where you assign organizational codes to schedule elements. Two default codes are available in every project.

Used to assign responsibility for activities, milestones, and groups to people, companies, or crews.

Used to assign a location to activities, milestones, and groups.

In addition to the two default codes, you can create custom code columns for your project. Click "+ New Code" at the right end of the table, or use the column header menu to insert a new code. Learn more in Create Custom Codes and Tags.

The Updates tab is where you track progress each period. Use this tab to record status, dates, and durations during each progress update.

The current state of the element: Not Started, In Progress, or Completed.

Note: Milestones can only be Not Started or Completed.

Codes used to track reasons why an activity was impacted, positively or negatively. This list is managed at the organization level from the Home screen under Libraries and Settings.

How much of the element's work has been finished, expressed as a percentage from 0% to 100%. Calculated from actual versus total duration.

The element's start date before any progress is recorded. Once the element moves to In Progress or Completed, it locks to the start date at the moment of that transition, so it reflects the pre-progress plan.

The element's finish date before any progress is recorded. Once the element moves to In Progress or Completed, it locks to the finish date at the moment of that transition, so it reflects the pre-progress plan.

The actual start date of the activity. Enter this date when performing progress updates on your project.

The actual finish date of the activity. Enter this date when performing progress updates on your project.

For in-progress activities, this is the planned start date for the balance of the remaining duration. This date moves out based on calendars and relationships each time the data date is advanced during a progress update. Once the activity is complete, this column is blank and Actual Finish populates.

The date the field team expects the activity to finish. You can enter it directly, or it can be calculated from the Remaining Duration you enter: setting one updates the other. This is different from the CPM-calculated Finish Date.

The baseline duration for the activity.

The expected total duration of an in-progress activity. This duration changes based on the Expected Finish date, which can be modified during progress updates.

The number of working days of effort still needed to finish the element. Updates as progress is entered and if Exp Finish Date is pushed out.

The number of working days spent performing work on this element.

The CPM Data tab shows the output of Planera's Critical Path Method (CPM) calculation. These values are calculated by the scheduling engine and cannot be manually edited. Note: Planera marks an element as critical when it sits on the driving chain from project start to project finish, not simply when its total float is zero. An element can carry positive float and still be critical, and an element with zero float is not critical unless it is on the driving chain.

The number of working days the element can be delayed without pushing out the project finish date, or a closer downstream constraint or interim milestone, whichever is tighter. Negative total float means the element is already contributing to a delay against that downstream element, often because a Finish On or Finish On or Before constraint sits earlier than the predecessor-driven dates.

The number of working days the element can be delayed without delaying any of its immediate successors. Always less than or equal to Total Float.

The earliest possible date the remaining work on this element can begin, based on predecessor logic and the CPM forward pass. In retained logic mode, this reflects when all predecessors will be satisfied and remaining duration begins counting down.

The latest date the remaining work can begin without delaying the project finish, calculated by the CPM backward pass.

The earliest possible date the remaining work on this element can finish, based on the CPM forward pass.

The latest date the remaining work can finish without delaying the project finish, calculated by the CPM backward pass.

The Variance tab compares your current schedule against a baseline version and the previous version of your schedule. The columns below are not visible by default; bring them in using the Add Fields button in the column header. For more on comparing versions, see Comparing Schedule Versions.

The start date of the activity in the baseline version of the schedule.

The number of calendar days difference between the baseline start date and the current version start date.

The finish date of the activity in the baseline version of the schedule.

The number of calendar days difference between the baseline finish date and the current version finish date.

The duration of the activity in the baseline version of the schedule.

The number of calendar days difference between the baseline duration and the current version duration.

The start date of the activity in the previous version of the schedule.

The number of calendar days difference between the previous version start date and the current version start date.

The finish date of the activity in the previous version of the schedule.

The number of calendar days difference between the previous version finish date and the current version finish date.

The duration of the activity in the previous version of the schedule.

The number of calendar days difference between the previous version duration and the current version duration.

For in-progress activities, Remaining Start shows the planned start date for the balance of the remaining duration. It moves out based on calendars and relationships each time you advance the data date. Once an activity is complete, this column is blank and Actual Finish populates.

Original Duration is the baseline duration and does not change. Expected Duration reflects the expected total duration of an in-progress activity and updates based on the Expected Finish date you enter during progress updates.

Planned Start is the pre-progress start date, not a baseline reference. It locks to the start date at the moment the element moves to In Progress or Completed. Actual Start is the date work actually began, which you enter during a progress update.

Negative total float means the element is already contributing to a delay against its tightest downstream anchor, which is the project finish date or a closer downstream constraint or interim milestone. That date cannot be met without compressing the schedule, adding resources, or adjusting predecessor logic or the constraint.

Early Start is the earliest possible date remaining work can begin, from the CPM forward pass. Late Start is the latest it can begin without delaying the project finish, from the backward pass. The difference between the two equals the Total Float.

Total Float measures how much an activity can slip without delaying the project finish. Free Float measures how much it can slip without delaying any immediate successors. Free Float is always less than or equal to Total Float.

The BL and Prev columns are not visible by default. Use the Add Fields button in the column header to bring them into your view.

Variance Codes track the reasons why an activity was impacted, positively or negatively. They are managed at the organization level from the Home screen under Libraries and Settings.

Click "+ New Code" at the right end of the table, or use the three-dot menu in any column header to insert a new code. See Create Custom Codes and Tags for more detail.