You are here

Extensions of Time (EOT)

Learn about the Extensions of Time process and how it can help improve the way you work.

What is it?

An Extension of Time (EOT) is a request to push out a completion or delivery date when there has been a delay caused by something out of the requestor’s control. The EOT goes through a process that grants an approval or rejection and, when approved, often leads to the submission of a claim.

Aconex is routinely used for the management of Extensions of Time across many industries and projects and the diagram below depicts the basic steps typically seen in an EOT process.

Why would you want it?

Projects that don’t have a good way to manage and track EOTs tend to have more issues. An efficient and effective process for managing EOTs helps the project stay on time and budget.

What does it look like?

Preparing to introduce an EOT process

Here are some things to consider when looking at introducing an EOT process:

Are all participants in the process using Aconex?

  • Aconex Mail allows both users and non-users of Aconex to participate.

Does the process need to be managed in the field?

  • Mail processes can be done in Aconex Mobile

Will reference or additional information be included at various points in the process?

  • Both Mail and Workflows allow each participant to include information with their response, Mail embeds that information while Workflows stores that information as part of the workflow record.

What are the reporting requirements?

  • Both Mail and Workflows allow you to track and report on status and response in real-time. Mail also allows you to report on to the details contained in the EOT itself.

Does your EOT have to end up in another system eventually?

  • Mail can be converted into other outputs or pushed automatically into other systems via software integrations.

  • Workflows make use of a registered document that can be downloaded and transferred.

Will every EOT follow the same path?

  • Mail allows for flexible distribution with minimal structure required.

  • Workflows are templated and repeatable for fully structured flows.

Does your procedure require wet signatures?

  • Mail allows you to include wet signatures as part of the procedure. Many clients find that the Aconex login and security model satisfies this requirement.

  • Workflows make use of a registered document so wet signatures can be included in the document itself.

What is our recommendation for managing it with Aconex?

We think Mail is the most powerful way of managing EOTs.

There are some circumstances where using an alternative, such as Documents and Workflows, may be best. If you’re not sure which option is right for your project, an Aconex consultant will help you work through your specific needs.

Additional Aconex tools you could use

Common features we see clients take advantage of when using Mail are Mail Forms, Restricted Fields and Mail Type Rules. Mail Forms and Restricted Fields allow project teams to capture and report on additional structured data while Mail Type Rules provide guidance as to what types of mail are best to respond with.

If your project is using Workflows, we typically see Templates and Review Sets configured. Templates provide a quick, repeatable process while Review Status Sets allow projects to ensure the right review terminology is used for the procedure.

Any feedback?

Thanks. A ticket has been opened with the Support Central team.