Work starts when conditions allow
Estimates, dependencies, skills and calendars affect scheduling. Tasks that cannot be scheduled remain visible in the result.
The API and screen are built in parallel.
Testing takes days 7–8. That is part of the timeline.
Urgent work takes day 7 for the same QA specialist.
The impact is visible. The team confirms the priority.
Two questions about your process. See how planning time could change if RunMyPlan handles the calculation.
Multiply monthly iterations by time per iteration. Enable JavaScript for an interactive estimate. Compare the time with your own plan. Try it with your plan →
Difference: 6 h 58 min per month.
Per iteration: 15 min to prepare and review + ≈30 s to calculate. Excludes initial setup.
Check the highlighted values to see the estimate.
There is no time saving. See whether the calculation helps with other decisions.
Compare replanning time with your usual process.
Try it with your planOpen the betaThe estimate depends on your inputs. Forecast accuracy must be checked separately against actual dates.
The focus is on work readiness and delivery constraints. A fully booked team alone does not explain a finish date.
Estimates, dependencies, skills and calendars affect scheduling. Tasks that cannot be scheduled remain visible in the result.
See what helps deliver the result sooner. Additional work is useful when it does not create another queue.
A queue for a specialist, dependent work or an unavailable environment becomes something to act on, rather than a guess about dates.
Show how the date is calculated and which inputs affect it. The team decides on commitments and buffers.
Scroll the timeline left or right.
QA calendarFour work items, API and screen in parallel, and one day when QA is unavailable.
The same scenario as above: parallel work, waiting and testing make up the forecast. Adding all task durations does not give the delivery time.
The API and screen are ready by the end of day 5. QA is unavailable on day 6, so testing starts on day 7.
API and screen work run in parallel: the longer branch determines the duration, followed by waiting and testing.
Estimates, availability or priorities changed? Update the inputs and run a new calculation before agreeing a date.
Start the discussion with specific work and dates. Check a new scenario instead of manually moving every related task.
Which work will give way to the urgent task? How far will the finish move? Discuss the impact of the chosen priority.
Add technical debt, a small task or keep a buffer? Define a scenario and check its impact on the main plan.
Before recalculating, review the summary of input changes. The team chooses additional tasks; completed plans can be compared manually.
You control the data and rules. The algorithm calculates the work sequence and forecast under those conditions.
Import your backlog from XLSX and confirm estimates, dependencies, people and availability.
Built on confirmed dataWork sequences and forecast dates that account for your constraints. You can also see work that could not be scheduled.
Deterministic calculationAgree on changes to scope, priority or availability. A new calculation helps assess the impact; the team makes the decision.
A forecast to inform the discussionDates are calculated by a deterministic algorithm. The result can be reproduced with the same data snapshot and the same algorithm and rules version.
Daily tasks stay in your system. For the first calculation, prepare your backlog in XLSX and confirm the team's calendar.
Your team updates the tracker through its usual workflow.
Upload tasks from a spreadsheet and confirm the column mappings. Example files are available to help you get started.
Available in betaConnect your calendar to account for meeting time in calculations. Connection availability depends on your Google account.
Available in betaRead-only task import. Connection availability depends on your project settings.
Limited accessIf your source can export tasks to a spreadsheet, prepare an XLSX file for import. Direct connectivity depends on the source.
Start with XLSXTake one task source and a specific replanning situation. Compare the first result with how you usually rebuild the plan.
Contact supportMeasure the time spent preparing and revising the plan. Note which decisions the result helped you make.
If you need help with your first calculation, we can discuss assisted setup separately.Then test other questions: can you tell what urgent work will delay, why the next stage is waiting and how the timeline adds up? Then try a complex case of your own and see whether the calculation helps you decide.
No. These are indicative figures: about 30 seconds to recalculate and about an hour for initial setup. Actual time depends on data volume and quality. Compare them with actual times on your own plan.
Your team keeps its usual tracker and daily workflow. Data must be prepared for calculation. Import support varies by source; the connection method is checked separately.
No. The date is a forecast based on confirmed inputs. Estimates, availability and priorities may change. The team assesses buffers, risks and external commitments.
Available time must be matched with ready tasks, skills and dependencies. You can test a scenario proposed by a person; automatic selection of additional tasks is planned for future development.
No. A deterministic algorithm calculates the plan. The team confirms the data and rules.
Sign in to the beta, create your workspace and set up a team. Start with one XLSX task set. Contact support if you need help.
Create a workspace, set up your team and upload your backlog. Your first calculation helps you check the inputs.