How the finish date is calculated
Visibr works out a plan's finish date from two things people enter: the work, in days, and the people, in days a week. The rule is one division, counted over the calendar one working day at a time.
What is entered and what is computed
Entered by people
- Each piece of work, with an estimate in person-days, in steps of half a day.
- Each person on the plan, as a percentage of the days a week they can work (5 at most).
- The start date of the plan.
- The target date: the date the plan is measured against.
Computed by Visibr
- The forecast finish date.
- The weeks the work will take.
- The start and end of each piece of work.
- Whether the plan is on track, late or unstaffed, and by how many working days.
The target is the only date a person types. The finish date cannot be typed, dragged or overridden.
The rule
time = scope ÷ people
weeks to finish = days of work left ÷ days of people a week
- Visibr counts Monday to Friday as working days. Saturdays and Sundays have no capacity.
- The forecast starts on the first working day on or after the later of today and the plan’s start date.
- A person gives a plan their days a week times their percentage, spread evenly over the five working days: someone with 5 days a week at 50% gives half a day of work each working day.
- Each working day’s capacity is spent on the open work from the top of the list down. A piece of work starts on the first day any of it is done and ends on the day none of it is left.
- The forecast finish is the day the last piece of open work ends.
- Work that is done or cut is not counted. Blocked work is still counted: the forecast assumes it will be unblocked.
- A plan is late when its forecast finish is after its target. The slip is the number of working days between the two.
- When work remains and nobody is allocated on any later day, the plan has no finish date. It is shown as unstaffed, with the days of work that have no one to do them.
- The forecast looks at most 780 working days ahead, which is three years.
- Every figure is rounded to one decimal when it is shown.
The worked example
A plan starts on a Monday. It has two pieces of work, Design at 5 days and Build at 10 days, and one person who works 5 days a week, all of it on this plan.
| Work | Days | Starts | Ends | When |
|---|---|---|---|---|
| Design | 5 | Mon 4 Jan 2027 | Fri 8 Jan 2027 | week 1 |
| Build | 10 | Mon 11 Jan 2027 | Fri 22 Jan 2027 | weeks 2 – 3 |
15 days of work ÷ 5 days a week = 3 weeks, which is 15 working days. The finish is the Friday of week 3: Fri 22 Jan 2027.
The same plan, late
Put the target on the Friday of week 2, Fri 15 Jan 2027. The plan is 5 working days late: 10 of the 15 days fit before the target and 5 do not.
Visibr then gives three ways back to the target, each worked out from the same numbers.
| Way back | Amount | How it is worked out |
|---|---|---|
| Cut scope | Cut 5 days of scope | The days of work the forecast does not finish by the target, rounded up to half a day. |
| Add people | Add 2.5 days a week of people | Those 5 days ÷ the 2 weeks from the start to the target, rounded up to half a day a week. |
| Move the target | Move the target to Fri 22 Jan 2027 | The forecast finish. |
An example with part-time people
Two people work on a plan with 26 days of work: one at 100% and one at 50% of a five-day week. Together they give 1.5 days of work each working day, which is 7.5 days a week.
26 days ÷ 7.5 days a week = 3.5 weeks, which is 17.3 working days. The work ends during the 18th working day: Wed 27 Jan 2027.
Assigned work
In Visibr a piece of work can be assigned to one person. Assigned work uses only its assignee's capacity; unassigned work uses whatever anyone has left that day. With nothing assigned, the result is the plain division above. Work assigned to someone who has no capacity on the plan on any later day cannot finish, and the plan is shown as unstaffed.
Logged time
When a plan in Visibr keeps a timesheet, the time logged on a piece of work is taken off its estimate, and the forecast spends capacity only on what is left. Work with more logged than estimated is flagged as over its estimate until it is re-estimated or marked done. Time logged on no particular piece of work counts in the timesheet only.
What is not modelled yet
Visibr keeps the calculation small and exact. These are real needs it does not cover today:
- Public holidays and time off. Every Monday to Friday counts as a working day.
- Days off for part of a week. A person’s capacity is the same every week of an allocation.
- Estimates given as a range, and the probability of hitting a date.
- Skills. Any person on the plan can do any work that is not assigned to someone.
- Dependencies between pieces of work, beyond their order in the list.
- Time zones. Dates are plain calendar dates, and today is the current date in UTC.
Questions about the calculation
Can the finish date be typed or dragged in Visibr?
No. In Visibr the only date a person sets is the target. The finish date moves when the scope, the people or their dates change, when time is logged on the work, or as days pass without the work being done.
Does Visibr count weekends and holidays?
Visibr counts Monday to Friday as working days and skips Saturdays and Sundays. It has no holiday calendar yet, so a public holiday on a weekday counts as a working day and the forecast is early by that day.
What does Visibr show when nobody is allocated?
Visibr shows the plan as unstaffed, with no finish date, and says how many days of work have no one to do them. The same happens when every allocation ends before the work does, or when work is assigned to someone with no capacity on the plan.