Business Proposal

A formal document that presents a problem and proposes a specific solution, with the goal of persuading decision-makers to act. Unlike a business report (which analyzes and informs), a proposal argues for a particular course of action.

Core Purpose

Proposals are persuasive by nature. The writer must:

1. Establish that a problem is real and worth solving
2. Propose a credible, actionable solution
3. Justify the solution with benefits and evidence
4. Anticipate objections and address ethical implications

The reader should finish convinced that this specific solution is the right one for this situation.

Required Structure (ADMN 233 Format)

Section	Purpose	Length
Title Page	Identifies document; descriptive unique title + name + job title	—
Executive Summary	High-level action-oriented synopsis of the problem	3–5 sentences
Introduction	Background on the problem; establishes why it matters	2–3 paragraphs of 3–4 sentences
Proposed Solution	States the solution clearly, then explains it; discusses implementation and benefits; use subheadings	Bulk of the document
Ethics	Anticipates human or environmental impacts during and after implementation	1 paragraph, 2–3 sentences
Conclusion	Restates direct and indirect benefits on a positive note	1 paragraph, 2–4 sentences
References	APA citations — only if external sources used	Optional
Personal Reflection	Professional experience with proposals + course learning applied	4–6 sentences

Total word count: 800–1100 words (excludes title page and references; includes personal reflection)

Executive Summary vs. Introduction

This is a common confusion point:

	Executive Summary	Introduction
Purpose	Standalone digest — what the problem is and what is proposed	Background context — why the problem exists
Stance	Action-oriented; already recommends	Neutral framing of the situation
Written	Last, placed first	Flows naturally at the start
Reader	Executive who may not read further	Any reader entering the document

See also: ExecutiveSummary

Proposal vs. Report

	Business Report	Business Proposal
Core mode	Analytical / informational	Persuasive
Output	Findings and conclusions	Recommended action
Structure driver	Findings → Conclusion	Problem → Solution → Benefits
Stance	Objective	Advocate for a position

See also: BusinessReports

Persuasion Techniques in Proposals

A strong proposal uses all three rhetorical appeals:

• Ethos — credibility of the writer; cite expertise or research where relevant
• Logos — logical case for the solution; benefits clearly tied to the problem
• Pathos — acknowledge the human dimension; show you understand what’s at stake for the audience

Consider both sides but resolve toward your recommended solution. Mentioning counterarguments (then refuting them) strengthens rather than weakens a proposal.

See also: RhetoricalAppeals, PersuasiveMessages

Ethics Section

Every ADMN 233 proposal must include an ethics paragraph. Think through:

• Internal impacts — effect on employees or teams during implementation
• External impacts — effect on clients, partners, or the public
• Long-term impacts — downstream effects once the solution is in place

This section signals that the writer has considered the full scope of consequences, not just the desired outcome.

Formatting Requirements

• Letter page size, 1.5 line spacing, 2.5 cm (1 inch) margins
• Standard font (Arial, Times, or similar), size 10–12
• Left text alignment
• Professional template from Word or Google Docs (or custom)
• Headings, subheadings, whitespace, bolding, colour, page numbers as appropriate

See also: DocumentDesign

Cross-Course Connections

RhetoricalAppeals — Aristotle’s ethos/pathos/logos are the structural backbone of persuasive proposals
PersuasiveMessages — the 5-component hook → intro → explanation → evidence → CTA maps onto the proposal’s Proposed Solution section
ExecutiveSummary — the exec summary is a standalone genre within the proposal
BusinessReports — proposals share structural DNA with reports but are explicitly advocacy documents

Key Points for Exam/Study

• Proposals are persuasive first; analytical second — tone and framing matter as much as content
• Executive Summary ≠ Introduction — they serve different readers with different needs
• The Ethics section is mandatory and must go beyond obvious statements; show you’ve thought about it
• All words must be your own; quoting the simulation platform counts as a citation (APA required)
• Graded primarily on writing skills — content originality is secondary to clarity, organization, and professional style

Diagram

flowchart LR
    A[Problem Identified] --> B[Executive Summary\nhigh-level action-oriented]
    B --> C[Introduction\nbackground + context]
    C --> D[Proposed Solution\nbulk of document\nstatement + implementation + benefits]
    D --> E[Ethics\nhuman & environmental impacts]
    E --> F[Conclusion\nrestate benefits, positive note]
    F --> G[Personal Reflection\nafter the formal report]

    style D fill:#d4edda,stroke:#28a745
    style B fill:#cce5ff,stroke:#004085