Weekly Executive Reset Prompt

Public field comparison

Weekly Executive Reset Prompt

Weekly Executive Reset Prompt

Reset the week by clarifying priorities, decisions, meetings, risks, energy, and the few tasks that matter.

Turn commitments, strategic priorities, unresolved decisions, risks, and available capacity into an evidence-grounded executive plan for the week.

—

Use this prompt to reconcile last week, rank this week’s outcomes, review meetings, surface decisions and risks, delegate clearly, and protect realistic focus time.

Weekly Executive Reset
Requirements Clarification
Output Quality Review
Review Checklist Building
Implementation Planning

Monday executive planning and capacity reset
Calendar and meeting portfolio review
Weekly decision and delegation triage
Prior-week reconciliation and leadership handoff

Goal or task
Current context
Constraints
Files, data, or examples
Definition of done

Planning week
Executive commitments and calendar
Strategic priorities and deadlines
Decision and delegation inventory
Team and stakeholder context
Capacity and constraints
Prior week evidence

Replace every bracketed placeholder before running. Give the model enough context to inspect assumptions, ask only blocking questions, and produce a concrete deliverable. For code prompts, include relevant files, errors, logs, and test commands.

In ChatGPT, replace every bracketed variable with current information. Provide the relevant calendar or agenda export, strategic priorities, deadlines, status reports, decision log, delegation notes, stakeholder constraints, capacity limits, and prior-week completion evidence. Redact unnecessary sensitive data, then run the prompt and answer only genuinely blocking follow-up questions.

Use this when you need a production-ready planning result in Productivity, not a generic brainstorm. The expected output should include findings, implementation steps, risks, and verification checks.

A business unit leader uses ChatGPT on Monday morning with a calendar export, quarterly objectives, unresolved approvals, team availability, and last week’s status report. The result identifies three outcomes, proposes low-value meeting changes, creates decision and delegation registers, exposes a capacity shortfall, and supplies a verification-based 24-hour handoff without claiming any calendar or stakeholder action occurred.

Expert

Expert

ChatGPT

ChatGPT

planning

planning

chatgpt
weekly-planning
priorities
productivity

chatgpt
weekly-planning
executive-productivity
decision-management
capacity-planning

Weekly Executive Reset Prompt | AMO.ng

Weekly Executive Reset Prompt | AMO.ng

Reset the week by clarifying priorities, decisions, meetings, risks, energy, and the few tasks that matter.

Build an evidence-grounded weekly executive plan covering priorities, capacity, meetings, decisions, delegation, risks, and verification.

Prompt-body line comparison

Removed Added Unchanged context

−Act as a senior Productivity specialist using ChatGPT. Your task is: [Goal or task].
+Create an executive reset for [Planning week] using only the information supplied below.
 
−Context:
−- Current situation: [Current context]
−- Constraints: [Constraints]
−- Available materials: [Files, data, examples, URLs, logs, notes]
−- Success criteria: [Definition of done]
+Planning inputs
+- Executive commitments and calendar: [Executive commitments and calendar]
+- Strategic priorities and deadlines: [Strategic priorities and deadlines]
+- Decision and delegation inventory: [Decision and delegation inventory]
+- Team and stakeholder context: [Team and stakeholder context]
+- Capacity and constraints: [Capacity and constraints]
+- Prior-week evidence: [Prior week evidence]
 
−Workflow:
−1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
−2. Make reasonable assumptions only when they are low risk, and label them clearly.
−3. Produce the main deliverable for "Weekly Executive Reset Prompt" with enough detail that a skilled operator can execute it immediately.
−4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
−5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
−6. End with the smallest safe next action.
+Input requirements
+The minimum reliable inputs are the planning week, dated commitments, current strategic priorities, and realistic capacity constraints. Decision inventory, stakeholder context, and prior-week evidence improve the result but may be incomplete.
 
−Output format:
−- Executive summary
−- Detailed plan or implementation
−- Risks and mitigations
−- Verification checklist
−- Next action
+If a missing date, timezone, immovable commitment, approval boundary, or capacity constraint could materially change the plan, ask only the blocking questions before proceeding. If the missing information is not blocking, produce a bounded draft and mark the affected items as unknown or unverified. Do not silently resolve contradictory dates, owners, priorities, or status reports.
 
−Do not give generic advice. Optimize for a production-quality planning outcome.
+Evidence and status rules
+- Treat pasted calendars, notes, metrics, status reports, and explicit user statements as supplied evidence, not independently verified facts.
+- Label material statements as Supplied fact, Assumption, Inference, Conflict, or Unknown.
+- Distinguish completed work supported by evidence from reported complete, planned, blocked, deferred, and unverified work.
+- Never claim that a meeting was changed, a message was sent, a decision was approved, a task was delegated, or a calendar event was created or cancelled unless the user supplies evidence that it occurred.
+- ChatGPT may analyze the supplied materials and propose a plan. It cannot inspect private calendars, email, project systems, or live organizational data unless their contents are provided in the conversation, and it must not imply that it performed external actions.
+
+Reset workflow
+1. Establish the planning frame: identify the date range, timezone, hard deadlines, fixed commitments, available working capacity, recovery needs, and any explicit instructions from authorized decision-makers.
+2. Reconcile the prior week: classify each carried item as completed with evidence, reported complete, still active, blocked, deliberately deferred, obsolete, or unknown. Preserve unresolved ownership and status conflicts.
+3. Build a demand-versus-capacity view. Estimate fixed meeting load, focus-time demand, operational overhead, and contingency buffer using the supplied information. Show the method and flag any estimate that lacks duration data. Do not create false precision.
+4. Rank no more than three weekly outcomes. For each, assess strategic impact, deadline pressure, executive leverage, consequence of delay, dependency readiness, effort, and confidence. Explain why excluded or deferred work falls below the cutoff.
+5. Review the calendar commitment by commitment. Recommend Keep, Shorten, Delegate, Decline, Move, Combine, or Needs review. For every proposed change, state the purpose, opportunity cost, affected stakeholders, preparation required, and approval or communication needed. Treat all changes as proposals only.
+6. Create a decision agenda. Separate decisions the executive can make now, decisions awaiting evidence, decisions owned elsewhere, and irreversible or high-consequence decisions requiring additional review. Include a deadline and cost of delay where supported.
+7. Design delegations without assuming acceptance. Specify the proposed owner, desired outcome, authority granted, definition of done, deadline, check-in point, dependencies, and escalation trigger. Flag overloaded, unavailable, or unauthorized owners.
+8. Map dependencies and stakeholders across outcomes, meetings, decisions, and delegations. Identify sequencing conflicts, single points of failure, and commitments that depend on unconfirmed responses.
+9. Build a risk radar covering deadline slippage, decision latency, stakeholder misalignment, capacity overload, sensitive personnel matters, financial or legal exposure, and insufficient recovery time only where relevant to the supplied material. Give an early-warning indicator, mitigation, owner, and escalation threshold for each material risk.
+10. Produce a realistic weekly operating rhythm: protected focus blocks, decision windows, meeting preparation, communication windows, buffer, and recovery periods. Do not schedule overlapping work or allocate all available capacity; expose unresolved overload instead.
+11. End with the smallest safe actions for the next 24 hours, identifying which actions the user may take directly and which require authorization, confirmation, or stakeholder communication.
+
+Authority, privacy, and safety boundaries
+- Do not send messages, alter calendars, assign work, approve spending, make personnel decisions, or represent that stakeholders agreed. Draft recommendations or communications for human review only.
+- Do not override stated organizational authority, confidentiality rules, employment obligations, legal review, financial controls, or security policy.
+- Minimize reproduction of sensitive personal, personnel, customer, legal, health, credential, and financial information. Recommend redaction when details are unnecessary for planning.
+- Mark high-impact, irreversible, personnel, legal, financial, security, or public commitments for explicit human approval.
+- Stop and request clarification when conflicting instructions, uncertain authority, absent critical dates, or sensitive information make prioritization unsafe. Otherwise continue with clearly bounded assumptions.
+
+Required output
+A. Planning basis
+- Planning period and timezone
+- Supplied sources
+- Assumptions, unknowns, and conflicts
+- Fixed constraints and available capacity
+- Confidence assessment with reasons
+
+B. Prior-week reconciliation table
+Columns: Item; Intended result; Current status; Evidence supplied; Carry, close, defer, or drop; Owner; Reason; Unresolved issue.
+
+C. Executive outcome stack
+Provide no more than three outcomes. Columns: Rank; Outcome stated as an observable result; Strategic link; Deadline; Impact; Cost of delay; Effort or capacity demand; Dependencies; Confidence; Acceptance evidence.
+Then list deliberately deferred items with the trade-off behind each deferral.
+
+D. Capacity and calendar audit
+First show estimated meeting load, focus demand, overhead, buffer, and remaining capacity. Then provide columns: Commitment; Purpose; Recommendation; Time recovered or required; Opportunity cost; Stakeholders affected; Preparation; Authorization or communication needed; Evidence status.
+
+E. Decision register
+Columns: Decision; Decision owner; Decision type and reversibility; Deadline; Evidence available; Evidence missing; Options and trade-offs; Cost of delay; Recommended disposition; Approval state.
+
+F. Delegation register
+Columns: Proposed outcome; Proposed owner; Authority boundary; Definition of done; Deadline; Check-in; Dependencies; Escalation trigger; Acceptance status. Use Proposed or Unconfirmed until acceptance evidence is supplied.
+
+G. Dependency and risk radar
+Columns: Outcome affected; Dependency or risk; Early-warning indicator; Likelihood and impact using qualitative ratings; Mitigation; Owner; Escalation threshold; Residual uncertainty.
+
+H. Weekly operating rhythm
+Present a day-by-day plan containing fixed commitments, protected focus blocks, decision windows, preparation, communication, buffer, and recovery. Identify overload, collisions, and items that remain unscheduled rather than forcing them into the calendar.
+
+I. Verification and acceptance checklist
+For each check, provide Expected condition; Actual observation from supplied evidence; Evidence reference; Status as Pass, Fail, Unverified, or Not applicable; Resolution owner.
+Include checks that:
+- every top outcome has an observable result, owner, deadline, capacity allocation, and acceptance evidence;
+- total proposed workload fits stated capacity with a visible buffer;
+- calendar recommendations support the ranked outcomes;
+- every decision and delegation has a valid owner and authority boundary;
+- dependencies, stakeholder communications, and escalation triggers are represented;
+- prior-week items reconcile without unsupported completion claims;
+- conflicting dates, statuses, or priorities remain visible until resolved;
+- no external action is described as executed without supplied evidence.
+
+J. Next-24-hours handoff
+List the smallest safe actions in order, with owner, timing, prerequisite, approval requirement, and intended evidence of completion. Finish with a short list of actions that remain proposed, blocked, or unverified.