Templates

Proposal templates accelerate development by capturing proven structures, boilerplate content, and winning strategies from successful proposals. Create templates from your best work and reuse them across similar opportunities, reducing proposal development time by 40-60%.

Overview

Templates in Cothon serve multiple purposes:

• Accelerate Development: Start new proposals with pre-structured content
• Ensure Consistency: Maintain quality and compliance across all proposals
• Capture Best Practices: Preserve winning approaches from successful bids
• Reduce Risk: Avoid starting from scratch on tight deadlines
• Onboard New Team Members: Provide examples of quality proposal content
• Scale Operations: Handle more opportunities with the same team

Types of Templates

Proposal Templates

Complete proposal structures for specific RFP types:

Federal Government IT Services

• Sections: All 18 standard sections
• Structure: FAR-compliant organization
• Boilerplate: Federal security language, compliance statements
• Variables: Agency name, contract number, dates
• Use for: Any federal IT services RFP

State/Provincial Services

• Sections: Executive Summary through Schedule (10-12 sections)
• Structure: State-specific requirements
• Boilerplate: State certifications, local preference language
• Variables: State name, project specifics
• Use for: State government services

Commercial Technical

• Sections: Solution-focused (8-10 sections)
• Structure: Benefit-oriented, less compliance-heavy
• Boilerplate: Commercial terms, SLAs, support commitments
• Variables: Client name, solution specifics
• Use for: Private sector technology RFPs

Construction/Facilities

• Sections: Safety plan, bonding, schedule-heavy
• Structure: Trade-specific organization
• Boilerplate: Safety commitments, insurance, certifications
• Variables: Project location, size, duration
• Use for: Construction and facilities management RFPs

Section Templates

Reusable templates for individual sections:

Standard Section Templates:

• Company Overview: Core capabilities, history, differentiators (rarely changes)
• Past Performance: Structured case study format (add new projects, maintain structure)
• Team Qualifications: Standard team structure (swap in relevant personnel)
• Quality Assurance: QA methodology boilerplate (consistent across proposals)
• Risk Management: Risk identification framework (adapt risks to project)
• Certifications: Company certifications and compliance (update annually)

Agency-Specific Templates:

• DoD Security Plan: DFARS compliance language
• VA Transition Plan: VA-specific transition requirements
• GSA Compliance Matrix: GSA evaluation criteria format
• NASA Quality Plan: NPR 7120.5 compliance

Service-Line Templates:

• Cloud Migration Technical Approach: Standard cloud migration methodology
• Cybersecurity Management Plan: Standard SOC structure
• Agile Development Approach: Scrum/Kanban standard practices
• Help Desk Support Plan: ITIL-based support framework

Boilerplate Content Libraries

Reusable paragraphs and content blocks:

Corporate Boilerplate:

• Company introduction (elevator pitch)
• Mission and values statement
• Geographic presence and facilities
• Corporate timeline and milestones
• Awards and recognition
• Financial stability statement

Capability Boilerplate:

• Technology platform descriptions
• Methodology overviews (Agile, DevSecOps, ITIL)
• Partnership descriptions
• Tool and technology summaries
• Standard processes (security, QA, project management)

Compliance Boilerplate:

• Security and privacy commitments
• FAR/DFARS compliance statements
• Equal opportunity statements
• Small business commitments
• Veteran employment statements
• Environmental compliance

Transitional Phrases:

• Section openings: "In response to Requirement X.X, [Company] proposes..."
• Evidence transitions: "Our proven capability in this area is demonstrated by..."
• Benefit statements: "This approach provides [Agency] with the following benefits:"
• Compliance confirmations: "[Company] understands and accepts this requirement and will..."

Creating Templates

From Existing Proposals

Convert successful proposals into reusable templates:

Selecting Source Proposals:

• ✅ Choose winners (proven success)
• ✅ Use high-scoring proposals (>85 quality)
• ✅ Select recent proposals (current best practices)
• ✅ Pick representative opportunities (typical requirements)
• ❌ Avoid highly unique, one-off proposals
• ❌ Don't use proposals with issues or low scores
• ❌ Skip proposals with outdated content

From Scratch

Build custom templates for specific needs:

Template Naming Conventions:

[RFP Type] - [Service Line] - [Variation]

Examples:
- Federal - IT Services - Standard
- State - Consulting - Healthcare
- Commercial - Cloud Migration - Enterprise
- DoD - Cybersecurity - CMMC Level 3
- VA - Application Development - Agile

Template Variables

Use variables for content that changes per proposal:

Standard Variables:

• {{company_name}} - Your company name
• {{company_short_name}} - Abbreviated company name (for headers)
• {{agency_name}} - Client agency/organization name
• {{rfp_number}} - Solicitation or RFP number
• {{rfp_title}} - Project or opportunity title
• {{contract_type}} - Contract type (FFP, T&M, CPFF, etc.)
• {{contract_value}} - Contract value or ceiling
• {{contract_duration}} - Contract period of performance
• {{submission_date}} - Proposal due date
• {{start_date}} - Anticipated project start date
• {{location}} - Project location or work site

Conditional Variables:

• {{if_federal}}...{{/if_federal}} - Content only for federal RFPs
• {{if_small_business}}...{{/if_small_business}} - Content for small business set-asides
• {{if_clearance_required}}...{{/if_clearance_required}} - Security clearance content

Repeating Variables:

• {{for_each_requirement}}...{{/for_each_requirement}} - Loop over requirements
• {{for_each_team_member}}...{{/for_each_team_member}} - Loop over team

Example Usage:

In response to {{rfp_number}} - {{rfp_title}}, {{company_name}}
proposes a comprehensive solution for {{agency_name}}.

Our team has delivered {{similar_projects_count}} similar projects
over the past {{experience_years}} years, resulting in over
${{total_contract_value}}M in successful federal IT implementations.

{{if_federal}}
We maintain a facility clearance at the {{clearance_level}} level
and employ {{cleared_staff_count}} cleared personnel.
{{/if_federal}}

When creating a proposal from this template, you'll be prompted to fill in all variables.

Using Templates

Creating Proposals from Templates

Template Matching: Cothon can suggest templates based on:

• RFP type (federal, state, commercial)
• Industry/domain (IT, consulting, construction)
• Agency (if you've bid to them before)
• Service line (cloud migration, cybersecurity, etc.)
• Keywords in RFP (CMMC, Agile, transition, etc.)

Customizing Template Content

Templates are starting points, not final products. Always customize:

Must Customize:

• ✓ Project-specific technical approach
• ✓ RFP requirement responses
• ✓ Team member names and qualifications
• ✓ Schedule and milestones
• ✓ Pricing and cost details
• ✓ Client-specific understanding section

Can Reuse (with caution):

• Company overview (verify current)
• Corporate certifications (check expiration dates)
• Standard methodologies (ensure still applicable)
• Facilities descriptions (verify accuracy)
• General capability statements (update if changed)

Never Reuse Verbatim:

• ❌ Old client/agency names
• ❌ Previous RFP numbers or references
• ❌ Outdated technical solutions
• ❌ Incorrect dates or timelines
• ❌ Copy-paste competitor names or proposal details
• ❌ Expired certifications or team members no longer with company

Quality Check: After creating from template, search for:

• Previous client names (find and replace all)
• Old RFP numbers
• Dates from previous proposals
• Orphaned cross-references
• Inconsistent terminology

Template Adaptation

How AI adapts templates to new RFPs:

Requirement Mapping:

1. Extracts requirements from new RFP
2. Maps requirements to template sections
3. Identifies gaps (requirements not covered by template)
4. Recommends new sections or content additions

Content Generation Strategy:

• Preserve: Keep template boilerplate that's universally applicable
• Adapt: Modify template content to address specific requirements
• Generate: Create new content for unique requirements not covered by template
• Remove: Delete template content not relevant to this RFP

Example:

Template (Federal IT Template):

Our security approach follows NIST 800-53 guidelines and implements defense-in-depth architecture.

Adapted for VA Healthcare RFP:

Our security approach follows NIST 800-53 guidelines, VA Handbook 6500 requirements, and implements defense-in-depth architecture specifically designed for healthcare data (PHI/PII) protection under HIPAA.

Template content preserved, specific VA and healthcare requirements added.

Template Management

Organizing Templates

Keep templates organized for easy discovery:

Categories:

• By RFP Type: Federal, State, Local, Commercial
• By Agency: DoD, VA, DHS, State of California, etc.
• By Service Line: IT Services, Consulting, Cloud, Cybersecurity
• By Contract Type: IDIQ, Task Order, Standalone, Recompete
• By Complexity: Simple (3-5 sections), Standard (8-12 sections), Comprehensive (15-18 sections)

Tagging: Add tags for easy search:

• agile, waterfall, devops
• clearance-required, small-business, 8a
• cloud-migration, legacy-modernization
• healthcare, financial-services, defense

Folder Structure:

Templates/
├── Federal/
│   ├── DoD/
│   │   ├── IT Services - Standard
│   │   ├── Cybersecurity - CMMC
│   │   └── Cloud Migration - IL4
│   ├── VA/
│   │   ├── Healthcare IT - Standard
│   │   └── Application Development - Agile
│   └── Civilian/
│       ├── IT Services - Standard
│       └── Cloud Migration - FedRAMP
├── State/
│   ├── California/
│   └── Texas/
├── Commercial/
│   ├── Healthcare/
│   └── Financial Services/
└── Archive/
    └── Deprecated/

Template Versioning

Track template versions over time:

Why Version Templates:

• Improve templates based on proposal outcomes
• Update with new company capabilities
• Refresh outdated content
• Document changes for audit/learning

Version Information:

• Version number (1.0, 1.1, 2.0)
• Last updated date
• Change summary ("Updated security section for CMMC 2.0")
• Updated by (user name)
• Active vs. archived

Version Strategy:

• Minor updates (1.0 → 1.1): Small content refreshes, typo fixes
• Major updates (1.0 → 2.0): Significant restructuring, major content changes
• New template (2.0 → 3.0 → Archive 2.0): Fundamental changes, keep old version archived

Active vs. Archived:

• Active: Used for new proposals (appears in template selection)
• Archived: Preserved for reference and existing proposals using that version
• Proposals created from archived templates continue working (not affected by archival)

Template Permissions

Control who can use and edit templates:

Permission Levels:

• View: See template content
• Use: Create proposals from template
• Edit: Modify template content
• Manage: Edit, version, archive, set permissions
• Admin: Full control including delete

Organizational Templates:

• Organization Templates: Available to everyone in org
• Team Templates: Shared within specific team
• Personal Templates: Only available to creator
• Public Templates: Shared across all Cothon users (if you choose)

Template Locking: Lock templates to prevent unauthorized changes:

• Locked: No edits allowed, use-only
• Approved: Only designated approvers can edit
• Draft: Anyone with edit permission can modify

Template Analytics

Track template performance:

Usage Metrics:

• Number of proposals created from template
• Average proposal quality score
• Win rate for proposals using this template
• Time saved vs. creating from scratch
• Most commonly customized sections

Performance Insights:

• Which templates produce highest quality proposals?
• Which templates have highest win rates?
• Which sections are most often removed/added?
• Where do users spend the most time customizing?

Improvement Opportunities:

• Low quality scores → Template may need updating
• High customization in certain sections → May need more flexibility
• Frequent section additions → Consider adding to template
• Frequent section removals → Consider making sections optional

Dashboard View:

Template: Federal IT Services - Standard
Version: 3.2
Last Updated: 2026-02-15

Usage Stats:
- 47 proposals created (last 6 months)
- Avg. Quality Score: 82 (↑3 from v3.1)
- Win Rate: 38% (18 wins / 47 total)
- Avg. Time Saved: 12 hours vs. from-scratch

Top Customized Sections:
1. Technical Approach (91% customization)
2. Past Performance (78% customization)
3. Schedule (65% customization)

Recommendations:
- Technical Approach shows high customization - consider more flexible structure
- Strong win rate suggests effective template - share best practices

Template Best Practices

Building Effective Templates

Start with Winners:

• Use successful proposals (wins) as template sources
• Incorporate evaluator feedback ("what we did well")
• Preserve winning themes and differentiators
• Maintain proven structure

Keep Templates Current:

• Review and update quarterly
• Update certifications and credentials annually
• Refresh past performance examples regularly
• Remove outdated technical content

Make Templates Flexible:

• Use variables for content that always changes
• Include optional sections for varied requirements
• Provide alternative content blocks
• Document customization guidance

Focus on Quality Over Quantity:

• Better to have 5 excellent templates than 50 mediocre ones
• Consolidate similar templates
• Archive low-performing templates
• Focus on high-use RFP types

Document Everything:

• When to use each template
• What to customize
• Common pitfalls to avoid
• Links to successful proposals using this template
• Version history and changes

Template Content Guidelines

Executive Summary Template:

• Generic value proposition (adapt to specific client)
• Standard company introduction
• Boilerplate differentiators (customize rankings/emphasis)
• Template structure: Understanding → Solution → Qualifications → Why Us

Technical Approach Template:

• Standard methodology descriptions (Agile, DevSecOps, etc.)
• Common architecture patterns (cloud, microservices, etc.)
• Tool and technology descriptions
• Requirement response structure
• Leave specifics as variables/placeholders

Management Approach Template:

• Project management framework (PMI, Scrum, etc.)
• Standard governance structure
• Communication plan template
• Risk management process
• Quality assurance methodology

Past Performance Template:

• Case study structure: Challenge → Solution → Results
• Metrics template: "X% improvement in Y over Z period"
• Client reference format
• Relevance scoring criteria
• Similarity demonstration approach

Compliance Matrix Template:

• Table structure: Req # | Requirement | Response | Section | Page
• Standard compliance language
• Formatting and organization
• Cross-reference methodology

Using Templates Effectively

Before Starting:

1. Select the most appropriate template
2. Review template guidance and documentation
3. Identify what will need heavy customization
4. Gather new content (team members, projects, etc.)
5. Upload RFP for requirement extraction

During Development:

1. Fill in all variables immediately (avoid "TBD")
2. Customize high-impact sections first (Executive Summary, Technical Approach)
3. Update boilerplate content that's changed since template creation
4. Remove irrelevant sections, add missing ones
5. Maintain template structure where it works

Before Submission:

1. Search for old client/RFP references
2. Verify all dates are current
3. Check certification expiration dates
4. Validate team member information
5. Ensure compliance matrix is RFP-specific
6. Review for consistency and flow

After Submission:

1. Note what worked well vs. what needed heavy customization
2. Collect evaluator feedback (if available)
3. Update template based on lessons learned
4. Share improvements with team
5. Consider creating new template variant if needs were significantly different

Template Library Curation

Continuous Improvement

Regular Review Cycle:

• Quarterly: Review usage stats, identify underperforming templates
• Semi-Annually: Major content updates, incorporate new capabilities
• Annually: Comprehensive audit, consolidate/archive, validate all content

Feedback Loop:

• Collect user feedback on templates
• Track which sections users frequently regenerate (indicates weak template content)
• Survey proposal teams on template effectiveness
• Analyze win/loss data for template-specific patterns

Template Health Metrics:

Template Health Score: 85/100

✓ Usage: High (42 uses in 6 months)
✓ Win Rate: Above avg (38% vs. 32% org avg)
✓ Quality: High (avg 82 vs. 78 org avg)
⚠ Last Updated: 4 months ago (review recommended)
✓ Documentation: Complete
✓ Version Control: Active

Template Consolidation

When to Consolidate:

• Multiple similar templates with low individual usage
• Templates with >80% overlapping content
• Confusion over which template to use
• Maintenance burden of too many templates

Consolidation Strategy:

Template Governance

Approval Process:

• Draft: Template created, under development
• Review: Submitted for approval
• Approved: Ready for organizational use
• Locked: No further edits (gold standard)

Roles:

• Template Author: Creates and maintains template
• Template Reviewer: Reviews for quality and compliance
• Template Approver: Approves for organizational use (usually VP or practice lead)
• Template Admin: Manages template library, permissions, archival

Quality Standards:

• All variables clearly defined
• No client-specific information
• Current content (< 6 months old)
• Comprehensive documentation
• Tested (at least one successful proposal)
• Compliance-reviewed
• Proper categorization and tagging

Advanced Template Features

Smart Templates

Templates that adapt based on RFP characteristics:

Adaptive Sections:

• Security section expands if RFP mentions CMMC, FedRAMP, or FISMA
• Small business section included if set-aside procurement
• Transition plan included if incumbent is mentioned
• Past performance emphasizes federal work if federal RFP, state work if state RFP

Conditional Content:

{{if_security_clearance_required}}
Our team maintains {{clearance_count}} active security clearances
at the {{clearance_level}} level. Our facility clearance (FCL) was
granted on {{fcl_date}} and remains in good standing.
{{/if_security_clearance_required}}

Requirement-Driven Sections:

• If RFP mentions "Agile," Agile methodology section is emphasized
• If "transition" is in requirements, transition plan is auto-included
• If "small business," small business plan is added
• If specific security standards mentioned, relevant certification section expanded

Template Fragments

Reusable content blocks smaller than full sections:

Common Fragments:

• Company Elevator Pitch (2-3 paragraphs)
• Security Commitment Statement (1 paragraph)
• Quality Assurance Process (3-4 paragraphs)
• Project Management Approach (4-5 paragraphs)
• Risk Management Framework (5-6 paragraphs)

Using Fragments:

Fragment Library:

Corporate/
  - Company Introduction (2 versions: formal, conversational)
  - Mission Statement
  - Geographic Presence

Methodologies/
  - Agile Development (Scrum variant, Kanban variant)
  - DevSecOps Pipeline
  - ITIL Service Management
  - PMI Project Management

Compliance/
  - FAR 52.xxx Compliance Statement
  - DFARS 252.xxx Compliance Statement
  - HIPAA Compliance Statement
  - SOC 2 Certification Description

Past Performance/
  - DoD Project Case Study Template
  - VA Healthcare Project Template
  - Cloud Migration Success Story Template

Template Intelligence

AI-powered template recommendations:

Auto-Suggest Templates: When uploading RFP, AI analyzes:

• RFP type (federal, state, commercial)
• Industry/domain keywords
• Agency name (if previously bid)
• Service line indicators
• Contract type

AI recommends: "Based on this RFP, we recommend: Federal IT Services - DoD - Cybersecurity template (92% match)"

Template Gap Analysis: AI compares RFP requirements to template:

Template Coverage Analysis:
✓ 85% of requirements covered by template
⚠ 10% of requirements need new sections:
  - Cloud Cost Optimization Plan (not in template)
  - VA-Specific Transition Plan (template has generic transition)
✗ 5% of template not relevant:
  - On-Premises Infrastructure (RFP is cloud-only)

Recommendations:
1. Add Cloud Cost Optimization section
2. Replace transition plan with VA-specific variant
3. Remove on-premises infrastructure section

Template Improvement Suggestions: After proposal submission:

Proposal: VA Healthcare Modernization
Template Used: Federal IT - VA - Standard (v2.3)

Improvement Suggestions:
1. Technical Approach required heavy customization (78%)
   → Consider making this section more flexible
2. Past Performance section well-received (evaluator score: 95/100)
   → Preserve this structure in future template versions
3. Added new section: Cloud Cost Governance
   → Consider adding to template for future VA cloud RFPs

Template Sharing & Collaboration

Sharing Templates with Team

Internal Sharing:

• Make templates available to your organization
• Set permission levels (use, edit, manage)
• Track usage and gather feedback
• Collaborative template improvement

Template Contribution:

• Team members propose templates
• Review and approval process
• Credit authors
• Build institutional knowledge

Template Marketplace (Coming Soon)

Public Template Sharing:

• Share templates with broader Cothon community
• Browse templates from other organizations (anonymized)
• Rate and review templates
• Contribute to industry best practices

Industry-Standard Templates:

• Cothon-curated templates for common RFP types
• Maintained by industry experts
• Regularly updated for compliance changes
• Free for all users

Frequently Asked Questions

Next Steps

• Auto-Generation - Generate content for templates
• Multi-Section Proposals - Understand section structures
• Company Profile - Update profile for better template content
• Collaboration - Work with team on template development
• Exporting - Export templates for offline use