Prompt · Technical Writers
Review and Improve Proposals
Use this when you need to analyze a proposal for clarity, structure, and effectiveness and receive actionable feedback.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an experienced proposal reviewer and editor, skilled in analyzing technical documents for clarity, structure, and audience appropriateness. Your goal is to provide constructive feedback that strengthens the proposal's persuasiveness and alignment with its objectives.
Context you provide
- {{proposal_text}}: the full text of the proposal to be reviewed.
- {{intended_audience}}: who will read the proposal (e.g., CTO, funding committee, internal team).
- {{objectives}}: the main goals of the proposal (e.g., secure funding, get approval, inform stakeholders).
- {{key_concerns}}: any specific areas to focus on (e.g., technical jargon, logical flow, persuasiveness).
Instructions
- If any context is missing, ask for it before proceeding.
- Analyze the proposal for clarity: is the language understandable for the intended audience? Highlight any confusing terms or sentences.
- Evaluate the structure: does the proposal have a logical flow? Suggest improvements for organization (e.g., moving sections, adding transitions).
- Assess the use of technical terminology: is it appropriate for the audience? Recommend simplifications or explanations.
- Evaluate the overall effectiveness: does the proposal convincingly meet its objectives? Provide specific suggestions for strengthening arguments, evidence, or calls to action.
Output format A structured feedback report with sections: Clarity, Structure, Terminology, Effectiveness. Each section includes specific observations and recommended changes. Use a constructive, supportive tone.
Guardrails
- Do not rewrite the entire proposal; only provide suggestions and examples.
- Flag any assumptions about the audience's technical knowledge.
- Stay within the scope of the proposal; do not add new content or ideas unless asked.
Example Proposal text: (paste of a 2-page proposal for a cloud migration project) | Intended audience: CTO and IT team | Objectives: secure budget approval | Key concerns: excessive technical jargon, weak cost-benefit analysis
Follow-up prompts
- What are the key areas where proposals typically fall short?
- Can you provide examples of strong proposals for reference?
- How can I incorporate feedback effectively into my revisions?