A project schedule is not created by simply adding a deadline to an estimate. You also need to consider how many hours you can dedicate each week, whether approvals or other delays may affect the work, and whether the project fits alongside your other commitments.
This guide explains how to evaluate whether a project can realistically be completed on time without confusing estimated work with project duration or available time. It also shows how the schedule results in the Project Decision tool help answer different planning questions.
1. Separate effort, duration, and deadline
Planning a project begins by separating concepts that are often confused. A single number cannot describe how much work the project requires, how long it will take, and when it needs to be finished.
The total work required to complete the agreed project scope.
The time you can realistically assign to this project during a period.
The amount of project work that can be completed within the available calendar window.
The calendar time needed to complete the effort at the planned allocation.
The date the project is expected to finish under the current assumptions.
The date by which the work is required or expected to be complete.
Effort describes how much work exists. Duration describes how long that work takes based on the time available each week. A deadline is the date the project needs to meet.
A 100-hour project is not automatically a two-and-a-half-week project. That depends on how many hours you can realistically dedicate to it each week. It would require that one person devote 40 productive project hours every week with no waiting time, interruptions, or competing responsibilities. At 16 dependable hours per week, the same effort requires 6.25 weeks before calendar adjustments.
That depends on how many hours you can realistically dedicate to it each week. If the project requirements have not yet been converted into hours, the guide on estimating and defining the scope of a fixed-price project explains how to identify deliverables, activities, revisions, assumptions, exclusions, and dependencies before planning the timeline.
2. Estimate available project hours per week
Available project hours per week should represent the amount of time you can realistically dedicate to this project each week. It is not your total working time, your ideal plan, or the maximum number of hours you could sustain only for a short period.
Start from real commitments
List your regular commitments before deciding how many hours are available for a new project. Include work for other clients, administrative tasks, sales, support, meetings, and personal commitments that regularly reduce the time available.
Available project hours = Total working hours - Other commitments
Example:
Plan with realistic availability
Choose a number you can maintain during a normal week. You may be able to work more hours for a few days, but that should not be the basis for planning the entire project.
3. Distinguish available hours from productive hours
Time assigned to a project is not always spent creating the final deliverables. Communication, preparation, file organization, reviews, coordination, and administrative tasks are also part of the project and should be included in the estimate.
Available project hours per week should be consistent with what you included in Estimated work. If your estimate includes meetings, coordination, and administrative tasks, your weekly availability should also leave time for those activities. Do not reserve 20 hours only for production work and assume everything else will happen outside the schedule.
Assuming every scheduled hour can be spent on focused work creates a plan that looks realistic on paper but is difficult to follow in day-to-day work.
4. Account for multiple projects and context switching
Project Decision evaluates one project at a time, but you may be working on several projects at once. Reduce Available project hours per week before entering them instead of assuming the tool knows about your other commitments.
Reserve time for existing commitments
- Ongoing projects and recurring client work.
- Client support and maintenance obligations.
- Sales calls, proposals, invoicing, and administration.
- Training, improving your business, and internal tasks.
- Planned leave, travel, and reduced-capacity weeks.
Working on several projects takes extra time
Two projects that each receive ten hours per week may require more than twenty hours of practical effort. Switching between clients, tasks, tools, or priorities takes time and can reduce your productivity. If your attention is divided across several projects, enter a lower Available project hours per week value.
5. Plan the timeline
These metrics determine how much calendar time is available for the project, when the work is expected to finish, and whether the plan meets the deadline.
Calendar time available
Calendar time available is the number of days between the Start date and the Deadline.
Calendar time available (days) = Deadline − Start date
This value includes weekends and other non-working days because it measures calendar time rather than working time. Holidays, vacations, business closures, and changing weekly availability should still be considered when they reduce the time available for the project.
Calendar weeks available is calculated to determine the Available project capacity. It converts the calendar time between the Start date and Deadline into the number of weeks available for the project.
Calendar weeks available = Calendar time available (days) ÷ 7
For example, 35 calendar days equal five weeks, while 17 calendar days equal about 2.43 weeks.
Estimated duration
Estimated duration shows how long the estimated work will take based on the Available project hours per week you entered.
Estimated duration = Estimated work ÷ Available project hours per week
Example:
If you can dedicate 20 hours per week to the project, 120 hours of estimated work require about six weeks to complete.
This calculation assumes you can maintain the planned weekly availability. Waiting for materials, client feedback, approvals, or planned time away may extend the schedule without increasing the estimated work.
Estimated completion
When you enter a Start date, Project Decision calculates an Estimated completion based on the Estimated duration. This is the expected completion date under the current project assumptions, not a guarantee.
Estimated Completion = Start date + Estimated duration
The Start date should reflect when the project can actually begin, not simply when the proposal is approved. Waiting for materials, access, deposits, or key decisions may delay the real start of the work.
Update the Estimated completion whenever the Estimated work, Available project hours per week, or Start date changes. The result helps you understand the effect of those changes, but it cannot predict delays caused by future events.
Deadline difference
Deadline difference shows whether the project finishes before, on, or after the planned deadline. It compares the deadline with the estimated completion date.
Deadline difference = Deadline − Estimated completion
A positive result means the project finishes before the deadline and still has schedule margin. A negative result means the project finishes after the deadline and the current scope, capacity, or schedule is no longer feasible without changes.
The result is displayed as:
- X days before deadline when the result is positive.
- On deadline when the result is zero.
- X days after deadline when the result is negative.
Example:
In this example, the project is expected to finish 5 days after the deadline. To bring the project back on schedule, you would need to reduce the scope, increase available capacity, extend the deadline, or combine several of these adjustments.
6. Calculate available project capacity
A schedule is useful only if enough working hours can fit between the Start date and the Deadline. These metrics convert calendar time into available project capacity and the weekly workload required to meet the deadline.
Available project capacity
When you enter a Start date and a Deadline, Project Decision calculates how many hours can realistically fit between those dates based on the Available project hours per week.
Available project capacity = Calendar weeks available × Available project hours per week
Example:
If the project requires 120 hours, only 100 hours fit between the Start date and the Deadline. The project therefore needs 20 more hours than the available time can support.
Available project capacity answers a different question than Estimated duration. Instead of asking how long the work will take, it asks how many hours can fit between the Start date and the Deadline based on the Available project hours per week.
Required hours per week
Required hours per week shows the average weekly workload needed to complete the Estimated work within the Calendar weeks available. It helps compare the project demand with the Available hours per week that can be dedicated to the project.
Required hours per week = Estimated work ÷ Calendar weeks available
Example:
Compare this value with the Available hours per week. If the Required hours per week exceeds the available weekly capacity, the project may need a longer deadline, reduced scope, or additional capacity.
7. Evaluate deadline feasibility
Capacity utilization compares the Estimated work with the Available project capacity and shows whether the Deadline is mathematically feasible, realistic in practice, and sustainable.
Capacity utilization
Capacity utilization shows what percentage of the Available project capacity is used by the Estimated work.
Capacity utilization = Estimated work ÷ Available project capacity × 100
The following interpretations explain what each capacity utilization result means:
The work fits mathematically.
Practical interpretation: Review whether the remaining time is sufficient for uncertainty.
The estimate consumes all calculated capacity.
Practical interpretation: The plan has no room for delays or unexpected work.
The work exceeds available capacity.
Practical interpretation: Change the scope, deadline, Available Hours per Week, or project resources.
Capacity utilization applies only to the current project. It does not measure overall workload, business utilization, or how much of your total working time is billable.
8. Recognize calendar limitations
Estimated duration provides a practical planning estimate, but it cannot reflect every detail of a real calendar. Weekends, holidays, vacations, business closures, partial weeks, and changing weekly availability may affect the actual completion date.
Public holidays, vacations, travel, and business closures reduce the time available for project work.
A project that starts or ends in the middle of the week may have less available time than a full week.
Some weeks may have more time available for the project than others, even if the overall average stays the same.
Waiting for feedback or approvals can delay the project even when no additional work is required.
Use Project Decision to estimate the schedule, then review your calendar whenever holidays, fixed dates, vacations, or changing weekly availability could affect the result.
9. Understand why the metrics are not duplicates
Several schedule results may seem similar at first, but each one answers a different question and helps you make a different project decision.
| Metric | Question answered | Useful decision |
|---|---|---|
| Estimated duration | How long does the work take at the normal allocation? | Estimate how long the project is likely to take. |
| Estimated completion | When is the work expected to finish? | Compare the expected completion date with the client's deadline. |
| Deadline difference | How many calendar days separate Estimated completion from the Deadline? | See how many days early or late the project is expected to finish. |
| Available project capacity | How many project hours can fit between the Start date and the Deadline? | See the maximum number of hours available for the project within the deadline period. |
| Capacity utilization | What share of deadline capacity does the work consume? | See how much of the available project capacity is already being used. |
| Required hours per week | How many hours per week does the deadline demand? | See whether the required weekly workload is realistic. |
For the exact definitions, formulas, date calculations, and special cases used, see the Project Decision Documentation.
To see how these schedule results work together with pricing, estimated work, and the other Project Decision results, review the Fixed-price project examples.
10. Add buffers and contingency
A project planned to use 100% of the Available project capacity has no room for normal delays. Leaving some extra time helps protect the completion date when unexpected situations arise.
Common reasons projects take longer
- Correcting mistakes or fixing problems found during review.
- Interruptions, illness, and reduced-capacity days.
- Working with unfamiliar tools or new types of work.
- Feedback cycles and delayed client responses.
- Waiting for suppliers, external services, or information from other people.
- Additional coordination when several participants are involved.
Make extra time part of the plan
You can leave extra time in different ways: by planning fewer hours than the Available project capacity, allowing extra calendar time before the Deadline, or combining both approaches. Make this decision explicit so the extra time is not treated as free work for new requests.
Available time and Supported Work measure different things. The project price may support more work even when there is no time left before the Deadline. The opposite can also happen: the schedule may have room, but adding more work could reduce the Effective Hourly Rate below your selected Minimum hourly rate.
11. Plan dependencies and waiting time
A project may have enough total hours before the Deadline and still finish late. Waiting for approvals, information, materials, or other people can delay the work even when enough hours are available.
Review the following dependencies and scheduling factors:
Some work cannot begin until another task or decision has been completed.
The client must provide information, access, feedback, or approvals when they are needed.
Suppliers, external services, specialists, printers, or other third parties can affect the project timeline.
Some tasks can happen at the same time, but only if the required people, information, and materials are available.
Agree on response times
If the project depends on feedback within two business days, make that expectation explicit. Also explain what happens if that feedback arrives later than expected. The schedule may move, the project may pause, or a new completion date may be needed.
These timeline assumptions, client responsibilities, approval windows, and rescheduling conditions should also be stated clearly in the proposal. The guide on writing a clear fixed-price proposal explains how to document the timeline, dependencies, responsibilities, and project change rules before work begins.
Identify the work that controls the deadline
Focus on the tasks and approvals that determine when the project can finish. Working faster on other tasks will not shorten the project if the main delay is waiting for an important approval or dependency.
12. Protect a sustainable workload
A project may appear to fit the schedule but still be difficult to deliver in practice. Long periods of overtime, frequent task switching, and a schedule with no room for unexpected events can reduce quality and make mistakes more likely.
The following levels help evaluate whether a project plan is not only feasible, but also realistic and sustainable:
The estimated work fits if everything goes according to plan and all available time is used.
The plan leaves room for meetings, interruptions, waiting for feedback, and weeks that are busier than expected.
The pace can be maintained without reducing quality, causing burnout, or affecting other commitments.
Consider decision time
Available hours are not the only limit on a project. Projects that require constant decisions, reviews, client discussions, or problem solving usually progress more slowly than repetitive work.
A very tight schedule may appear to have enough time, but constant pressure can slow decisions, create unnecessary rework, and reduce attention to detail.
If a project requires many important decisions, use a more conservative weekly allocation instead of assuming every available hour will be equally productive.
Preserve recovery time
A realistic schedule should leave some time to recover after especially busy periods. That recovery may be needed after deadlines, launches, travel, long meetings, or weeks with unusually heavy workloads.
When every week is planned at full capacity, even a small delay or urgent request can force overtime, postpone other work, or reduce quality. The schedule may still look possible on paper while becoming harder and harder to deliver reliably.
Do not assume that every free hour should immediately be assigned to more work. Leaving some free time makes it easier to deal with normal interruptions, recover after busy periods, and keep future projects on track.
When reviewing a demanding schedule, consider how long the higher workload must continue, what other work it affects, and how delays or reduced quality could affect your client and your business.
13. Respond to an unrealistic deadline
An unrealistic date does not create only two options: accept or decline. Identify which project variable can change and present the consequences clearly.
Remove, simplify, or defer deliverables so the required effort fits the available window.
Protect the deliverables required for the central outcome or fixed date, and defer lower-priority work that does not need to be completed in the same window.
Preserve the work and normal pace by increasing the calendar time available.
Assign more dependable hours only when the increase is genuinely sustainable.
Deliver the highest-priority outcome first and move remaining work into a later phase.
Increase parallel capacity where the work can be divided without creating excessive coordination.
Reduce review rounds, shorten response windows, consolidate decision authority, or move non-critical approvals so waiting time does not control the completion date.
Obtain materials earlier, remove blockers, or restructure sequencing so critical work can begin or continue sooner.
Present structured alternatives
Instead of only saying that the deadline is impossible, show the Estimated work, Required hours per week, Deadline difference, and one or more practical alternatives. For example: keep the full scope and extend the deadline, preserve the deadline by prioritizing the most important deliverables, move lower-priority work to a second phase, or adjust the review and approval process if it affects the schedule.
If the required date materially changes the workload, risk, delivery conditions, or commercial terms, reassess the resulting engagement using the guide on evaluating a fixed-price project before quoting.
14. Evaluate the commercial impact of urgency
Project Decision does not automatically increase the project price because of a tight deadline. However, an urgent project may justify a higher price if it creates extra costs or makes it harder to deliver other work.
Taking on more work than your schedule allows can affect more than the current project:
- Working overtime or outside your normal schedule.
- Delaying or declining other paid projects.
- Less flexibility to deal with normal interruptions or unexpected work.
- Extra coordination or faster external services.
- Higher risk of mistakes, rework, or missed commitments.
- Losing the chance to accept other projects because your schedule is already full.
Consider these effects when deciding the project price and terms. Your Minimum hourly rate is the lowest rate you want to accept, not the automatic price for an urgent project.
If you have not yet established your Minimum hourly rate, the guide on choosing your minimum hourly rate explains how to derive it from income requirements, business costs, billable capacity, time off, taxes, and profit goals.
15. Recalculate after scope changes
Additional meetings, revision rounds, deliverables, or other work increase Total Work. If the project price and your available hours stay the same, the change can affect both the project's economics and its schedule.
The approved version of the project before any new work is added.
The Current Project plus the additional work you want to evaluate.
Scenario Analysis shows how additional work changes Total Work, Effective Hourly Rate, Deadline, Capacity Utilization, and Supported Work. It does not change the original Current project automatically.
For the complete process of identifying, evaluating, approving, and documenting additional work, see the guide on managing scope creep and project changes.
16. Avoid common scheduling mistakes
Using all working hours as project availability.
Other clients and business responsibilities also require time.
Confusing work with duration.
Project hours do not determine the schedule unless you also decide how many hours per week you can dedicate to the project.
Accepting the deadline before estimating the work.
A deadline cannot be evaluated until you have estimated the work required.
Planning at 100% of capacity.
The schedule leaves no room for delays, interruptions, or other unexpected events.
Ignoring dependencies.
Available hours do not help if you are waiting for information, approvals, or materials before you can continue.
Assuming immediate feedback.
Waiting for client feedback or approvals can delay the project even when no additional work is required.
Treating overtime as normal capacity.
Working extra hours for a short period does not mean you can maintain that pace throughout the project.
Adding people without considering coordination.
Some work cannot be divided easily, and extra coordination may reduce the expected benefit.
Changing scope without recalculating the schedule.
Even small requests take time and can delay the project.
Relying on only one schedule result.
Estimated Completion, Capacity Utilization, and Required hours per week each show a different part of the planning picture.
17. Deadline feasibility checklist
- The complete project scope has been converted into Estimated work.
- Available project hours per week have been calculated after excluding other commitments.
- The weekly allocation reflects what you can realistically maintain.
- Meetings, coordination, reviews, and administration have been included in the estimate.
- The Start date reflects when the project can actually begin.
- Holidays, leave, shutdowns, and irregular weeks have been reviewed.
- Client and third-party dependencies have been identified.
- Required response and approval times are explicit.
- Estimated duration and Estimated completion have been reviewed.
- Calendar time available reflects the intended date window.
- Deadline Difference has been reviewed.
- Available project capacity has been compared with Estimated work.
- Capacity Utilization leaves enough room for unexpected delays.
- Required hours per week are realistic for your normal workload.
- Projects that require frequent decisions or reviews have been considered when planning your weekly availability.
- The schedule leaves some room to recover after especially busy periods.
- The Deadline does not depend on routine overtime.
- Scope changes trigger a new review of the schedule and completion date.
- Alternative options are ready if the requested deadline is not realistic.
18. Frequently asked questions
How do I know whether a project can fit before a deadline?
Estimate the complete project work, determine how many hours per week you can realistically dedicate to it, consider waiting time and non-working periods, and compare the available capacity with the work required. A deadline is realistic only when the required weekly pace fits your normal availability, not just the mathematical calculation.
Is project effort the same as project duration?
No. Project work is the total amount of work required, usually expressed in hours. Duration is the calendar time needed to complete that work based on your weekly availability. A 100-hour project can take three weeks, eight weeks, or longer depending on your available hours and any waiting time.
Should I use all of my weekly working hours as project capacity?
Usually not. Project capacity should exclude time reserved for other clients, administration, sales, support, internal work, recurring responsibilities, and some room for unexpected events. Using your theoretical maximum availability usually creates unrealistic schedules.
What does capacity utilization above 100% mean?
It means the estimated work is greater than the project capacity available before the deadline under the assumptions entered. The project needs more time, a longer deadline, a higher weekly allocation, fewer deliverables, more help, or another change to the plan.
Can a project be profitable but still have an unrealistic deadline?
Yes. Project economics and the schedule are evaluated separately. A project may preserve your Minimum hourly rate while still requiring more weekly hours than you can realistically provide or finishing after the deadline.
How much schedule buffer should I include?
There is no universal percentage. The right amount depends on how confident you are in the estimate, how much uncertainty the project contains, how long approvals usually take, how many other people the project depends on, and the cost of missing the deadline. The buffer should be planned deliberately rather than hidden inside the estimate.
What should I do when the required hours per week is too high?
Consider extending the deadline, reducing or dividing the work into phases, prioritizing the most important deliverables, increasing your weekly availability if it is sustainable, improving approval times, adding help where practical, or declining the proposed deadline. Avoid relying on overtime as the normal solution.
Ready to test your project schedule?
Enter your Estimated work, Available project hours per week, Start date, and Deadline in Project Decision to review Estimated Completion, Capacity Utilization, Required hours per week, and other schedule results.
Open Project Decision