Technical Writers Crave Structure

Technical (Solutions) writers crave structured outlines for the following reasons:
1. Most don't like to write, and structure increases their confidence.
2. They are usually fully billable, and structure allows them to satisfy the writing requirement faster.
3. Several writers may be working together, and structure keeps them unified in their approach and results in uniform, higher quality content.

The following is an example of an outline for a solutions section of a proposal. The example is an excerpt from one of our model service proposal documents.

Solutions Outline with Writing Guidelines Inserted in Red

3.1 Task ___________________________________

Task introduction: List the important aspects of the task.

  • What makes your approach to this task of value
  • Why your approach is unique
  • Why you are doing it this way
  • Features and benefits
  • 3.11 Subtask ___________________________________

    Purpose of subtask, e.g. In this task we will...

    Objective of task, e.g. The objective of this task is to...

    A proposal outline needs to be in as much detail as possible; the more detail the better. Proposal managers should use their experience, information in the Request for Proposal, and legacy content to prepare an outline of all of the required sections of a proposal.


    This article has been viewed: 5072 times

    Rate This Article