A specifier's annotated guide to reading returned bid leveling schedules: which lines hide a changed scope, and which evidence to demand.

Publicerad den: sep 30, 2024

Bid Leveling: A Smart Lock Specifier Guide

Bid Leveling: A Smart Lock Specifier Guide

This piece hands over bid leveling specifier guide in the form a specifier can actually use, with the evidence list attached. Bid leveling is usually described as a meeting. Three bids come in, the panel puts them onto one basis, and a recommendation goes out. From the consultant's chair it is a reading exercise before it is a meeting. Three schedules come back, and the first question is not which one reads best but what each one was levelled onto. A sheet can be levelled perfectly onto a basis that is not yours, and it will still look complete.

Direct answer. To put it plainly: bid leveling specifier guide has to hold for bid leveling specifier guide. bid-leveling has to hold at the same time. The sections below describe the order bid leveling specifier guide is settled in. A bid leveling specifier guide is a working pack for the people who write the requirement. bid leveling specifier guide is the first section handed over. Every bid leveling specifier guide template comes with it.

  • Frame the requirement — use a template that names the physical constraints in bid leveling specifier guide
  • Catalogue the evidence — attach the conformity file for the SKU behind bid-leveling
  • Deliver it in one request — issue one complete package per door class, not one per query
  • For bid leveling specifier guide, the order below is fixed and bid leveling is the reference point.

This guide is written for the door hardware consultant who issued the basis sheet and now has to read three returns against it. It is a transcript, because the work is not a checklist of items to tick. It is a sequence of decisions about what a line in a return actually claims, what it decides once accepted, and what has to arrive before the line can be treated as answered.

Two boundaries hold throughout. No commercial figure appears anywhere in this guide; every number a levelling sheet would carry belongs to a written offer for a named configuration, and it resolves through the request a quote route. And where a consequence turns on the law of the place the contract will be signed, the question is handed to counsel under a CONFIRM-WITH-LOCAL-LEGAL line rather than answered here. Nothing in this guide is legal advice.

The exchange below is illustrative. It assembles commonly-reported reviewer experience into a plausible reading session between two roles. It is not a record of any real meeting, project, company, supplier, client or authority, and the figures a real session would contain have been deliberately left out.

Two voices and what each turn

VoiceStands forOwnsDoes not own
ConsultantThe door hardware consultant who issued the basis sheet and owns the specificationWhat the requirement was, which doors it applied to, and what a return must answerWhether the document behind a return covers the variant that was quoted
VerifierThe independent reader who re-reads the returns against the doors, the standards and the evidence, then writes the mark-upWhether each line is a restatement, a deviation or an omission, and what closes itWhether the panel should compare the returns in this round at all

Three notations recur below. An annotation names the code a turn produces and states what the code means in practice. An evidence line names the document that closes a gap and the party who must issue it. A confirmation line hands a jurisdictional question to the authority that owns it. The codes themselves are tabulated once the first two turns have earned them. Every commercial claim here has to be checked against the smart door locks.

Turn 1 — Three returns, three possible bases

Consultant: The three levelled schedules came back this morning. One is four pages, one is nine, one is four pages with an appendix. Which do I open first?

Verifier: None of them. Open the basis sheet you issued, put the three returns beside it, and answer one question for each return: what did this bidder treat as the object being compared?

Consultant: I assumed levelling meant they restated onto my basis.

Verifier: Levelling means that somebody restated something onto some basis. The basis is the document that states what is being compared and what has been left out of the comparison. If your sheet says one door type, one scope of supply, one evidence set and one commercial basis, and a bidder returns their standing schedule, they have levelled onto their own basis. That return cannot be compared with anything, because you cannot see what they normalised away.

Consultant: So the defect is invisible in the table itself.

Verifier: It is invisible in the table and visible in the length. Four pages against nine is not a reliable signal of a thorough bidder or a careless one. It is a signal that one bidder listed fewer things, and until you know which things, the difference is unreadable.

Annotation — M1, basis drift. A return is a conforming response only if it is levelled onto the issued basis. Record, for each bidder, the basis it used, the line count of the issued sheet, the line count of the return, and the basis lines that received no answer at all.

Evidence to demand. The bidder's own statement of the basis it levelled onto, plus a completed copy of the issued basis sheet with every line answered — offered, substituted, or answered with a nil return. A return that offers its own schedule is not a conforming return and cannot be made conforming by asking again.

CONFIRM-WITH-LOCAL-LEGAL — whether a return prepared on a basis other than the issued one may be admitted at all, and what follows for a bidder who did not adopt the issued basis, depends on the tender rules and the governing law. Confirm with counsel in the jurisdiction where the contract will be signed, before the panel rules on admissibility.

Consultant: And if one bidder plainly levelled onto my basis, one partly did, and one used their own?

Verifier: Then you do not have a comparison. You have three packages of differing structure, and the panel may still choose between them — but the recommendation has to say that the choice was made between differently structured packages rather than between equal ones. That disclosure is the thing that protects the decision when somebody asks, months later, what was actually being compared.

Turn 2 — Restatement, deviation, and the line that is simply gone

Consultant: Suppose the basis is right. Line 14 asks for the lock together with a named evidence set. One bidder writes "as specified". Another writes "equivalent, see appendix". Another writes nothing at all.

Verifier: Three different acts performed under one line. The first is a restatement: the same object described in the bidder's own language. The second is a deviation: a different object, which the bidder has flagged as a substitution. The third is an omission: the line has vanished from the return and the requirement has gone with it.

Consultant: "As specified" and "equivalent" sound like the same answer.

Verifier: They are close to opposites. "As specified" claims identity and gives you nothing to check. "Equivalent" concedes difference and obliges the bidder to show you why the substitute is acceptable. The first creates work; the second hands work back with a document attached. The third does neither.

Consultant: The missing line is at least visible.

Verifier: It is not. A missing line in a comparison table looks exactly like a line that was covered. Nothing in the sheet says the requirement was dropped, so nothing in the sheet says the requirement was dropped, and the first person who notices may be the approver at submittal stage or the installer holding a lock that cannot do what the specification requires.

Annotation — M2, D1 and O1. M2 is a restatement: same object, different description, no change to the compared product. D1 is a deviation: a genuinely different object, which must stay visible in the comparison rather than being absorbed into it. O1 is an omission: an issued basis line with no answer, which must be counted against the return by line number before the sheet is compared at all.

Consultant: So the omissions are counted before anyone looks at what the bidders said.

Verifier: They are counted from the basis, not from the returns. Take the issued sheet and mark every line. Then take each return in turn and mark which issued lines it answered. The gaps are the finding. A page of narrative about how closely the bidder understood your specification tells you nothing about the three lines that were never answered at all.

The annotation codes this transcript uses

The codes are a marking convention, not a scoring system. Their purpose is to make a mark-up legible to somebody who was not in the room: the panel, the client, or the person who inherits the file after handover.

CodeWhat the line presents asWhat it actually decidesThe question that closes it
M1A schedule in the bidder's own layoutWhether a comparison is possible at allWhich basis was this return levelled onto, and where does it diverge from the issued one
M2The same requirement in different wordsNothing; it removes description noise from the sheetDo both descriptions name the same object, in the same configuration
D1The same line with a stated substitutionWhether two bids are the same product or twoWhat exactly differs, in what respect, and who accepts the substitution
O1Nothing at allWhether the requirement survived the returnWhich issued line is unanswered, and what document closes it
S1A standard offered as general proofWhich question the evidence actually answersWhich document family answers this question, and which family the offer used
E1"Complies with X"What you are actually relying onWhich of the four documents it is, and who holds it
V1A document attached to a lineWhether that document covers what you are buyingWhich variant the document's scope names
F1A brochure page or a self-declarationWhether anything has been tested at allWhere the third-party document with a scope and a number sits
X1A market-access claimWhich clearance route your shipment depends onWhich authority signs for which market, and who carries the obligation
D2An offer for a door familyWhether the schedule and the offer describe the same doorsWhich door types in the marked schedule this line covers
R1A silence in the recurring columnWho carries the ongoing work and costWhat is licensed, hosted, retrained and renewed, and by whom
W1A sentence about a boundaryWhere responsibility for a failure stopsWhich party is answerable once the door is installed and handed over

A mark-up that carries codes but no document requests is an opinion. Every code above pairs with an evidence request, and the pairing is the output. The Smart Lock Factory Sample Testing Guide is the point where several of these requests stop being paperwork and start being a physical check.

flowchart LR
    A["Returned sheet · issued basis"] --> B["Basis check · M1"]
    B --> C["Line grading · M2 D1 O1"]
    C --> D["Scope check · S1"]
    D --> E["Evidence check · E1 V1 F1"]
    E --> F["Difference register · no figures"]
    F --> G["Graded sheet and evidence request list"]

Turn 3 — The sentence that collapsed four different documents

Consultant: Line 14 came back with a file attached. The description says the product is "certified to the electromechanical lock standard".

Verifier: Stop at the word "certified", because the sentence has told you four different things at once. Ask which document it actually is. A test report says somebody tested a sample. A certificate says a body attests conformity, and it carries a scope and a validity. A declaration of conformity is the manufacturer's or importer's own legal claim, signed and dated. Marking is the symbol printed on the product or its label. "Certified" as a phrase collapses all four, and the four carry very different weight when a question is asked later.

Consultant: What am I actually being offered here?

Verifier: That depends on the file, not the sentence. Then two more questions sit underneath the first. Does the document's scope name the exact variant in the line, or a sibling variant, or a family? And does the standard it names cover the object you are buying at all? EN 14846 covers locks and latches that are electromechanically operated. EN 12209 covers mechanically operated locks, latches and locking plates. A battery-driven smart lock belongs to the first family. A bidder who returns mechanical evidence against an electromechanical requirement has not answered the question, however clean the paperwork looks.

Consultant: And if the mark is on the box while the file is in the folder?

Verifier: Neither one proves the other. The marking tells you the product was presented into a market under some regime. The file tells you a body tested or attested something. The link between them is a third document: the manufacturer's or importer's declaration, naming the variant and referencing the document it relies on. Without that link, the evidence in your folder is about a product, and the product on the pallet is a different one.

Annotation — E1, V1 and F1. E1 is a conformity sentence with no document type behind it. V1 is a document whose scope names a different variant from the one quoted. F1 is a facade: a marketing image or a self-declaration offered where a third-party document is expected. The request that closes all three is the same request in three different forms. For bid leveling specifier guide, the position on this ladder is what the purchase decision turns on.

Evidence to demand. The certificate, with its scope, its validity and its number; the signed declaration that names the variant fitted and references that certificate; confirmation that the quoted variant matches the scope; and, where no certificate exists for that variant, the test report on a described sample with the gap recorded rather than glossed.

There is a ladder here, and it is worth naming because the failure mode is predictable. A marketing image sits at the bottom. Above it sits a self-declared declaration. Above that, a test report on a sample. Above that, a third-party certificate carrying a scope and a number. Above that, a certificate covering the exact variant you are buying. At the top sits the production-control evidence that keeps a certificate valid after the sample passed. For bid leveling specifier guide, the position on this ladder is what the purchase decision turns on.

RungWhat you are holdingWhat it will not survive
marketing imageA page with a logo and a badgeAny question asked in writing
Self-declared declarationA supplier's own claim, signed and datedAn approval route that expects a third-party body
self-declared DoCA report describing one sampleA question about the variant you were actually quoted
test report on a sampleA body's attestation, bounded by its scopeA question about a variant outside that scope
third-party certificate with scope and numberThe document matched to the object in the lineNothing structural; check validity and production control
certificate for the exact SKU/variant being purchasedThe audit trail that keeps the document true after the sampleA change of supplier, factory or sub-tier without notice

The recurring commercial failure is buying at the second or third rung and discovering at installation that nothing above them exists. The What Certifications Should I Request From a Smart Lock Supplier? note sets out that request in a form you can send; the point here is narrower, which is that a levelling sheet is where the low rung enters and gets normalised into a comparison as if it were the high one.

Turn 4 — One document family asked to answer another's question

Consultant: There is a line about the fire doors. The bidder has attached the fire test for the door assembly.

Verifier: That is a document about an assembly. Fire-resistance testing works on the door or shutter assembly with its hardware fitted, so it cannot be reduced to a certificate for the lock. It is good evidence for the door set and no evidence at all for the lock as a product. A levelling sheet that uses it as the lock's conformity line has made a scope substitution, and the substitution is invisible because the document looks impressive.

Consultant: Where does that leave an electronic lock on a door held open during the day?

Verifier: You have to name which function you are asking about. A standard written for electrically controlled hold-open on fire and smoke door assemblies carries mains-power expectations and an interface to fire detection inside its own scope, and a battery-only arrangement does not fall inside it automatically. That is a design decision, taken before the lock is chosen, not a clause decision taken after the returns are in.

Consultant: And the radio and the adaptor?

Verifier: Separate families, separate evidence. A lock performance standard does not speak to radio, and a radio authorisation does not speak to the mechanical locking function. The same separation applies to electrical safety, where a mains-connected gateway or charging adaptor sits inside regimes a battery-powered lock never enters. Most poor procurement comes from asking one family to answer another's question, and a levelling sheet is exactly where that error gets written down in a tidy row and then copied into the specification.

Consultant: Is there a way to see this from the question side rather than the document side?

Verifier: Yes. Take the requirement first and let it choose the family. A standard describes what the standard tests, and it stops there; it never speaks for a factory and it never speaks for the product in your hand. Each question has one family that answers it properly.

graph LR
    n1["Locking function on the leaf"] --> e1["Lock performance standard, electromechanical or mechanical"]
    n1 --> e2["Radio and electromagnetic regime"]
    n1 --> e3["Electrical safety for the adaptor"]
    n2["Door on a protected route"] --> e4["Door assembly fire test, hardware fitted"]
    n2 --> e5["Electrically controlled hold-open standard"]
    n3["Escape opening"] --> e6["Escape device standard for the lever"]
    n3 --> e7["Escape device standard for the panic bar"]
    n4["Accessible opening"] --> e8["Accessibility standard for operable parts"]
    n5["Reader to controller"] --> e9["Interface protocol specification"]

Annotation — S1, scope substitution. A line answered with a document from the wrong family. The mark-up names the family the offer used and the family the question needed, so the panel can see that the return did not answer the question rather than that the return answered it badly.

Evidence to demand. One line per family, each naming its own document type, its holder and the object it covers. The Smart Lock OEM Technical Specification note is useful here because it forces the object to be described before any evidence is attached to it.

Turn 5 — The line that describes a door you do

Consultant: The returns are priced by door type. Our schedule has five types. One bidder returned four lines, one of which reads "standard commercial door".

Verifier: "Standard commercial door" is a category error unless you have defined the category. Your schedule is the population, and the population is what the return has to cover. An escape opening, a fire door, an accessible opening, a staff-only door and a public retail door are five different requirement sets. When a return collapses them into one line, you have a deviation and a scope loss in the same line, and the loss is the dangerous half because the door you care about most is the one that disappeared into the generic description.

Consultant: What am I looking for on an accessible opening?

Verifier: The operable-part requirements in the published accessibility standard: one mechanism, the actuation force the standard sets, the closing speed and the reach ranges. Two things matter. First, these are properties of the assembly and of the operating force of the hardware on that leaf, so a handle that needs two deliberate movements to retract the latch does not deliver them. Second, they are a per-door question, so the schedule has to say which openings they apply to, otherwise the return will price them generically and nobody will notice.

Consultant: And the escape doors?

Verifier: Egress and locking arrangements are governed by the life safety code for the occupancy, and the escape device on the leaf is a separate question from the lock that secures it. A lever-operated escape device and a horizontally actuated panic bar are different objects under different standards, and a return that offers one device type across every escape opening has quietly answered a question you did not ask. On a fire door, the hardware is assessed as part of the assembly under the installation and maintenance rules that govern fire door hardware, which is why a lock change after the fire strategy is settled can reopen an assembly question that was considered closed.

Consultant: So I need the schedule marked, not just supplied.

Verifier: Marked by function rather than by location: escape, fire, accessible, staff-only, public. Then every line of every return is checked against that marked schedule, and a line naming a door type you do not have is a deviation worth a question. Sometimes that question is worth asking for a different reason: it can reveal that the bidder read the drawings and found a door type that you forgot to schedule.

Door in the scheduleWhat the requirement turns onThe evidence family to ask forWhat the return must name
Escape openingEgress and locking arrangements for the occupancy, plus the escape device type on the leafThe escape device standard matching the device actually fittedThe device type, and whether the lock changes how the door releases
Fire or smoke doorThe assembly with its hardware fitted, and the maintenance regime that follows itThe assembly test and the assembly's own documentationThe assembly, never the lock alone
Held-open doorWhether the hold-open arrangement is electrically controlled and how it is poweredThe hold-open standard, plus the proposed power arrangementThe power arrangement and the release interface
Accessible openingOperable-part requirements of the published accessibility standardAccessibility evidence for the operable partsThe operating force and the number of movements required
Staff-only and public openingKey control, credential handling and audit expectationsThe credential standard and the position on event-log retentionThe credential family and who administers it

Evidence to demand. The door schedule marked by function; the site survey that produced it, in the form set out in the Smart Lock Retrofit Site Survey and the Hotel Smart Lock Site Survey; the measurement data for every opening where an existing case is reused, in the format of the Smart Lock Door Measurement Guide; the fire strategy; the escape strategy; and the accessible route drawings.

Turn 6 — The credential line, the interface line

Consultant: Every return compares "app and card" across all doors. That is the wording in the brochure.

Verifier: "App and card" is a marketing phrase and it hides two separate decisions. The first is the credential. A short-range proximity card family and a vicinity-type card family are different radio topologies with different ranges, and the requirement should name the family and the standard the reader implements rather than the words card and app. The second is the interface between reader and controller. One legacy wiring convention carries no encryption and no device addressing, while a specified open protocol carries both, and the choice decides how much of the door perimeter you can retrofit and how much you can read off the bus when it misbehaves.

Consultant: Does the software belong in the basis sheet at all?

Verifier: It has to, because the recurring work is never levelled if you do not ask for it. Ask what is hosted, where the data sits, who administers the credentials, what is retained and who may read it. Door event logs that record who opened which door and when are personal data, so retention, hosting location, processor arrangements and deletion terms belong in the basis as items. Left out, every bidder treats them as free, and the cost of the assumption arrives later in a different budget, owned by a different department.

Consultant: Some returns name ecosystems.

Verifier: Treat every ecosystem name in a return as unproven until it appears in the dated product documentation for the exact SKU you are buying, and confirm on the product page for the specific SKU. The short list of names that appear on every brochure is not a list of standards, certificates or test results, and none of them survives being asked to name the model, the variant and the platform version in writing. If the supplier will not write it down, the line stays open in the mark-up.

Annotation — R1 and E1 applied to the recurring column. R1 is a silence where a recurring item should have been priced: administration, hosting, renewal, retraining, replacement of a credential stock. E1 is a conformity sentence attached to a platform rather than to a document. The Smart Lock Credential Security note covers the credential side in the depth it deserves.

Turn 7 — The battery, the adaptor and the paperwork

Consultant: One return has a battery line and a separate charging adaptor line, and the adaptor is priced on its own.

Verifier: Good, because they belong to different regimes and that is exactly why they must not be levelled into a single hardware line. A cell inside a device is covered by the battery standards, and the transport rules are what a freight forwarder asks to see before accepting a lithium-containing shipment. A mains-connected adaptor sits inside electrical safety regimes that the battery lock never enters. One of the two decides whether the goods clear the forwarder's acceptance desk; the other decides whether the adaptor is safe to plug into a socket in a guest room.

Consultant: And the market-access paperwork?

Verifier: That is a per-market and per-shipment question, and in several markets the obligation sits with the importer rather than the factory. India is the sharpest illustration, where product registration and wireless equipment approval are frequently the importer's obligation to complete. Australia and New Zealand separate radio and electromagnetic obligations from a separate state-based electrical safety approval, so a charging adaptor can be inside a regime while the lock is outside it. The Gulf routes run through certificate-of-conformity schemes whose listed products change over time, so whether a given SKU falls inside a listed regime is a per-product check. Write each route as a named document, a named holder and a named jurisdiction, then ask which party is responsible for it.

Consultant: What about the environmental claims?

Verifier: Ingress protection and mechanical impact codes are two-part numbers that buyers quote freely and suppliers over-claim, so ask for the test method and the description of the tested sample. An operating temperature range is usually a statement about which environmental test methods were run, not a promise about every site. A corrosion claim normally rests on a neutral salt spray test, and the useful question is which standard and which exposure cycle, because two laboratories can produce two different-sounding numbers from the same product.

Annotation — X1. A line whose claim is about market access rather than about the product. The mark-up records the jurisdiction, the route, the document expected and the party responsible. A line that says the goods "come with approval" is an omission of all four.

Evidence to demand. The transport test summary for the lithium cell; the electrical safety document for the adaptor; the route-specific market paperwork, with the holder named; the ingress and impact codes with their test method and tested sample description. The Smart Lock Factory Audit China note is where the production-control rung of the evidence ladder gets checked in person, on the factory floor rather than in a file.

Turn 8 — The register that names a difference without pricing it

Consultant: Now the difficult part. Three returns that are not comparable. How do I write the comparison without an arithmetic column?

Verifier: You write it as a register of what the differences are about, and you keep the arithmetic out of the comparison altogether. The temptation is to normalise the scope lines into a single column so the panel can read one number. That is the moment the evaluation stops being auditable, because a later reader cannot see what was normalised and you cannot reconstruct it. A difference register names the nature of each difference, cites the line it came from, and states what would resolve it. The figure behind each difference is settled in a written offer for the named configuration, quantity band and delivery term, which is where figures belong.

Register entryWhat it recordsThe question it leaves open
Basis noteWhich basis each return was levelled onto, and where it diverges from the issued oneWhether the panel may compare the returns in this round
Deviation noteThe line where the bidder substituted, in the bidder's own wordingWho accepts the substitution, and in which document it is recorded
Omission noteThe issued line that received no answer, named by its numberWhat evidence closes it, and by when it must exist
Scope noteThe line answered from the wrong document familyWhich family answers the question
Evidence noteThe line whose document type or variant is unprovenWhich document closes the gap
Recurring noteThe recurring column nobody pricedWhat is licensed, hosted, retrained and renewed, and by whom
Boundary noteWhere responsibility for a door stopsWhich party carries the failure once installed
Market noteThe clearance route a shipment depends onWhich authority signs, and in which jurisdiction

Consultant: So the panel reads a register of differences and no difference amounts at all?

Verifier: The panel reads a register that states, for each difference, what kind of difference it is and what would close it. The amounts come from the offers, which are written against a named configuration and a named delivery term rather than against whatever the panel inferred from a table. That is the whole discipline: the comparison says what is being compared and what is not comparable yet, and the offer says what it costs.

Turn 9 — The clarification that arrives after the panel

Consultant: One bidder sent a note this afternoon. It says an earlier line was a typing slip and the product is the other one.

Verifier: That is not a clarification. It is a change to the compared object, and the rule that decides it was written before the returns came in, or it does not exist. If the basis sheet allowed clarifications inside a stated window, this is one, and it must be handled identically for every bidder inside that window. If the window has closed, it is a change, and a change accepted for one bidder re-opens the comparison for everyone or is refused for everyone. What must not happen is acceptance in private, because the predictable next development is a second bidder learning of the same opening.

Consultant: And if two bidders then produce different documents for the same line?

Verifier: Then the sheet has done its job. Two documents for one line means the line was never unambiguous, and what you have learned is something about your own basis, not only about the bidders.

Annotation — version control. Every return carries a version and a date, every clarification carries both as well, and the graded sheet records which version of which document was read. Without that, the mark-up describes a document set nobody will ever be able to reconstruct.

CONFIRM-WITH-LOCAL-LEGAL — whether a clarification may be admitted after the stated window closed, at what point the offer crystallises for the purposes of the contract, and what follows if a change is later alleged to have been admitted improperly are contract questions governed by the law of the place the contract is signed. Confirm with counsel rather than relying on a general clause in the basis sheet.

The handover: what the consultant leaves with the panel

The mark-up is finished when it is a pack rather than a set of notes, and the pack has five parts.

  1. The basis statement, dated and versioned, with the marked door schedule it was built from, so that every later reader can reconstruct what was asked.
  2. The graded sheet: every issued line coded, with the evidence status and the open question recorded beside it, and the omissions counted from the basis rather than inferred from the returns.
  3. The difference register, naming the nature of each difference and the evidence that would resolve it, with no commercial figures anywhere in it.
  4. The evidence request list, addressed, with a named party against each item and the document type required.
  5. A short statement of what could not be normalised, which is therefore not compared, and which is therefore a decision the panel is taking on different grounds.

Two of these are often merged into one spreadsheet, and they should not be. The basis is what was asked for, the graded sheet is what came back, and the register is what the two do not share. A merged sheet cannot show which of the three a reader is looking at, and the register in particular is the document that survives a challenge to the award.

The working formats behind this pack are published separately and are worth pairing with it: the Bid Leveling: Reviewer Checklist covers the review pass itself, the Bid Leveling: Documents a Specifier Should Demand list covers what to ask for once the codes have told you where to look, and the Bid Leveling: Template Language for a Specification note covers the drafting of the basis sheet that all of this depends on. The vocabulary used here is set out in the Smart Lock Glossary: Bid Leveling Definition for B2b Buyers, and the treatment of where the risk of a levelled comparison ends up belongs with Bid Leveling: Cost and Risk Consequences.

Four questions that outlive the award

What is still valid at installation? A certificate carries a validity and a scope, and the production-control evidence that keeps it true is the rung most often missing. Between the award and the installation, a factory may change, a sub-tier may change, a firmware version may change. The graded sheet should say, for every evidence line, what would have to be re-checked and who is responsible for re-checking it.

Which line of the sheet becomes a submittal requirement? Every coded line that survives the comparison becomes an item on the submittal checklist, with the document type, the holder and the object it must cover. The Smart Lock Procurement Checklist for B2B Buyers note is a reasonable starting shape, and the Smart Lock System Integrator Procurement Guide covers the handover to the party who will actually run the doors.

What happens when the variant changes? A change notification that reaches the finished product but not the part is a notification that arrives too late, because parts change quietly. The clause should reach the type designation of the cylinder, the reader, the cell and the firmware, and should say what the supplier must do when one of them changes.

Which unresolved item stays open until handover? Keep the omission notes and the open questions as a live list with an owner and a date, and do not let the award close them. An unresolved line at the panel stage is a conversation; the same line unresolved at submittal stage is a substitution, and a substitution at handover is a dispute.

To run this method against a factory that publishes its own configuration, send the configuration through the request a quote route, where the offer is written against the named model, variant, quantity band and delivery term rather than against a summary table. A return that cannot be answered in those terms is usually a return that was never levelled onto your basis in the first place.

None of this is legal advice. It is a method for reading a returned schedule honestly, and the consequences that follow from it in your jurisdiction belong with counsel.

Din kundvagn
Din upplevelse på denna webbplats förbättras om du tillåter cookies. Cookiepolicy
Chat on WhatsApp