Last updated: October 31, 2026 · Reviewed by export engineering
A tender panel does not read a certificate. It reads a file set against a clause list, and it scores each clause as met, partly met or not met. One missing page can cost the whole bid, which is why the useful question is not "are you certified" but "for this model, in this market, which of the clauses can you answer today and which need days". This page answers that question with a matrix, an issue-time table, and the redaction rules that decide what can leave the building.
The distinction between a certificate and a file set matters at the first shortlisting. A certificate is one page with one scope. A bid pack is an index, a set of reports, declarations, statements and drawings, each named to the tender's own clause numbering. A supplier who sends a folder of certificates has sent raw material; a supplier who sends a pack has done the assembly work, and the bid manager can see in 10 minutes whether the submission is complete.
Three things separate a pack from a certificate. First, the pack is organised by the tender, so each document sits against a clause and carries a page number that matches the index. Second, the pack states absences, because a tender panel that finds a missing item late marks the whole submission down. Third, the pack names the model, because a report issued for SLK-2020 at 306 mm x 75 mm x 15 mm does not cover a slim escutcheon or a different reader option, even when the electronics are the same.
The assembly rule we work to is simple: one model, one market, one pack. A pack that serves two models in two markets becomes a folder nobody can score. Where a tender covers several door types, the pack carries one section per model with its own index page, and the covering letter states which model is offered against which door. What each document covers is at certifications and compliance documents, and the standards are listed by name at standards.
Evidence check: a tender pack is complete when every clause in the buyer's list has either a document, a written statement of what is held, or a written statement that the item is not available for that model. Silence is the one answer a panel will not score.
Two common misunderstandings follow from this. The first is that an ISO 9001 certificate answers a product clause; it answers a process clause and the panel will treat it as such once it reads the scope. The second is that a report can be extended to a similar model by explanation; it cannot, because the scope describes a tested sample. Both points are set out in the comparison at certifications and in the testing route at the testing laboratory.

Compliance is not one file. It is a set assembled for a specific tender and a specific market, with each document attached to the model it covers and the scope it does not cover stated in writing.
The table maps five tender types to the files usually requested. It is a starting list for a clause review, not a legal opinion: the tender document itself defines what is mandatory, and the buyer's compliance adviser decides what a submission needs. The issue column is a service target from the desk, confirmed per request.
| Tender type | Usually mandatory | Usually optional | Typical issue window |
|---|---|---|---|
| Public building (ministry, municipal, transport) | Model test reports for EMC and safety, declaration of conformity naming the model, RoHS evidence, ISO 9001 certificate with its scope page, warranty statement, factory audit report | Fire-door assembly report where the schedule is fire rated, environmental policy, laboratory accreditation page, spare-parts list | Same day for files already held for the model; 3-5 days where a declaration has to be reissued with the buyer's project name |
| Hotel group (brand standard or management company) | Model test reports, fire-door evidence for corridor doors, finish sample and colour reference, declaration of conformity, installation manual, encoder and card specification | PMS interface statement, training plan, brand-standard compliance sheet, spare-parts list | Same day for held files; 1-2 days for a redacted review set; extra days where a finish has to be sampled |
| Education (school, campus, university) | Model test reports, declaration of conformity, warranty statement, authorisation and master-card policy statement, installation manual | Fire-door assembly report, vandal-resistance statement, batch programming record, training record | Same day for held files; 3-5 days for a policy statement written to the tender's wording |
| Residential developer | Model test reports, declaration of conformity, door compatibility sheet with leaf thickness in mm, warranty statement, packing and labelling specification | Fire report for corridor doors, finish samples, spare-parts list, handover training record | Same day for held files; 1-2 days for the compatibility sheet against a specific door schedule |
| Distributor tender | Model list with parameters, declarations, packaging specification, price schedule as a commercial annex, spare-parts list | Marketing assets, training plan, territory letter, sample arrangement | Same day for the model list; 3-5 days where the annex has to follow the buyer's price template |
Read the matrix with two cautions. A row describes what buyers in that segment usually ask for, not what every tender requires; the clause list wins. And the mandatory column is a product set for a battery-powered card lock, not for every product a factory sells: a 4G lock adds a radio question, a glass-door lock adds a door-type question, and a fire-door leaf adds an assembly question.
Where a tender asks for something outside the matrix, the answer is a clause note rather than a guess. A clause note states what is held, what is not held, and what producing the missing item would involve. That note is the document a bid manager can forward to the panel without editing it.
The question behind every bid schedule is whether the file set can be produced before the submission closes. The table separates the items that exist for a model from the items that require work. The windows are desk service targets confirmed in the reply to each request; they are not delivery commitments and they do not move with order volume.
| Item | Ready now | Takes days | What triggers the time |
|---|---|---|---|
| Model test report | Yes, where the model and market are covered | No | Nothing beyond a copy and a page count; the report is held as issued |
| Declaration of conformity | Yes, for the model as issued | 3-5 days where it must name the buyer's project or legal entity | A reissue needs a signatory, a new reference and a check against the report list |
| ISO 9001 certificate and scope page | Yes | 1-2 days for a scope letter written to the tender's wording | The letter has to be signed and matched to the certificate's scope |
| Fire-door assembly report | Yes, where the tested configuration matches the schedule | Not applicable where the configuration differs; that is a new test | Substitution of hinge, closer or leaf moves the request outside the report |
| EMC and safety reports | Yes, where held for the model | No | Copy only; the standards editions are those named on the report |
| RoHS evidence | Yes, as a declaration and material list | 1-2 days for a model-specific material list | The list has to be pulled from the current bill of materials |
| Redacted review set | No | 1-2 days | Redaction is prepared by hand, one page at a time, and checked twice |
| Translated document set | No | 3-10 days per language, depending on length | Translation plus a check that model codes and standard numbers survive intact |
| Notarised or apostilled copy | No | Quoted per request; the notary sets the date, not the factory | A public notary or a chamber of commerce handles the legalisation |
| New test for a new model | No | Quoted per test after a laboratory slot is confirmed | A new sample, a laboratory booking and a report cycle |
Two lines in that table decide most bid calendars. The redacted set takes days because redaction is manual, so a bid manager who needs it for a panel meeting should request it before the model is finalised rather than after. The new-test line takes as long as the laboratory takes, and no desk commitment changes that. Where a tender closes before a test can report, the honest options are to bid the model that already holds the paper or to ask the panel whether a test-in-progress letter is acceptable.
A document pack leaves the factory carrying information that belongs to other customers, to the factory's cost base and to the model's development history. The redaction rules below are the standard set. Anything outside them is a written request, and some requests are refused.
| Field | In a review set | Reason |
|---|---|---|
| Buyer or project name on a previous order | Redacted | Another customer's identity is not ours to disclose, even when the model is the same |
| Unit price and payment terms | Redacted | Commercial terms are specific to a quotation and a volume |
| Other customers' specifications and drawings | Redacted | A private-label drawing can describe a product that is not yet public |
| Tooling drawings and mould data | Redacted unless an NDA is signed | Tooling is the factory's development cost and sometimes the buyer's property |
| Model code, tested configuration and standard editions | Shown | These are the fields a panel must be able to verify |
| Laboratory name, accreditation number and report number | Shown | Without them the report cannot be traced to its issuer |
| Internal defect and rework statistics | Redacted in a tender pack | Internal quality data sits in the inspection report for the order, not in a bid pack |
| Certificate originals | Offered after the order is placed, or against a signed receipt | Originals are single copies and some markets require them with the shipment |
An NDA is the normal route for drawings and tooling data. It has to be signed before the drawings are sent, it has to name the entity receiving them, and it has to state what happens when the relationship ends. A verbal promise of confidentiality is not a route, and neither is a purchase order that mentions confidentiality in a footer. Where the buyer's own NDA template is used, we read it before signing rather than after.
Two limits are absolute. We do not provide a certificate, report or declaration that has been altered, and we do not issue a document that names a model we did not test. A request to "put our logo on the report" or to "change the model code on the certificate" is refused in writing, because an altered document is worse than a missing one at every stage of a tender. The scope rule behind that refusal is at certifications.
Biometric data and privacy documentation
UKCA declaration of conformity
Fire door assemblies and their hardware constraints
ANSI and BHMA grade references
How a document request is handled
Certification questions buyers ask mostThe assembly order below is the one that produces a pack a panel can score. Working in a different order usually produces a folder with documents that answer the same clause twice and no document for the clause nobody noticed.
The steps are sequential because each one depends on the last. A cover sheet written before the index will name a model the pack does not support; a translation started before redaction will translate fields that are later removed. The same discipline is used for a project schedule, described at project management.
Not included: the items below are outside what any factory document pack can supply. They are listed because a bid manager who expects them will build a schedule that cannot be met.
The boundary is not a negotiating position. A pack that promises one of these items will be corrected later, and the correction will usually arrive after the submission deadline. Bid managers plan around it: they bid the model that holds the paper, or they ask the panel a written question early enough to change the requirement.
Six checks catch most of the failures that cost a shortlisting, and each one takes minutes rather than hours. They are checks on the pack as submitted, not on the product, and they can be run by a bid manager without a technical background.
| Check | What to compare | What a correct pack shows |
|---|---|---|
| Clause coverage | Tender clause list against pack index | Every clause has a line, and every line has a page reference; no clause is answered twice by different documents |
| Model match | Model code on the report against the code in the offer | The code is identical, including finish and reader option, and the offer does not describe a variant the report omits |
| Standard edition | Standard year on the report against the tender's requirement | The edition is the one the tender names, or the pack explains the difference in the gap note |
| Signatory | Name and address on the declaration against the manufacturer named in the file | The entity that signs is the entity that builds, and the address matches the audited site |
| Page integrity | Index page numbers against the printed pages | No missing page, no duplicated page, and the total page count in the cover sheet is correct |
| Redaction | Review set against the release set | Commercial fields are removed consistently, and no redaction hides a field the panel needs to verify |
Evidence check: a pack is submission-ready when a reader who has never seen the model can follow the index, find the report number, read the scope paragraph and confirm the signatory without asking a question. That is a 10-minute test, and it is the same test the panel will run. Where the pack fails it, the fix belongs in the index or in the gap note.
The underlying reports come from the testing route described at the testing laboratory and quality control. The factory's audit trail and site scope are at the factory tour, and the market-by-market document logic is at certifications.
For a single model and a single market, yes, once the model file is checked against the clause list. The reply is an index with each clause marked as held, to be produced, or not available. Where several models or markets are involved, the pack is split into sections and each section gets its own index, because a combined pack is harder to score and easier to misread.
No. A certificate and a test report name the manufacturer and the model that was tested. What can be issued in your name is a statement about the documents held for the model, and a private-label agreement can define how your brand appears on the product and the packaging. The scope rule behind this is explained at certifications.
A service target of 1-2 days for a single model, confirmed in the reply to the request. Redaction is manual, so a pack covering several models or a long report set takes longer and is quoted per set. Asking before the model is finalised is the practical move, because redaction can then be prepared once rather than twice.
Yes, and we read it before signing. The NDA must name the receiving entity, define what counts as confidential, and state what happens to the drawings when the relationship ends. We do not send tooling drawings, private-label artwork or another customer's file before the NDA is signed, and a purchase order footer does not replace it.
The gap note says so, names what is held instead, and states what a test against the named standard would involve. The bid manager then chooses: commission the test, offer a model that already holds the evidence, or bid with the gap declared. What we will not do is describe an untested configuration as compliant in a covering letter.
Only where the lock sits inside the tested configuration. A fire-door report covers leaf, frame, hinges, latch or lock, closer and coordinating devices as one assembly. If your schedule substitutes a closer or a hinge, the report does not follow the substitution, and the honest route is a new evaluation or a different hardware set.
Yes, for the documents the tender names. Translation is a service target of 3-10 days per language depending on length, confirmed per request. Model codes, standard numbers and report references are checked after translation, because a mistyped report number is the fastest way to lose a panel's confidence.
The pack becomes the order file. The documents that were redacted for review are released in full where the market requires it, originals travel with the shipment where a paper copy is needed, and the model document list is attached to the order so the next reorder starts from the same evidence. The handover file is described at project management.
The fastest route to a complete pack is the clause list itself. Send the tender document with the clauses numbered, the model or models you intend to offer, the destination market and the submission date. The reply is an index that marks each clause as held, to be produced or not available. A pack requested without a clause list comes back as a general document set, useful for reading and not for scoring.
Send the numbered clauses, the model codes and the submission date. The reply is an index with a held or gap status on every line.
Model-specific certificates and test reports are supplied on request; the certificate belongs to the model, not to the factory. Current MOQ policy and lead time are confirmed in writing with each quotation.
Request a tender document packAsk the export desk