Concourse & Jira Cloud Portal
Put Simply:
We’re shifting from a flat deliverable structure to a more nuanced taxonomy under the new term “Engagement Artifact.” This change introduces four distinct categories—Deliverable, Work Product: Client, Work Product: Internal, and Event—which better reflect the full range of artifacts created during engagements.
Why It Matters:
Improves clarity and usability: Users will better understand the type and purpose of each item in the delivery plan.
Supports standardization and consistency: Clear definitions help ensure the right terminology and artifacts are used in proposals, delivery, and compliance reviews.
Enables more intelligent structuring and reporting: Systems can filter, report, and visualize engagement data more meaningfully based on artifact type.
Reduces confusion between draft and final versions of client-facing work.
What’s Needed:
Update the PDM data model to rename L4 items as “Engagement Artifacts” and apply the four new subcategories.
Update UI across scope, delivery plan pages, and other areas of concourse to display these categories.
Integrate taxonomy changes into the Admin Portal for governance and ongoing content curation.
Validate mapping of existing L4s to the new taxonomy.
Coordinate timing of rollout with user training and system integration teams.
Update Concourse Guide
Conduct testing across systems to avoid disruptions in workflows or reporting.
New Taxonomy
Categorization Type |
Definition |
Examples |
Viewable to client? |
Engagement Artifact |
An engagement artifact is any document, file, or material created, used, or referenced during a project or engagement. These artifacts encompass project plans, deliverables, meeting minutes, reports, templates, and other documentation that supports the execution and management of the engagement. |
||
Deliverable |
Deliverable is a work product or outcome produced during an engagement and intended for the client. It is the tangible result of the engagement's efforts that will be handed over to the client, such as final products, reports, or services that meet their needs and expectations. |
Business Strategy |
Yes |
Work Product: Client |
A client work product is any interim document or output that is created during the course of a project that is not intended to be a final deliverable to hand off to a client. These might include research notes, drafts, internal analysis documents, spreadsheets, meeting notes, and other materials that are used to develop the final client deliverables. |
Process Taxonomy: Initial |
Yes |
Work Product: Internal |
An internal work product is any document or material created during an engagement for use within PwC. These can include internal reports, plans, and other documents that help manage and execute the engagement. |
Billing Process: Draft |
No |
Event |
An event is a specific activity or occurrence during an engagement. These can include meetings, workshops, milestones, and reviews. They help keep the engagement on track, facilitate communication, and allow for progress assessment and adjustments. |
Client initial briefing: Conduct |
Yes |
1
Promoted to Feature
0
Promoted to Feature