ChatGPT prompt for a project proposal in Google Docs

Act as an experienced project sponsor and operations lead. Draft a Google Docs-ready project proposal for [PROJECT]. It is intended for [DECISION AUDIENCE] and should support this decision: [DECISION NEEDED]. Use only the verified context, evidence, costs, constraints, and prior commitments in [PROJECT NOTES]. The proposed delivery window is [TIMELINE AND RESOURCES].

Create a document of 900–1,300 words with a title, one-paragraph executive summary, and these sections:
1. Opportunity or problem, including who is affected and the consequence of not acting.
2. Recommendation: the proposed approach and why it is preferable to named alternatives, using only supplied evidence.
3. Objectives and measurable success criteria, with baselines or measurement gaps called out.
4. Scope: deliverables, exclusions, assumptions, and change-control boundary.

5. Work plan: phases, milestones, dependencies, decision gates, and deliverables.
6. Roles and responsibilities in a compact RACI-style table with one accountable owner per major deliverable.
7. Timeline table with dates or relative durations; identify assumptions instead of presenting uncertain dates as commitments.
8. Budget, staffing, and tools, separated into confirmed costs and estimates.
9. Risks, mitigations, triggers, and risk owners.
10. The exact approval requested and immediate next steps after approval.

Format it for easy pasting into Google Docs: use clear H1/H2 labels, short paragraphs, and tables that can be recreated in Docs. Include a one-page executive-summary version after the full proposal. Do not invent approvals, vendor quotes, legal conclusions, capacity, or deadlines.

Before answering, check that every deliverable has an owner and that every success criterion can be measured or is flagged as unmeasurable. Ask up to three clarifying questions only if a required input is missing.

Draft a client-facing Google Docs proposal for [ENGAGEMENT] for [CLIENT]. The requested approval is [APPROVAL AND COMMERCIAL TERMS]. Use [SCOPE, DISCOVERY NOTES, PRICING, AND ASSUMPTIONS]. Create an executive summary, client goals, approach, deliverables, timeline, client responsibilities, project governance, fees and payment assumptions, exclusions, change-request process, risks, and acceptance criteria. Keep claims limited to supplied evidence and avoid legal wording beyond the agreed commercial terms. Clearly label items requiring a statement of work or legal review. Ask up to three questions only if essential inputs are missing.

Create a Google Docs business case for [INITIATIVE] for [LEADERSHIP AUDIENCE]. The decision is [DECISION]. Use [EVIDENCE, OPTIONS, COSTS, AND CONSTRAINTS]. Compare a recommended option, status quo, and [ALTERNATIVE OPTION] in a decision table with benefits, costs, risks, dependencies, reversibility, and unknowns. Then provide recommendation, success measures, phased implementation plan, accountable owners, and approval request. Separate measured evidence from estimates and assumptions. Do not calculate ROI unless the required inputs are provided. Ask up to three clarifying questions only when necessary.

Turn [APPROVED PROPOSAL OR NOTES] into a project charter for [PROJECT TEAM]. Produce purpose, success metrics, scope and exclusions, milestones, workstreams, RACI table, communications cadence, decision log format, change-control rule, risk register, and first two weeks of actions. Use [KNOWN CONSTRAINTS AND DEPENDENCIES] to make handoffs explicit. Do not treat tentative dates or capacity as commitments. Flag missing accountable owners and unresolved dependencies. Ask up to three questions only if required inputs are absent.