Every RFP workflow run creates a Workbook — a structured, column-based data record that captures every requirement, every generated response, pricing line items, and compliance status. The Workbook is the live data layer under your proposal. It drives generation, tracks review, and exports to templates.
When a workflow run processes an incoming RFP, it creates two artifacts: a draft document (the proposal text) and a Workbook (the structured data that underlies it). The Workbook is not just a log — it is the source of truth for the entire response lifecycle, from requirement extraction through final delivery and win/loss tracking.
Think of the Workbook as the spreadsheet your team would build manually to manage a complex RFP response — requirement tracking, response drafts, pricing schedule, compliance status — except it's auto-populated by the workflow, live-updated by the AI blocks, and directly drives document generation. It replaces the 40-tab Excel workbook that every proposal manager secretly maintains.
One Workbook per RFP run. Each time a new RFP is processed through the workflow, a new Workbook is created. The Workbook is linked to the workflow run, the generated document, the CRM opportunity (if connected), and the knowledgebase entry created after submission.
The Workbook has a fixed set of system columns populated by the workflow engine, plus configurable custom columns your team can add for internal tracking. System columns are auto-populated; custom columns are for manual entry or calculated fields.
Sequential identifier (REQ-001, REQ-002...) assigned during extraction. Used as the primary key for cross-references between sheets.
Verbatim requirement text extracted from the RFP document. Never paraphrased — the exact language from the source document for legal accuracy.
The RFP section number and heading where the requirement appears (e.g., "3.2.1 — Contractor Qualifications"). Enables quick cross-reference with the source document during review.
Classified as: mandatory (shall/must/will language), preferred (should/encouraged language), or informational (background context, no response required).
1–5 score derived from the RFP's evaluation criteria language. Requirements in sections marked "heavily weighted" or with high point values in the evaluation rubric receive higher scores.
IDs of other requirements that are interdependent. Helps reviewers understand groupings — for example, three separate requirements that are all addressed by the same technical solution.
The AI-drafted response text for each requirement. Linked to the requirement by ID. Appears as a section in the proposal document and as a row in this sheet simultaneously.
The knowledgebase chunks that were used as source material for this response. Displays the document name, section, and relevance score. Enables reviewers to verify the source and assess AI synthesis quality.
0.0–1.0 score representing the AI's confidence in the response quality. Based on knowledgebase match score and generation model self-assessment. Scores below 0.75 are highlighted for priority reviewer attention.
Set by the human reviewer: approved, edited, needs-rewrite, flagged. The workflow gate requires all mandatory requirements to have a non-null review status before approving the proposal for delivery.
Free-text notes from the reviewer. Notes on needs-rewrite or flagged responses are required before the gate can be passed. These notes feed back into workflow improvement recommendations.
The section and page number in the generated proposal document where this response appears. Keeps the Workbook and proposal document synchronized — editing the Workbook row updates the proposal section.
Beyond requirements and responses, every RFP Workbook includes dedicated sheets for pricing data and compliance tracking — the two areas where gaps are most costly.
| Column | Source | Description |
|---|---|---|
| Line Item ID | Auto | Maps to requirement or scope item |
| Description | Auto (CPQ) | Product/service name from CPQ catalog |
| Unit | Auto (CPQ) | UOM from CPQ line item |
| Quantity | Auto / Manual | From extracted scope or manual entry |
| Unit Price | Auto (CPQ) | Live price at generation time |
| Extended Price | Auto | Quantity × Unit Price, calculated |
| Discount % | Auto (CPQ) | Applied discount from CPQ rules |
| Net Price | Auto | After discount, before tax |
| Pricing Status | Auto / Manual | complete / needs-review / manual-required |
| Reviewer Approved | Manual | Checkbox — required before gate passes |
The pricing sheet is directly linked to the proposal's pricing exhibit. Any change in the Workbook updates the proposal document in real time during the review phase.
The compliance matrix is a purpose-built view of the Workbook that maps every mandatory requirement to its response location. It is auto-generated and can be included in the proposal as a compliance exhibit — a standard requirement for government RFPs.
| Column | Source |
|---|---|
| Requirement ID | Auto — from requirements sheet |
| RFP Section | Auto — source reference |
| Requirement Summary | Auto — AI-condensed one-liner |
| Compliance Status | Auto — Compliant / Partial / Exception |
| Response Location | Auto — proposal section reference |
| Supporting Documents | Auto — linked compliance docs |
| Exception Notes | Manual — for partial compliance |
Gap detection: Any mandatory requirement without a response is highlighted in red. The human gate cannot be passed while red rows remain — this enforces 100% coverage before submission.
The Workbook is not a standalone artifact — it is the data layer that drives the proposal document. Three export modes connect the Workbook to your final output format:
During the review phase, the Workbook and the proposal document are bidirectionally linked. Edit the response text in the Workbook — the proposal updates. Edit directly in the document — the Workbook row updates. No manual sync step. No version drift.
After reviewer approval, the Workbook data is merged into your Word or PDF proposal template via merge field mapping. Workbook column values populate template variables (e.g., {{pricing.total_value}}, {{rfp.submission_deadline}}). Output is a final, formatted proposal document.
Export any Workbook sheet to Excel or CSV for integration with downstream systems — CRM opportunity updates, contract administration systems, or compliance reporting tools. The compliance matrix exports directly to the standard government-contract compliance exhibit format.
When Salesforce (or another CRM) is connected, the RFP Workbook is a two-way data source:
Every Workbook maintains a complete change history. For regulated industries and government contracting, this audit capability is essential for demonstrating that the proposal was reviewed and approved by a qualified person — not just generated and shipped.
The audit log is exportable as a PDF attestation document — useful for submission packages that require documentation of the proposal preparation process.
The Workbook lifecycle doesn't end at proposal delivery. When you receive notification of the outcome, record it in the Workbook's Outcome field. This single action triggers three downstream effects:
Winning proposals are automatically added to the knowledgebase, tagged with the outcome and relevant metadata. Future RFPs in the same industry and scope type will retrieve this content.
Win/loss outcomes update the classification model's training data. Over time, the scoring block learns which opportunity characteristics correlate with wins — improving the accuracy of future bid/no-bid recommendations.
The linked Salesforce (or HubSpot) opportunity is updated with the outcome, proposal value submitted, and a link to the full Workbook. Your pipeline reporting automatically reflects the proposal cycle data.