How to Write an Internal Proposal

by Samuel Hamilton; Updated September 26, 2017
Company problems, like leaky faucets, are annoying and costly.

Working for a company can be as frustrating as it is rewarding. Sometimes, problems exist and nobody seems to take notice. Though addressing the problem directly may be outside of your realm of responsibilities, as a conscientious employee, you could compose and submit an internal proposal for addressing the problem. Writing an internal proposal requires you to focus your attention on how your proposed solution will save money for the company.

Step 1

Identify a problem that is either costing your company money or impeding your company’s productivity.

Step 2

Clarify the problem and exactly why it is hurting the company. For example, your company may overspend on photocopying memos that can just as easily be distributed electronically. In this case, you would need to calculate the cost of printing, copying and distributing these memos, versus the cost of simply emailing the memos to a list of company employees.

Step 3

Limit the scope of the problem. If the problem is only specific to a particular section of the company such as maintenance, payroll or human resources, make this known. Limiting the scope of the problem will demonstrate to any potential proposal reviewers that you’ve done your homework in terms of preparing to tackle this problem.

Step 4

Specify the time and frequency of the problem. For example, the aforementioned photocopying gaffe only occurs when memos are distributed, but memos could be distributed two to three times a day, once a week or twice a month. Specifying the time and frequency allows you to accurately predict both the cost of the problem and the savings associated with fixing the problem.

Step 5

Provide history, if possible, as to why the problem exists. For example, photocopying memos for distribution could have been a bureaucratic holdover from a previous supervisor that was simply mimicked and carried on.

Step 6

Detail the amount of money the company will save by addressing the problem in the short and long term, ranging from monthly to quarterly to yearly.

Warnings

  • Do not implicate a subordinate, colleague or supervisor in providing the history of the problem.

References

  • "Technical Communication: A Reader-Centered Approach"; Paul V. Anderson; 2010

About the Author

Samuel Hamilton has been writing since 2002. His work has appeared in “The Penn,” “The Antithesis,” “New Growth Arts Review" and “Deek” magazine. Hamilton holds a Master of Arts in English education from the University of Pittsburgh, and a Master of Arts in composition from the University of Florida.

Photo Credits