This tutorial (YouTube video by William Doyle MRICS) explains how to capture and allocate delays on construction sites. It describes two capture approaches: (1) record an activity-level reason for variance using a free-text field and contract-based categories (e.g., weather, ground conditions), and (2) log discipline/activity-level delay entries with time recorded against specific causes (e.g., plant breakdown, materials not on site). The video then covers allocation options (assign delays to an activity or a specific item), and shows reporting/tag analysis that aggregates lost working time by tags and allows filtering by discipline or activity. The presenter encourages viewers to suggest future topics and points to a knowledge base and the YouTube channel for more content.
Chapters
Foreign. Gather. In this video I'm going to talk to you about how to categorize and first capture issues affecting progress or delays on site. So let's go into some example records. So there's two ways to do this gather. We give you the flexibility to do it the way that you need to do so the step sheet to focus on our worklog and hours allocation. So option one, we've got an activity here which we not completed. We can see the reason for variance which is a free text field. We can add as much issues as we want here. We could say it's flooded, we rain. Okay. So we're gathered in whatever reason we thought was applicable here. Choose the the various category from your contract. So this one could be ground conditions, potentially could be weather, unexpected physical conditions, what we go for. So we can start to see that and that we're 50 meters rather than 100. That's step one or option one, sorry option two is that we actually start to capture as a discipline issues, effective progress list of activities. It's equivalent breakdown, plant breakdown, how you categorize that materials not on site, whatever it needs to be. And then we capture the time against it, the reason variance as well. So we can see here how long it's broken down for. Maybe it was broken down for maybe two hours. So it's like 300 hours and we can start to see that. Then we get to allocation. So allocation again we've got two ways of doing this. We can allocate against that activity or maybe against a specific one. So equipment breakdown, two hours. We can put that reason for various in there. Whatever it needs to be. We can put all that information there. So simply open up. See here two hours. We just put that reading variance in. So we make it quite flexible for people to do so. How's that looking reports? Well, if we go back to the shift record list, we've already tagged equipment breakdown and physical conditions. There's two different delays here. We've tagged it with the relevant early warning, potentially the conversation event associated with that in reports. I probably just fast forward straight to some example from the key insights. So we look at the tag analysis and we can start to see lost working time by tags. You can also filter this by discipline activity however you want to do it. So yeah, have a play around. That's just a quick video allow you to understand how to capture issues affecting progress and potential delays on site. If you like this video, feel free to suggest some more. This suggestion was from the team at Murphy's. Please subscribe to our YouTube channel or look at our knowledge base for more of these videos. Thank you much.
