
Two documents arrive at the same project within a week of each other. One is a brand’s sustainability checklist, written by an operator to describe what it wants evidenced. The other is a purchaser’s certification list, written to establish what may legally be supplied. They look similar, they use some of the same words, and they are not the same kind of instrument. Most of the avoidable conflict in a hotel lighting package comes from treating them as though they were.
The pattern is familiar to anyone who has run a FF&E submittal in the last few years. The operator’s design guide has acquired a sustainability appendix. The purchasing department has its own compliance schedule, usually older, usually written for market access rather than for reporting. The lighting supplier receives both, is asked to complete both, and discovers that a handful of lines cannot be answered the way either document expects. What happens next depends less on the product than on whether anyone has built a crosswalk between the two.
This article sets out that crosswalk. It separates what each list is actually for, identifies the four kinds of item that appear in both, names the five places where they collide in practice, and describes how to write an answer that neither overstates what is held nor loses a project over a gap that could have been named. It does not resolve any particular scheme’s requirements, because those change by market and by version; it describes the shape of the problem, which does not change.
- 01Two Lists, Two Different Jobs
- 02Why They Rarely Align
- 03The Four Kinds of Item You Will Meet
- 04What a Brand Checklist Is Actually Buying
- 05What a Certification List Is Actually Requiring
- 06Five Places the Lists Collide
- 07The Crosswalk Method
- 08The Answer That Survives an Audit
- 09Who Signs What
- 10Writing It Into the Tender
Two Lists, Two Different Jobs
A brand sustainability checklist is a reporting instrument. It exists because the operator has committed to someone, an investor, a lender, a corporate reporting function or its own board, that it will be able to describe the environmental characteristics of its buildings. The checklist is the mechanism by which a property supplies that description. Its purpose is to produce statements the operator can stand behind at group level.
A buyer certification list is a market-access instrument. It exists because a product cannot be placed on sale in a given territory without demonstrating conformity with that territory’s requirements. Its purpose is to keep non-conforming product out of the market, and it is enforced by authorities rather than by the operator.
Those two purposes produce documents with different logic, and the difference shows up in four places. A checklist asks about characteristics of a product or a project; a certification list asks about conformity of a product. A checklist is usually answered by the supplier and accepted by the operator; a certification list is answered by a test report and accepted by an authority. A checklist changes when the operator’s reporting framework changes; a certification list changes when the regulation changes. And a checklist can contain items that have no product-level answer at all, while a certification list is, by construction, made only of items that do.
Once that is clear, the practical consequence follows. A supplier cannot treat the two documents as one exercise, and a buyer cannot accept a single answer for both. The same certificate cannot satisfy a checklist item about material provenance, and the same declaration cannot satisfy a conformity requirement. The rest of this article is about how to hold both in view without duplicating work.
Why They Rarely Align
Four structural differences explain almost all of the misalignment, and each of them produces a specific kind of missing answer.
They describe different objects. The checklist is usually written about a building, a room type or a project, because that is the unit the operator reports on. The certification list is written about a product, because that is the unit that enters the market. A guestroom contains a dozen lighting products, a ceiling void and a control system; a checklist item about “lighting” in a guestroom is a compound question, while a certificate is a single-product document. The supplier is therefore asked a question at a level it does not sell at.
They measure different things. A checklist tends to ask about characteristics: what a product is made of, how much energy it uses in operation, whether it can be repaired, whether its components can be separated. A certification list tends to ask about conformity: whether the product meets a safety requirement, an ingress requirement, an electromagnetic requirement. Characteristics and conformity are independent. A product can be excellent on one and compliant on the other, or the reverse.
They have different owners. The checklist belongs to a sustainability or design function inside the operator’s organisation, and it is often new. The certification list belongs to purchasing or compliance, and it is often inherited from a previous project and not fully re-read. Where a checklist item and a certification item appear to conflict, the two owners may not have spoken to each other, and neither may have authority over the other’s list.
They move at different speeds. Reporting frameworks are revised on a cycle set by the operator and its advisors. Regulations are revised on a cycle set by the market. A project that starts under one version of each and completes under another is normal. A submittal that does not record which version it answered will be read later as though it answered the current one.
None of this is anyone’s fault in particular. It is what happens when a reporting instrument and a market-access instrument are applied to the same purchase order. The remedy is procedural: name the object, name the property, name the owner and name the version, on every line.
The Four Kinds of Item You Will Meet
When both lists are laid side by side, the items sort into four kinds. The sorting is worth doing before anything is answered, because each kind needs a different document and a different signatory, and mixing them is the root of most wasted effort.
| Kind of item | What it asks | Who issues the evidence | Typical scope error |
|---|---|---|---|
| Conformity | Does the product meet a mandatory requirement for this market? | An accredited test laboratory, with the manufacturer’s declaration | Assuming a conformity mark says something about material, repairability or energy in use |
| Performance | How does the product behave, measured in a defined way? | An accredited laboratory, or the manufacturer under a stated method | Applying a performance result obtained on one variant to a different size or finish |
| Management system | Does the organisation operate a recognised process for quality, environment or similar? | A certification body, against the organisation, not the product | Presenting an organisation-level certificate as evidence about a specific product |
| Declaration | What does the supplier state about the product’s characteristics, and on what basis? | The manufacturer, sometimes with third-party verification | Offering a declaration where a verified document was requested, or the reverse |
The management-system row deserves emphasis because it is the most frequently misread. A certificate issued to an organisation confirms that the organisation operates a process. It does not confirm that any particular product was made under that process, and it says nothing about the product’s characteristics. When a brand checklist asks for evidence of environmental management, a management-system certificate is a reasonable answer. When a buyer’s list asks for it in a product-level column, the answer belongs at organisation level and should be recorded as such, not silently promoted.
The declaration row is where the most useful work happens, because most of a lighting supplier’s real answers live there. Declarations are legitimate, they are the normal instrument for characteristics that no regulation tests, and they carry an obligation: the issuer must hold the basis. A declaration without a stated basis is not a weaker document than a verified one; it is a different thing altogether.
What a Brand Checklist Is Actually Buying
It helps to be precise about the transaction. When an operator sends a sustainability checklist to a supplier, it is not buying a product property. It is buying a defensible sentence for its own reporting, and it needs that sentence to survive an internal review and possibly an external assurance process.
Three requirements follow from that, and they explain most of the questions that seem unreasonable to a supplier. First, the statement has to be attributable: the operator needs to know who said it, so that if it is challenged it can be traced. Second, it has to be dated, because the reporting period matters. Third, it has to be bounded, because a statement that overreaches is worse for the operator than a narrower statement that holds.
This is why a well-run checklist asks for document references rather than for adjectives, and why a supplier’s willingness to name a gap is valued rather than penalised. A checklist answer that reads “declared at material level, certificate attached, diffuser not assessed” gives the operator something it can put in a report. An answer that reads “sustainable materials used throughout” gives it a liability.
There is a live example of how these checklists have tightened. A global hotel group published an all-electric prototype design this year, offered to owners as a repeatable model for new-build projects, and its accompanying sustainability list names LED lighting among the required items alongside other building measures. The significance is not the specific technology, which the industry has specified for years. It is that lighting has moved from a design decision into a checklist line with an owner, a document and a reporting consequence. Once a brand’s checklist names an item, the supplier’s answer becomes part of the operator’s reporting chain, and the standard of evidence rises accordingly.
For the buyer, the practical reading is this: a brand checklist item should be answered at the level the operator reports at, with a named document and a date, and with an explicit statement of what the document does not cover. That last clause is not a concession. It is what makes the answer usable.
What a Certification List Is Actually Requiring
A certification list is narrower and harder. It is narrower because each item usually corresponds to a defined requirement with a defined test and a defined threshold. It is harder because the consequence of a missing item is not a weaker report but a blocked shipment.

Three features of this kind of list cause trouble in a lighting package. The first is that requirements attach to the product as placed on the market, which means the version, the variant and the model reference all matter. A report for one variant of a family is not a report for the family. The second is that some requirements attach to the installation rather than to the product, so the product certificate is necessary but not sufficient, and the responsibility for the remainder sits with the project rather than the factory. The third is that the list is usually written for the destination market, and a project sourcing across borders can end up with two lists that both apply to different parts of the same building.
That last point is worth spelling out, because it is where dual-brand and cross-border projects fail. If a fixture is bought for a property in one market but specified under a brand standard written in another, the certification list that governs the shipment and the list that governs the brand may not be the same list. Neither is wrong. They are answering different questions, and the submittal has to show both answers rather than choosing one.
The correct handling of a certification item is therefore procedural and rather boring: identify the requirement, identify the market, identify the product variant, obtain the report that corresponds to all three, and record the date. Where a report exists for a related variant, record it as related rather than as held. Where a requirement attaches to the installation, record it against the installer’s scope and not the factory’s. Our guide to how lighting certifications work covers the document types in more detail; the point here is the bookkeeping discipline, because that is what the two lists have in common.
Five Places the Lists Collide
With both lists sorted, the collisions become predictable. Five types account for almost every real dispute, and each has a standard resolution that does not require either side to abandon its document.
| Collision | What it looks like | Resolution |
|---|---|---|
| An item with no product-level answer | The brand asks about a building characteristic, such as how a space is commissioned, in a column that expects a product document | Answer at project level and name the party responsible; record the product line as not applicable, with a reason |
| A requirement the brand does not ask for | The buyer’s list includes a market-access requirement that the checklist omits entirely | Keep both. Answer the certification item as conformity and the checklist item as characteristic; do not merge them into one line |
| The same word at different scope | Both lists ask about energy, one meaning consumption in operation and the other meaning a declared rating for a component | Define the term in the submittal before answering; a footnote in the schedule prevents the argument later |
| An organisation certificate in a product column | A management-system certificate offered as evidence for a specific model | Record at organisation level, and state plainly that it does not attach to the product |
| A version or date mismatch | The document predates a design change, a finish change or a component substitution | Re-issue or re-confirm; treat a document older than the last design revision as open, not held |
The first collision is the one that most often escalates, because it looks like a refusal. A supplier receiving a building-level question in a product-level column has three options: ignore it, invent an answer, or explain the mismatch. Only the third is useful, and it is only possible if the submittal has somewhere to record a not-applicable item with a reason. A schedule without that column forces the supplier into one of the first two options, which is how a checklist ends up with a plausible answer that nobody can support.
The third collision, the same word at different scope, is the quietest and the most expensive. Energy is the usual example. A brand checklist asking about energy may be asking about the operating consumption of the installation, which is a design question involving controls and hours of use. A buyer’s list may be asking about a declared rating for a lamp or a driver, which is a component document. Both are legitimate, neither substitutes for the other, and a submittal that answers “energy” once will be read as answering whichever question the reader had in mind. Defining the term costs one line and prevents a variation order.
The Crosswalk Method
The crosswalk is a single table with five columns, built once per project, and it replaces a great deal of correspondence.
Column one: the brand item, as written. Copied verbatim, with the checklist version recorded. Paraphrasing at this stage loses the wording that the operator’s reporting will later be checked against.
Column two: the certification item, as written, or a note that none exists. Many brand items have no certification counterpart, and saying so is part of the work. The reverse also occurs: a certification requirement with no checklist line, which is common where the checklist was written for a different market.
Column three: the kind of evidence, using the four kinds from earlier. Conformity, performance, management system or declaration. This column is what stops a declaration being offered where a report was required, and the reverse.
Column four: the owner. Not the supplier in general, but the party who will produce the document: the factory, the glassworks, the driver supplier, the test laboratory, the installer, the commissioning agent. An item with no named owner is an item that will still be open at handover.
Column five: residual risk. What remains true even when the document arrives. This is the column that experienced buyers value most, because it records the difference between what the document proves and what the project needs. A material certificate with a residual note that the finish layer is not covered is a stronger submittal than the same certificate presented as a complete answer.
Two rules keep the crosswalk honest. The first is that a row is answered only when a dated document exists and is referenced; until then it is open, and open rows are reported as open. The second is that the crosswalk is versioned along with the design. A crosswalk that answers revision A and is used at revision C is worse than no crosswalk, because it carries the appearance of control.

The crosswalk also changes the conversation with the operator, and this is worth anticipating. Once the brand’s checklist items are mapped to evidence types, some of them turn out to be unanswerable at product level, and a few turn out to be unanswerable at all in the current state of the supply chain. Raising that early is uncomfortable and it is the most reliable route to a checklist that can be signed. The alternative is a submittal full of confident answers that collapse at the first assurance review, which is a worse outcome for everyone including the supplier.
The Answer That Survives an Audit
A supplier’s answer to either list should have three parts, in this order, and the order matters because it prevents the reader from inferring more than was said.
What is held. The document, its issuer, its date, and the exact product or component it covers. Named, not described. If the document covers a variant, say which variant.
What is not held. The specific gap, stated plainly. Not “we are working on it” as a substitute for a gap, and not silence. A gap named by the supplier is a manageable item; a gap discovered by an auditor is an incident.
What will be produced, by whom and by when. A commitment with a date and a named issuer, or an explicit statement that no document will be produced because the chain does not generate one.
The failure mode this structure prevents is the migration of a pending item into a held item. In practice, a document described as “in progress” enters a submittal pack, is summarised in a covering note, and by the time it reaches the operator’s reporting function it is indistinguishable from a document that exists. The corrective is mechanical: a register where every row has a state, and a rule that only a dated file changes the state.
There is a second failure mode worth naming, because it is specific to certification lists. A supplier holding a report for one variant may reasonably believe it covers a closely related one, and in a commercial conversation that belief is often expressed as coverage. In a compliance conversation it is not coverage, and the difference has consequences at customs. The safe formulation is to state what the document covers and to treat everything else as a separate row, however similar the products look.
Finally, the answer should say what the document does not prove. A test report proves performance under the tested conditions. A declaration of conformity proves compliance with the declared requirement. A material certificate proves what the material is. None of them proves that a particular installation will work, that a finish will last, or that a component will remain available. Stating that boundary is not hedging. It is the part of the answer that a competent reviewer is looking for.
Who Signs What
Responsibility in a two-list project is distributed, and most of the friction comes from people assuming it is not. Four roles matter, and each signs a different thing.
The operator’s sustainability function owns the checklist and the reporting statement that follows from it. It decides whether a declared item is acceptable or whether verified evidence is required, and it is the party able to accept a narrower answer than the checklist asked for.
The buyer or purchasing function owns the certification list and the commercial consequence of a missing item. It decides whether a shipment can proceed, and it is the party that a factory will call when a document is late.
The factory’s quality function owns the product-level documents and the accuracy of what is declared. It signs the declaration and holds the basis, and it is the party that will be asked to defend the declaration years later.
The third-party laboratory or certification body owns the test result or the organisation certificate, within the scope it was engaged for. It does not certify a project, does not certify an installation and does not certify that a family of products shares a result obtained on one variant. Where a body is asked to do any of those things, the correct answer is that the scope does not extend there.
The boundary that causes most trouble sits between the second and third of those. A buyer’s list is written by a party that wants certainty about a shipment; a laboratory issues a result about a sample. The gap between the two is filled by the factory’s declaration and by the buyer’s acceptance of it, and there is no document that closes the gap entirely. Projects that understand this build the acceptance step into the schedule. Projects that do not spend the last month before handover exchanging emails about a report that was not going to cover the question.
Writing It Into the Tender
All of the above becomes much easier if the tender documents do four things. None of them is unusual, and each of them removes a category of argument.
Name the version of each list. The checklist version and the certification list version, with dates, in the tender. A supplier answering an unversioned list is answering a moving target, and the answer will be read against whatever version is current at audit.
Ask for the crosswalk, not just the answers. Requiring a five-column crosswalk at tender stage costs a supplier a few hours and gives the buyer a document it can manage for the life of the project. It also reveals, before award, which items are unanswerable.
Provide a not-applicable column with a reason field. Without it, building-level questions in product-level rows will be answered with something invented. With it, the honest answer becomes the easy answer.
State the remedy for an open item. What happens at handover if a row is still open: a retention, a substitution, a recorded exception signed by the operator. A requirement without a stated consequence becomes a negotiation, and negotiations at handover are conducted by whoever is under most pressure.
One further clause is worth adding for lighting specifically: require the product reference, the variant and the finish to appear on every document. Most scope errors in this area are variant errors, and they are cheap to prevent at tender and expensive to resolve at shipment. The same discipline underlies our note on what a standard actually requires of a lighting specification and our guide to auditing a specification sheet for internal consistency; both are about the same underlying habit, which is to name the object before answering the question.
The closing point is that the two lists are not in competition. A brand checklist and a certification list ask different questions about the same fixture, and a project needs both answers. The work is not to reconcile them into one document but to keep them separate, map them once, and record the state of every row. A supplier that can do that is easier to buy from than one that cannot, and an operator that asks for it gets a reporting statement it can defend. On a project with a sustainability appendix and a compliance schedule, that is most of the battle.
Frequently Asked Questions
Can one certificate satisfy both a brand checklist and a certification list?
Usually not, because they ask about different properties. A checklist tends to ask about characteristics, such as material or repairability, while a certification list asks about conformity with a mandatory requirement. The two are independent: a product can conform fully and have weak characteristics, or the reverse. Each needs its own evidence.
What is the difference between a performance document and a conformity document?
A conformity document states that a product meets a mandatory requirement for a market. A performance document reports how the product behaved when measured in a defined way. Conformity is a gate; performance is data. A performance result can support a design decision without establishing conformity, and conformity can be established without any useful performance data.
Why is an organisation certificate not product evidence?
Because it is issued to the organisation and confirms that a process is operated. It does not confirm that a specific product was made under that process, and it says nothing about the product’s characteristics. It is the right answer to a question about management, and the wrong answer to a question about a model.
The brand asks about something with no product-level answer. What do we do?
Answer at the level where the answer exists and name the party responsible, then record the product line as not applicable with a reason. This requires the schedule to provide a not-applicable column. Without one, the supplier is forced to invent an answer or leave a blank, and both are worse than an honest mismatch.
What happens if the test report predates a design change?
It becomes an open item rather than a held one. A report covers the configuration that was tested, so a change to a component, a finish or a dimension puts the coverage in question. The correct action is to re-confirm or re-test, and until that is done the row stays open regardless of how minor the change appears.
How should a project handle two certification lists that both apply?
Keep both, and record which one governs the shipment and which one governs the brand standard. On dual-brand or cross-border projects this is common and neither list is wrong. The submittal has to show both answers rather than selecting one, because the shipment and the brand are separate obligations.
Is a crosswalk worth building if the project is small?
It is proportionally more valuable on a small project, because a small project has fewer people to absorb an ambiguity. A single table with five columns, built at tender stage and updated at each design revision, is a few hours of work and it removes the most common cause of a delayed handover.
Holding a Brand Checklist and a Certification List at Once?
Send us both documents with their versions, the destination markets and the product references you are specifying, and we will return a crosswalk that separates conformity from characteristics, names the owner of each item and states where we cannot produce evidence. We would rather answer a checklist honestly than defend a sentence we did not write.
Our hotel lighting section collects the specification notes for project work, and the ceiling lamp, floor lamp and about us pages set out how we document the products we supply.













