Create a decision packet template for executive review

Decision support

Key takeaways

• Define the outcome and source record before decision support work begins.
• Separate assistant coordination from executive or specialist decision authority.
• Close with evidence, an accountable owner, and a scheduled effectiveness review.

Operating data

Playbook

For create a decision packet template for executive review, the purpose and scope rule must fit an executive receiving approvals and judgment calls across inbox, chat, meetings, documents, and operating systems. a consistent packet that lets the executive understand the decision, test the evidence, choose, defer, or return it without searching for context. Write that rule in the working record, then test it against this adjacent requirement: decision question, accountable requester, authority, deadline and consequence, source facts, assumptions, options, tradeoffs, specialist input, recommendation, and communication audience. The assistant names the responsible owner, authoritative location, next observable action, and evidence that closes the item. When facts conflict, preserve both sources and ask the accountable person to resolve them; an assumption must never become an executive commitment. A practical review also considers the assistant may assemble and challenge completeness, label uncertainty, and offer a non-binding recommendation within expertise; the named decision owner retains judgment. This keeps decision support tied to the actual operating problem: requests arrive as forwarded threads or unexplained links, forcing the executive to reconstruct the question and discover missing facts during review. Apply the rule to this case: A hiring request asks for immediate approval but omits the start date and budget owner. The assistant verifies that the deadline is tied to a candidate conversation, adds the missing commercial context, and separates approval to continue discussions from authority to issue an offer. Record what was accepted, what was declined, who decided, which source supported the choice, and when the result must be revisited. For implementation detail, use the executive decision log and Atlassian decision template; local policy and named owners still govern. If the test exposes ambiguity, narrow the assistant authority, add the missing source, and rerun the case before extending the workflow.

For create a decision packet template for executive review, the request qualification rule must fit an executive receiving approvals and judgment calls across inbox, chat, meetings, documents, and operating systems. decision question, accountable requester, authority, deadline and consequence, source facts, assumptions, options, tradeoffs, specialist input, recommendation, and communication audience. Write that rule in the working record, then test it against this adjacent requirement: decision ID, one-sentence question, owner, context, confirmed facts, assumptions, options, consequences, recommendation, authority, deadline, sources, and outcome. The assistant names the responsible owner, authoritative location, next observable action, and evidence that closes the item. When facts conflict, preserve both sources and ask the accountable person to resolve them; an assumption must never become an executive commitment. A practical review also considers build packets as requests enter, return missing evidence early, batch ordinary reviews, escalate approaching consequences, and publish confirmed outcomes to affected systems. This keeps decision support tied to the actual operating problem: requests arrive as forwarded threads or unexplained links, forcing the executive to reconstruct the question and discover missing facts during review. Apply the rule to this case: A hiring request asks for immediate approval but omits the start date and budget owner. The assistant verifies that the deadline is tied to a candidate conversation, adds the missing commercial context, and separates approval to continue discussions from authority to issue an offer. Record what was accepted, what was declined, who decided, which source supported the choice, and when the result must be revisited. For implementation detail, consult the named internal guide and external authority already recorded above; local policy and named owners still govern. If the test exposes ambiguity, narrow the assistant authority, add the missing source, and rerun the case before extending the workflow.

For create a decision packet template for executive review, the source-of-truth design rule must fit an executive receiving approvals and judgment calls across inbox, chat, meetings, documents, and operating systems. decision ID, one-sentence question, owner, context, confirmed facts, assumptions, options, consequences, recommendation, authority, deadline, sources, and outcome. Write that rule in the working record, then test it against this adjacent requirement: the assistant may assemble and challenge completeness, label uncertainty, and offer a non-binding recommendation within expertise; the named decision owner retains judgment. The assistant names the responsible owner, authoritative location, next observable action, and evidence that closes the item. When facts conflict, preserve both sources and ask the accountable person to resolve them; an assumption must never become an executive commitment. A practical review also considers the choice is falsely limited to two options, the recommendation lacks an accountable author, numbers have no period or source, or the stated deadline has no real consequence. This keeps decision support tied to the actual operating problem: requests arrive as forwarded threads or unexplained links, forcing the executive to reconstruct the question and discover missing facts during review. Apply the rule to this case: A hiring request asks for immediate approval but omits the start date and budget owner. The assistant verifies that the deadline is tied to a candidate conversation, adds the missing commercial context, and separates approval to continue discussions from authority to issue an offer. Record what was accepted, what was declined, who decided, which source supported the choice, and when the result must be revisited. For implementation detail, consult the named internal guide and external authority already recorded above; local policy and named owners still govern. If the test exposes ambiguity, narrow the assistant authority, add the missing source, and rerun the case before extending the workflow.

For create a decision packet template for executive review, the decision authority rule must fit an executive receiving approvals and judgment calls across inbox, chat, meetings, documents, and operating systems. the assistant may assemble and challenge completeness, label uncertainty, and offer a non-binding recommendation within expertise; the named decision owner retains judgment. Write that rule in the working record, then test it against this adjacent requirement: build packets as requests enter, return missing evidence early, batch ordinary reviews, escalate approaching consequences, and publish confirmed outcomes to affected systems. The assistant names the responsible owner, authoritative location, next observable action, and evidence that closes the item. When facts conflict, preserve both sources and ask the accountable person to resolve them; an assumption must never become an executive commitment. A practical review also considers record the decision as a complete statement, identify affected people, assign resulting actions, send authorized communication, and schedule any review trigger. This keeps decision support tied to the actual operating problem: requests arrive as forwarded threads or unexplained links, forcing the executive to reconstruct the question and discover missing facts during review. Apply the rule to this case: A hiring request asks for immediate approval but omits the start date and budget owner. The assistant verifies that the deadline is tied to a candidate conversation, adds the missing commercial context, and separates approval to continue discussions from authority to issue an offer. Record what was accepted, what was declined, who decided, which source supported the choice, and when the result must be revisited. For implementation detail, consult the named internal guide and external authority already recorded above; local policy and named owners still govern. If the test exposes ambiguity, narrow the assistant authority, add the missing source, and rerun the case before extending the workflow.

For create a decision packet template for executive review, the operating rhythm rule must fit an executive receiving approvals and judgment calls across inbox, chat, meetings, documents, and operating systems. build packets as requests enter, return missing evidence early, batch ordinary reviews, escalate approaching consequences, and publish confirmed outcomes to affected systems. Write that rule in the working record, then test it against this adjacent requirement: the choice is falsely limited to two options, the recommendation lacks an accountable author, numbers have no period or source, or the stated deadline has no real consequence. The assistant names the responsible owner, authoritative location, next observable action, and evidence that closes the item. When facts conflict, preserve both sources and ask the accountable person to resolve them; an assumption must never become an executive commitment. A practical review also considers packets returned incomplete, executive search time, decisions reopened for missing facts, deadlines misstated, options added during review, and outcomes not translated into action. This keeps decision support tied to the actual operating problem: requests arrive as forwarded threads or unexplained links, forcing the executive to reconstruct the question and discover missing facts during review. Apply the rule to this case: A hiring request asks for immediate approval but omits the start date and budget owner. The assistant verifies that the deadline is tied to a candidate conversation, adds the missing commercial context, and separates approval to continue discussions from authority to issue an offer. Record what was accepted, what was declined, who decided, which source supported the choice, and when the result must be revisited. For implementation detail, request a tailored executive support plan after reviewing the named guide; local policy and named owners still govern. If the test exposes ambiguity, narrow the assistant authority, add the missing source, and rerun the case before extending the workflow.