Concourse & Jira DC Portal

Put Simply:
Before a project is activated in Jira, teams should be able to compare the finalized contract from Icertis to the scoped delivery plan in Concourse. This ensures that what the client has agreed to in writing is exactly what’s being delivered—catching mismatches before they turn into delivery or compliance issues.

Why It Matters:

• Prevents misalignment: Validates that all deliverables in the contract are represented in the delivery plan—and vice versa.

• Reduces risk: Catches discrepancies before Jira activation, when changes are much harder to correct.

• Supports audit and compliance: Provides a clear reconciliation point between legal agreements and delivery obligations.

• Improves client trust: Ensures teams deliver on exactly what was promised—nothing more, nothing less.

• Streamlines approvals: Gives engagement leads, legal, and PMs a final checkpoint before committing the plan to execution.

• Sets up for future automations: including billing and client approvals.

What’s Needed:
🔍 Comparison Logic & Matching Engine

• Parse deliverables from the signed Icertis contract

• Align and compare those deliverables with the Concourse delivery plan (by ID, name, metadata)

• Highlight any missing, extra, or mismatched deliverables

📄 User Experience Flow

• Add a “Compare to Contract” step before Jira activation

• Show side-by-side comparison or flagged mismatches

• Provide guidance or action prompts to reconcile issues before proceeding

Not in Scope:

• Automatically resolving mismatches—users must manually reconcile discrepancies

• Real-time editing of the contract from Concourse—this flow is read-only for contract comparison