Structured RFQ & Intake

From purchase request to RFQ, structured at every step.

Key Takeaway

When purchase requests arrive as scattered emails, context gets lost and RFQ quality varies by person. Centralizing intake ensures every sourcing event starts with a complete, traceable record.

The sourcing event begins when someone in your organization needs to buy something. Purchaser captures that request through a centralized channel (email or portal), assigns it to the right buyer, and tracks any clarification before the RFQ is created. Team-level templates ensure the final RFQ is consistent regardless of who creates it.

Your team

• Submits the purchase request, clarifies requirements when asked, defines scope boundaries, and sets the vendor list and submission deadline.

Purchaser

• Captures and logs the request, routes it to the right buyer, tracks clarification, applies team templates, and distributes the RFQ to invited vendors.

Input

• Purchase request (email or portal), specifications, vendor list

Output

• Structured RFQ record linked to the original request, with full intake audit trail

What breaks without this

When purchase requests arrive as emails to individual buyers, context gets lost in forwarding chains. Each buyer drafts their own RFQ from scratch, with different wording and different levels of detail. The result: vendors receive inconsistent requirements and fill in the gaps with their own assumptions.

Vendor Submission Normalization

Heterogeneous submissions aligned to a common evaluation structure.

Key Takeaway

You can't compare bids fairly until they're in the same format. Normalization makes that possible.

Normalization is the process of transforming vendor submissions, which arrive in incompatible formats like PDFs, Excel workbooks, and email attachments, into a common format for comparison. Purchaser extracts and normalizes every submission against the RFQ structure before evaluation begins.

Your team

• Reviews the normalization output, resolves flagged ambiguities, and confirms the submission registry is complete.

Purchaser

• Extracts line items from every submission format, maps vendor line items to RFQ requirements via Smart Mapping, flags gaps and additions against the RFQ baseline, and tracks quote versions through negotiation.

Input

• Vendor submissions (PDF, Excel, email, portal exports)

Output

• Structured comparison: every vendor mapped to the same line-item structure

What breaks without this

Without normalization, comparing submissions means comparing the vendors' organizational logic, not their actual bids. Price differences reflect structural formatting choices, not genuine cost differences.

Technical & Commercial Evaluation

Scope compliance established before pricing enters the evaluation.

Key Takeaway

Review technical scope before price to prevent low bids that exclude required work from anchoring the evaluation.

Technical compliance, whether each vendor's submission actually covers the required scope, is evaluated before commercial pricing is considered. This sequencing prevents price from anchoring the evaluation before scope deviations have been identified. Purchaser surfaces all deviations and flags them for team review.

Your team

• Reviews deviation flags, conducts technical scoring against predefined criteria, makes scope clarification decisions, and applies commercial weighting.

Purchaser

• Generates the structured comparison view, surfaces deviations by line item, produces the evaluation matrix calibrated to the team's criteria.

Input

• Structured comparison, evaluation criteria

Output

• Deviation flag report + structured evaluation matrix with scores

What breaks without this

When pricing enters the room before scope has been established, evaluators anchor on price. Scope gaps get rationalized rather than resolved. The result is a low bid that undercovers the actual scope, a change order waiting to happen.

Portfolio Visibility & Control

Consistent process maintained across simultaneous sourcing events.

Key Takeaway

When every package uses the same process, portfolio-level patterns become visible without manual coordination.

Capital project procurement rarely operates on a single RFQ at a time. Purchaser maintains the same process across every concurrent sourcing event, so the normalization, evaluation, and documentation produced for Package A is consistent with Package B, C, and D running in parallel.

Your team

• Monitors active package status, allocates evaluation resources across concurrent events, coordinates cross-package vendor relationships.

Purchaser

• Applies consistent defaults across all active events, tracks submission status by package, surfaces portfolio-level visibility without manual aggregation.

Input

• Multiple concurrent RFQ packages

Output

• Portfolio status view: all active events in a consistent state

What breaks without this

Without consistency across packages, each procurement event becomes its own improvised process. Portfolio visibility requires manual coordination. Mistakes made in one package are repeated in the next.

Governance & Award Traceability

Complete, auditable record from inquiry through award recommendation.

Key Takeaway

A real audit trail is generated at each stage, not assembled retroactively when someone questions the award.

The award recommendation is supported by a complete, traceable record: the original RFQ, all vendor submissions, the normalization output, the evaluation matrix, and the decision rationale. This record is produced as a natural output of the structured process, not assembled retroactively.

Your team

• Reviews the award recommendation, documents the final decision rationale, obtains required approvals, and issues the purchase order.

Purchaser

• Compiles the complete audit trail from intake through evaluation, produces the award recommendation summary, and packages all documentation for stakeholder review.

Input

• Completed evaluation matrix, decision rationale

Output

• Award recommendation with complete audit trail, from intake to decision

What breaks without this

Governance imposed at award on a process that was ambiguous from intake through evaluation is retrospective documentation, not a real audit trail. It cannot reconstruct the decision with integrity.

What the same sourcing event looks like.

Stage

• Without Purchaser
• With Purchaser Capturing the request
• Purchase requests arrive as emails to individual buyers, forwarded without context. Each buyer drafts their own RFQ from scratch.
• Requests flow through a single channel. Purchaser assigns them, tracks clarification, and applies team templates before the RFQ goes out.

Building the comparison

• An analyst manually reformats each submission into a master spreadsheet, line by line. Hours of work per RFQ, repeated for every event.
• Purchaser extracts and normalizes every submission automatically. The structured comparison is ready before the analyst opens their laptop.

Identifying scope gaps

• Scope gaps are discovered through line-by-line reading. Many go undetected until post-award, when they become change orders.
• Purchaser flags every gap, addition, and deviation by line item before evaluation begins. Nothing reaches the evaluation stage unreviewed.

Running concurrent events

• Each RFQ package follows its own improvised process. Coordination across packages requires manual status tracking and team check-ins.
• Purchaser applies the same structure to every event. Portfolio status is visible in a single view without manual aggregation.

Documenting the award

• Award documentation is assembled after the decision, a reconstruction from memory, emails, and spreadsheets that is difficult to audit.
• The audit trail is produced automatically as a byproduct of the structured process. Every stage is documented at the time it happens.

Five artifacts. One complete audit trail.

Each stage of the sourcing process produces a structured document. Together, they form a traceable chain from the original requirement through the final award — the kind of record that satisfies auditors, clients, and stakeholders without requiring retroactive reconstruction.

1. Intake Record: The original request, routing history, clarifications, and final RFQ: a complete chain from purchase request through vendor distribution.
2. Submission Registry: A complete log of every vendor submission received, with timestamps and format metadata.
3. Structured Comparison: All vendor submissions mapped to the RFQ structure, with scope deviations and assumptions surfaced.
4. Evaluation Report: Structured scoring against predefined criteria, with technical findings separated from commercial review.
5. Award Documentation: The complete audit trail: criteria, scores, rationale, and supporting documentation, in one exportable package.