← Back to prompts
RevOpsRevOps Analystbeginner 15 min saved

Action Item Deadline Organizer

Turn daily activity notes into prioritized, deadline-aware next steps with clear delegation options.

Customise & copy

Add the context you have. The prompt updates as you work.

Paste notes, emails, meeting follow-ups, or other work activity from today.

Use a clear date format such as 2025-03-08.

List confirmed deadlines and the project or task each deadline belongs to.

List names and, when useful, their roles or areas of ownership.

Live prompt

4 fields
Extract actionable next steps from the activity notes and return only the following four sections, in this exact order:

Due Today/Tomorrow
- [task] — [due date or "overdue"]

Due This Week
- [task] — [due date, if known]

Can Wait
- [task] — [due date or "no stated deadline"]

Delegate-able
- [task] — Delegate to: [team member]

Rules:
- Use {{todays_date}} to interpret relative dates and classify deadlines accurately.
- Use {{project_deadlines}} as the deadline authority when it conflicts with the notes.
- Use {{team_members}} to identify realistic delegation options; delegate only tasks clearly suited to a named person.
- Extract explicit tasks and implicit tasks only when the notes clearly indicate a required next action. Do not invent tasks, owners, dates, priorities, or dependencies.
- Put overdue tasks in Due Today/Tomorrow and label them "overdue".
- Include each task in only one section. Put delegate-able tasks in Delegate-able rather than another section.
- Keep bullets concise and actionable. Do not add introductions, conclusions, explanations, or conversational filler.
- If a section has no items, write "- None" under that heading.

Activity notes:
{{raw_activity_notes}}

Today's date:
{{todays_date}}

Known project deadlines:
{{project_deadlines}}

Team members available for delegation:
{{team_members}}

Proof before you use it

A real example

Tested on gpt-5.6-luna on 2026-09-10

{
  "todays_date": "2025-03-08",
  "team_members": "Maya Chen — Sales Operations\nJon Bell — Web Analytics\nPriya Shah — Legal",
  "project_deadlines": "Q3 launch pricing revision — 2025-03-10\nAnalytics setup — 2025-03-14\nPrivacy copy approval — 2025-03-12\nLaunch email draft — 2025-03-13",
  "raw_activity_notes": "Reviewed the Q3 launch brief. Need to send revised pricing to Maya. Client asked whether analytics setup can be completed by Friday. Waiting on legal feedback for the privacy copy. Draft the launch email after pricing is approved."
}

A small ritual that works

How to use it

  1. 01Paste notes, emails, or follow-ups into Raw activity notes.
  2. 02Enter today's date in a clear format.
  3. 03Add confirmed project deadlines and available team members.
  4. 04Review the four categorized sections and assign or complete the next steps.

Why it works

The prompt turns unstructured activity notes into a compact action list by defining four deadline- and ownership-based sections. It establishes clear rules for interpreting relative dates, prioritizes known project deadlines when notes conflict, separates delegation from personal work, and limits extraction to explicit tasks or clearly implied next actions. The required headings, concise bullet format, and empty-section fallback create a predictable structure for reviewing priorities quickly.

Where it fails

The structure depends on the notes and supporting fields containing enough information to identify tasks, deadlines, ownership, and delegation suitability. Ambiguous wording, incomplete date context, unclear references to people, or deadlines that are not recorded in the known-deadlines field can make classification uncertain. The prompt also cannot reliably determine whether a task is appropriate for delegation when roles or responsibilities are not described.

Customisation tips

Adapt the section names if your workflow uses different urgency bands, such as Today, This Week, Waiting For, and Someday. Add a dedicated field for task owners or dependencies if those distinctions matter. Expand the team-members field with roles, project ownership, or availability to support more precise delegation. If your organization uses a specific date format, priority system, or definition of overdue, state it directly in the rules. You can also add a section for blocked items when waiting conditions are important to planning.

Watch-outs

  • Relative dates are interpreted against the supplied today's date, so that field should use a clear and consistent format.
  • Known project deadlines take precedence over conflicting dates in the activity notes, which may change how a task is categorized.
  • The delegation rule is intentionally conservative: a named team member and a clear fit are needed before assigning a task.
  • Implicit tasks are limited to next actions clearly indicated by the notes; broader project planning is outside the prompt's scope.

Works in

Daily work reviewsMeeting follow-upsProject operationsTeam task planning

Was this useful?

Submit your variation

If your version helps, it may be published with your name and a link back to you.

Want to make AI useful across your team? Explore Atul's training.