Spot the change.
Read the headline and hierarchy to find the commitment or group worth inspecting.
Resources
Follow the evidence.
Understand the next decision.
Know what to bring into Capasight, what its insights can tell you, and where to look next—from a portfolio signal to the work behind it.
Explore with Franklin in the app demo →Start with the inputs
Bring the plan and the work into view.
Estimates, dates, progress and team context give the insights meaning. Their availability determines which questions can be answered.
| What you provide | What you can learn |
|---|---|
| Original estimates and emerging work | Whether the work being described still matches the assumptions behind the commitment. |
| Work-item hierarchy and relationships | Which underlying items contribute to a concern at initiative, feature or epic level. |
| Start dates, due dates and sprint windows | Which commitments may slip, where timing is unclear, and which delivery periods need attention. |
| Status and remaining work | What is still open, and how unfinished or overdue work may affect new commitments. |
| Teams and delivery groups | Who carries the work, where groups share a commitment, and where ownership needs clarification. |
| Team capacity and planning cadence | Where demand may exceed available delivery capacity, even when the overall horizon appears to fit. |
The same flow as the guided tour
Start high. Follow the question deeper.
Understand the context.
Follow dates, remaining work and capacity to the evidence behind the signal.
Choose the next conversation.
Take the finding and suggested action to the people who can change scope, timing, priority or capacity.
01
Overview
See portfolio pressure, hierarchy-level findings and delivery-group context. Start here to choose where to look next.
What needs attention before the next commitment?
02
Delivery & Dates
Inspect slippage and date health, then expand a commitment to see its underlying work and explanation.
Is timing constrained by capacity, late work or incomplete planning evidence?
03
Capacity
Inspect individual sprints and delivery groups. An overall fit can still contain crowded periods.
Where is work competing for the same delivery window?
04
Remaining work & Estimation
Explore unfinished demand and emerging scope. Connect the work still to land with the assumptions in the original estimate.
Does the remaining work still fit the plan?
05
Actions
Read the insight and suggested action together. Use the evidence to focus a review with the decision owner.
What change is justified—and who needs to discuss it?
This is an exploration path, rather than a requirement to visit every screen. Franklin’s on-demand tour can guide you from any page in the demo.
Signal · Context · Action
Read a finding as a starting point.
Early signals
Look for estimate growth, slipping commitments and gaps in dates or planning evidence.
What changed—and can it be judged?
Capacity context
Check the period, group and underlying work. A late item is not automatically a capacity problem.
What is constraining the outlook?
Actions
Use the suggested next step to frame a decision. Review scope, dates, sequencing or capacity with the team.
What should we inspect or revisit next?
Key terms
A few terms to orient your exploration.
Scope integrity
Whether emerging work remains aligned with the original estimate and commitment.
Demand and capacity
The work asking for delivery time, and the teams’ ability to deliver it within the periods in view.
Forecast and commitment
The evidence-based outlook and the date you have promised. A difference is a reason to inspect the plan.
Carryover and overdue work
Unfinished work that can compete with new commitments for delivery capacity.
Sprints to clear
An indication of the time needed to clear the existing workload. It does not promise that additional work will fit.
Not judged
A result that cannot be established from the available planning evidence or configuration. Check Quality for what is missing.
Next steps
Explore, prepare or ask for help.
Explore with Franklin
Use the sample portfolio and ask Franklin to walk you through the features of any demo page.
Open the guided app demo →Prepare your planning data
Quality identifies evidence gaps. Configuration, Setup Guide and User Guide explain their purpose in the demo; detailed setup guidance belongs in the application.
Review the planning inputs ↑Bring your question to us
Discuss what you are trying to understand, the affected commitment and the evidence you have available.
Connect with us →For data handling and deployment guidance, see Security and Privacy. Support covers Capasight:Lite for Jira, Capasight for Azure DevOps and Capasight for monday.com alike, by email at contact@capasight.co.uk. For application support, include the app version — in Jira under Apps, Manage your apps; in Azure DevOps under Organization settings, Extensions — the “Data as of” time and what the screen showed. Each product is used under its licence agreement; Azure DevOps licences are ordered through the order form.
Capasight:Lite for Jira
Capacity, demand and delivery forecasts for Jira Cloud.
Ask Franklin, Capasight’s AI — in Rovo, Atlassian’s AI: whether a value stream or ART is over capacity, what will be late, when one item will really be delivered and what to fix first, answered in Capasight’s own figures about the page you have open, and only from work you can see. It needs Rovo switched on for your site; Capasight runs no AI model of its own and sends nothing outside Atlassian.
About Capasight:Lite → How to use Franklin →Capasight for monday.com
Capacity, demand and delivery forecasts for monday dev.
Ask Franklin, Capasight’s AI — in monday sidekick, beside Capasight’s board view: what is over capacity, which work will be late and why, when an epic will really land and what to fix first, answered in Capasight’s own figures about the page you have open. Its screens run in your browser; Franklin’s answers are worked out on monday.com’s own app hosting.
Install on monday.com → How to use it →