We would like to request the development of a Schedule Change Tracking Module within Hive to improve project transparency, schedule governance, and portfolio-level reporting. Our organization manages numerous high-impact initiatives, and visibility into schedule variance - at both the task and milestone level - is essential for accurate forecasting, risk mitigation, and executive reporting.

The requested enhancement would allow Hive users to automatically or manually capture schedule changes over the lifecycle of a task or milestone. This added functionality would help project managers quickly understand delays, root causes, and impacts to critical paths and go-live dates.

Requested Fields / Data Points

The module should track the following fields for each task or milestone:

1) Task / Milestone Name

Description: Display the associated task or milestone.

Preferred Functionality: Ability to link the entry directly back to the task or milestone card in Hive.

2) Original End Date

Description: The originally planned completion date recorded at task creation or at baseline.

3) Actual End Date

Description: The actual or updated projected completion date.

4) Delay in Days (Calculated Field)

Formula: Actual End Date – Original End Date.

Purpose: Provides immediate visibility into schedule slippage.

5) Go-Live Impact in Days (Calculated if Possible)

Description: Automatically calculates expected downstream delay to the project go-live or target completion date.

6) Critical Path Impact in Days (Calculated if Possible)

Description: Quantifies how the schedule change affects critical-path activities and overall project duration, based on dependencies.

7) Reason Notes (User-Defined Dropdown List)

Description: Selectable list of standardized reasons for schedule changes (e.g., resource constraints, vendor delay, scope change, technical issue), with optional free-text notes.

Purpose: Helps with root-cause analysis and reporting accuracy.