Concourse Feedback

Put Simply:
Some deliverables scoped in Concourse are contractual obligations that require client approval. This feature enables a tagged, automated workflow where those deliverables—once completed—trigger an approval process via Jira. Once approved, the deliverable and its approval metadata are sent to SaveIt for permanent recordkeeping.

Why It Matters:

• Ensures compliance: Captures and preserves client approvals for contractual deliverables, reducing legal and delivery risk.

• Closes a historical gap: Many teams forget to collect or store approvals, delaying revenue recognition and increasing exposure.

• Automates manual processes: Streamlines the handoff between delivery, clients, and storage—reducing friction and boosting consistency.

• Supports audit readiness: Provides a clear, automated audit trail for each client-approved deliverable.

• Improves delivery ops: Encourages clean, repeatable workflows for finalizing key outputs across large, complex programs.

What’s Needed:
🧾 Deliverable Tagging & Triggering

• In Concourse: Flag scoped items as “Contractual Client Deliverables”

• In Jira: Automatically apply a tag upon project creation that enables a special approval workflow

🔁 Approval Workflow via Power Automate or Jira Automation

• When tagged deliverables move to a “Client Approval” status:

  • If the file is attached in Jira → embed in client email

  • If it lives in SharePoint → send SharePoint link in client email

  • If not available → notify internal team to collect the file

📬 Client Interaction & Status Handling

• Email client with link or file to review

• Upon approval:

  • Mark Jira issue as “Client Approved”

  • Push deliverable and metadata to SaveIt

• If no approval after X days → auto-send reminders

🔐 Governance, Tracking, and Storage

• Ensure approvals and file versions are logged

• Store both in SaveIt for audit/compliance use

• Track all status transitions within Jira and SaveIt