Six Proposal Management Tools I Can’t Live Without


As proposal professionals, we continually look to find ways to lead our teams and ensure we are getting the best results possible. Tina Benson suggests in an article published on the Chartered Management Institute website that, “by and large, teams reflect their management. So being an effective, proactive manager increases your team’s chances of achieving success.” In line with Benson’s suggestions, as Proposal Managers, we can make great strides in increasing the success of our teams by leveraging the following six proactive proposal management tools.

1. Proposal Schedule
One of the first things I establish for each of my proposals is the proposal schedule. This schedule drives the timeline for my team and helps ensure we achieve our final submission in the smoothest way possible. The proposal schedule should set the dates for key milestones and events. For most large efforts, these milestones include the Blue Team, Green Teams, Pink Team, Red Team, and Gold Team, as well as all associated author pens down dates and times. To establish my proposal schedule, I typically work backwards from the delivery date. I always schedule sufficient time for final editing, production, book check, and delivery. In addition, I try to keep 10 percent of the available time in reserve to manage unforeseen events, such as a system crash, family emergency, or client crisis that requires immediate attention.

2. Proposal Outline and Compliance Matrix
The next key tool I establish for each proposal is my proposal outline and compliance matrix. This document maps each of the RFP requirements back to my proposal outline so that the team can be sure we are addressing all requirements in our response. The proposal outline and compliance matrix defines section numbers, headings, page allocations, assigned writers, and corresponding RFP sections. When outlining, I always organize sections according to the proposal instructions, unless otherwise specified by the RFP. Where the evaluation criteria do not align cleanly to the instructions, I add in additional headings. Next, I map in any relevant SOW or other RFP sections, as necessary. This is usually required in the technical and past performance sections of the response.

To facilitate evaluation, I always follow the order of the RFP, even if the order does not make logical sense to me or my team. I use language very close to the RFP to make the compliance mapping easy for the evaluators. In addition, when the Government’s numbering scheme is clear, I include the RFP section mapping in parentheses after each heading to further facilitate the evaluation.

3. Style Guide & Wall of Truth
Another key document I stand by as a Proposal Manager is the Style Guide and Wall of Truth. A proposal style guide is a set of standards for the writing, formatting, and design of a proposal. This critical document establishes style requirements to promote consistency. Style guides set standards to be used in areas such as punctuation, capitalization, formatting of numbers and dates, table appearance, and other areas. The standards should include conventions from the proposal department’s standard style guide (if it has one) but should also be tailored to the requirements of each individual customer and RFP. I reserve the “Wall of Truth” section to include proposal-specific items that pop up during proposal development. These items might include the number of cleared personnel employed by the company, the years of experience the company has supported the customer, and proposal-specific nomenclature.

By establishing style guidelines early on with a style guide, proposal writing starts out consistent. To make sure this happens, I find it helpful to review the style guide with my writers before they start writing. This helps ensure that writers are using common conventions from the start. Having writers use a common style guide also makes editing easier in the end because most of the inconsistencies are already addressed. It further streamlines the editing process because the style conventions are already defined for the editors. Additionally, if you have multiple editors, they will all be editing to the same set of standards. You can read more on Style Guides here.

4. Action Items List & Status Trackers
Action Item Lists and Status Trackers are also very useful management tools. The Action Item List is a chronological master list of action items, requests, assignments, and deliverables. Typically, an item will remain on the Action Item List until the Proposal Manager or Capture Manager closes it out. If a critical item on the Action Item List is not closed out in a timely manner, it might be escalated for immediate attention by senior management. 

Related to the Action Item List are Status Trackers. Status Trackers are particularly helpful for large efforts with multiple teammates and many moving parts. I like to use individual Status Trackers to track the status of teammate data calls, customer past performance questionnaires, and other similar requirements. Action Item Lists and Status Trackers help identify and resolve roadblocks and critical issues, and they can help in flagging any identifying any potential showstoppers as well.

5. Proposal Workspace
Another critical proposal tool is the proposal workspace. Before the proposal kickoff, I always work with my team to establish a proposal workspace that includes a file repository to organize and secure proposal related data, including solicitation files, capture and solution information, proposal management documents (e.g., schedule, outline and compliance matrix, etc.), potential reuse information, working proposal drafts, and graphics. Typically, I establish this workspace using a supporting application, such as SharePoint, Privia, or Virtual Proposal Center (VPC). These collaborative software applications also include built-in features for version control to help revert to a previous version if critical content is accidentally deleted. My team then uses the collaboration portal for writer collaboration, color team reviews, and final production.

6. Daily Stand-Up Meetings
Daily stand-up meetings help to flag any issues that might be preventing the team from moving forward. My stand-up meetings typically include a brief capture update, a review of upcoming schedule milestones and deadlines, a quick status of each major section, and an action item review. Because I don't want to interfere with the productivity of my team, I try to limit my daily stand-up meetings to no more than 15 minutes. I schedule separate meetings for issues that seem like they will require more time.


Final Thoughts
As proposal professionals, we continually look to find ways to lead our teams and ensure we are getting the best results possible. To do so, we should strive to be effective, proactive managers. One way to this is to leverage proactive proposal management tools. By establishing solid proposal schedules, clear proposal outlines and compliance matrices, detailed action item lists and status trackers, and logically organized proposal workspaces, we set the stage for smooth proposal development. To help manage the proposal process and these tools, we can use daily stand-up calls to help flag critical issues that might be preventing the team from moving forward. Though there are certainly other tools that I use to help manage my proposal teams—these six tools are the ones that I simply cannot live without.


Written by Ashley Kayes, CP APMP
Senior Proposal Consultant, AOC Key Solutions, Inc. (KSI)


Comments

  1. Hello Ashley, As usual your blogs are very informative. I am sure Zbizlink (A proposal writing and management software) covers all above mentioned key points.

    ReplyDelete
  2. Good Post! Thank you so much for sharing this pretty post, it was so good to read and useful to improve my knowledge as updated one, keep blogging…
    Project Management Apps

    ReplyDelete

Post a Comment

Popular posts from this blog

6 Strategies To Tackle Tight Page Limitations

Why the Proposal Process has Always Been Agile

Agile Proposal Development: A Spotlight on Scrum