Concourse & Jira DC Portal

✅ Put Simply

Allow users to generate a polished, client-ready export pack that contains only the Playbook content tied to the Building Blocks inferred during scoping — customized based on the specific engagement context.

✅ Why It Matters

During pursuit and proposal stages, teams need a fast, reliable way to articulate how PwC delivers work. Playbooks — as the structured expression of our delivery frameworks — are the authoritative source of this. But without a way to easily pull scoped, relevant Playbook content together, teams are left manually hunting for content and assembling inconsistent decks.

The Scoped Export Pack ensures that:

• Content is automatically filtered based on what’s in scope.

• Only relevant Playbooks and their Frameworks, Activities, and Deliverables are included.

• The output is formatted for client-facing use, helping pursuit teams move quickly and confidently.

This elevates the professionalism of our delivery story and eliminates friction from pursuit workflows.

✅ What’s Needed (Static):

• JSON packages for Activities, Deliverables by Stage or Block

• Static files (.docx, .pdf, .pptx) for manual export simulation

✅ High-Level Acceptance Criteria

1. Given a user completes engagement scoping in Concourse,
   When Building Blocks are inferred from selected Offerings,
   Then the system should allow the user to initiate a Scoped Export Pack that pulls Playbook content tied to those Building Blocks.

2. Given the export pack is generated,
   When the user reviews the document,
   Then it should include:

   • An overview of each included Playbook

   • Frameworks within each Playbook, aligned to the PDM lifecycle

   • Associated Activities and Deliverables (with optional descriptions)

   • Visual content such as the PDM diagram with active Framework highlights

   • Optional value statements and differentiators

3. Given multiple Playbooks are included,
   When the export is structured,
   Then the content should be organized clearly by Playbook name and PDM stage.

4. Given content may need to be tailored for internal or external use,
   When a user chooses the export format,
   Then they should have options to include or exclude internal notes, tags, or placeholders.

5. Given Playbooks are updated in the system,
   When a new Scoped Export Pack is generated,
   Then the export should always reflect the most current version of each Playbook.

6. Given a user is in a pursuit setting,
   When they download the pack,
   Then the result should be available in a clean, shareable format (e.g., PDF or formatted PowerPoint deck).

Not in Scope:

• Live templating or real-time export formatting

Related Functional Requirements: FR4.1, FR3.3