Concourse Feedback


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.


PROVIDE YOUR FEEDBACK

ePro

    Estimation in Scoping | Estimation Landing Page

    Determine if/how we want to design the transition between scoping and estimation. In other words, after a user leaves the Delivery Plan page and before the first estimation step (likely Drivers or Work Item Assignment), consider building a landing...
    Carly Hu 11 months ago in  0 PM Refinement

    Triangulated Estimation Workflow

    The hand-offs between the Solution Master spreadsheet, E Pro effort model, and Flex tool create a looping, manual process (“spreadsheet → E Pro → Flex → spreadsheet”) that consumes days of effort and causes repeated re-work. Although Flex can impo...
    Katie Cousino about 1 year ago in  0 In Review

    Estimation in Scoping | Multi-Model Estimations

    Put Simply: When an estimate includes multiple estimation models, users can edit details for each model independently and switch between models in the estimation flow. I would say this is still in decision but almost certainly correct Acceptance C...
    Carly Hu about 1 year ago in  0 Not started

    Real-Time Feedback on Estimation Inputs

    Put Simply: Give users immediate visibility into how their inputs — like drivers, complexity, or accelerators — impact effort estimates as they make selections. Acceptance Criteria: Changes to inputs (e.g., increasing complexity counts, enabling...
    Carly Hu about 1 year ago in  0 Not started

    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 t...
    Garrett Kelchner about 1 year ago in  0 Not started

    Role-Level Roll On/Roll Off Timelines

    Put Simply Statement: Configure staggered start and stop dates for each role on a Team within an Estimation Model. Why it Matters: Models resource usage and general delivery timelines more accurately, improving planning and cost estimation. i.e. I...
    Garrett Kelchner about 1 year ago in  0 Not started

    Support for Phased Engagements

    Put Simply Statement: Enable modeling and estimation across multiple phases and years for complex projects. Why it Matters: Supports real-world sales and delivery cycles, especially for ERP and AI projects, increasing accuracy and stakeholder conf...
    Garrett Kelchner about 1 year ago in  0 In Review

    ePro-->Flex Integration

    Put Simply Statement: Export hours, staffing plans, and contractor data directly and accurately into Flex Why it Matters: Streamlines budgeting, reduces manual entry, and ensures data integrity across connected systems. What’s Needed: Integratio...
    Garrett Kelchner about 1 year ago in  0 Not started

    Accelerators (AI vs. Non-AI)

    Put Simply Statement: Assign opt-in or opt-out savings by work item and distinguish between AI and non-AI tools. Why it Matters: Supports margin management and provides visibility into AI’s impact on project delivery and profitability. What’s Need...
    Garrett Kelchner about 1 year ago in  0 Not started

    Dynamic/Conditional Drivers

    Put Simply Statement: Allow a single user input (driver) to impact multiple work items differently. (i.e. a Driver has 1.5x / 2x / 2.5x uplift for Driver 1 / 2 / 3 Allow a driver to have varying impact depending on Project details (i.e. N of Offer...
    Garrett Kelchner about 1 year ago in  0 Not started