Concourse Feedback

From Nish:
Once the scope has been identified and selected for the RFP, the user will need to download the inventory of deliverables and include it as part of the response to the potential client. Can we provide an export option for the L1-L6 before activating the scope.

Internal Team Notes:

Put Simply:
Teams need a simple, standardized way to export scoped deliverables for use in Statements of Work (SoWs), RFP responses, and for delivery using client systems. This reduces manual effort, improves clarity, and builds confidence with clients by providing consistent, branded outputs aligned to what was scoped.

Why It Matters:

• Scope as a Deliverable: The scope of the engagement is typically considered a deliverable in it's own right.

• Standardization & Efficiency: Speeds up the process of creating polished, compliant documentation for internal and external use.

• Client Confidence: Gives clients a clear, accurate understanding of what they’re getting—aligned to offerings and the PDM framework.

• Sales Enablement: Supports pre-sales and demo scenarios by validating and sharing draft scopes quickly.

• Supports Iteration: Works well with draft scoping workflows, enabling export of evolving plans for review and discussion.

• Compliance-Ready: Helps meet internal legal and regulatory standards through structured, consistent documentation.

What’s Needed:

• Export options from relevant views (e.g., by offering, building block, or deliverable list).

• Consider adding: Branded, configurable templates (PDF, Word, Excel) tailored to SoW and RFP use cases.

• Access to metadata and deliverable structures via scope services.

• Role-based access controls to manage who can export and what data is included.

• This requires approval from Delivery Excellence Leadership and Risk

Not in Scope:

• Live integration with external contract systems or full automation of proposal generation.

• Manual creation of one-off templates outside the centralized export system.