Workload allocation plan for team leads

Create a weekly workload allocation plan for a shared-service team.

Use these inputs:

**Work intake register**
[paste work register with these fields: Work ID, requestor, task description, service or process, required skill, estimated hours, earliest start date, deadline, priority, dependency, status]

**Team availability register**
[paste staff register with these fields: employee name, role, skills, available hours by day, planned leave, fixed commitments, current assigned work]

**Allocation rules**
[paste rules, such as priority order, maximum concurrent tasks, work that only named people may perform, handover requirements, and work that must not be delayed]

Allocate each open work item to a named person and a working day. Do not allocate more hours than a person's available hours on any day. Preserve time for fixed commitments. Match required skills before balancing workload.

Return exactly four sections:
1. **Allocation plan** as a Markdown table with: Work ID | Task | Assignee | Day or date | Allocated hours | Deadline | Reason for assignment.
2. **Capacity conflicts and unallocated work** as a Markdown table with: Work ID or person | Conflict | Hours affected | Deadline impact | Recommended action.
3. **Decisions for team leads** as a numbered list. Each decision must state the owner, decision needed, latest decision date, and consequence of no decision.
4. **Assumptions and missing data** as a bullet list.

If an estimate, skill match, deadline, dependency or availability entry is unclear, do not invent it. Mark the item `Needs confirmation`, keep it out of committed capacity where necessary, and explain the effect on the plan. If no feasible allocation exists, say so plainly and show the shortfall in hours.

Audit the proposed workload allocation plan against available capacity, skills and deadlines.

**Proposed allocation plan**
[paste plan with: Work ID, task, assignee, day or date, allocated hours, deadline]

**Work intake register**
[paste register with: Work ID, required skill, estimated hours, priority, deadline, dependency, status]

**Team availability register**
[paste register with: employee name, skills, available hours by day, leave, fixed commitments]

Check each assignment for five conditions: enough available hours on that day, required skill held by the assignee, estimated hours fully covered, dependency completed before work starts, and deadline met.

Return:
1. A **conflict register** Markdown table: Conflict ID | Work ID or person | Check failed | Evidence from the input | Hours or date impact | Severity (`blocks delivery`, `at risk`, or `minor`) | Action needed.
2. A **person-by-day capacity table**: Person | Day or date | Available hours | Allocated hours | Remaining hours | Status.
3. A **team lead decision list**, ordered by deadline, with: decision required | options available | recommended option | decision owner | decision-by date.

Do not silently move work, change priorities or assume overtime. Where the inputs conflict, report both values, mark `Needs confirmation`, and identify which team lead must resolve it.

Compare allocation options for the workload plan below. Produce options that make the trade-offs visible to team leads.

**Open work and commitments**
[paste table with: Work ID, task, priority, required skill, estimated hours, deadline, dependency, requestor, consequences of delay]

**Available team capacity**
[paste table with: employee name, skills, available hours by day, leave, fixed commitments, work that cannot be reassigned]

**Current allocation plan, if one exists**
[paste current plan or write `No current plan`]

Create three feasible options where the data permits:
- Option A: protect the highest-priority deadlines.
- Option B: balance workload across qualified people.
- Option C: minimise disruption to current assignments.

For each option, return a Markdown table with: Work ID | Assignee or `unassigned` | Scheduled day or date | Hours | Deadline outcome | Change from current plan.

Then return a comparison table: Option | Deadlines met | Work delayed or unassigned | Capacity shortfall | Skill or dependency risks | Decisions required.

Finish with **Recommended decision**, a short numbered list that names the decision owner, the choice needed and the latest date to decide. If fewer than three options are feasible, state why. Do not assume overtime, contractors, priority changes or cross-training unless these are explicitly supplied. Put unknown estimates, skills or dates in an **Assumptions and missing data** list.

Update a live workload allocation plan after operational changes. Keep unaffected assignments in place unless moving them is necessary to meet a higher-priority deadline or resolve a capacity conflict.

**Current allocation plan**
[paste plan with: Work ID, task, assignee, scheduled day or date, allocated hours, deadline, priority, status]

**Changes since the plan was issued**
[paste changes with: change ID, type such as absence/new work/delayed dependency/revised estimate, affected person or Work ID, effective date, details]

**Work intake register**
[paste register with: Work ID, required skill, estimated hours, deadline, priority, dependency, status]

**Updated availability register**
[paste register with: employee name, skills, available hours by day, leave, fixed commitments]

Return exactly these sections:
1. **Updated allocation plan** as a Markdown table: Work ID | Assignee | Day or date | Hours | Deadline | Status (`unchanged`, `moved`, `new`, or `unassigned`).
2. **Changes from the prior plan** as a Markdown table: Work ID | Previous assignment | New assignment | Reason | Delivery impact.
3. **New risks and conflicts** as a Markdown table: Risk or conflict | Affected work | Deadline impact | Owner | Action needed.
4. **Team lead decisions needed today** as a numbered list, ordered by urgency.

Do not hide displaced work. If a change makes a deadline impossible, label it `Cannot meet deadline with current capacity`, show the hours shortfall, and offer only options supported by the input. For unclear data, use `Needs confirmation` and state what information is required.