Recommend which tasks to delegate, defer, or delete

Author: AILesson7 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Triage an overloaded task list while preserving authority, commitments, learning, and hidden work. Provide: Task inventory, People and authority, Capacity and priorities. Expected result: A reversible task disposition plan with reasons, handoffs, dates, and confirmation gaps.

1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Triage the task inventory into Do, Delegate, Defer, Delete candidate, Clarify, or Waiting. Recommendations are not executed decisions.

Tasks, outcomes, deadlines, effort, status, dependencies, and affected people:
[tasks]

Owners, helpers, skills, privacy, authority, and handoff cost:
[authority]

Capacity, priority outcomes, non-negotiables, reviews, and trade-offs:
[priorities]

Preserve every task ID and distinguish externally committed deadlines from self-imposed dates. Check whether the task is necessary for an outcome, legally/ethically required, a dependency, already substantially complete, a useful learning responsibility, or duplicated elsewhere. Account for coordination, briefing, review, access, and follow-up cost when considering delegation. Never assign a person who has not accepted work or expose restricted information.

For each task recommend one disposition with confidence, rationale, consequence, prerequisite approval, next action, owner or Unassigned, and review/date. “Delete” must remain a candidate until the authorized owner confirms and affected people are informed; state what record to retain. For delegation provide a complete handoff brief and acceptance signal. For deferral give a trigger/date, not an indefinite someday. Reconcile all IDs, total known effort by disposition, and show an alternative if the user's priority assumption changes.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Task inventory
T1 client proposal due Wed, 3h, promised by me, draft 70%. T2 weekly dashboard due Fri, 2h, manager uses it; analyst Kai has automated-data skill. T3 redesign team folder icons, self-set Friday, 1.5h, no dependent. T4 privacy training due 30 Sep, 45m, mandatory and personal completion. T5 answer vendor security questionnaire, due today, effort unknown, requires security facts. T6 copy old meeting notes into new template, 2h, same searchable notes already in Drive.
People and authority
I own T1/T3/T6 and may stop internal cosmetic work. Manager owns dashboard requirement and can approve delegation. Kai has not been asked; briefing/review estimated 30m each. Security lead owns questionnaire answers; I may coordinate but cannot approve. Training cannot be delegated. No restricted vendor data may go into general chat.
Capacity and priorities
I have 5 hours before Friday. Protect client promise, compliance, and decisions based on dashboard. Reduce low-value work. Manager review tomorrow 15:00. Next archive review 30 Sep.

Example output

Coverage T1-T6. Do T1 (high confidence): externally promised, 70% complete, 3h estimate; next action is a 60-minute completion block, owner you. Do T4 by 30 Sep (high): mandatory, personal, 45m; calendar it after this week's pressure, not delete/delegate. Clarify/Waiting T5 (high): you lack answer authority and effort is unknown. Today send the security lead a restricted-channel request for ownership, deadline, questionnaire location, and required response signal; escalate the deadline rather than invent answers.

Delegate candidate T2 (medium, pending manager and Kai): 2h production may move, but your known cost remains 1h briefing/review. Handoff: outcome=Friday dashboard using existing definition; sources/access=approved workbook only; acceptance=figures reconcile and manager-required tabs render; deadline=Thursday draft; Kai replies “Accepted” before ownership changes; you review 30m. If either declines by tomorrow 15:00, T2 returns to Do and consumes 2h, requiring another trade-off.

Delete candidate T3 (high): no dependent and cosmetic; you have authority, but record “not pursued—capacity/low outcome value” and notify the team only if expectation was shared. Delete candidate T6 (medium): duplicate migration appears unnecessary because Drive is searchable; confirm no retention/template requirement at the 30 Sep archive review before closing, retain source links. Known personal load if T2 is accepted: T1 3h + T4 .75h + T2 overhead 1h = 4.75h, leaving .25h plus unknown T5 coordination. If dashboard is the overriding priority and delegation fails, defer the remaining T1 polish only with client agreement; do not silently miss the promise.

Why this works

  1. 1

    Disposition rules reduce overload without pretending that every task is optional or transferable

  2. 2

    Including handoff and review cost prevents delegation from hiding work rather than reducing it

Check the result

  • Is every task ID accounted for with one recommendation and a concrete next step

  • Are delegation acceptance and deletion authority explicit rather than assumed

  • Does the effort summary include briefing, review, and follow-up costs where known

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Recommend which tasks to delegate, defer, or delete”?

For “Recommend which tasks to delegate, defer, or delete,” prepare Task inventory, People and authority, and Capacity and priorities. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Recommend which tasks to delegate, defer, or delete” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A reversible task disposition plan with reasons, handoffs, dates, and confirmation gaps—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Recommend which tasks to delegate, defer, or delete”?

The published test record for “Recommend which tasks to delegate, defer, or delete” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore

Where this recipe fits

Keep the work moving