# High-Level View. Ground-Level Action.

Managing thousands of tasks across multiple trades can be overwhelming. To help project teams cut through the clutter, we've introduced Grouping & Bulk Allocation in the New Table View. This enhancement brings structure to task data by grouping tasks based on key attributes like trade, subcontractor, or custom fields, while enabling batch updates through intuitive summary rows.

### **Why This Matters**

For General Contractors and project managers juggling timelines, teams, and trade packages, quick visibility and actionable insights are vital. This feature delivers a smarter way to track and manage grouped data in one view. It also supports accountability by prompting note entries for bulk changes, and ensures auditability by logging those actions into the task history.

### **What’s New?**

* Group tasks by key fields (e.g., Trade, Subcontractor, Assignee, Location, Zone)
* Summary rows display aggregate values such as:
  * *Min/Max Dates* for planning fields
  * *Sum* of quantities, costs, and workforce across planned, actual, and baseline values
  * *Average* for fields like Progress and Variance
* Fields like *Task Status, Trade, Zone, Assignee*, and *Custom Fields* support bulk updates directly from the summary row
* Each bulk change applied to *Custom Fields* prompts for confirmation and optionally captures a note for audit history. 
* Compatible with pinned columns and filters.

### **How It Helps**

This feature reduces the need for repetitive manual edits, offering a higher-level control to manage grouped tasks more effectively. Teams can quickly identify progress gaps, take bulk actions with confidence, and maintain clear records of who changed what and why. Whether you're reviewing a project’s daily progress or updating subcontractor deliverables, this saves time while improving traceability.

### **Example Use Cases**

* **Trade-Wise Status Correction**\
  The planning team groups tasks by *Trade* and finds that all electrical tasks are still marked “In Progress” despite site confirmation of completion. They bulk-update the *Task Status* to “Completed” directly from the summary row—no note is prompted, but the update is logged in history for accountability.
* **Reallocation Based on Assignee Grouping**\
  A supervisor notices that an engineer has left mid-sprint. By grouping tasks under *Assignee*, they update all their tasks to a new responsible person. Since this is a direct field edit (no note required), it streamlines reassignment while maintaining progress.
* **Custom Field Flag for Design Review Required**\
  The project engineer introduces a *Custom Field (Checkbox)* called “Needs Design Clarification”. After grouping tasks under this field and identifying issues in multiple zones, they bulk-enable this checkbox for the relevant group. A **confirmation note is prompted**, and they add: “Drawing mismatch observed on site – flagged for design team.”

{% hint style="info" %}

### **Key Considerations & Caution Points**

**Summaries are limited to specific columns** – not all fields in Table View support summarisation. 

**Bulk allocation is only supported on selected fields**, primarily:

* *Task Status*, *Trade*, *Zone*, *Assignee*, *Custom Fields (select, radio, checkbox)*.

**Only custom fields (select, radio, checkbox)** support **confirmation modals** with the option to add a note – other fields do not prompt for justifications.

**Date fields** such as Planned/Actual/Baseline Start or End only support **summary views (Min/Max)** – no bulk editing.

**Progress and Variance** support summary display (*Average*) but are **not editable** through the bulk action row.

**Attachments column** displays an object count summary but cannot be edited or allocated in bulk.

Bulk edits made without confirmation prompts are still **logged for traceability** in the task history
{% endhint %}

{% hint style="warning" %}
**Early Release**: This is an early access release, and we’re actively gathering feedback to enhance the feature in future updates.

**Occasional Refresh Required for Summaries**\
After making bulk updates for multiple levels of grouping, it may be necessary to refresh the view to ensure that the summary fields reflect the most recent changes accurately.
{% endhint %}