Prompts / Management & Leadership

ChatGPT prompt for time management

This prompt turns a workload, calendar, and deadlines into a practical weekly plan. Use it when priorities are competing and the plan must be fair to the people doing the work.

PromptOpen ChatGPTOpen Claude
I need a time-management plan for [PERSON OR TEAM] covering [PLANNING PERIOD]. Build it from the work, deadlines, and constraints below; do not assume people can work overtime or invent available time.

Inputs
- Work and deadlines: [WORK AND DEADLINES]
- Capacity and calendars: [CAPACITY AND CALENDAR]
- Goals and priority rules: [GOALS AND PRIORITY RULES]
- Dependencies, risks, and non-negotiables: [DEPENDENCIES AND CONSTRAINTS]

First, identify the 3–5 outcomes that matter most in this period. Classify every item as must do, should do, could do, or defer, using the priority rules. Estimate effort only when my input provides enough basis; otherwise label the estimate as unknown and state what is needed. Account for meetings, focused-work blocks, handoffs, review time, and a reasonable buffer for interruptions.

Produce:
1. A short priority decision record explaining what is protected, deferred, delegated, or needs a scope decision.
2. A calendar-ready plan by person and day, with time blocks, owner, expected output, and the next dependency.
3. A workload table showing planned hours versus usable capacity. Flag any overload, single point of failure, or deadline that depends on an unconfirmed assumption.
4. A daily 10-minute check-in agenda and a Friday review that tests completed outcomes rather than activity.
5. Three specific tradeoffs to make if capacity drops by 20%.

Keep the plan operational: use named deliverables, not vague tasks such as “work on project.” Do not schedule private calendar details or infer medical, caregiving, or personal obligations from gaps.

Before answering, check that no person exceeds the usable capacity supplied and that every must-do deadline has an owner and next action. Ask up to 3 clarifying questions only if a required input is missing.

Fill in

PlaceholderWhat to enterExample
[PERSON OR TEAM]Name the person or team whose work the plan covers.Customer education team: Maya, Colin, and Priya
[PLANNING PERIOD]Enter the dates or time horizon for the plan.Monday 6 October through Friday 17 October
[WORK AND DEADLINES]List deliverables, due dates, estimated effort if known, and current status.Publish onboarding guide by Oct 10; revise 6 help articles by Oct 17; prepare webinar slides by Oct 15; Maya has drafted the guide.
[CAPACITY AND CALENDAR]State usable work hours, fixed meetings, planned leave, and protected focus time.Each person has 28 usable hours weekly after recurring meetings; Priya is out Oct 13; webinar rehearsal is Oct 14, 2–3 p.m.
[GOALS AND PRIORITY RULES]Describe the outcomes that matter and the rules for deciding what wins in a conflict.Protect the onboarding launch first, then reduce support tickets; customer-facing commitments beat internal polish.
[DEPENDENCIES AND CONSTRAINTS]List approvals, handoffs, tools, risks, and work that cannot move.Legal must approve the guide before publishing; product screenshots arrive Oct 8; no evening work.

How to use

  1. Paste the prompt and replace every bracketed input with your actual workload and available capacity.
  2. Keep capacity to usable hours after meetings, routine work, and planned leave; do not enter nominal 40-hour weeks.
  3. Check the workload table before sharing the plan and decide what to defer where it shows overload.
  4. Follow up with: “Re-plan this for a two-day delay in the legal approval while preserving the highest-priority outcome.”

Variations

Personal weekly plan

Use this for one person’s week rather than a shared team schedule.

Variation
Create a weekly plan for me for [DATES]. My commitments are [FIXED COMMITMENTS], my tasks are [TASKS WITH DEADLINES], and my top outcomes are [TOP OUTCOMES]. Allocate realistic focus blocks, administration time, and a 15% interruption buffer. Return a daily schedule, a ranked task list, and a defer list. Explain conflicts between deadlines and capacity. Do not assume evenings or weekends are available. Check that no day exceeds [DAILY AVAILABLE HOURS], and ask up to 3 questions only if a required input is absent.

Project recovery plan

Use this when a project is late and the team needs a contained catch-up plan.

Variation
Build a recovery plan for [PROJECT] after [CAUSE OF DELAY]. The remaining deliverables and dates are [REMAINING WORK], available people and hours are [CAPACITY], and dependencies are [DEPENDENCIES]. Return a critical-path table, a two-week schedule by owner, risks needing escalation, and the smallest scope cuts that protect [NON-NEGOTIABLE OUTCOME]. Separate confirmed facts from assumptions. Check that every critical-path task has one owner and that the proposed plan fits stated capacity. Ask up to 3 questions only if needed inputs are missing.

Meeting reset

Use this when meetings are crowding out execution time.

Variation
Audit this team’s recurring meetings: [MEETING LIST]. The team’s essential decisions and collaboration needs are [DECISIONS AND NEEDS], and our current delivery problems are [DELIVERY PROBLEMS]. Recommend keep, shorten, combine, convert to async, or cancel for each meeting. Produce a revised weekly meeting map, agendas for meetings kept, and async templates for work moved out of meetings. Preserve required stakeholder decisions and do not invent attendance data. Check that each retained meeting has a decision, owner, and expected output. Ask up to 3 questions only if a required input is missing.

Tips

  • Plan against usable capacity, not contracted hours; recurring meetings, support coverage, reviews, and interruptions consume real delivery time.
  • A task without a defined output and next dependency is not schedulable, so turn “finish deck” into a specific draft, review, or publish action.
  • Treat overload as a prioritization decision, not an individual productivity problem; explicitly defer, reduce scope, or add capacity.
  • Reserve buffers around approval-dependent work because a calendar block cannot force another team to respond.

FAQ

Can AI estimate how long tasks will take?

It can organize estimates you provide and identify uncertainty, but its estimates are not evidence. Use prior work, task owners, or time tracking for consequential commitments.

How much buffer should a weekly plan include?

A common starting point is 10–20% of usable time, adjusted upward for reactive roles, approvals, and unfamiliar work.

Should I include individual personal constraints?

Include only the availability people choose to share for planning. State unavailable periods without supplying personal reasons.

Related prompts

All Management & Leadership prompts →

Get a few prompts like this every week

Something Big is a free AI newsletter read by 50,000+ professionals. About three short emails a week with prompts and tools that work, plus what changed in AI and what to do about it.