01
Ask every offer the same question.
Autodesk’s bill-of-materials documentation distinguishes items, quantities and revisions. Use that logic to agree a reference version before comparing proposals.
Begin with the shared requirement: affected zones, expected functions, retained equipment and deliverables. Every offer should be readable against that baseline. When requirements change, share the same correction with the relevant contacts and request a dated response. Without this step, two totals may describe different projects.
Build a review table with one row per function or deliverable and one column per offer. Record “included”, “optional”, “excluded” or “to confirm”, then the page or response supporting that status. Vague wording remains an open question. The aim is to make differences discussable and traceable, rather than create an automatic score.
02
Rows to compare before the total.
Scroll the table horizontally to compare all three columns.
| Topic | What to align | Expected evidence |
|---|---|---|
| Functions and zones | Covered uses, boundaries and retained equipment. | Explicit response to the brief version. |
| References and quantities | Exact model, unit, accessories and dependencies. | Dated equipment list with alternatives identified. |
| Services | Supply, installation, configuration, testing and user training. | Work description and owner of each step. |
| Software and access | Required licences, term, renewal and account ownership. | Applicable terms and handover arrangements. |
| Documents and support | Plans, results, planned backups and support channel. | Deliverable list and support scope. |
| Commercial presentation | Separate base and options, stated taxes, delivery charges and validity. | Written offer clarifying missing points. |
03
Review in four passes.
Check scope
First identify missing functions, uncovered zones and exclusions. An option needed to meet the requirement must be discussed before an overall comparison. Keep future requests on separate rows so they are not confused with immediate needs.
Check units
Compare matching units: item, pair, batch or length. Request a kit breakdown when accessories are unclear. Do not assume a cable, power supply or licence is included simply because operation requires it.
Check responsibilities
Identify who installs, configures, tests and hands over documents. If several parties participate, ask who verifies interfaces between their scopes. A “commissioning” line is clearer when described through observable work and deliverables.
Request clarifications
Send a numbered list of differences with the offer reference and requirement version. Request a written response for each point. Update the table status and date; an undocumented verbal exchange remains marked for confirmation.
04
Example: two offers for a meeting room.
ILLUSTRATIVE EXAMPLE
Fictional case: the requirement includes a display, content sharing and a remote meeting with two-way voice. Offer A describes equipment and configuration; offer B describes supply only.
Align functions
List the three required functions on separate rows. Check how each proposal provides voice capture and remote playback. A shared display model alone does not make the offers equivalent.
Clarify the missing service
Ask whether B can include configuration, testing and user handover, or whether another team will handle them. Do not add a guessed cost to fill the gap. Wait for a response with a reviewable scope.
Define the observable outcome
Plan a test call with a remote participant and content sharing from the intended computer. Assign an owner and a deliverable to that check. The choice can then account for clarified scope and remaining reservations.
This example gives no real price, model or result. Compatibility and functions must be checked for the proposed references and project conditions.
05
What must remain explicit at selection.
The selected version
Reference the latest reviewed offer, annexes and clarifications. Archive earlier versions without leaving them in the current pack as if still valid. Selected options must be identifiable without reconstructing the whole conversation.
Reservations and dependencies
Keep a short list of remaining confirmations: area access, compatible model, availability or another party’s task. Record the effect of an unfavourable answer and who decides the next step.
Expected deliverables
Specify expected documents, tests and user explanations. Mark non-applicable items rather than leaving blanks. The same list can prepare acceptance without inventing new requirements on the last day.
06
Plan evidence as well as promises.
Fluke Networks highlights retaining test results with cabling documentation. Ask which reports will be delivered and how their identifiers will match the site.
Then apply your project’s own expected-outcome list: demonstrated use, delivered document, transferred access or recorded reservation. A feature list does not prove that the proposed combination works in your configuration. Defining checks before ordering helps teams prepare suitable resources and explain limitations.
07
Common comparison questions.
Is the same brand enough?
No. Check the exact model, accessories, functions and operating conditions. Similar references can serve different requirements.
How do I compare a kit with separate items?
Request the kit’s written contents and align quantities and units. Separate included items from accessories ordered separately.
What does a blank field mean?
Nothing confirmed. Turn it into a question: included, excluded, optional or not applicable? Retain the answer and date.
Can I estimate a missing line myself?
An internal estimate must remain labelled as an assumption. It does not become a supplier commitment. Request a written response to compare confirmed scope.
When is the comparison ready for a decision?
When material differences are explained, responsibilities understood and reservations visible. The decision should name the chosen version and remaining open conditions.
08
Turn a difference into a verifiable answer.
Identify the line and both versions
Example: “Brief V3, reception zone: six points requested; offer B V1: four points listed. Are the other two excluded or grouped?” Attach only the relevant extract. A general question such as “is your offer complete?” hides the actual difference.
Ask for an explicit consequence
Ask which exact reference, quantity, accessories and document change, then the effect on services and proposed timing. If a model is replaced, ask what preserves the required function and what changes. A family datasheet alone does not prove variant equivalence.
Reconcile the corrected offer
When the answer arrives, compare the new version with the question, check that the old option has not been added to its replacement, and retain the answer with the decision. An email can clarify a point without updating the PDF: confirm which version will govern before continuing with the team.
Technical sources
External reading references. These documents explain principles; they do not certify catalogue products or their combination.
- Bills of Materials — Item references, quantities and revisionsAutodesk · Sources consulted on
- Document Cabling Certification with LinkWare PC and LinkWareLiveFluke Networks · Sources consulted on