Learn the EPD definition, see how a third-party verified environmental product declaration is read in a tender or submittal, and know what evidence to demand.

Đăng lúc: Th11 08, 2024

Smart Lock Glossary: EPD Definition for B2B Buyers

Smart Lock Glossary: EPD Definition for B2B Buyers

Consistent vocabulary removes a surprising share of disputes, so epd definition is defined precisely here. The submittal file looked complete. The door schedule was signed, the hardware set was confirmed against the frame dimensions, backset and spindle sizes were entered line by line, the escutcheon and faceplate drawings were attached, and a spare-unit plan sat at the back of the pack with the re-keying procedure stapled to it.

Direct answer. In brief, this article covers epd definition from epd definition to the decision record. It states what to confirm about epd definition on the dated product page where a figure is involved. An epd definition is a reference entry. It holds definitions, options and trade-offs. epd definition is the entry point for epd definition.

  • Fix the terms — use one vocabulary for epd definition across the project
  • Present the options — list the routes available for definition taken one word and what each is for
  • Present the trade-off — record what you give up with each route in performance question is different
  • For epd definition, epd is what each step has to answer to.

The reviewer's reply was one sentence: provide an environmental product declaration for the specified lock, or this line item cannot be scored.

Three people read that sentence and understood three different things. The specifier thought it was a test report and expected the laboratory to produce one. The main contractor thought it was a document the supplier already held somewhere on a website. The importer thought it was marketing and asked whether the manufacturer could write one on letterhead.

Nobody had an EPD definition on the table before the arguing started, and each wrong reading costs the programme something different: a rejected submittal, a scored-down bid, a shipment that arrives with paperwork nobody can file. The manufacturer, when the request reached him through a fifteen-message chain, asked what a life cycle had to do with a lock that ships in a carton.

This entry is not a dictionary entry. It is a working answer to the question a buyer actually has when the abbreviation appears in a quotation, a tender schedule or a submittal response: what the document is, what it decides, what people get wrong about it, what evidence settles the argument, and where in a real transaction it does its work. Where the term touches a scoring rule or a legal obligation, the answer is not mine to give, and the article says so at each of those points.

The published companion piece on what certifications should I request from a smart lock supplier covers the safety and performance documents. This one covers the environmental document, which is the one most often asked for by people who have never read one.

The definition, taken one word at a time

An environmental product declaration is a third-party verified document describing a product's life-cycle environmental impacts. That is the whole of it. Every word in the sentence is doing work, and most of the disputes in the message chain above come from skipping one of them. The same question as epd definition, read from a different angle, is covered in Smart Lock Glossary: NAICS Code Definition for B2B Buyers.

Third-party. Somebody independent of the manufacturer produced or checked the statement. The same logic the trade applies to a laboratory report applies here: an accredited body's value is its independence, and a report written by the party with a commercial interest in the answer is not worth the same. When a supplier says a declaration is "ours", the useful question is who else signed it, in what capacity and against what stated rules. The published guide to how a supplier is actually verified makes the same point from the opposite direction: verification is only worth what the independence of the verifier is worth.

Verified. Note that this is not the same word as tested. Verification is a review of a piece of work — in this case a life-cycle account — performed and recorded by someone who did not perform it. A test report answers "what happened when this sample was put on the rig". A verification statement answers "did the person who added up the life cycle do it according to the stated rules". Confusing the two is how a project ends up with a fire-door test report in the environmental slot of a submittal and a reviewer who sends the whole pack back.

Document. It is a file with a version, a date and an identity, and it can be handed to a third person who was not in the room. This matters more than it sounds. A claim repeated in a datasheet, a sustainability page or a sales email is not a document; it is a sentence. The moment a tender asks for an environmental product declaration it is asking for a retrievable record that somebody else can read and score, which is why "we are sustainable" never satisfies the line.

Describing. Not grading, not ranking, not certifying. A declaration reports quantities. It does not hand down a verdict, and it does not carry a pass mark. This single verb is the source of most of the expensive confusion, so it gets its own section below.

A product's. The unit of the declaration is a product, and a product has to be identified precisely enough that the thing in your submittal and the thing in the declaration are demonstrably the same item. A family name is not an identity. This is exactly the discipline the trade already applies to a listing, which covers a specific model in a specific configuration rather than a range.

Life-cycle. From raw material to end of life, which for a door-mounted electronic product is a longer story than for most hardware: the substrate and the finish, the pressed parts, the reader and the secure element, the standby current a unit draws for years on a live door, the power source a facility changes on a maintenance calendar, the credential infrastructure that has to exist for the lock to be useful at all, and the day the unit is decommissioned, re-keyed or scrapped. Which stages a particular declaration includes is a question about that declaration, not about smart locks in general.

Environmental impacts. Plural. Several categories of effect, reported separately, not one score. A buyer who receives a single number has received a summary, not the declaration, and a summary cannot be scored against a rubric written for the underlying categories.

Put the seven readings together and the EPD definition resolves into something a procurement engineer can act on: an independently reviewed, versioned account of what a specifically identified product does to several environmental accounts across its life, offered as evidence for someone else's scoring rule. The same question as epd definition, read from a different angle, is covered in Smart Lock Glossary: CFS Definition for B2B Buyers. The same question as epd definition, read from a different angle, is covered in Smart Lock Glossary: One Time Code Definition for B2B Buyers. Specifications at this level come off the smart door locks.

What the document actually decides

Strip away the wording and the term touches one commercial question: can this product be scored.

A public tender that awards points for environmental evidence cannot award points against an assertion. It needs a document the assessor can read without taking the bidder's word for anything. A green-building client working through a rating scheme is in the same position — the person filling in the scheme's submission does not want to be the one who decides whether a lock qualifies, because that decision will be audited later by somebody who was never introduced.

So the declaration decides three practical things.

It decides whether your line item enters the scoring at all. In many tender packs the presence of the document is the gate; the content is what earns the points. A missing document is not a zero, it is a non-submission, and in a pack where the hardware schedule is being levelled across bidders the difference between the two can be the difference between being comparable to the other bids and being excluded from the comparison.

It decides which bidder is exposed. On a project with a nominated supplier, the party who nominated is the party who now has to answer for the evidence the nominated supplier cannot produce. That is a contractual question about who carries the gap, and it is worth knowing before the submittal rather than after. Whether your form of nomination transfers that obligation is a matter for the contract, so route it to CONFIRM-WITH-LOCAL-LEGAL with the actual nomination wording in front of you.

It decides how much of the project is genuinely covered. One declaration for one SKU on a schedule with forty door types does not cover the schedule. This is where the reference to life-cycle scope earns its keep, and where buyers most often accept a document that describes a different product than the one they are buying.

It decides a fourth thing nobody mentions until the end of the project: whether the document is still true when the goods arrive.

For the buyer-side framing, the checklist in smart lock procurement checklist for B2B buyers is where the environmental line usually sits, alongside the documents that carry money rather than points.

The performance question is a different question

The most expensive confusion about an environmental product declaration is the belief that it certifies performance. It does not. It is not a certificate of performance, and it is not a carbon claim about a building either. Those are the two errors written into the trade's own definition, and both are easy to make because the documents arrive in the same folder.

A performance document answers whether the hardware does something under stated test conditions. A European burglary-resistance scheme grades an assembly, and the highest band applies to the assembly as tested rather than to a lock standing alone. An ANSI grade is a published band for a hardware category, and grades drawn from different ANSI/BHMA standards for different categories are not comparable to each other. A UL listing covers a specific model in a specific configuration and is read by insurers and specifiers as a statement about tested performance. A third-party laboratory report is issued on a sample, in a configuration, and does not stretch to variants.

An environmental declaration answers none of those questions. It is describing quantities of effect across a life. If you put a declaration in the performance slot of a submittal, the reviewer is not going to debate the numbers with you — the reviewer is going to note that the wrong class of evidence was offered, and the pack comes back.

What the reviewer needsThe document that answers itWhat goes wrong if the substitute is an environmental declaration
Resistance of an entrance assembly to attackA graded test of the assembly as built and installedThe grade read off a performance scheme is absent; the declaration proves nothing about attack
Durability and cycle behaviour of the mechanismA test on a stated sample and configurationThe reader has no way to bound the fleet's behaviour
Ability to be specified and installed in a listed useA listing for the model in the configuration suppliedThe insurer or specifier has nothing to read off the label
Scoreable environmental evidence for a tender or rating schemeA third-party verified declaration of life-cycle impactsThe performance reviewer rejects the class of document; the scoring reviewer has no document at all

The distinction is worth this much space because it is where programmes lose time most reliably. A buyer who asks a supplier for "the certification for the green requirement" is asking for a thing that does not exist, and a supplier who answers that request with a test report has just created a documentation gap that will surface at bid levelling. The pattern of where these gaps appear is the subject of the reference on what conformity paperwork means, which handles the adjacent family of documents — the manufacturer's own legal statement, and the process by which a manufacturer establishes that a product meets the requirements of a standard.

One more boundary, because it gets conflated constantly. A declaration describes a product. A building's carbon account describes a building, and it is assembled from every product in it plus the construction, the energy and the use. Presenting a product-level document as a claim about the finished structure is the second error in the standard definition, and it is the one that reaches as far as the client's own filings, which is why any statement of that kind belongs in front of somebody qualified rather than in a submittal cover note: CONFIRM-WITH-LOCAL-LEGAL.

Six near neighbours that get mistaken for an EPD

The reference shelf is crowded. Most of the confusion around the EPD definition is not confusion about the declaration itself, it is confusion about the documents that sit either side of it.

TermWhat it genuinely isThe sentence people wrongly treat as equivalent
Declaration of conformityThe manufacturer's own legal statement that a product meets the applicable requirements"It is third-party evidence" — it is the supplier speaking about itself, and it is also not a test report
Conformity assessmentThe process by which a manufacturer establishes that a product meets the requirements of a standard"The certificate" — the certificate is one output of the process, the process is not the paper
Third-party laboratory reportAn accredited body's findings on a sample in a configuration"It covers the range" — it does not extend to variants
Digital product passportA structured, machine-readable record of a product and its compliance data"New evidence" — it is a data carrier; it carries evidence, it does not create it
Chain of custodyThe documented, unbroken record of who held the goods"A document in a drawer" — it is a process, and it starts before the container is closed
Country of originThe country in which goods were produced under the applicable rules"What the supplier wrote on the invoice" — it is a substantive determination with evidence behind it

Each of those mix-ups has a different failure mode on a real project, and it is worth walking through them once rather than discovering them in sequence.

The declaration of conformity swap. A supplier sends a signed page stating the product meets applicable requirements, and the coordinator files it under "environmental". Nothing in a manufacturer's own legal statement describes life-cycle impacts, and nothing in it is third-party verified. The tender scoring line stays empty. Separately, the conformity page is doing a different and important job: it records what the supplier asserts and is accountable for. Filing one document in two places destroys both.

The conformity assessment swap. "We underwent conformity assessment" is a sentence about a process. A buyer who receives it as an answer should ask the ordinary follow-up: which documents may I legitimately demand from that process, and which of them exist as outputs. A process has no page count.

The laboratory report swap. A test report is on a sample and a configuration. It is the strongest evidence you can get for the performance question and it says nothing about the environmental question, and it will not stretch from the model tested to the variant ordered. That last clause matters on any project where the schedule has been value-engineered mid-tender.

The passport swap. A structured record is a delivery mechanism. It changes how a buyer or a regulator retrieves evidence, and it changes nothing about whether the evidence exists. A passport that carries no verified declaration behind it is a well-organised empty folder. The published treatment of smart lock environmental specification guide is the better starting point for specifying the substance rather than the carrier.

The chain of custody swap. Custody records are about who held the goods; declarations are about what the product does across its life. On a recall the custody record is what lets you scope the loss, and because it is a process that starts before the container is closed it is usually the thing that breaks first on a multi-leg consolidation.

The origin swap. Origin is a determination with evidence behind it, made on the facts of the specific product by the authority that administers the rules — and for some buyers it is the whole bid. It is not a supplier's assertion and it is not an environmental statement. Any duty, marking or preference consequence of an origin finding belongs to the authority and to your own adviser, never to this reference: CONFIRM-WITH-CUSTOMS-BROKER.

Whose paper is it: origin, verification and the version

There is a quieter confusion than the six above, and it costs projects more hours because it looks like a solved problem.

A tender asks for an environmental product declaration. Somebody finds one. It is real, it is verified, it carries a date and it describes a lock. It is not the declaration for the product being bought.

The document in the folder may differ from the product on the schedule in any of four ways.

It describes a different model. The identification line names a product, and a family name is not an identification. Match the declaration to the item the way you would match a listing to a configuration.

It describes the same model in a different configuration. Hardware assemblies are built to order. A unit supplied with a different cylinder housing, a different power arrangement or a different reader is a different configuration, and configuration is where the life-cycle account gets its shape.

It predates a change. A supplier notice that a product or its specification has changed is a notice about an approved configuration. A change that improves the product is still a change to what was approved, and a declaration written before it is a statement about what came before.

It is not the version the reviewer will accept. Some scoring rules read the date of the document as part of eligibility. Whether your rule does is a question about your rule and it is answered by the authority running the tender, not by the supplier and not by this article: CONFIRM-WITH-LOCAL-LEGAL.

The record-keeping discipline follows from that list. When the document enters your file, it should arrive with the identity of the product it covers, the date of the document, the identity of the party that verified it, and a pointer to the configuration it was written against. A page in a PDF folder with none of those four annotations is not evidence, it is a rumour with a colour scheme.

Where an EPD bites in a smart-lock programme

Defining the term is half the job; the other half is knowing the moments at which the term does its work. An environmental declaration is not a standing property of a product. It is a document that intersects a programme at specific points, and at each point a different person is holding a different question.

flowchart TD
    A[Specification drafted with a scoring line] --> B[Quotation arrives with a document list]
    B --> C{Declaration named and identified}
    C -->|No| D[Gap surfaces at bid levelling]
    C -->|Yes| E[Submittal pack assembled]
    E --> F{Scope matches the ordered configuration}
    F -->|No| G[Configuration request before award]
    F -->|Yes| H[Reviewer scores the line item]
    G --> H
    H --> I[Order confirmed with the document schedule]
    I --> J[Change notice issued during production]
    J --> K{Declaration still describes the delivered goods}
    K -->|No| L[Replacement evidence requested]
    K -->|Yes| M[Goods arrive and the file is checked]
    L --> M
    M --> N[Site acceptance and punch list]
    N --> O[End of life and replacement decision]

Specification. The line is written here, usually by a specifier who has read the scheme's requirements and translated them into a document name. The buyer's job at this stage is not to produce anything; it is to make sure the line names a document rather than an aspiration, because "environmentally responsible" cannot be delivered, verified or levelled. The frequency with which this class of question appears in incoming requests is the same pattern the RFQ reference tracks in what an RFQ should contain.

Quotation and bid levelling. Here the term does its most damaging work. A bidder who submitted the test report instead of a declaration looks, on a levelled sheet, like a bidder who submitted nothing. Levelling compares documents by name, and a document with the wrong name is a missing document even when the folder is full.

Submittal. The pack is assembled for a reviewer who was not on the call. Everything that was understood between the parties now has to survive being read by a stranger, which is why an identifier, a date and a verifier's name need to be legible on the first page the reviewer touches rather than buried in the appendix. The punch-list stage is where the shortcuts taken here get counted.

Award and order confirmation. The order references what was discussed; the proforma referenced at the order stage is a non-binding indicative document and creates no obligation, so whatever environmental evidence means something has to appear in the binding paperwork. A declaration that mattered for scoring should matter for the document schedule too, if it is going to be worth anything on arrival.

Production and change. A product change notice lands somewhere in this window. It is the moment the environmental file most often quietly becomes wrong, because nothing on the purchase order shouts that the description in a third-party document no longer matches the unit being built.

Arrival and site acceptance. Site acceptance criteria are what the goods are actually judged against. If the document schedule was written into them, the mismatch is caught at the dock while there is still something to do about it. If it was not, the mismatch is caught at the final certificate, when the container is already opened and the units are already on doors.

End of life. The replacement question — refresh versus replace, and what a decommissioning and re-keying plan costs in units, labour and material — is where a life-cycle document and a total-cost model finally meet. The companion treatment of what total cost of ownership means for locks is the one that holds the arithmetic; the declaration holds the environmental quantities, and neither number substitutes for the other.

The evidence to demand, and in what order

This is the field-check part of the entry: what to ask for, and what each request settles.

#RequestWhat it settlesThe follow-up it usually triggers
1The declaration itself, as issuedWhether a document of the requested class exists at allWhich product identifier is printed on it
2The product identifier and configuration it coversWhether it describes the item on your scheduleA configuration request if the schedule differs
3The date of issue and the stated validity windowWhether the reviewer's rule can accept itA replacement request if it predates the tender
4The identity of the verifying party and its independenceWhether "third-party verified" means anythingThe accreditation question, if the reviewer asks it
5The impact categories reportedWhether the scoring rubric can be filled from the documentA request for the categories the rubric needs
6The stages of the life includedWhether the account covers use and end of life or stops at the factory gateQuestions about standby draw and power source handling
7The change notices issued since the date of issueWhether the delivered goods are still the described goodsThe re-issued document request
8The same document in machine-readable formWhether the passport or data route can carry itA note that a carrier is not new evidence
9Written confirmation of which SKUs on the schedule it coversWhether forty door types are covered by one pageSKU-level rationalisation of the request list

Requests 1 through 3 are cheap and they are where most of the wasted weeks hide; request 7 is the one that only becomes obvious after the first delivery.

Two cautions on the asking. Do not ask a supplier to produce a document for your tender without asking what the underlying work would be; a declaration commissioned as paperwork has a weak account behind it, and the weak account is what gets audited. Nor should a scanned page be treated as proof of the work — the page is the output, and the process behind it is what the term names.

Whether the environmental evidence carries any fiscal consequence — a deduction, a preferential treatment, a reporting obligation for the buying entity — is a local question about the buying entity's own position, and this reference gives no answer to it: CONFIRM-WITH-LOCAL-LEGAL, with your own adviser and the actual tender documents.

Reading the scope line before you read the numbers

Buyers open a declaration at the results table. Reviewers open it at the scope.

The scope line is where the document states what it is talking about: which product, which configuration, which functions the product performs, which stages of its life are inside the account and which are outside, and which impact categories are reported. It is a short block of text, and it is the only part of the document that lets you judge whether the numbers below it are numbers about your lock.

Three habits make this readable in a few minutes.

Read the exclusions first. A life-cycle account that stops at the factory gate is a legitimate document answering a narrower question, and it is not a defect in the supplier. It becomes a problem only when a rubric asks about the use phase and the document does not cover it. Knowing which case you are in changes the request you make — a broader account, or a different line item.

Match the function unit. Life-cycle quantities are reported per a stated unit of function, and the unit is chosen so that different products can be compared for doing the same job. A door that is controlled for ten years is the function; the hardware, the reader, the power source and the credential infrastructure are means to it. If the unit in the document is not the unit your schedule is thinking in, the comparison a reviewer is about to make is between two different questions.

Check the packaging claim's reach. Some declarations include transport packaging in the account, some do not. That single decision changes what the document can be used to say on a project with a low-waste condition, and it is a scope decision rather than a performance one.

This is also the section where the buyer's own language discipline pays. A programme that asks for "an EPD" without a product identifier, without a configuration and without a list of the impact categories its rubric needs will get a document it cannot score, twice. The environmental conditions a lock faces in service — temperature, humidity, dust, cleaning agents and their effect on a finish — are treated from the engineering side in smart lock environmental testing, and it is worth reading that before deciding what you want a life-cycle account to include, because the use phase of a lock is largely a function of what the door and the facility do to it.

Three scenes from a submittal

Not case studies, and no operator is being named. These are constructed to show where the definition does work; the numbers are planning assumptions belonging to the programme in the scene, not figures from any supplier.

Scene one, the wrong class of paper. A hospitality retrofit, several hundred doors, a rating scheme in the client's brief. The coordinator receives a request for an environmental product declaration, forwards it as "please send your environmental certification", and receives back a humidity and salt-spray test report plus a page of marketing copy about recyclable cartons. The pack is submitted. The reviewer's note reads: environmental evidence — not of the requested class. Two weeks, and the line scores nothing. The failure was not the supplier's; it was a request that did not name a document.

Scene two, the right paper, wrong product. A residential portfolio tender. A declaration exists, is verified, is dated inside the window the rule allows and is filed with pride. It identifies a model from the same family as the one specified, in a cylinder and power configuration the ordered units do not use. Nobody read the scope line until the assessor did. The programme's remedy is a configuration request and a re-issued document; the programme's cost is the delay to award, and the lesson is that a family name is not an identifier.

Scene three, the paper that went stale. The evidence was clean at award. Mid-production the supplier issues a notice: a component in the mechanism has changed. Functionally the unit is the same or better, and the change is welcome. It is still a change to an approved configuration, and the third-party account filed with the client describes the configuration before it. At the final certificate the client's environmental submission is rebuilt from scratch because nobody matched the notice against the document schedule at the arrival check.

The three scenes share one diagnosis. In each, a party treated the term as a property of a company rather than as a scoped, dated, identified document about a specific product — which is precisely what the definition refuses to be.

The rest of the term sheet travels with it

An environmental declaration almost never arrives in a project alone. It arrives in a file that also contains Incoterms lines, document requests and payment terms, and the reference discipline that keeps the environmental question clean is the same discipline that keeps the money questions clean.

Term people reach for when they mean an environmental documentWhat it actually carriesWhat to do with it
Incoterms line with a named placeAllocation of cost, risk and delivery obligation at a stated placeKeep it out of the evidence file; without the named place it decides nothing
HS codeThe harmonised tariff classification customs applies to the goodsAsk what classification is claimed and on what facts; the same physical lock can classify differently by material, power source and function: CONFIRM-WITH-CUSTOMS-BROKER
NAICS codeA statistical classification of business activityDo not read it as a product classification or a customs code
Letter of creditA bank promise to pay against conforming documentsThe bank checks the papers, not the goods, so document names must be right
Proforma invoiceA non-binding indicative document issued before the orderIt records what was discussed; it is not a tax invoice and obliges nobody
VAT lineA consumption tax charged and collected at sale in many marketsWhether a number in the buying entity's country changes anything is a local answer: CONFIRM-WITH-LOCAL-LEGAL
MOQA supplier's commercial floor for an order, not a technical minimumNever a document request, and never quoted by us

The habit worth building is one term sheet for the whole file, in which every abbreviation is written out in full once, with the name of the party who stands behind it. Three letters that mean a certificate of origin in one context and container on rail in another are exactly why the habit exists.

Where the smart lock itself enters the picture

A declaration describes a product, so a lock's own architecture is what the account is made of, and the buyer who understands the architecture can ask better questions about the scope.

The mechanical half is hardware the trade has described for a century: escutcheon, faceplate, strike plate, wrap-around plate, spindle, backset, keyway, shroud, euro-profile or rim cylinder, latch or deadlatch, bolt throw, single-point or multi-point locking, a clutch that lets the outside handle work without destroying the mechanism, surface mount or through-bolt fixing, jamb preparation, and in some schedules panic hardware and a door closer sharing the opening with the lock. The electrical half is what makes the life cycle longer and stranger than a mechanical one: a reader, a secure element holding a device-unique key, crypto rotation and firmware signing, an event memory and an audit log, standby current drawn continuously on a live door, a power source on a maintenance calendar, and a credential lifecycle that starts at user provisioning and ends at decommissioning.

Two features shape any sensible account of a lock's use phase. Standby current is drawn for years on every unit, installed in their tens of thousands. And the credential infrastructure — cards, fobs, templates, the readers that accept them — is a real material and energy cost of running a controlled door, which raises a scope question with no universal answer: does a product-level declaration cover the credentials that make the lock usable, or stop at the unit that ships?

Neither question is settled by a supplier's preference. Both are settled by reading the scope statement in the document you have and comparing it with the rubric you are being scored against. Where the answer matters for procurement, the material composition and finish choices behind these parts are handled in smart lock materials: complete buyer guide, and the credential side of the ledger is described in how a lock credential lifecycle works.

Radio exposure is worth one boundary note here, because it arrives in the same folder. The measure of radio-frequency energy absorbed by tissue is a radio-transmission question and says nothing about a lock's mechanical or security performance, and nothing about its environmental account either. If a radio-related document is offered as environmental evidence, the class of paper is wrong a second time.

What we do not say about this term

This reference defines a document class; it is not a statement about our own products. Nothing here is offered as a declaration, a verification, a test result or a performance figure, and nothing here says that any particular lock does or does not carry an environmental product declaration. Whether a specific model in a specific configuration is covered by a document of this class is answered by the document itself, produced and identified on request, and a general text cannot stand in for it.

What we will do is answer the question in the same shape the rest of this library uses: name the product, name the configuration, name the impact categories your rubric needs, and tell you which documents exist and which do not. Where an environmental line in a tender drives a configuration choice — a different power arrangement, a different reader, a different packaging route — that is a specification conversation and it belongs on the record before award rather than in a clarification email after the scoring closes. The route for it is /request-a-quote, and the same request that gets a price gets the document list. If you are assembling a pack rather than a price, /buyer-resources is where the term sheets and submittal formats live, and /quality-control covers the evidence classes we do produce.

A blank row for your own programme

The fastest way to find out whether your organisation understands the EPD definition is to fill the table below without asking anybody for help. Blank cells are the gap.

FieldYour answerWhere the answer comes from
The exact document name the rubric requiresThe tender or scheme text, quoted
The product identifier on your scheduleThe door and hardware schedule
The configuration you are actually buyingThe order confirmation
Which schedule lines a single document would coverYour own SKU list
The impact categories the rubric scoresThe scoring sheet
The life-cycle stages the rubric needsThe scheme, not the supplier
Who verifies, and who checks that verificationThe document and the assessor
Who owns the document after awardYour own record-keeping rule
What triggers a re-requestThe change-notice process
Who signs off the final submissionThe client's requirement

The last two rows are the ones that fail silently on live projects. A programme that cannot say who owns the environmental file after award will not notice when a change notice makes it wrong.

Questions to leave in the file

Some of these have no general answer, and knowing which is which is the point of the entry.

A general answer exists: what an environmental product declaration is; what it is not; which documents are adjacent to it; which scope fields a reviewer reads first; where in a transaction the term does its work.

A local answer exists, and it is not this article's to give: whether your tender rule requires the document, accepts a substitute, dates it, or scores its content; whether the buying entity's tax position is affected by anything environmental at all; what, in your jurisdiction, a product-level statement can lawfully be used to imply about a building. Those go to CONFIRM-WITH-LOCAL-LEGAL.

A per-supplier answer exists and is obtainable: which identified product, in which configuration, is covered by which dated document, verified by whom, and what changed after it was issued. Ask for it in the shape of the evidence table above and the answer arrives as paperwork rather than prose.

A per-product answer exists where the lock's own architecture decides the scope: what the use phase includes, and whether the credential infrastructure sits inside the account or outside it. Where a field check is needed rather than a document request, the door and frame preparation questions are covered in how a door is prepared for a lock.

The buyer who can hold the line — the definition, the scope, the identity of the paper and the identity of the person who verified it — does not need anybody else's opinion about what a lock's environmental document means. Not a verdict, not a certificate, not a claim about a building: a dated, scoped, independently reviewed description of a product, filed against the name of the product you are actually buying.

Giỏ hàng của bạn
Trải nghiệm của bạn trên trang web này sẽ được cải thiện bằng cách cho phép cookie Chính sách cookie
Chat on WhatsApp