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.
Extensions of existing engagements often build on the original work and deliverables and leverage the same team. Previously Map would support the addition of multiple WBS codes, in the same way Concourse should support links to multiple FlexForecast budgets and Salesforce opportunities.
See business case here for related request
CONC-I-658
Hi Michael! This is amazing information! Thank you so much for sharing this! This will be a great starting point for us as we begin our research!
There's actually two idea in this portal that you might find interesting as well! CONC-I-458 relates to change orders and you didn't directly call this out but CONC-I-349 focuses on adding several Flex IDs to one workspace. Feel free to check out those ideas as well!
Thank you again, we really appreciate it! We'll stay in touch as we continue our research journey!
I would say most of my projects are extended in some form, the main forms being:
Change Order to original SOW / EL: generally this would be incremental work related to the original contract - this is the main case where I believe it would be appropriate to link engagements. In my experience this could be as many as 20-30% of my engagements. I've generally only seen 1-2 change orders on an engagement before creating an entirely new contract, typically not for more than a few months.
New SOW / EL: often this would be an entirely new scope of work for the same client / business unit - it may / may not be appropriate to link engagements depending on overlap of scope. I would say this is even more common (maybe 50-60% of engagements) but there may need to be guidance around what conditions must be present to link an entirely new contract to an existing Concourse engagement
Metrics / Info:
For one engagement we had a Concourse support resource say we could continue to use the same Concourse file for extensions of a single engagement, so we did, but did not have the ability to include information for the additional Salesforce opp, WBS code, etc. So there is a risk to data quality that workspaces may be used related to an engagement not listed in the workspace properties / links.
Other benefits of this feature would be reduced setup time and confusion for the project team as project phases transition, ability to effectively leverage relevant materials / assets across phases, and more streamlined review for engagement leadership
Hello everyone! Thank you again for submitting and voting for this idea! As we do our research we'll be reaching out with questions! Here are a couple of things we would love to get some clarity on:
On average, what percentage or number of your engagements require an extension?
Are there any other relevant metrics we should know about? Time it takes in Concourse to try and workaround this, length of extensions, etc.
We'll continue to reach out and stay in touch as we have more questions. Thank you all again!
Thank you for submitting this idea - we’re excited to see the interest it has generated! We’ve established a Concourse research team that is completely focused on exploring user generated ideas like this. I've assigned this to our Concourse research team and they will be in touch as they explore this idea further!