Professional Writing And Communication Prompts

INPUTS
[report or notes]; [audience]; [decision needed]; [length limit]

PROMPT
Write an executive summary for readers who may not read the full report. State the purpose, most consequential findings, practical implications, recommendation, and decision required. Preserve important numbers, qualifications, and disagreements from the source. Distinguish findings from your interpretation and do not introduce new evidence. Use a concise professional tone within the length limit. Include a small decision table if comparison is essential. End with the three source passages or sections supporting the main conclusions and any uncertainty leadership should understand.

INPUTS
[situation]; [recipient]; [confirmed facts]; [impact]; [recovery plan]; [tone]

PROMPT
Draft an email communicating this difficult update clearly and respectfully. Lead with what has changed, explain the impact, and acknowledge any responsibility supported by the facts. Present the recovery plan with owners, dates, and realistic commitments. Separate confirmed information from what is still being investigated. Include a concise subject line and a direct request or next update time. Avoid blame-shifting, vague reassurance, and unnecessary detail. Provide a shorter alternative and a checklist for facts, commitments, and the recipient's likely questions.

INPUTS
[decision]; [approver]; [options]; [recommendation]; [evidence]; [deadline]

PROMPT
Write a decision request that allows the approver to act without searching through background material. State the exact decision, why it is needed now, the recommended option, supporting evidence, main tradeoff, and deadline. Summarize alternatives in a compact table when useful. Include the consequence of waiting and the action that follows approval. Keep background proportionate to its relevance. Finish with a ready-to-use response line and a list of missing information that would materially change the recommendation.

INPUTS
[meeting notes]; [participants]; [project]; [known dates]

PROMPT
Convert the meeting notes into an accurate record and action plan. Separate decisions, proposals, unresolved questions, and assigned actions. Preserve names and dates exactly; use unassigned or to confirm when ownership or timing is unclear. Create a short meeting summary and an action table with task, owner, due date, dependency, and status. Do not turn discussion into agreement. Draft a follow-up message asking participants to confirm ambiguous items. End with a check for contradictions between the notes and the proposed action list.

INPUTS
[project]; [milestones]; [completed work]; [risks]; [next steps]; [audience]

PROMPT
Create a project status update that explains whether the objective and timeline remain achievable. Summarize progress against milestones, distinguish completed outputs from work in progress, and describe blockers with their impact and owner. Use a clear status assessment supported by the supplied facts. Include next steps, decisions needed, and changes since the last update. Avoid a long activity log. Provide a concise email version and a structured report version. Finish with a check that dates, responsibilities, and escalation requests are consistent.

INPUTS
[problem]; [proposed change]; [evidence]; [costs]; [stakeholders]; [constraints]

PROMPT
Write an internal proposal that makes the case for this change without overstating certainty. Explain the current problem, evidence of its impact, proposed approach, alternatives, implementation needs, and risks. Address the strongest reasonable objection and include a small pilot if the change can be tested. Use supplied cost information and mark missing estimates. Deliver a concise proposal with a decision request and measurable evaluation criteria. End with a stakeholder consultation plan and the conditions under which the proposal should be revised or withdrawn.

INPUTS
[text]; [reader]; [reading level]; [required terminology]; [length limit]

PROMPT
Rewrite this text so the intended reader can understand and use it easily. Preserve the original meaning, conditions, and important technical terms, explaining those terms briefly when needed. Replace long sentences, vague nouns, and unnecessary jargon with concrete language. Improve the order so essential information appears early. Return the revised text followed by a short list of ambiguities the original does not resolve. Do not fill those gaps with assumptions. Finish with a side-by-side explanation of three changes that most improve comprehension.

INPUTS
[occasion]; [audience]; [main message]; [speaker experience]; [duration]; [tone]

PROMPT
Write three possible openings for this speech or presentation. Build one around a concrete situation, one around a relevant question, and one around a verified observation. Connect each opening directly to the main message and explain why the audience should care. Use only supplied experience and evidence; do not invent personal stories or statistics. Develop the strongest version into an opening of the requested duration with a natural transition to the first topic. End with delivery notes for pacing and emphasis.

INPUTS
[incident]; [recipient]; [confirmed impact]; [responsibility]; [remedy]; [future prevention]

PROMPT
Draft a professional apology that acknowledges the actual incident and its impact. Accept the responsibility established by the facts without inventing details or making excuses. Explain the immediate remedy, realistic timing, and prevention steps. Keep the tone direct and proportionate. Provide an email version and a short spoken version. Distinguish commitments already authorized from proposed actions requiring agreement. End with a checklist for sincerity, accuracy, and follow-through, and identify any fact that should be confirmed before the message is sent.

INPUTS
[topic]; [source documents]; [performance figures]; [risks]; [decision request]

PROMPT
Prepare a leadership briefing with a clear narrative and concise supporting detail. Lead with the conclusion and the decision needed. Summarize the relevant performance, explain changes and their possible causes, and present material risks or uncertainties. Use consistent definitions and periods for figures; flag mismatched data rather than quietly reconciling it. Provide a two-page briefing structure, a decision table, and five likely questions with evidence-based answer outlines. End with information that belongs in an appendix rather than the main briefing.