Progress Updates can be recorded to represent any delays and improvements made to a Task over time. As the plan progresses the team can log updates to keep the plan accurate and allow for a deeper understanding of the leading causes of delay and who's responsible.
Delays can be added to any day of a Task to show it's no longer on track to finish as planned. Just hit the Thumbs Down, choose a Delay Reason, log the days of impact and add optional comments or photos. It'll update the schedule automatically ad start building your delay history. Delays can be added to a Task from anywhere in the project, but let's start by looking at recording a Delay from List View.
Open a List View
Click on the Task card
Configure your delay by selecting a Delay Reason, impact type, days of impact, comments, images and record date
Use the Thumbs Up to mark a Task as On Schedule. You can log that work went ahead as planned or even ahead of schedule, and optionally pull the end date in if things are moving faster than expected. Improvements can be added to a Task from anywhere in the project, but let's start by looking at recording one from List View.
Open a List View
Click on the Task card
Configure your On Schedule or Shorten event by selecting an impact type, days of impact, comments
Changing the dates of a Promised Task will automatically trigger a Progress Update. Changing the dates of Promised Tasks in a chain will trigger an option to apply Progress Updates to other Tasks that are Promised in the chain.
Update the end of a Promised Task
Configure your Delay by selecting a Delay Reason, impact type, days of impact, comments, images and record date
If you have additional Promised Successors, choose Yes to apply the same delay to the linked Tasks
Select
See also:
When a Progress Update is added, the Task Colour for that day will change to show the Progress Update added for that day. Red represents a Delay and green represents On Track or Shortened.
Open
Make sure that Show Progress Updates is enabled
Days with delays turn red
Days that are On Track or Improved turn green
Each Task keeps a running record of delays, improvements and updates - including who made the change, when it was logged and what the impact was.
Right Click a Task and select View Details
Click the icon to open the Activity Log
See a chronological list of all Delays and Improvements added to the Task over time
See also:
If a delay or improvement was logged by mistake, it can be removed from the Task. The original event itself will still be visible in the Task's activity log as a past record, but the delay & impact will not count on the Task any longer.
Open the Task in the right-hand panel and click
Hover over the Progress Update and click the ...
Click Delete
Creating Delay Reasons lets you build a reusable library of Delay Reasons to add when adding a delay to Tasks.
Open the Delay Reasons page, then click
Create your custom Delay Reason by entering a name and selecting a category
Once Delays have been logged, you can filter any View to show Tasks impacted by specific Delay Reasons - or simply highlight all Tasks that have recieved any Delay at all.
Click and
Select Delay Reason in the first dropdown
Select from Is, Is Not, Is Empty and Is Not Empty
See also: create & share
As the team starts to record delays against Tasks, all updates (including Delays, On Track & Improvement events) can be traced back to the responsible Task Owner or Subcontractor. This makes it easy to understand how all parties are performing across the project.
User Power BI to build custom reporting on delays and performance, based on data in your weekly Published Versions. Aphex provides free templates as a starting point but everything can be customised to suit your project reporting requirements.
Utilise Aphex Insight to track Delay Concentration by Delay Reason. See trends and drill down into specific Tasks to identify which Delay Reason has the highest delay concentration.
See also:
imagesrecord dateNoThe Net Delay Number is shown as a on the end of the Task Bar
Select your desired Delay Reason in the third dropdown
Move
A tasks's start and end date has been moved (pushed later)
Selected working day to record the event against
Type
Delayed On Schedule
Improved
Reason
Reason for the change. This can be configured by each project individually and typically contains reasons such as "Awaiting Access".
Amount
Impact of the update is recorded in a Value that represents a duration in working days (+ or -)
Amount by
User who recorded the update
Created at
Timestamp of when the update was recorded
Shorten
A task’s end date has been improved (brought earlier).
Move
A tasks's start and end date has been moved (brought earlier)
Environmental
Inadequate Planning
Insufficient Resources
Prior Work
Quality
Safety
Scope Change
Submittals and Approvals
Multi-select