WRIT6000 Chap.8 Proposal Design and Feasibility
Proposal Design and Feasibility
Proposal form depends on whether the request is solicited or writer-initiated and whether the audience sits inside or outside the organisation. A solicited proposal must answer published criteria directly, while a writer-initiated proposal must first establish why the issue belongs on the reader's agenda.
Internal readers may already know systems and terminology, whereas external readers often need more context, credibility and explanation of organisational capability. This chapter treats what, how, when and cost as persuasive evidence rather than administration. Method shows that the proposed action can produce the promised result. A timeline reveals sequence and dependency.
A budget exposes the labour, access, equipment, maintenance, evaluation and contingency the plan actually requires. Benefits become credible when they connect to activities and measures rather than broad improvement claims. The proposal should form a traceable line from verified problem through authorised audience, bounded method, resources, timing, benefit and evaluation.
A break anywhere in that chain weakens the approval case. This framework is especially important when revising an AI-produced proposal. Fluent generic prose may invent local details, address someone without authority, hide implementation work or promise effects that the method cannot measure.
Tracked human revision should reveal consequential judgment: corrected facts, changed scope, verified evidence, reordered reasoning and feasible evaluation. The completed document is persuasive because its parts demonstrate that the writer understands both the decision and the work required after approval.
What this chapter covers
- 01
Solicited and unsolicited proposals
- 02
Internal and external proposal audiences
- 03
Requests for proposals and response criteria
- 04
Method, resources and timeline dependencies
- 05
Budgets, assumptions and transparent ranges
- 06
Benefits, evaluation and final approval request
Worked example · free
Design a quiet-shopping trial
- 1Ground the need in verified customer experience.
- 1Propose a bounded trial with affected-reader consultation.
- 1Divide responsibilities between the store and association.
- 1Name resources, timing and operational constraints.
- 1Define evidence for the continuation decision.
Key terms
- Solicited proposal
- A proposal written in response to a stated request and its criteria.
- Unsolicited proposal
- A writer-initiated proposal that must establish why the issue deserves attention.
- Internal proposal
- A proposal addressed to a decision-maker within the writer's organisation.
- External proposal
- A proposal sent to a separate organisation, sponsor or client.
- Feasibility
- The practical fit among method, authority, resources, timing, risk and expected result.
Proposal Design and Feasibility FAQ
How does proposal type change the writing?
A solicited proposal must answer published criteria directly, while an unsolicited proposal first establishes why the issue belongs on the reader's agenda. Internal readers may know systems and terminology; external readers often need more context, credibility and explanation of organisational capability.
Why is the budget part of the argument?
Budget categories reveal what the method actually requires and whether the writer understands implementation. Equipment, staff time, access, maintenance, evaluation and contingency should connect to activities. Use verified quotes or transparent ranges instead of invented precision, and explain what could change the estimate.
What should tracked changes reveal in the assignment?
They should show consequential human judgment: corrected local facts, a properly authorised audience, narrower scope, verified evidence, reordered reasoning, feasible methods and measurable benefits. Grammar correction may help polish, but it does not demonstrate the contextual and rhetorical decisions that repair a generic draft.
Assessment move
Collect four short proposal situations and classify each on two axes: internal or external, and solicited or writer-initiated. For every situation, identify what the audience already knows, what authority it holds and which criteria or objections will shape approval. Draw a proposal chain with seven nodes: problem, audience, method, resources, timing, benefit and evaluation.
Write one sentence at each node and draw the reasoning link to the next. Mark any jump where a promised benefit does not follow from the method, a resource is missing or the measure cannot detect success. Build a simple work breakdown for one proposal. List activities, responsible roles, dependencies and outputs before estimating time or cost.
Add staff effort, access, equipment, maintenance, evaluation and contingency where relevant. Use verified quotes or transparent ranges rather than invented precision, and state what could change the estimate. Draft a benefit statement at three levels: immediate output, short-term outcome and larger aspiration. Keep the proposal claim at the level its method and evidence can support.
Next, review an AI-produced draft line by line. Label generic language, unsupported local detail, invented evidence, misplaced audience authority and hidden implementation work. Make tracked revisions that change the approval logic, then comment on why each alteration matters to the reader. Compare the original and revised versions and select the three changes that most affect credibility, feasibility or value.
Finish with an adversarial review. Imagine a reader who accepts the need but doubts capability, cost or measurement. Write the question that reader would ask and point to the exact proposal section that answers it. If no section does, revise the chain. This practice makes feasibility visible rather than leaving it as an optimistic tone.
