Bid Records

Bid records are the foundation of your organization's competitive intelligence system. Each record captures everything about a single procurement opportunity: from initial evaluation through bid submission to final outcome. Over time, these records accumulate into an institutional knowledge base that drives strategic decisions and improves win rates.

A well-maintained bid record tells the complete story of an opportunity—why you pursued it, how you approached it, who you competed against, whether you won, and what you learned. This structured capture of bidding experience ensures hard-won lessons aren't lost when team members change or memories fade.

Understanding Bid Records

What is a Bid Record?

A bid record is a comprehensive log of your organization's interaction with a specific procurement opportunity. It can represent:

• Submitted bids: Opportunities where you prepared and submitted a proposal
• No-bid decisions: Opportunities you evaluated but chose not to pursue
• Lost opportunities: Bids submitted but not awarded to your organization
• Wins: Successful bids that resulted in contract awards
• Watch items: Opportunities you're monitoring without active pursuit

Each record links to the original opportunity (if from the Tenders system) or can be created standalone for opportunities from other sources or historical tracking.

The Bid Record Lifecycle

Bid records evolve through distinct stages:

Each stage has specific data needs. Early stages focus on evaluation criteria and decision factors; later stages capture bid details, competitors, and outcomes.

Creating Bid Records

From the Tenders System

The fastest way to create a bid record is directly from a tender opportunity:

Manual Creation

For opportunities not in the Tenders system (e.g., historical bids, private sector work, or external sources):

Bulk Import (Historical Data)

For importing dozens or hundreds of historical bid records, see the Importing Data Guide.

Bid Record Fields

Core Opportunity Information

These fields identify and describe the procurement opportunity:

Your Organization's Response

These fields track your evaluation, decision, and bid:

Outcome Tracking

Once the procurement decision is announced, capture the result:

Competitive Intelligence

Document who you competed against and what you learned:

As you add competitors to bid records, the system automatically builds Competitor Profiles showing their win rates, typical bid amounts, and bidding patterns.

Lessons Learned

The most valuable intelligence often comes from reflection:

Administrative Fields

These fields support workflow and organization:

Managing Bid Records

Updating Records as Opportunities Progress

Bid records are living documents that evolve. Update them at key milestones:

When Evaluation Begins

Status: Discovered → Evaluating

• Assign team members to evaluate
• Set strategic priority
• Document initial impressions in notes

After Bid/No-Bid Decision

Status: Evaluating → Bidding (or No-Bid)

If bidding:

• Update status to "Bidding"
• Note key differentiators or approach
• Estimate bid amount (update later with actual)
• Assign proposal team

If not bidding:

• Update status to "No-Bid"
• Document why: "Outside core capabilities", "Too competitive", "Insufficient margin", etc.
• Save immediately—no-bid intelligence prevents future wasted effort

When Bid is Submitted

Status: Bidding → Submitted

• Record actual bid amount
• Enter submission date
• List known competitors (if you know who else bid)
• Note any unique elements of your proposal

When Outcome is Announced

Status: Submitted → Won or Lost

If you won:

• Update outcome to "Won"
• Record decision date
• Capture awarded amount
• Schedule a "why we won" debrief

If you lost:

• Update outcome to "Lost"
• Record winner and awarded amount if known
• Capture number of bidders if disclosed
• Critical: Document why you lost while details are fresh
• Request formal debrief from issuing organization if available

Editing Existing Records

To update a bid record:

Deleting Records

Bid records can generally be deleted by:

• The user who created them
• Organization administrators
• Users with explicit delete permissions

Before deleting, consider:

• Archive instead: Many organizations prefer archiving old records to preserve history
• Data integrity: Deleting records removes them from analytics and competitor profiles
• Team visibility: Other team members may reference this record

To delete:

1. Open the bid record detail view
2. Click the More Actions menu (often a "..." icon)
3. Select Delete Bid Record
4. Confirm deletion (this action is typically permanent)

Organizing Bid Records

Using Folders

Organize bid records into folders by year, department, category, or any structure that makes sense:

Using Tags

Tags offer more flexible organization than folders (records can have multiple tags):

Common tagging strategies:

• By stage: "active-bid", "awaiting-outcome", "closed"
• By priority: "strategic", "routine", "opportunistic"
• By risk: "high-risk", "safe-bet", "stretch-opportunity"
• By outcome reason: "pricing-too-high", "strong-incumbent", "missed-requirement", "new-capability"
• By type: "sole-source", "competitive", "set-aside", "protest-rebid"

Create a tagging convention for your organization and use it consistently to maximize filtering power.

Smart Filters

Most Org Intelligence systems offer saved filters for common views:

Pre-built filters:

• Open Bids: Status = Evaluating, Bidding, or Submitted
• Recent Outcomes: Outcome recorded in last 30 days
• Wins This Year: Outcome = Won, Decision Date in current year
• High-Value Opportunities: Opportunity Value > $1M
• My Assigned Bids: Assigned Team includes current user
• No-Bid Decisions: Bid Decision = No-Bid

Create custom filters:

Attaching Documents

Bid records become more valuable when you attach supporting materials:

What to Attach

During evaluation:

• RFP or solicitation document (PDF)
• Preliminary capability matrix
• Evaluation checklist or scoring sheet
• Competitive intelligence on known competitors

During bidding:

• Bid outline or storyboard
• Draft technical approach
• Pricing spreadsheets
• Past performance references

After outcome:

• Final submitted proposal (PDF)
• Official debrief notes or letter
• Win/loss analysis document
• Presentation used in oral proposal (if applicable)

Winning bids:

• Executed contract
• Award notice
• Successful technical approach (for reference)
• Pricing strategy that won

How to Attach Documents

Document Permissions

Attachments inherit the bid record's permissions:

• Organization members with access to the record can view attachments
• Admins can delete attachments
• If the bid record is shared via link, recipients can view attachments (unless restricted)

Collaboration Features

Assigning Team Members

Bid records support multi-user collaboration:

Team Lead: Primary owner who drives the bid decision and proposal (if bidding). Typically receives notifications about record updates.

Assigned Team: All team members involved in evaluating or bidding this opportunity. May include:

• Capture manager
• Proposal manager
• Technical leads
• Pricing analyst
• Contracts specialist

To assign team members:

1. Open the bid record for editing
2. In the Assigned Team field, search for and select users
3. Optionally set one as Team Lead
4. Save the record

Assigned users will see this record in their "My Assigned Bids" filter and may receive notifications about updates (depending on your organization's settings).

Comments and Discussions

Most bid records include a comments section for team discussions:

Use comments for:

• Asking questions about requirements
• Sharing insights from debrief meetings
• Discussing bid/no-bid recommendations
• Flagging risks or concerns
• Sharing competitive intelligence

Comment features:

• @mentions: Tag specific users to notify them (e.g., "@jane What's your read on the past performance requirements?")
• Thread replies: Keep related comments together
• Edit/delete: Correct mistakes or remove outdated comments
• Activity timestamps: See when each comment was added

Activity Logs

Every bid record maintains an activity log showing:

• Who created the record and when
• All field changes (old value → new value)
• Status transitions
• Comments added
• Documents attached or removed
• Team member assignments

Activity logs create an audit trail and help new team members understand a bid's history.

Bid Record Best Practices

1. Create Records Early

Don't wait until you decide to bid. Create records as soon as an opportunity enters serious evaluation:

Why early creation matters:

• Captures bid/no-bid reasoning even if you choose not to bid
• Provides a collaboration space during evaluation
• Ensures you don't lose track of opportunities
• Starts the clock for time-to-decision metrics

When to create:

• Immediately when an opportunity looks promising during tender browsing
• When a department or partner asks if you're interested
• When you decide to invest time in evaluation (even if just an hour)

2. Document No-Bid Decisions

Organizations often neglect to record why they chose NOT to bid. This is a mistake:

Value of no-bid records:

• Prevents repeatedly evaluating the same unsuitable opportunities
• Reveals patterns in what your organization can't or won't do
• Informs capability development priorities
• Shows executives what you're saying "no" to and why

Good no-bid documentation:

Title: Cloud Infrastructure Services - Dept of Finance
Status: No-Bid
Bid Decision: No-Bid
Decision Date: 2025-03-15

Why We Didn't Bid:
"Required AWS GovCloud experience (5+ years). We're primarily Azure/GCP. Building AWS GovCloud practice would take 12+ months and this $2M opportunity doesn't justify that investment. Recommend no-bid unless we see 3+ similar opportunities."

Tags: capability-gap, aws-govcloud, declined

This record prevents your team from evaluating similar AWS GovCloud opportunities until your capability changes.

3. Update Promptly at Milestones

Bid records are most accurate when updated immediately after key events:

Update immediately after:

• Bid/no-bid decision: Capture reasoning while fresh
• Bid submission: Record actual bid amount and submission date
• Outcome announcement: Log win/loss and decision date
• Debrief meeting: Add lessons learned while they're vivid

Waiting even a few days leads to forgotten details and reconstruction errors.

4. Capture Honest Loss Analysis

The most valuable intelligence comes from honest assessment of losses:

Avoid:

• "They didn't understand our approach" (blaming evaluators)
• "Politics" (vague conspiracy theories)
• "Unfair evaluation" (unless you have evidence)

Instead, be specific:

• "Our price was 15% higher than winner. We included full-time PM but RFP only required part-time supervision."
• "We didn't address mandatory requirement 3.7 (cybersecurity certification). Evaluation team marked us non-compliant."
• "Our past performance projects were from 2018-2020. Winner had 3 projects from 2023-2024. Our examples were too old."

Specific loss analysis drives improvement. Vague blame doesn't.

5. Tag Consistently

Develop organizational tagging conventions:

Recommended tag categories:

• Outcome reasons: pricing-too-high, missed-requirement, weak-past-performance, strong-incumbent
• Risk level: high-risk, safe-bet, stretch-opportunity
• Strategic importance: strategic-priority, revenue-critical, capability-development
• Competition level: highly-competitive, few-bidders, sole-source
• Opportunity type: new-client, repeat-client, expansion-opportunity

Use consistent tags across records to enable powerful filtering and trend analysis.

6. Attach Reference Material

For wins, attach materials that made you successful:

• Winning technical approach (redact proprietary details if needed)
• Successful pricing strategy
• Effective past performance examples
• Strong proposal cover letter or executive summary

These attachments become a template library for future similar bids.

7. Conduct Timely Debriefs

Schedule debrief meetings within 1 week of outcome announcement:

Win debriefs:

• What differentiated our proposal?
• Were our estimates accurate?
• What surprised us about the evaluation?
• How can we replicate this success?

Loss debriefs:

• Why did we lose (specific reasons)?
• What did winner do better?
• Were our assumptions wrong?
• What would we do differently?

Capture debrief notes in the bid record immediately after the meeting.

8. Link to Capability Profiles

When updating your Company Profile, reference specific bid records as evidence:

• "We claim 5+ years of cloud security experience. Bid records X, Y, Z demonstrate this."
• "We updated our past performance to emphasize recent work. Wins in 2024-2025 now lead our examples."

This creates traceability between claimed capabilities and proven performance.

9. Review Quarterly

Schedule quarterly reviews of your bid records:

What to review:

• Are win rates trending up or down?
• Which types of opportunities have highest win rates?
• Where are you losing most often?
• Are no-bid reasons consistent (revealing capability gaps)?
• Is bid preparation time improving?

Use these reviews to refine bid strategy and capability development priorities.

10. Clean and Maintain Data

Prevent data degradation with periodic maintenance:

Quarterly maintenance:

• Merge duplicate competitors (e.g., "ABC Corp" and "ABC Corporation")
• Update missing outcome data if now available
• Correct obvious errors (e.g., bid amounts with extra zeros)
• Archive very old records (7+ years) to reduce clutter

Annual maintenance:

• Review and update folder structure if needed
• Consolidate or standardize tags
• Export data for backup
• Assess if old records should be archived

Frequently Asked Questions

Next Steps