Capacity is a number.
Planning is a conversation.

Start with the working day.

Each sample team member has a Monday–Friday working pattern. A full-time pattern contains eight hours on each of five days, giving forty hours before time off. Mira works six hours Monday through Thursday and does not work Friday: twenty-four hours. Leo works eight hours Monday through Thursday: thirty-two hours.

Time off reduces the selected person's capacity for that day to zero. It does not silently remove existing project allocations. If work remains on an unavailable day, the planner shows the conflict so you can decide where it belongs.

Give project work a place.

An allocation has a person, project, working date, whole-hour duration and optional note. It represents intended project work, not a meeting or actual time entry. You can add one from the main action or an empty day, and edit any existing block to change its person, project, date or hours.

The demo accepts one through twelve whole hours on weekdays. It allows an allocation to exceed a person's daily capacity, because seeing and resolving an overlap is part of planning. A preview explains the resulting load before you save.

A week can fit while a day does not.

Ava has forty hours of weekly capacity. On the sample Monday, Atlas has eight hours and Daylight has four. That day contains twelve planned hours against eight available hours, so it is four hours over capacity. Ava's remaining week may still contain free time, but the Monday conflict must remain visible.

The overbooked-people count includes any person with at least one day where allocated hours exceed capacity. It is not calculated only from the weekly percentage. A zero-capacity day with any allocated work is also overbooked.

Keep the remaining room honest.

For each person, available weekly hours are the greater of zero and capacity minus allocated hours. Team availability sums those person-level values. This prevents one person's excess hours from cancelling another person's free time in the headline number.

Availability is not a promise that every remaining hour is interchangeable. Roles, context and individual needs still matter. The role labels and project context help a planner make a considered decision; the demo does not rank people's performance.

Compare the plan with an estimate.

The project view adds every allocation attached to that project across all dates in local storage. The planner's weekly totals include only its selected Monday–Friday range. These are intentionally different scopes, and each is labelled.

Sample project estimates are fixed reference hours. Remaining estimate is the estimate minus planned hours and may become negative. Nothing in this demo represents actual work, invoices, payroll, productivity scoring or financial reporting.

Try a useful planning loop.

1. Open the sample week and find Ava's overloaded Monday.
2. Open the four-hour Daylight allocation.
3. Move it to a person or day with sufficient capacity.
4. Save and check the overbooking indicator and project totals.
5. Mark a day as time off and inspect what changes.

All changes are saved locally in this browser when storage is available. Export week creates a CSV of the selected week's project allocations. Reset sample plan restores the original allocations, time off and notes. No messages, invitations, HR updates or external records are created.