Download Writing a Effective Technical Proposal: Tips and Guidelines and more Study notes Construction in PDF only on Docsity! Tips for Writing a Better Technical Proposal • Pay attention to the response due date and time. Late proposals are normally unacceptable. • Review the Statement of Work/Specifications (Section C of most solicitations). Understand what the project entails and requires. Be realistic in assessing your ability to do the work. • Review the Schedule of Items (Section B). If it’s important enough to be detailed in this schedule, it’s important enough to be addressed in your technical proposal. Do not simply use this schedule to create a calendar of events, but do incorporate all elements in your plan of operation. If you possess a unique skill, qualification, license, certification, etc. be sure to mention it. • Pay attention to detail… if you “cut and paste” from previous proposals, be sure to update things like solicitation numbers and the name of the project. Turn on spell checker and proof-read your proposal for obvious grammatical/syntax errors. The attention to detail you devote to your proposal does reflect on the attention you might be expected to devote to our project. Do not “hop scotch” back and forth between topics. If you are addressing experience/past projects, consolidate them into one section. If a previous project is not “obviously” related to this project; discuss what particular skills were required / demonstrated that translate to this one. • Review and carefully follow the Instructions to Offerors (Section L). If it lists four items that must be included in your proposal, include them, and in the same relative order listed. • Most construction RFPs will require four key sections in the technical proposal: (1) organization, (2) equipment, (3) plan of operation, and (4) quality control. Organization is where you list the general experience of key employees like project managers/superintendents and any sub-contractors. The list of equipment is meant to demonstrate both that you know what equipment will be required to complete the project and that you have access to it. If you are going to dig pits or trenches, a sturdy shovel will suffice, but we’d usually prefer to see an excavator. The fact that you own an obscure piece of equipment that won’t be used on this project is irrelevant. The plan of operations is the “heart” of the technical proposal. It should be a narrative that logically incorporates all the key elements in Sections B and C with sufficient detail to demonstrate your understanding of the project, your vision for organizing, sequencing and completing the various work elements, and that supports/justifies your price. Quality control is more than a supervisor paying attention to or spot-checking the job being done by workers. How are you measuring, evaluating and controlling the work being done? What assurances do you offer that construction will be square/level/plumb? Or that a pipeline will be pressure/leak tested before being buried? • If a key project element infers a specific skill (e.g., plumbing, which would normally necessitate a qualified plumber) don’t neglect to mention that when you address organization/experience.
