# Project Schedule Outline

Builds a task-level schedule outline with durations, dependencies, and assigned roles from your WBS and milestone plan. Use it to turn your work breakdown into an ordered task list ready to load into a scheduling tool.

## Prompt

## Context
You are a project management assistant helping me build a schedule outline for [PROJECT NAME] at [ORGANIZATION NAME]. Project start date: [PROJECT START DATE]. Target completion date: [TARGET COMPLETION DATE]. WBS or task list: [WBS OR TASK LIST]. Key milestones with dates: [MILESTONE LIST]. Available roles or resources: [ROLES AND RESOURCES]. Working days per week: [WORKING DAYS PER WEEK]. Known non-working periods (holidays, blackout windows): [NON-WORKING PERIODS].

## Task
Build a schedule outline as a table with these columns:
- Task ID (sequential)
- Task name
- WBS reference (if provided)
- Duration (in working days)
- Predecessors (task IDs this task depends on)
- Assigned role
- Milestone flag (yes or no)
- Notes (constraints or assumptions for this task)

After the table:
1. Calculate the total schedule duration in working days and confirm whether it fits within the start and end dates.
2. Identify the critical path: the chain of tasks where any delay pushes the end date.
3. List the top three schedule risks visible from the task list and dependencies.

## Standards
- Durations are in working days, not calendar days. Account for [WORKING DAYS PER WEEK] and the non-working periods I listed.
- Do not invent durations or dates for tasks where I have not provided enough information. Write [ESTIMATE NEEDED] and flag it.
- Critical path is based on the dependencies I provide, not assumptions.
- Do not add tasks outside the WBS or task list I provided.
- Schedule risks must be grounded in the task list and constraints, not pulled from a generic risk library.
- Recompute the total duration from the task durations before stating whether the schedule fits. Show the math.
- If any named input is missing or the task list is incomplete, ask before building the schedule.

## Variables

- PROJECT NAME
- ORGANIZATION NAME
- PROJECT START DATE
- TARGET COMPLETION DATE
- WBS OR TASK LIST
- MILESTONE LIST
- ROLES AND RESOURCES
- WORKING DAYS PER WEEK
- NON-WORKING PERIODS

## Input checklist

- [ ] Approved WBS or task list with dependencies you have identified
- [ ] Project start and hard completion dates from the approved charter
- [ ] Key milestone dates, especially any hard external deadlines
- [ ] List of available roles or resources and any known availability constraints
- [ ] Non-working periods: company holidays, blackout windows, seasonal shutdowns
- [ ] Confirm all dates, resource counts, and durations come from your planning records, not the AI
- [ ] Keep individual employee names and salary details out of the prompt

## Verification checklist

- [ ] Recount total working days yourself against a calendar, accounting for non-working periods
- [ ] Verify the critical path by tracing predecessor chains manually for at least the longest sequence
- [ ] Confirm no tasks were added that fall outside your approved WBS or scope
- [ ] Check every [ESTIMATE NEEDED] flag and replace with a real estimate before loading into your scheduling tool
- [ ] Milestone dates in the schedule match the approved milestone plan
- [ ] Schedule risks are grounded in your actual constraints, not generic boilerplate
- [ ] Review the full schedule with the team before baselining it in your project tool

## Sample output

Sample output. Generated by AI from sample inputs:

Schedule Outline: Atlas Warehouse Consolidation
Northwind Industrial Supply | Start: June 2, 2026 | End target: September 30, 2026 | 5-day work week | Blackout: August 2-31 (fulfillment peak)

| ID | Task | WBS | Duration (days) | Predecessors | Role | Milestone | Notes |
|---|---|---|---|---|---|---|---|
| T1 | Charter approved | 1.6.1 | 0 | None | Sponsor | Yes | Project start milestone |
| T2 | Site A layout survey | 1.1.1 | 3 | T1 | Warehouse Director | No | Must access Site A during off-peak hours |
| T3 | Draft floor layout | 1.1.2 | 5 | T2 | Warehouse Director | No | |
| T4 | Layout review and approval | 1.1.3 | 3 | T3 | Sponsor | Yes | Target July 10 |
| T5 | Submit rack permits | 1.2.1 | 2 | T4 | Facilities Lead | No | External dependency; permit turnaround [ESTIMATE NEEDED] |
| T6 | Permits received | 1.2.1 | 0 | T5 | Facilities Lead | Yes | Hard target July 15 |
| T7 | Schedule rack installer | 1.2.2 | 3 | T6 | Facilities Lead | No | |
| T8 | Rack installation | 1.2.3 | 10 | T7 | Contractor | No | Must complete before August 2 blackout |
| T9 | Load inspection | 1.2.4 | 2 | T8 | Third-party inspector | Yes | Target August 1 |
| T10 | System reconfiguration | 1.3.2 | 8 | T4 | IT Manager | No | Vendor support days included |
| T11 | Inventory record audit | 1.3.1 | 5 | T1 | Warehouse Supervisors | No | Can run parallel to layout work |
| T12 | Physical inventory transfer | 1.3.3 | 15 | T9, T10, T11 | Warehouse Supervisors | No | Starts September 1 after blackout |
| T13 | Post-transfer count verification | 1.3.4 | 3 | T12 | Warehouse Supervisors | No | |
| T14 | Staff redeployment plan | 1.4.1-4 | 20 | T1 | HR Lead | No | Runs parallel; complete by September 20 |
| T15 | Go-live acceptance | 1.5 | 0 | T13, T14 | Sponsor | Yes | Target September 30 |

Total working days on critical path: T1-T4-T6-T8-T9-T12-T13-T15
Working days available June 2 to September 30, excluding August 2-31: approximately 83 days.
Critical path length: 0+3+5+3+2+0+3+10+2+15+3+0 = 46 days. Fits within available time with buffer, but only if permits arrive on schedule.

Schedule risks:
1. Permit turnaround (T5-T6) is external. If permits slip past July 15, rack installation cannot finish before the August 2 blackout, pushing go-live past September 30.
2. The August 2-31 blackout freezes the physical move window. Any task starting the physical transfer (T12) must wait until September 1 regardless of readiness.
3. Vendor support days for system reconfiguration (T10) are not yet confirmed. A vendor scheduling conflict delays T10 and T12.

## Customization notes

Load the output table directly into your scheduling tool (Microsoft Project, Smartsheet, Asana, or similar) by matching column names. For larger projects, run the schedule one phase at a time to avoid truncation. Add a resource column for capacity planning if more than one person shares a role. For agile projects, swap duration in days for story points and replace the critical path section with a sprint-by-sprint rollup.

---

From The Logistics, Operations & Project Management Library at vetslearn.com/libraries/logistics-pm