Concourse & Jira DC Portal


Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.


For immediate technical support, please follow this guidance to open a Service Now ticket.

Change Order Support

Put Simply Statement:
Allow estimation and scoping to be adjusted for scope additions/removals

Why it Matters:
Essential for lifecycle management and contract compliance, supporting ongoing project changes.

What’s Needed:

  • UI for submitting and tracking change orders.

    • This would likely be on the scoping side of things, not on Estimating

    • Potentially would want to display "differences" in the way ePro does today?

  • Logic for updating estimates and scope.

    • would it be updating estimates and scope or making add-on estimates/scopes

  • Audit trail of all changes.

  • Early ACs:

    • Users can initiate a change order at any time.

    • All changes are tracked and auditable.

    • Updated estimates and scope are visible to all stakeholders.

    • Ability to estimate change order scope as incremental additional scope compared to original ePro estimate and send only delta scope to Flex. ​

    • Ability to create estimates for change orders that are linked to original estimate. These estimates should be differentiable for reporting purposes

  • Garrett Kelchner
  • Jul 17 2025
  • Not started
  • Admin
    David Martinez commented
    13 Oct 01:03

    Delivery estimator supports currently adding or removing things from the potential scope defined in the model. In addition to this, we have started work to get recommendation on potential items missed during the model itself. The only extra thing I could see around this would be adding custom items. Will be reviewing this to see if it still applies.