Project Deadline Planner

Features

• One task per line, “name, estimated hours”, comma-separated
• Or set a single “total hours” instead of listing tasks (it wins if filled)
• Counts the working days left before the deadline, skipping weekends by default
• The deadline day is inclusive, and the rule is stated in the result
• Needed hours per day, compared against the hours you can spend
• A verdict line: green when it fits, red when it does not
• Optional daily start time, shown as a window such as “09:00–13:00”
• Zero working days left, or a past deadline, gives a verdict with no division by zero

How to use

1. Write one task and its estimated hours per line, e.g. “write docs, 6”
2. Fill in the deadline (or use “total hours” instead of task lines)
3. Set the hours per day, days per week and whether to skip weekends
4. Results appear at once: working days left, hours per day and the verdict

FAQ

Does the deadline day itself count as a working day?

Yes. “Deliver on Monday” usually means you can still work on Monday, so the deadline day is included. This is the cautious direction: counting one extra day makes the per-day figure smaller and the verdict more likely to say “feasible”. The other way round would tell you it fits when it does not — that is the mistake that actually costs you. The rule is written into the result.

Are public holidays deducted from the working days?

No. Only Monday to Friday (or whatever days-per-week you chose) are counted — holidays and make-up days shift from year to year, and a stale built-in table misleads more than no table at all. Deduct them yourself when you need an exact schedule.

How do “days per week” and “skip weekends” interact?

With skip-weekends on, the working days are simply Monday to Friday and the days-per-week figure is not used. With it off, the first N days of each week starting from Monday count (6 means Monday to Saturday, 7 means every day). The result states which rule was applied.