01Margin
Convert scope expansion into a change request
Why$6,600 of estimated delivery investment came from work added after scope lock.
ActionReview added items with the client and formalize the next-cycle scope.
\n What changed,
\n \n \n
Client SDLC ROI Report
What changed,
what shipped,
and what it cost.
A client-ready summary of delivery value, scope movement, rework, coordination, and AI-assisted delivery economics — built from the signals already flowing through your tools.
ContractsTrackerCodeReleasesCalendar
example-reports Retailexample-reports Checkout ReplatformQ1 2026
01 / 08
Section one
Executive summary
During Q1 2026, Example report workspace delivered 2 work items, merged 2 PRs, and shipped 1 release for example-reports Retail on example-reports Checkout Replatform. Scope movement after the agreed baseline: 2 additional work items entered the cycle after lock, contributing an estimated $6,600 to the delivery investment. AI-assisted delivery is not yet measured — tag AI-assisted pull requests to unlock it. Report confidence is currently 80% — improving confirmed reporting assumptions can improve confidence next period.
\n\n \n \n \n \n
\n Delivered work
2items
- Merged PRs2
- Releases1
- Milestones0
Delivery investment
—
- Coordination$150
- Scope expansion$6,600
- Rework$0
Scope expansion
$6,600
- Items after scope lock2
- Reopened tickets0
- Margin riskUnknown
AI delivery impact
Not yet measured
- Tag AI-assisted PRsto unlock
!Recommended commercial action
Discuss scope expansion before the next reporting cycle and convert recurring unplanned work into a change request or retainer adjustment.
Action this cycle
Owner · Delivery lead · due before next QBR\n \n \n \n
What shipped
Refunds fail for split tender, Card vault migration
What changed
2 items added after scope lock; 0 tickets reopened; 1h of attributed coordination.
Needs attention
Ticket-to-PR linkage at 100%, meeting tagging at 100%, and explicit AI-assisted work tagging.
example-reports Retailexample-reports Checkout ReplatformQ1 2026
02 / 08
Delivered work
What shipped
\n \n \n \n \n
\n Completed work items
2
Across feature, fix, and platform
Merged PRs
2
100% linked to a ticket
Releases
1
In the reporting period
Delivery milestones
0
Customer-visible checkpoints
| Work item | Type | Evidence | Status | Completed |
|---|---|---|---|---|
Refunds fail for split tender EXAMPLE-REPORTS-42 | Bug fix | 1 PR | Shipped | 2026-03-01 |
Card vault migration EXAMPLE-REPORTS-1 | Feature | 1 PR | Shipped | 2026-02-10 |
Delivery proof, not developer surveillance. Scopeworth links every report claim back to delivery evidence — tickets, pull requests, releases, and merges — so a client can verify what shipped without asking for a code review.
example-reports Retailexample-reports Checkout ReplatformQ1 2026
03 / 08
Delivery investment
What it cost
\n \n \n
\n Total estimated delivery investment
—
Period delivery spend is not available. Contract value is not period spend.
Cost composition
Scope expansion · —
Meetings & coordination · —
Rework · —
Feature build, review and other delivery support are attributed once Invoice Defense's cost model is connected.
Estimated cost by category
These figures are directional and depend on available data, role-based cost assumptions, and project mapping quality. See report confidence.
example-reports Retailexample-reports Checkout ReplatformQ1 2026
04 / 08
Margin risk
Where scope changed
Estimated scope expansion impact
$6,600
Work added after the original scope was agreed, plus reopened and re-sized baseline work.
Margin risk: UnknownConvert to change request
\n \n \n \n \n
\n Added after scope lock
2 items
Tickets created after the cycle started
Reopened tickets
0
Reopened baseline work
Estimates grown after lock
0
Baseline items re-sized
Attributed coordination
1h
Attributed meetings
Scope expansion signals
\n| Signal | Count | Estimated impact | Suggested action |
|---|---|---|---|
Tickets added after scope lock Created after the baseline | 2 | $6,600 | Convert into change request |
Reopened baseline tickets Reason for reopening not classified | 0 | $0 | Clarify acceptance criteria |
Estimates grown after lock Baseline items re-sized mid-cycle | 0 | $0 | Add review owner earlier |
Attributed coordination meetings Meeting purpose not classified | 1h | $150 | Separate discovery from delivery budget |
“Why is this month’s invoice higher than expected?”
What the delivery evidence for Q1 2026 shows. The team delivered 2 work items, 2 PRs and 1 release for example-reports Retail during Q1 2026, while also absorbing 2 additional work items worth an estimated $6,600 after the scope baseline.example-reports Retailexample-reports Checkout ReplatformQ1 2026
05 / 08
Quality & rework
Where rework happened
\n \n \n \n \n
\n Rework cost
$0
— of delivery investment
Reopened tickets
0
Of 2 completed
Estimates grown
0
Baseline items re-sized
Unestimated movement
0
Counted, not valued
Interpretation. Rework here is reopened and re-sized baseline work, not individual performance. This suggests an opportunity to improve scope clarity and acceptance criteria before implementation starts — not to add pressure on individual engineers.
\n Recommended action. Add a scope confirmation checkpoint before implementation starts on high-complexity items. Capture acceptance criteria in the ticket and confirm with the client before the work enters the build queue.
example-reports Retailexample-reports Checkout ReplatformQ1 2026
06 / 08
AI-assisted delivery
Modeled AI cycle-time comparison
Not yet measured. AI-assisted delivery economics need at least one merged pull request tagged as AI-assisted and one non-assisted baseline merge in this project. Add an ai-assisted label or commit trailer to relevant work to unlock this section.
example-reports Retailexample-reports Checkout ReplatformQ1 2026
07 / 08
Trust & data health
How trustworthy this report is
80%Score
Medium confidence
Weaker coverage on confirmed reporting assumptions and release / deployment evidence. Review the recommendations on this page to improve evidence coverage.
Why this matters. Scopeworth does not pretend messy delivery data is perfect. Report confidence shows where the evidence is strong, where assumptions were used, and what should be improved before relying on the report for commercial decisions.
\n Recommended data improvements
\n1. Add client / project labels to all relevant tracker issues
2. Include ticket IDs in PR titles or branch names
3. Tag client / project names in calendar events
4. Explicitly mark AI-assisted work where possible
Scopeworth focuses on client, project, and team-level delivery proof. It is not designed to rank individual engineers or create performance-review leaderboards. Delivery proof, not developer surveillance.
example-reports Retailexample-reports Checkout ReplatformQ1 2026
08 / 08
From insight to action
What to do next
02Process
Separate discovery from implementation budget
Why1 meetings (1 h) were attributed to this project.
ActionCreate a dedicated discovery / clarification budget bucket.
03Data
Improve ticket-to-PR traceability
Why0% of PRs were not linked to tickets.
ActionRequire ticket IDs in branch names and PR titles.
04AI
Track AI-assisted work explicitly
WhyAI-assisted delivery cannot be measured until assisted work is tagged.
ActionAdd an AI-assisted field or label to relevant work items.
05Client
Use this report in the next client review
WhyThe report provides a shared view of shipped work, cost, scope movement, and risks — useful for QBRs, retainer reviews, and invoice discussions.
ActionUse the executive summary and scope expansion sections in the next QBR or invoice discussion.