Grid View

The grid view shows the WBS items as a numbered list. Tasks and items in successive tiers of the hierarchical structure are assigned with WBS codes and numbered in the outline numbering system or custom WBS codes, depending on how the schedule was created.

• Outline numbering system - Applies to schedules created with standard WBS code settings. The schedule items, like the phases, deliverables, work packages, tasks, subtasks, and activities in the successive hierarchical tiers, are numbered in the outline numbering system.   For example, the subtasks of task 2.3 are numbered as 2.3.1, 2.3.2, 2.3.3, and so on. 
• Custom WBS Codes - Applies to schedules created with custom WBS code settings. Each schedule item is numbered with WBS codes representing its hierarchy from the root level task. For example, if the WBS code for the root level task is HOM, the first level task is FOU, and the next level task is coded DIG, then the last level task is numbered HOM.FOU.DIG.

The grid shows each item with its details like durations, start/end dates, assigned subcontractor, dependencies, progress percentage, and more. You can customize the table columns to view the details you want to view for the schedule items.

To view the schedule in the grid view

• Open the project management schedule
• Click 'Schedule' on the top
  • Choose 'Master schedule' if you are the general contractor
  • Choose 'Schedule' if you are a subcontractor

The 'Schedule' interface opens in the 'Grid' view by default. 

• Choose 'Grid View' from the drop-down on the top left to return to the 'Grid' view if you are on a different view.

Examples are shown below:

Standard WBS codes:

Custom WBS codes:

Filtering options:

The filter drop-downs at the top let you filter the tasks based on the assigned contractor and the status:

• Use the contractor filter to view the tasks assigned to a specific contractor
• Use the status filter to view only the tasks on a specific execution state. The available options are:
• Draft - Task items that have been added but are yet to be published
  •  Draft - Task items that have been added but are yet to be published
  • Scheduled - Task items that are pulled and added to the field schedule but are yet to be started 
  •  In Progress - Task items that are currently under execution
  • Completed -  Task items that are completed to currently under execution 100%
• Click the 'Reset' button to clear the applied filters

Columns and actions:

The grid view shows the table of the scheduled items with details under various columns. You can directly edit the details in each column, for example, to specify the start dates, labor required, estimated time needed for completion, and so on for any unpublished tasks at any time. Once a task is published, you cannot make any edits. The following list explains the columns shown by default. You can add more columns by right-clicking the table header and choosing the columns from the drop-down.

• S No - The serial number to identify the task item 
• Collaboration - Click the icon to chat with the participants of the task. See Chat and collaborate on a scheduled task for more details.
• Item type indicator - Shows whether the line item is a critical task, milestone, checkpoint, or inspection event.

	-	Critical Task
	-	Checkpoint
	-	Inspection Event
	-	Milestone

• Color code - Color assigned to the task. This enables you to group-sort tasks with easy identification. The colors reflect in the Gantt chart too.
• WBS code - The code assigned to the scheduled item, according to the WBS. In standard format, the WBS coding follows the outline numbering system. In custom format, the items are numbered with the custom prefix you defined for each level. 
• Task name - The label of the phase, deliverable, work package, task, or subtask, added as the schedule item. The name shortly describes the task. 
• Planned Days - The estimated number of days required to complete the task. The value is auto-populated for parent-level tasks depending on the values of the children.
• Planned Hours - The manhours or labor required to complete the item within the mentioned duration. As mentioned for the duration, the values for parent items are auto-computed from the values entered for their children.
• Depends on - The dependencies of the item. Shows the item or the task which needs to be commenced/completed in order for execution of this task, according to the dependency relationship. 
• Planned Start - The date at which the item is planned to commence. You can specify the start dates only for the items at the lowest level of the hierarchy.
  • Start dates for dependent tasks are auto-filled once you specify the predecessors and the dependency relationships. You can also change the date as required.
  • The dates for the parent-level tasks are auto-filled based on the lowest-level child tasks in that branch.
  • You can change the start dates for revising the schedule in the course of the project by setting task-wise baselines.
• Planned End - The estimated completion date of the item. This is auto-calculated from the start date and the task's duration, taking the holidays and working weekdays into account.
• Progress- The current completion percentage of the task.
  • Field level tasks - Fetched from the reports from the foreman. The project managers can also manually update the progress.
  • Assigned Tasks - The subcontractor shares the tasks' progress with the general contractor.
  • Parent-level tasks - Auto-calculated from the progress of the children.
• Assigned to - The contractor company to which the work package, task, or subtask is assigned. 

You can customize the table by adding new columns or removing existing columns. 

• Right-click on the table header and choose the columns from the options.

• Planned Quantity - The total amount of work done/deliverables planned.
• Actual Quantity - The amount of work done/deliverables realized with the current progress state. Fetched from the 
• Assigned User - The team member responsible for tracking the task
• Actual Start - The real commencement date of the task on the field.  Fetched from the actual start date of the first last-tier item of the task branch in the WBS hierarchical tree structure. 
• Actual End - Auto-populates once the task reaches 100% completion. The real completion date of the task is fetched from the date of the completion of the final last-tier item of the task branch in the WBS hierarchical tree structure. 
• Predicted End - Auto calculated from the planned start date and the current progress.

The following values are auto-calculated from the task dependencies, their relationships, and the critical path. These apply only to non-critical tasks.

• Early Start - The earliest date at which the task can be started.
• Early Finish- The earliest date at which the task can be completed. 
• Late Start- The latest date at which the task can be commenced. 
• Late Finish- The latest date at which the task can be completed. 
• Slack- The permissible number of days the task can be started after the planned start date without affecting the overall schedule.
• Time to finish - The number of days remaining to complete the task.