Bid leveling coordination: the shared register, the clause types that close a gap, and the questions that unblock an award.

Yayınlandı: Nis 10, 2025

Bid Leveling: Coordination Between Architect and Supplier

Bid Leveling: Coordination Between Architect and Supplier

Bid leveling is the stage where a design team's specification and a supplier's response are finally read against each other. It is also the stage where coordination between the architect and the supplier either works or quietly fails, and the working has far more to do with shared method than with anybody's technical depth.

Direct answer. To put it plainly: bid leveling coordination has to hold for bid leveling coordination. bid-leveling has to hold at the same time. The sections below describe the order bid leveling coordination is settled in. A bid leveling coordination supplies the template, the evidence list and the deciding questions. bid leveling coordination is where the bid leveling coordination pack is applied.

  • Frame the requirement — use a template that names the physical constraints in bid leveling coordination
  • 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
  • In bid leveling coordination, this sequence is what bid leveling is checked against.

The reason is structural. One party arrives holding the design intent: a door schedule, a set of clauses, an approval route, and a building that will be inspected in its finished state. The other party arrives holding product reality: what the factory can actually build, what has been tested on which sample, what paperwork exists, and what a destination market will accept at the border and on site. Each side knows things the other does not. Neither side, by default, has anywhere to put what it knows so the other can see it.

That somewhere is the whole subject of this article. Bid leveling coordination is the work of building one shared working surface during the response window and keeping it current while answers arrive. When that surface exists, the comparison at the end is between two responses against the same issued requirement. When it does not, the comparison is between two documents describing different buildings, and the differences get settled on site by people who were not in the room.

Two parties holding different halves of the truth

The coordination problem is usually described as a communication problem, and it is not one. Communication implies two people with the same information who fail to share it. In a bid leveling window the two sides hold systematically different information, and each side's behaviour is rational given what it holds. That makes the failure structural rather than personal, and structural failures need structural remedies.

An architect is optimising for a building that will be signed off. A hardware consultant is optimising for a clause set that can be defended in a substitution submittal. A supplier is optimising for a commercial outcome and for a defensible position later if the buyer asks for something the catalogue does not cover. A main contractor, often holding the door schedule rather than the design team, is optimising for a programme that has already been fixed. Each objective is rational, and each pulls in a slightly different direction on any given clause.

Question in the windowWhat the design side is holdingWhat the supplier side is holdingWhere the two normally diverge
Which door does this coverThe schedule revision, the opening type, the locationThe product family and the configuration optionsThe supplier answers for a product; the schedule describes a building
What does the clause requireThe intent, the reason the clause existsThe capability and the limits of what can be builtIntent is written as a function, capability is written as a feature list
What proves itThe evidence type and the rung the project needsThe evidence that exists for some sample or variantEvidence exists for a sibling, not for the quoted variant
Who carries the obligationThe consultant's own duty to the clientThe factory's duty to the buyerThe importer may hold the market obligation instead of the factory
When must it existThe programme milestone that the approval route imposesThe date the document can realistically be producedThe milestone was written as a hope, not a production plan

A useful discipline for a consultant reviewing this window is to ask, of every open row, which side is short of information and which side is short of authority. A row where the supplier simply does not know is a research task. A row where the supplier knows and cannot supply is a design decision that travels back to the design team. A row where the supplier can supply but the specification never asked for the right thing is a drafting failure, and it belongs to whoever wrote the clause. Sorting the three apart early is most of what coordination consists of. The catalogue entry point for this is the smart door locks.

The published procurement guidance in How to Verify a Smart Lock Manufacturer Before Placing an Order approaches the same territory from the buyer side, and the supplier-side counterpart sits in Smart Lock Supplier Due Diligence Checklist. This article is about the space between the two: the working method during the window itself.

What a clause actually decides

Most coordination failures at the clause level trace back to one misconception: that a clause describes a product. A clause does not describe anything. A clause decides.

Read that way, a clause in a bid leveling schedule decides four things: what is required, what document demonstrates the requirement, what object that document must cover, and what happens to the response if the document does not exist by the stated milestone. Everything else a clause appears to say is context or commentary. When a consultant asks what a clause decides, the answer is never that the product should be stainless steel. It decides that a specific performance claim must be demonstrated by a named document type, covering a named object, by a named date, with a stated consequence if it is missing.

That reframing produces four clause types, and each binds a different party.

Clause typeWhat it decidesWho it bindsWhat it does not decideCoordination failure when absent
Requirement clauseThe function the opening has to deliver, and the door type it applies toThe supplier, against the design intentHow the function is achieved, or by which productResponses answer a product brief nobody wrote
Evidence clauseWhich document type demonstrates the requirement and what that document must nameThe supplier, and the reviewer who accepts itWhether the evidence is good enough for the programmeEvery supplier sends a different kind of document
Deviation clauseHow a departure from the requirement is recorded, and where it is judgedBoth parties, with an owner namedWhether the departure is acceptableDeviations are adjudicated late, in the evaluation meeting
Boundary clauseWhat the evidence explicitly does not coverThe buyer, against the document's own scopeAnything about another standard or another market routeOne standard's evidence is used to answer a different question

The practical value of naming these four types is that it makes the coordination question precise. When a supplier sends a document and a reviewer says that is not what was asked for, the disagreement is usually a clause-type mismatch: an evidence clause was answered with a marketing image, or a requirement clause was answered with a declaration of conformity that says nothing about the function. Naming the type turns an argument about adequacy into an instruction about the next action. For bid leveling coordination, the position on this ladder is what the purchase decision turns on.

The same four types are used in the template language covered in Bid Leveling: Template Language for a Specification, and the reviewer-facing version is set out in Bid Leveling: Reviewer Checklist. The coordination discipline that matters here is different from both: it is about the order in which the four are worked, and about who is holding the pen.

Four documents that never travel together

The single most useful distinction a consultant can carry into a bid leveling window is between four document types that buyers routinely call the same thing. A supplier saying its product has CE may be pointing at any of them, and the coordination fails if the register cannot say which one arrived.

DocumentWhat it actually isWhat it can be used to showWhat it cannot showThe question to ask
Test reportA body tested a sample and recorded the resultThat a sample of that type was tested against a named standardThat the quoted variant, finish or site was testedWhich sample, which variant, which clause
CertificateA body attests conformity, with a scope and a validity periodThat conformity was attested inside the stated scopeAnything outside that scope, or after expiryWho holds it, the number, the scope page, the validity
Declaration of conformityThe manufacturer or importer makes its own legal claimThat a named party has taken responsibility for the claimThat any third party verified itWho signed it, on what date, with which annexes
MarkingA symbol printed on the product, label or packagingThat a market-access regime was declared for the product as placed on the marketWhich clauses of which standard were tested, and on whatWhich regime, which legal basis, where the marking appears

Note the shape of the failure. The marking is the most visible and the least informative; the certificate is the most load-bearing and the most often replaced by a screenshot. A window in which the document type is not a register column ends with the reviewer accepting whichever artefact is easiest to obtain, which is rarely the one the programme needs.

graph LR
    A["Requirement clause"] --> B["Evidence entered in the register"]
    B --> C{"Which document type arrived?"}
    C -->|Test report| D["A sample was tested"]
    C -->|Certificate| E["A body attests, with scope and number"]
    C -->|Declaration| F["The manufacturer or importer claims"]
    C -->|Marking| G["Printed on the product or label"]

Applied to bid leveling coordination, the acceptance order runs: a marketing image, a self-declared declaration of conformity, a test report on a sample, a third-party certificate carrying a scope and a number, a certificate covering the exact variant being bought, and audit or production-control evidence that keeps the earlier rung valid after the sample passed. The recurring commercial failure mode is buying at the second or third rung and discovering during installation that nothing at the sixth rung was ever in anyone's plan.

CONFIRM-WITH-LOCAL-LEGAL: which conformity route applies to a given product in a given market, and which authority or body signs the acceptance, is decided per product and per market. Confirm the route and the accepting body with local counsel and the approving authority before any clause is written, and do not assume that one market's acceptance practice transfers to another.

The handoff points that decide the window

Coordination is a sequence, not a mood. There are identifiable points where information must move from one party to the other, and each point has an owner and a gate condition. If the gates are not written down, the coordination degrades into a stream of emails that nobody can reconstruct when a deviation has to be defended at award.

flowchart TD
    A["Design intent frozen · door schedule revision and clause set issued"] --> B["Responses received · held, not yet compared"]
    B --> C["Coordination window opens · deviations logged against clause numbers"]
    C --> D["Clarification loop · questions batched by class, answers logged verbatim"]
    D --> E{"Any register row still open?"}
    E -->|Yes| D
    E -->|No| F["Evaluation · each response read against the issued clause set"]
    F --> G["Award · evidence hand-off list and revision triggers issued"]

The first gate is the one most often skipped. If the door schedule revision and the clause set are still moving while responses are being written, the supplier is answering a moving target and the reviewer is comparing answers to a question that no longer exists in the same form. Freezing the intent before the window opens is the precondition for every later comparison.

The second gate is most often skipped in the opposite direction: responses are compared to each other before they are compared to the clause set. Reading two responses side by side produces an impression of difference that is frequently an artefact of different response templates. Reading both against the issued clause set produces a list of rows, each of which either passes, deviates or is silent, and that list is what a reviewer can defend.

The last gate is the one most often forgotten. Coordination is not finished when the award is made. What leaves the window is an obligation list, and it needs names on it.

The scope map: which standard answers which clause

A recurring coordination error is asking one document to answer a question that belongs to another family of standards. A lock performance standard, a fire-door standard, an EMC and radio standard, and an electrical safety standard answer four different questions. Most of the pressure in a bid leveling window comes from clauses written without that separation, so the supplier is asked for one artefact to cover several scopes.

What the clause is really askingThe document family that answers itWhat that family coversWhat it does not answer
Durability, strength and security of a mechanically operated lock or latchEN 12209, with its classification code and use categoriesMechanical lock performance under the current published editionElectronically driven locking, cylinders, multi-point bodies
The mechanical and electrical locking function of a battery-driven smart lockEN 14846, for electromechanically operated locks and striking platesThe electromechanical locking function and its test methodRadio or EMC behaviour, fire resistance, escape-device logic
The cylinder, where a keyed override or key control is specifiedEN 1303Cylinder durability, key control, pick and drill resistanceThe lock body itself, and any electronics
A multi-point doorConfirm the published title and scope of the current edition of EN 15685Multi-point locking locks and locking platesSingle-point smart lock bodies
A lock fitted to a fire doorEN 1634-1, where hardware is tested as part of the door assemblyThe fire resistance of the door assemblyAny standalone fire certificate for a lock
An electrically controlled hold-open on a fire or smoke doorEN 14637, with its interface to detection and its mains expectationsHold-open systems for fire and smoke door assembliesNon-fire doors, and battery-only systems, which sit outside its own scope
A controlled-access openingEN 12361 for interlock devices, after confirming the published title and scopeElectronically controlled door opening interlock devicesOrdinary smart lock function, which is why the citation is often wrong
An escape openingEN 179 for lever-operated escape devices, EN 1125 for panic bar devicesEmergency escape device requirements by device typeEach other's device type
Egress and locking arrangement by occupancyNFPA 101 in North AmericaEgress and locking arrangements for occupanciesProduct-level evidence of any single device
Electromagnetic holding devicesANSI/BHMA A156.23Holding force, duty cycle and indoor or outdoor useGeneric electric lock performance
Electrified lock hardwareANSI/BHMA A156.25Cycling, security, operation, strength and environmental testsThe access control system around it
Power locks at the openingUL 1034Electrical safety and performance of power locksSystem-level classes, which sit with UL 294
The access control system as a wholeUL 294Performance classes for system unitsThe individual door hardware
Wireless capability of the deviceEU RED with the applicable harmonised radio and EMC standards, or the North American radio authorisationEmissions, immunity and radio behaviour for the wireless functionMechanical durability, ingress, fire performance
Mains-powered accessories in the same packageLow voltage directive, with IEC 62368-1 as the ICT safety frameElectrical safety of the adaptor, gateway or controllerThe battery-driven lock, which is a different regime
Accessible operation of the hardwareADA and ANSI A117.1Operable part rules, operating force, reach and clearancesFire and security performance

Writing this map into the register as a boundary column is cheap and it prevents the most expensive category of dispute. Two standards in the same row of a bid comparison mean one of them was cited to answer a question it was never written to answer, and the reviewer who discovers that at the approval stage has to reopen the whole response.

CONFIRM-WITH-LOCAL-LEGAL: the above families are the usual scope statements, and editions change. Confirm the published title, the current edition and the scope of any designation against the standard text that the destination market's approval route will actually apply, and confirm with local counsel which of them binds a given project.

The shared register: one page both parties edit

The coordination artefact that distinguishes a working bid leveling window from a failing one is a single register, issued with the request for quotation and updated by both sides throughout the window. It is not a spreadsheet of prices and not a comparison matrix. It is a record of every clause, what was asked, what was answered, what remains open, and who owns each open row.

The columns that make it work are the ones a normal clarification email does not have. Without a document type column, the reviewer cannot tell what arrived. Without an object column, the answer cannot be checked against the quoted variant. Without an owner column, open rows have no mechanism to close.

ColumnWhat it holdsWhy it cannot be optional
Row and clause referenceThe register row number and the clause it answersMakes a question, an answer and a decision traceable to one line
Requirement as issuedThe clause text or a faithful restatementStops the answer drifting into a different question
Response as receivedThe supplier's own wording, entered verbatimPrevents paraphrase from softening a deviation
Deviation classFit, capability, evidence, regulatory or programmeRoutes the row to the party that can close it
Document type offeredTest report, certificate, declaration or markingPrevents a weaker artefact being accepted silently
Holder, number and dateWho issued it, the number, the issue dateDistinguishes a live document from a screenshot
Object coveredDesignation, variant, finish and site as quotedChecks the evidence against the thing being bought
Edition citedThe edition and amendment the document refers toEditions change, and a superseded document is not evidence
StatusOpen, answered, accepted, rejected, transferredMakes the window auditable
Owner and dateWho closes it, and by whenAn open row without an owner survives the award
Revision triggerWhat change would reopen the rowConnects the register back to the door schedule

A worked fragment shows how the register absorbs the ordinary friction of a window. These rows are illustrative and generic; they show the shape, not any real project.

RowRequirement as issuedResponse as receivedClassDocument offeredStatus
12Overhead closers shall be coordinated with the door leaf swing for the scheduled leaf sizeThe closer offered matches the scheduled leaf; coordination detail is required for the wider leafFitManufacturer installation drawingOpen, owned by the supplier
19The locking function shall be demonstrated for the electromechanical variant quotedA test report exists for a sample of the mechanism, not for the quoted finish variantEvidenceTest report on a sampleOpen, milestone renegotiated in writing
24Radio capability shall be evidenced for the destination marketA declaration of conformity and the market marking are offered; the radio authorisation document is named but not attachedRegulatoryDeclaration and markingOpen, transferred to the importer
31Staged delivery shall align with the door installation sequenceThe supplier can only commit to a single consolidated deliveryProgrammeSupplier statementOpen, commercial decision to the buyer

Note what the register is not doing. It is not adjudicating. Every one of those rows is still open when it is written, and the value of writing it is that the row has a class, an owner and a date. A clarification email that says the closer needs checking carries none of that. The commercial outcome of each row is a separate decision, taken by the party named in the owner column, and where a figure is involved the supplier produces it against a named configuration through request a quote.

Running the clarification loop without a deadline spiral

The loop itself is simple and gets complicated only because of timing. Questions arrive in the first days, answers take longer than anyone expected, new questions appear in the answers, and the window closes on a date that was fixed before any of it started. Coordination problems in practice are less about the substance of the questions and more about how they were batched and closed.

Four rules keep it manageable. Batch questions by class rather than sending them as they occur, so the supplier can answer in one considered response. Log answers as they arrive, verbatim, against the row that asked them, so the register and the correspondence never diverge. Freeze the question set when the response window closes, with one recorded exception for questions raised by an answer that changes the requirement. And assign every open row to a named owner before the window closes, because a row without an owner becomes an unfunded obligation in the award package.

The question set that reliably unblocks a window is short. It asks about scope, about document type, about object coverage and about edition, and it asks each one in a form that can be answered by pointing at a document.

  1. Which revision of the door schedule does this response answer, and does it cover every door type listed for this package?
  2. Which clause set has the response been written against, and is it the specification as issued or a later revision?
  3. For every declared deviation, which class does it belong to: fit, capability, evidence, market access or programme?
  4. For every evidence clause, which document type is offered, who issued it, what is the number, and what is its issue date?
  5. What does that document name: designation, variant, finish and production site, and does it match what you quoted?
  6. Which edition and any amendment does the document refer to, and is a later edition in force in the destination market?
  7. Which documents exist today at which ladder level, and when can a higher level be produced for the quoted object?
  8. Which market-access obligations fall to the importer or the local entity rather than the factory, and who holds that evidence at award?
  9. What happens to this response if the door schedule changes at this door type, and which rows would reopen?
  10. At award, what evidence hand-off do you propose, in which form, to which named recipient?

Questions three, seven and eight usually have to be asked twice, because the first answer describes a situation rather than answering. Question seven in particular tends to come back as a statement that the certification is in place, which is exactly the phrase that produced the four-document confusion in the first place. Asking which document type, at which ladder level, for which object, by when converts a claim into a schedule.

The broader supply-side preparation for the same window is covered in What Documents Should You Request From a Smart Lock Supplier? and in Smart Lock RFQ Guide for International Buyers.

Reading a deviation against the design intent

A deviation is not an error and it is not a negotiation position. It is a factual statement that the offered product does not do what the clause asked, or that the evidence for what it does is not yet in the required form. Reading it correctly means classifying it before reacting to it, because each class has a different owner, a different closing mechanism and a different cost if it is left open.

ClassHow it usually presentsWhat closes itWho decidesCost of leaving it open
FitThe product does not suit the scheduled leaf, frame, handing or glass conditionA dimensioned survey and a corrected configuration, or a revised schedule entryConsultant with the design team, then the supplierThe clause survives into the shop drawing stage and becomes a submittal dispute
CapabilityThe catalogue does not offer the function the clause asks forA change to the clause, an alternative product, or a design changeThe design team, because the intent is theirs to setThe intent is lost silently and the building inherits whatever was delivered
EvidenceThe product exists and works, but the evidence for the quoted object is at a lower level than the clause namesA milestone change or an evidence clause change, agreed in writingBuyer and consultant jointlyA weaker document is accepted by default and the gap surfaces at installation
RegulatoryThe route to market in the destination market differs from what the clause assumedConfirmation of the applicable route with local counsel and the accepting bodyThe party holding the local obligationDocumentation is missing at the border or at the approval inspection
ProgrammeThe supply route cannot meet the staged sequence in the clauseA revised programme, an alternative sourcing route, or a rephased installation sequenceBuyer with the main contractor and the supplierThe installation sequence is built on a supply assumption that was never real

The reading skill is knowing which class a deviation belongs to before deciding how hard to push. A capability deviation cannot be closed by chasing the supplier harder; it can only be closed by changing the requirement or the product, and both are decisions the design team owns. An evidence deviation can almost always be closed by moving the milestone, provided the milestone was written with a consequence and the move is agreed in writing. A fit deviation is usually the cheapest to close, because a dimensioned survey settles it, and it is the one most often left open because it looks too small to raise in a window full of larger rows.

Two habits keep this reading honest. Record the deviation in the supplier's own words before any interpretation is applied, because interpretation is where a limitation starts to look like a preference. And ask, of every capability deviation, what the design team intended to achieve, then record that intention in the register next to the clause. A register that records only the clause shows a list of gaps; a register that also records the intent shows the design decisions the gaps require.

Coordination failures and their early signals

Coordination failures are usually diagnosed after the award, when they are expensive and hard to fix. Each of the patterns below has a signal that appears inside the window, usually in the first week, and a repair that is available before the window closes.

Failure patternEarly signal inside the windowRepair available before the award
Two clause sets in circulationThe specification and the schedule issued with the request for quotation carry different clause numbers or wordingDeclare one clause set authoritative, reissue, and restart the answer window against it
No register existsAnswers live in threads, and two people give different accounts of what was agreedStand up the register with the columns above and backfill the open threads into it
Deviations are adjudicated during evaluationResponses are compared and winners emerge before the open questions are answeredStop the comparison, reopen the window, close rows before ranking
Evaluation compares responses to each otherDifferences in response format are being read as differences in offerRe-read both against the issued clause set and produce the row list instead
A lower evidence level is accepted without a noteThe document offered carries no scope, number or date, and nobody objectedName the ladder level in the register, set the milestone, or amend the clause
The same product is compared across different schedulesOne response covers a door type another response does notSplit the package by door type before any comparison
One party owns the deadline but not the registerThe window date was set but nobody was made responsible for closing rowsName the register owner in the coordination plan and give them the milestone
The design changes after responses landA door schedule revision was issued and no row was reopenedAdd revision triggers to the register and re-open the affected rows by rule
Evidence is demanded for the wrong scopeA request cites one standard family for a question belonging to anotherApply the scope map to the evidence schedule and split the requests
The obligation holder is assumed to be the factoryThe factory cannot produce the market-access document the clause namesIdentify the local holder and transfer the row with a named recipient

The signal worth watching most closely is the one in the second row. A window without a register produces a specific symptom: the design team believes a deviation was closed and the supplier believes it was raised. That symptom is invisible at award, because the award looks clean, and it reappears as a substitution, a contractor query or an approval question during inspection. The register is the only thing that makes the window legible to people who were not in it.

Where the evidence ladder fits into coordination

The evidence ladder is not only a quality concept; it is a scheduling tool, and coordination is where it is either applied or ignored. Each rung carries a different amount of time, a different owner and a different risk if it turns out not to exist.

Ladder levelWhat it buysWhat it cannot carryCoordination action
marketing imageA first cut at scope and appearanceAny obligationLog it as a lead, not as an answer
self-declared DoCA named party taking responsibility for a claimThird-party verificationRecord who signed it and on what date
test report on a sampleEvidence that a sample of that type was testedCoverage of the quoted variant or siteRecord the sample, then set the milestone for the stronger rung
third-party certificate with scope and numberAttested conformity inside a stated scopeAnything outside that scopeCheck the scope page against the object in the register
certificate for the exact SKU/variant being purchasedEvidence matched to the thing being boughtCoverage of later production changesConfirm the production site and the variant string
production-control records that hold the approval open after the sample passedConfidence the earlier rung still holdsSubstituting for a missing testAsk what keeps the certificate valid after the sample passed

Two coordination decisions follow directly from the ladder. The first concerns the milestone: a clause that names a document type without naming a date is satisfied by whatever arrives first, which is rarely the rung the programme needed. The second concerns the owner: at the lower rungs the supplier can usually produce something quickly, whereas the upper rungs usually require the applicant to be the party named in the certificate or the declaration, and that party is sometimes the importer rather than the factory.

That last point is where the ladder and the market-access routes meet. A radio authorisation, a national conformity certificate or a pre-shipment conformity document is frequently held by the importer or the local entity in the destination market, because the legal obligation sits there. Coordination has to assign that row correctly at the start, otherwise a supplier who cannot produce the document has been asked to do something outside its role. The supplier-side verification path is in Smart Lock Factory Audit Checklist for International Buyers, and the sample-stage counterpart is in How to Evaluate Smart Lock Samples Before Bulk Ordering.

How the coordination loop changes by market

The coordination method is portable, but the substance of what gets coordinated is not, because the evidence a market expects differs. A clause set written for one region and issued unchanged into another is the most common source of an unresolvable row in the window.

Market contextWhat changes in the coordinationThe question to put in the register
European construction products routeDoor hardware sold as a construction product sits on a route where a declared performance document and the underlying test evidence are separate artefactsWhich declared document answers which clause, and where the underlying evidence sits
United Kingdom after the transition periodMarking acceptance practice varies between specifiers and approving bodiesWhich marking does the approving route for this project expect, and who confirms that
North AmericaLock-level, device-level and system-level standards answer different questions and are routinely cited interchangeablyIs this clause a lock question, a device question or a system question
Australia and New ZealandRadio and electromagnetic obligations and state-based electrical safety for mains-connected equipment are separate, so an adaptor can be in scope while the lock is notWhich items in this package are in which regime
IndiaProduct registration and wireless equipment approval often sit with the importer rather than the factoryWhich rows are the importer's to close, and by when
Gulf and South-East Asian destination routesPre-shipment conformity documentation determines whether goods clear, and whether a product is inside a listed regime is a per-product questionIs this product inside a listed regime, and which document clears it

The pattern across all six rows is the same: the design team writes the clause from the building's perspective, the supplier answers from the product's perspective, and the market sits in the middle with its own set of documents that neither party named. Coordination is the act of making the middle visible, in the register, at the start of the window rather than at the border or the inspection.

CONFIRM-WITH-LOCAL-LEGAL: every statement in this table describes a route that is per product, per market and, in some cases, per factory. Confirm the applicable route, the accepting body and the documentation set with local counsel and the market's conformity authority before a clause, a deviation or a milestone is written, and do not rely on a document issued for a different destination market.

The order the questions come

The question set above can be handed to a reviewer on the day, and the order it is asked in decides how much of the window it consumes. Scope first, because a response that covers the wrong door types against the wrong clause set leaves a much shorter evidence conversation than one that does not. Evidence second, because the document type, the object that document names and the edition it cites decide how much of the ladder still has to be climbed. Ownership third, so that a row nobody can close becomes a funded obligation rather than a delay. Handover last, because it is the part most often left undocumented, and the part that whoever administers the doors after handover inherits without knowing it.

What good coordination looks like at award

The test of a bid leveling window is not how it went. It is what leaves it. A coordinated window produces an award package with four parts, and a review of that package tells you immediately whether the coordination was real or performed.

The first part is the specification as issued, with the door schedule revision named. The second is the accepted deviation schedule, where every deviation has a class, a decision, a decision owner and a date. The third is the register, with every row either closed or transferred to a named owner with a milestone attached, so the open rows become funded obligations rather than loose ends. The fourth is the revision trigger list, which says what changes reopen which rows, and to whom that change is notified.

Two failure patterns look superficially like coordination and are worth naming. A window where everything was resolved and nothing was recorded leaves the award holding verbal understandings that the contractor and the supplier remember differently. A window where every deviation was accepted with a note in a meeting leaves the acceptance existing only in the mind of whoever ran the meeting. Both produce an award that looks clean and a project that does not.

The practical counsel is that the coordination artefact has to outlive the window. It should be issued with the award, referenced from the purchase order, and handed to the party who will administer the doors after handover, because that party inherits every open row without knowing it inherited anything. Articles in this series cover the cost and risk consequences of the same window in Bid Leveling: Cost and Risk Consequences, the demand set in Bid Leveling: Documents a Specifier Should Demand, and the working conversation in Bid Leveling: A Smart Lock Specifier Guide.

The boundary of this article

This article is not legal advice, and it does not determine what any market requires. It describes a working method for coordinating two parties through a bid leveling window: what a clause decides, what document answers it, who closes an open row, and what to ask for while the window is still open.

Conformity routes, approval routes and the treatment of equivalent or substituted products are decided per product, per market and per contract, and they change. Any clause, milestone or deviation decision described here should be checked with local counsel and with the approving authority for the project before it is written into an issued document.

Commercial figures are never generic. Any number that will appear in a comparison is produced by a supplier against a named configuration, a named schedule and a named destination market, and it should be obtained through request a quote rather than inherited from a summary in an old bid document. A factory that publishes its own process, testing and inspection detail is described in Smart Lock Factory Testing: What Should Be Tested? and in Smart Lock Factory Inspection Checklist, and those pages are a reasonable starting point for the supplier-side conversation a register is meant to structure.

Sepetiniz
Bu siteyi kullanırkenizin deneyimini çerezlere izin vererek iyileştirebilirsiniz. Çerez Politikası
Chat on WhatsApp