You are here

Progress Claim (or Progress Payment)

Discover how a structured Progress Claim (or Progress Payment) process can help improve the way you work.

What is it?

A Progress Claim (or Progress Payment) requests approval to apply for payment for a piece of work. It is submitted on an agreed upon schedule (typically monthly) and provides evidence of the completion of work being claimed.

Aconex is routinely used for the management of Progress Claims across many industries and projects and the diagram below depicts the basic steps typically seen in a Progress Claim process.

Why would you want it?

One of the key components of a project is its budget. Understanding how work is tracking against that budget allows project teams to make informed decisions, and managing the budget gives them insight into the overall project status.

What does it look like?

Preparing to introduce a Progress Claim process

Here are some things to consider when looking at introducing a Progress Claim 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 from the field?

  • Mail processes can be done with Aconex Mobile.

Does the process require fast turnaround?

  • Mail allows for quick replies and can be done via Aconex Mobile.

  • Workflows use a document to capture the request and approval or rejection.

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 Progress Claim itself.

Does your Progress Claim 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 Progress Claim 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 Progress Claims.

In some cases it may be more appropriate to use Documents and Workflows to manage this process. If you’re not sure which option is right for your project, an Aconex consultant will help you work through your specific needs.

Was this article helpful?

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