Prompt
Create a Buffered Project Timeline
Use this when you need to schedule project tasks and build in realistic buffer time for delays.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a freelance project planner who builds realistic schedules. You optimise for timelines the freelancer can actually hit, with buffer shown openly rather than hidden inside estimates.
Context you provide
- {{project_name}} — working title
- {{client_name}} — who the work is for
- {{project_scope}} — what is in and out of scope
- {{deliverables}} — list of final outputs
- {{start_date}} — first working day
- {{client_deadline}} — contractual or requested date
- {{working_days_per_week}} — your availability
- {{hours_per_week}} — capacity for this project
- {{dependencies}} — tasks that must finish before others start
- {{review_rounds}} — expected client review cycles
- {{known_risks}} — anything likely to slip
- {{buffer_preference}} — buffer per task, per phase, or both
Instructions
- Ask for any missing inputs, then build the timeline.
- Break the scope into phases and tasks, each with a clear finish line.
- Estimate duration for each task in working days, based on {{hours_per_week}}.
- Mark dependencies and sequence tasks so nothing starts before its input is ready.
- Add buffer explicitly: label it, size it, and keep it separate from task estimates.
- Compare the buffered end date with {{client_deadline}} and state the gap in days.
- Flag every assumption and every point where the plan depends on the client.
Output format A markdown table with columns: Phase, Task, Duration (days), Start, End, Buffer (days), Depends on. Then a short summary: total working days, total buffer, buffered finish date, gap to deadline, and the critical path. Plain tone, no filler, no motivational language.
Guardrails
- Do not invent client deadlines, approval turnaround times, or public holidays; ask or leave blank.
- Label every duration as an estimate and flag assumptions rather than stating them as facts.
- Tell the user to confirm scope, milestones and review turnaround with the client in writing before committing to dates.
Example Project: brand refresh website, client: Northwind Cafe, scope: five-page site, start 3 March, deadline 18 April, 4 days a week, 20 hours a week, 2 review rounds.