To review a tender pricing schedule, match each priced item to the delivery commitment it supports: what will be provided, in what quantity, for how long, and under which assumptions. Then resolve differences between the technical response and the pricing documents before approving either. The objective is a consistent offer, not simply a spreadsheet that adds up.
This guide provides an internal review method, not a universal procurement procedure. Instructions differ between countries, buyers and individual opportunities. Use the forms, submission rules and clarification channels specified for your tender. There is no single procurement regime shared by all English-speaking markets.
Start with the right tender pricing schedule
Identify the current pricing template, technical draft, specification and relevant clarification or amendment records. Record their versions and sources. An accurate comparison against an outdated attachment can create false confidence. Keep the buyer's instructions available during the review, especially any rules governing units, optional items or the separation of technical and financial information.
Agree what each document is for. The submitted pricing schedule is not the same as an internal costing model or a margin discussion. Retain working calculations and commercial reasoning in an appropriate internal location. Do not add columns, qualifications or explanatory notes to a required submission form unless the instructions allow them.
Use a copyable reconciliation table
Copy the following table into your internal review document and replace the sample entries with actual references. The four rows are illustrative checks, not statements about a real tender. A row is closed only when the relevant source, decision and updated documents can be identified.
| Item or reference | Technical commitment | Pricing basis | Check or action | Owner and evidence |
|---|---|---|---|---|
| Training | Four on-site workshops | Two remote sessions | Resolve quantity and delivery-mode mismatch | Delivery and pricing leads; source section and decision |
| Support | Twelve months of coverage | Six monthly units | Check period, unit and coverage window | Service lead; schedule and revised line |
| Data migration | Two source systems in scope | One migration activity | Confirm whether the line includes both systems | Technical lead; scope reference and inclusion note |
| Travel | Visits to three locations | Travel treatment unclear | Confirm how visits are covered under the required form | Commercial lead; approved pricing basis |
Use a stable identifier for each issue. Add source section or page references to the first column when applying the table. Where a line correctly covers several deliverables, record why; do not create extra priced items merely to make the documents look symmetrical.
Check meaning before arithmetic
A correct total does not prove that the offer covers the promised work. Read the line description and technical passage together. Ask whether they describe the same output, delivery conditions and responsibility. Particular attention is useful where one contributor writes about an outcome while another estimates activities or time.
- Check units: person-days, sessions, licences, sites and months describe different things. Make the relationship explicit.
- Check quantities and duration: compare repeated activities, mobilisation, delivery and any stated support period.
- Check dependencies: distinguish inputs the team will provide from inputs expected from the buyer or another party.
- Check scope boundaries: keep inclusions, permitted options and unresolved assumptions visible without silently treating them as agreed facts.
Then review calculations, formulas and carried totals within the permitted template. Confirm that the displayed currency and number formats are unambiguous. Refer tax or contractual interpretation questions to the appropriate reviewer; this consistency check does not determine the applicable treatment.
Worked example: four workshops, two priced sessions
Consider a fictional training tender. Its current specification asks for four on-site workshops. The technical response describes those four workshops, but a reused internal estimate still contains two remote sessions. The mismatch affects quantity and delivery mode, so doubling an amount without reviewing the underlying work would not resolve it.
The delivery lead first confirms the requirement against the current source and checks preparation, session duration, location and staffing. The pricing owner then revises the estimate for the confirmed delivery basis and updates the permitted submission fields. The technical author verifies that the narrative, resource plan and schedule still describe the same approach.
Both owners record the source, decision and changed version in the reconciliation table. A reviewer checks the exported files, not just the working documents. If the source is actually ambiguous, the team uses the stated clarification process and records the unresolved decision. Silence from the buyer must not be treated as confirmation.
Close issues with named reviewers
Assign a technical owner and a pricing owner to material discrepancies. Separate “identified”, “decision required”, “updated” and “verified” so that editing a number does not automatically close an issue. Where one correction affects several sections, list them before making changes and check each afterwards.
Before approval, reconcile the final file versions and remove internal review notes from client-facing documents. Follow the tender's instructions if pricing information must remain outside the technical submission. Extend this focused review with the tender response review checklist, and use the document confidentiality guide when deciding which working materials belong in the submitted pack.
Frequently asked questions
Must every technical paragraph have a separate price line?
No. A single line may cover several activities or an overall deliverable. Follow the required pricing structure and keep an internal explanation of coverage. The aim is traceability, not a one-to-one match that changes the buyer's template.
Can AI approve the pricing review?
No. AI can assist with extracting requirements and preparing draft content, but people must verify sources, scope, calculations and approvals. Do not assume that a drafting tool is a pricing calculator or that it detects every inconsistency.
Make the offer tell one consistent story
A useful review ends with resolved differences, clear owners and identifiable final documents. Explore MyWiseDocs to support requirement extraction, response structuring and first-draft preparation. Your specialists retain responsibility for pricing decisions, factual checks and final approval.