Shipley Proposal Guide 3 Rd Edition

What Shipley Proposal Guide Actually Is

The Shipley Proposal Guide is a methodology for structuring winning proposals, most commonly used in government contracting and large B2B sales environments. It was developed by Shipley Associates, a consulting firm that has been around since the 1970s. The third edition expanded on the original framework with more detail on capture planning, evaluation criteria mapping, and compliance management. It is not free software. It is a process you learn and then apply. Most people treat it like a template checklist. That is a mistake. The guide is really about discipline — forcing your team to answer specific questions before they start writing. If you skip those questions, your proposal will look fine on the surface and lose on substance every time.

Getting the Shipley Proposal Guide 3 Rd Edition

You can purchase the book directly from Shipley Associates or through major book retailers. It is sold as a physical copy and sometimes as a downloadable PDF depending on the vendor. There is no legitimate free version. Any site offering a "free download" is likely distributing a pirated copy or an outdated version that misses key updates. The third edition itself comes with companion materials — usually spreadsheets and checklists — that some resellers bundle separately. Check what is included before you buy. The core methodology is in the book. The extras are nice but not essential. The Shipley approach breaks the proposal lifecycle into distinct phases: opportunity identification, capture planning, solution development, proposal writing, and review. Each phase has defined deliverables and gates. You do not move forward until the gate is signed off. This sounds bureaucratic and it is, but that is the point. Most lost proposals come from teams that started writing before they understood what the customer actually wanted. Here is how I have seen it play out. A team gets an RFP for a $4 million IT modernization contract. They read the requirements document, assign sections to writers, and start drafting. Six weeks later they submit. The proposal is compliant. It looks professional. They get scored in the lower third and lose. The problem is they never did proper capture planning. They never met the customer before the RFP dropped. They never understood the evaluation weighting. Shipley would have forced them to answer those questions first.

The win themes section is where most people struggle. Win themes are not marketing slogans. They are concise statements that connect your capability directly to the customer's stated and unstated needs. A proper win theme answers the question "why should the customer pick us?" in one or two sentences. I once worked on a proposal where the win theme was "we are the best provider of cloud services." That got zero points during evaluation because it told the customer nothing specific about their situation. We rewrote it to reference the exact clause in the RFP about data sovereignty and explained how our architecture met that requirement. The score moved up significantly.

Common Pitfalls That Cost Proposals

The biggest issue I see is compliance mismanagement. The Shipley method requires a compliance matrix — a document that maps every requirement in the RFP to the exact section and page number in your proposal. When this is done poorly, reviewers can find a requirement and either miss your response entirely or spend five minutes digging through pages to find it. Both outcomes are bad. I have spent hours manually cross-checking compliance matrices because the automated tools did not handle cross-references correctly. The workaround was simple: export the matrix to a flat spreadsheet, add column filters, and run a vlookup against the RFP requirement numbers. It takes about ten minutes and catches mismatches that would otherwise go unnoticed until after submission. Another pitfall is the volume of content. Shipley emphasizes thoroughness, and teams often interpret that as "more is better." A 200-page technical volume where nothing stands out is worse than a 80-page volume where the key differentiators are obvious. The guide does acknowledge this, but it does not scream it loud enough. I learned this the hard way on a defense contract proposal. We wrote 180 pages on our past performance because the RFP asked for it. The evaluators skimmed through it and scored us average. Another firm submitted 60 pages with three detailed case studies that directly mirrored the RFP's pain points. They won. The difference was relevance, not completeness.

What the Guide Does Not Cover Well

The Shipley Proposal Guide 3 Rd Edition is strong on structure and process. It is weaker on pricing strategy and capture planning for competitive situations where you are not the Incumbent. The pricing chapter gives general guidance but does not go deep into cost modeling techniques like activity-based costing or real-options pricing. If you are running a cost-realistic proposal for a complex engineering contract, you will need to supplement Shipley with other resources. The capture planning section assumes you have time before the RFP drops. In reality, many opportunities come through sole-source nominations or emergency acquisitions where you have days, not months, to prepare. The framework still applies, but you have to compress it aggressively and drop some of the gates. There is also a gap when it comes to small business certifications and subcontracting plans. The guide mentions these briefly but does not provide a practical workflow. For SBIR/STTR proposals or contracts with significant subcontracting requirements, you will need to layer in additional planning that Shipley does not address. I keep a separate checklist for those items and integrate it with the Shipley timeline rather than trying to force everything into one system.

A Practical Walkthrough

Start with the opportunity. Read the RFP at least twice. The first pass is for comprehension. The second pass is for hunting — flag every requirement, constraint, evaluation criterion, and compliance checkbox. Build your compliance matrix immediately. Do not wait until the draft is ready. I recommend creating the matrix in the first 48 hours, even if you fill it in partially. An empty matrix is worse than an incomplete one because it creates a false sense of security. Next, develop your win themes. Write three to five of them. Test each one against the evaluation criteria. If a win theme does not connect to at least one evaluation factor, cut it. Simple as that. Then assign sections. Use the Shipley outline format, but adapt it. Do not follow the template rigidly if the RFP structure calls for something different. The goal is readability for the evaluator, not adherence to a book. Writing happens after the outline is approved. That approval step is where most teams fail. They skip it because they are behind schedule. When you are behind schedule, skipping the outline makes the problem worse, not better. You end up rewriting entire sections because the structure was wrong. I have watched a proposal team spend three full days reorganizing a volume because they started writing without a sign-off. That time could have been spent on content development if they had stopped and gotten the outline approved first.

Review is the final gate. Shipley recommends multiple review cycles: team review, compliance review, red team review, and golden team review. Each has a different purpose. Compliance review checks the matrix. Red team review simulates the evaluator's perspective. Golden team review is the final polish. Do not combine these. I have seen teams merge compliance and red team into one session because they were short on time. The result was both reviews were superficial. A compliance reviewer who is also asked to evaluate persuasiveness will miss compliance gaps because they are thinking about narrative flow instead of checkbox matching.

Who Should Use This

The Shipley method works best for mid to large organizations that bid regularly and have the overhead to support a structured process. If you are a small startup that bids two or three proposals a year, the framework may feel heavy. You can still use parts of it — the compliance matrix and win theme development are universally useful — but you do not need the full gate system. For teams that bid monthly, the discipline pays for itself quickly. The time saved in rework and the improvement in win rates usually justify the upfront investment in learning the methodology. The guide itself is dense. It is not a light read. I would recommend keeping it on your desk and referring to specific chapters as needed rather than trying to read it cover to cover before your next proposal. The methodology is better absorbed in context. You will remember the compliance matrix section better when you are actually building one than you will from reading about it in isolation.