Multi-Section Proposals

Cothon generates 18 specialized proposal sections, each designed for specific evaluation criteria. This guide explains each section and how to customize them.

Section Overview

Section Details

1. Executive Summary

Purpose: First impression and value proposition

Contents:

• Company introduction
• Understanding of opportunity
• Solution highlights
• Key differentiators
• Win themes

2. Understanding

Purpose: Prove you understand the client's needs

Contents:

• Client background and context
• Current challenges
• Desired outcomes
• Success criteria
• Stakeholder needs

3. Technical Approach

Purpose: Explain your solution

Contents:

• Solution architecture
• Technology components
• Requirement responses
• Innovation elements
• Technical differentiators

4. Methodology

Purpose: Describe your framework

Contents:

• Development methodology (Agile, Waterfall, etc.)
• Process frameworks
• Standards compliance
• Best practices
• Continuous improvement

5. Work Plan

Purpose: Detailed breakdown of work

Contents:

• Work Breakdown Structure (WBS)
• Task descriptions
• Deliverables
• Dependencies
• Acceptance criteria

6. Schedule

Purpose: Timeline and milestones

Contents:

• Project timeline
• Major milestones
• Phase gates
• Dependencies
• Critical path

7. Management Plan

Purpose: Project governance approach

Contents:

• Organizational structure
• Roles and responsibilities
• Communication plan
• Decision-making processes
• Escalation procedures
• Change management

8. Staffing Plan

Purpose: Team structure and allocation

Contents:

• Team organization
• Role descriptions
• FTE allocation
• Ramp-up plan
• Backup/succession

9. Key Personnel

Purpose: Showcase team expertise

Contents:

• Team member bios
• Relevant experience
• Certifications
• Education
• Availability commitment

10. Past Performance

Purpose: Demonstrate relevant experience

Contents:

• Similar contracts
• Client references
• Performance metrics
• Lessons learned
• Awards and recognition

11. Quality Assurance

Purpose: Quality management approach

Contents:

• QA/QC processes
• Testing approach
• Quality metrics
• Continuous improvement
• Defect management

12. Risk Management

Purpose: Risk identification and mitigation

Contents:

• Risk identification process
• Risk register
• Mitigation strategies
• Contingency plans
• Risk monitoring

13. Security

Purpose: Security approach and compliance

Contents:

• Security framework
• Data protection
• Access controls
• Compliance (PIPEDA, etc.)
• Security certifications

14. Transition Plan

Purpose: Onboarding and eventual handoff

Contents:

• Transition-in approach
• Knowledge transfer
• Training plan
• Transition-out planning
• Documentation

15. Small Business

Purpose: Subcontracting and small business participation

Contents:

• Small business goals
• Subcontracting plan
• Mentor-protégé relationships
• Indigenous participation (if applicable)

16. Compliance Matrix

Purpose: Point-by-point requirement response

Contents:

• Requirement reference
• Compliance statement
• Response location
• Evidence/explanation

17. Pricing Summary

Purpose: Non-sensitive cost overview

Contents:

• Pricing approach
• Cost structure
• Value proposition
• Optional pricing

18. Appendices

Purpose: Supporting documentation

Contents:

• Resumes
• Certificates
• Past performance details
• Letters of commitment
• Technical diagrams

Customizing Sections

Reordering

Drag sections to match RFP requirements:

1. Open the proposal editor
2. Click and drag section headers
3. Or use Reorder Sections menu

Hiding Sections

Skip sections not required:

1. Click the section menu (...)
2. Select Hide Section
3. Hidden sections won't export

Adding Custom Sections

Create additional sections:

1. Click Add Section
2. Name the section
3. Write or generate content

Section Relationships & Dependencies

Content Flow

Sections build on each other to tell a cohesive story:

Executive Summary (synthesizes all sections)
    ↓
Project Understanding (shows you get it)
    ↓
Technical Approach (how you'll do it)
    ↓
Management Approach (how you'll manage it)
    ↓
Team Qualifications (who will do it)
    ↓
Past Performance (proof you've done it before)
    ↓
Risk Management (how you'll handle problems)
    ↓
Schedule (when you'll do it)
    ↓
Compliance Matrix (proof you meet all requirements)

Cross-References

Sections should reference each other for coherence:

• Executive Summary references highlights from all other sections
• Technical Approach references team qualifications and past performance
• Management Approach references staffing plan and quality assurance
• Compliance Matrix references specific sections for each requirement

Customizing Section Structure

Reordering Sections

Match RFP instruction letter order:

Hiding Sections

Exclude sections not required by the RFP:

Hidden sections can be unhidden later if needed.

Adding Custom Sections

Create additional sections for unique RFP requirements:

Splitting Large Sections

Break oversized sections into sub-sections:

When to Split:

• Section exceeds page limits
• RFP requests multiple sub-topics
• Content clarity improved by separation

How to Split:

1. Create new section with related title (e.g., "Technical Approach - Architecture" and "Technical Approach - Security")
2. Move content between sections
3. Update cross-references
4. Renumber if necessary

Merging Sections

Combine related sections if RFP allows:

When to Merge:

• RFP doesn't specify separate sections
• Content is thin when separated
• Reduces overall page count

How to Merge:

1. Copy content from secondary section
2. Paste into primary section with clear sub-headings
3. Delete secondary section
4. Update compliance matrix references

Section Checklist

Use this checklist when reviewing each section:

Content Quality

• Addresses all relevant RFP requirements
• Includes specific examples and details
• Quantifies benefits with metrics where possible
• Avoids generic or template language
• Maintains professional tone throughout
• Uses active voice and clear language

Compliance

• Follows RFP structure and terminology
• Includes all required elements
• Cites requirement numbers/references
• Within page limits (if specified)
• Follows formatting requirements

Coherence

• Flows logically from introduction to conclusion
• Transitions smoothly between topics
• Consistent with other sections
• No contradictions with other sections
• Appropriate level of detail

Evidence

• Includes supporting data and metrics
• References past performance examples
• Cites industry standards or certifications
• Includes diagrams or visuals (if appropriate)
• Provides references for claims

Differentiation

• Highlights unique capabilities
• Demonstrates competitive advantages
• Connects features to client benefits
• Addresses client pain points
• Reinforces win themes

Evaluation-Driven Section Weighting

Align section emphasis with evaluation criteria:

High-Weight Factors

If the RFP states:

"Technical approach will be weighted 40% of the total score"

Response Strategy:

• Allocate 40% of page count to technical sections
• Expand Technical Approach to maximum allowed pages
• Add Technical Appendices if allowed
• Reference technical approach in Executive Summary
• Connect past performance to technical capabilities

Evaluation Criteria Mapping

Section Templates

Create reusable templates for standard sections:

Company Boilerplate Sections

These sections rarely change between proposals:

Certifications & Corporate Qualifications

• Company certifications (ISO, CMMI, etc.)
• Insurance coverage
• Security clearances
• DUNS, CAGE codes
• Small business status

Facilities & Resources

• Office locations
• Lab facilities
• Equipment inventory
• IT infrastructure
• Collaboration tools

Template Benefits:

• Consistency across proposals
• Faster proposal development
• Reduced risk of outdated information
• Easy centralized updates

RFP-Type Templates

Standard structures for common RFP types:

Federal IT Services

• Section order per FAR guidelines
• Security section always included
• Small business plan mandatory
• Detailed transition plan

State/Provincial Services

• Local presence emphasis
• State-specific certifications
• Regional reference projects
• Local workforce utilization

Construction Projects

• Safety plan (mandatory)
• Environmental compliance
• Bonding and insurance details
• Local subcontractor plan

Section Formatting Best Practices

Visual Hierarchy

Use formatting to improve readability:

Heading Levels

Section Title (H1)
  Major Topic (H2)
    Subtopic (H3)
      Detail (H4)

Lists

• Use bullets for non-sequential items
• Use numbers for sequential steps or priorities
• Limit nesting to 2-3 levels maximum

Emphasis

• Bold for key terms on first use
• Italics for emphasis or document titles
• SMALL CAPS for acronyms on first use (then regular)

Tables & Figures

Use tables for comparative or structured data:

Good Uses of Tables:

• Compliance matrices
• Staffing plans (roles, hours, rates)
• Past performance summaries
• Requirement responses
• Schedules and milestones

Figure Numbering:

• Number consecutively within each section
• Format: "Figure 3.1: System Architecture Diagram"
• Reference in text: "as shown in Figure 3.1"

White Space

Don't overcrowd pages:

• 1-inch margins (unless RFP specifies otherwise)
• Line spacing: 1.5 or double (per RFP)
• Space between sections
• Generous margins around figures

Common Section Mistakes

Executive Summary

❌ Mistake: Writing the executive summary first ✅ Fix: Write it last, after all other sections are complete

❌ Mistake: Making it too long (5+ pages) ✅ Fix: Keep to 2-3 pages maximum, focus on highlights

❌ Mistake: Repeating entire sections verbatim ✅ Fix: Synthesize key points, add no new information

Technical Approach

❌ Mistake: Describing what you'll do without explaining why ✅ Fix: Explain rationale for technical decisions

❌ Mistake: Using generic technical descriptions ✅ Fix: Tailor to specific RFP requirements

❌ Mistake: Overwhelming with technical jargon ✅ Fix: Write for non-technical evaluators, explain acronyms

Past Performance

❌ Mistake: Listing every project you've ever done ✅ Fix: Select 3-5 most relevant projects with detail

❌ Mistake: Vague descriptions without metrics ✅ Fix: Quantify results: uptime, cost savings, timeline

❌ Mistake: Missing client contact information ✅ Fix: Include current client POC with phone and email

Management Approach

❌ Mistake: Generic project management descriptions ✅ Fix: Specific plans for THIS project

❌ Mistake: No connection to technical approach ✅ Fix: Align management processes with technical work

❌ Mistake: Ignoring agency-specific processes ✅ Fix: Address required reporting, approvals, protocols

Compliance Matrix

❌ Mistake: Vague "see Section X" references ✅ Fix: Specific page numbers and direct responses

❌ Mistake: Missing requirements ✅ Fix: Double-check every single requirement is listed

❌ Mistake: Copy-pasting requirement text ✅ Fix: State how you comply, not just what the requirement is

Advanced Section Strategies

Win Theme Integration

Weave win themes throughout all sections:

Example Win Themes:

1. Proven experience with this exact system
2. Deep understanding of agency mission
3. Local presence and rapid response
4. Innovation with risk mitigation

Integration Approach:

• Open each major section with relevant win theme
• Use win themes as topic sentences
• Close sections by reinforcing themes
• Bold or highlight theme statements

Discriminator Emphasis

Highlight unique advantages that competitors can't match:

Identifying Discriminators:

• Incumbent knowledge (if you are incumbent)
• Exclusive partnerships or tools
• Unique team qualifications
• Patents or proprietary methods
• Geographic advantages

Emphasizing Discriminators:

• Dedicated subsections for unique capabilities
• Callout boxes or side panels
• Testimonials from clients
• Competitive comparison tables (if allowed)

Deductive vs. Inductive Structure

Deductive (Conclusion First):

• State the approach/solution upfront
• Then provide supporting rationale
• Best for technical evaluators
• Example: "We will use microservices architecture because..."

Inductive (Build to Conclusion):

• Present requirements and constraints
• Analyze alternatives
• Conclude with recommended approach
• Best for narrative flow
• Example: "Given the need for scalability... we evaluated... therefore microservices..."

Most proposal sections benefit from deductive structure. State your approach clearly, then support it.

Storyboarding Sections

Before writing, outline the narrative:

1. Opening Hook: Compelling first sentence
2. Context: Requirement or problem
3. Solution: Your approach
4. Evidence: Why it works (past performance, data)
5. Benefits: Value to client
6. Closure: Transition to next topic

This story structure keeps evaluators engaged.

Frequently Asked Questions

Next Steps

• AI Refinement - Improve section quality and coherence
• Exporting - Format sections for submission
• Auto-Generation - Generate content for sections
• Templates - Save section structures for reuse
• Compliance Best Practices - Ensure all requirements are met