In short. Possessing a document is not the same as having proof. A brochure, a datasheet, an inspection checklist, a load test report and a certificate each carry a different evidential weight, and each applies only to the equipment, configuration, date and scope it names. We label each document with an evidence status and a claim boundary, so you can see what is established and what still needs verification.
Why evidence status needs to be stated
Generator decisions are often made on the strength of a file someone forwarded. A brochure from 2009 is used to prove a current rating. A no-load start after a service visit is treated as proof that a standby set will carry the plant. An old certificate issued to a differently named firm is presented as a current credential. None of these documents is necessarily false, but each is being asked to prove more than it can. Stating the evidence status and the claim boundary alongside every document makes the limitation visible wherever the document is used to support a decision.
The evidence status labels we use
| Status | Meaning | Can support | Cannot support |
|---|---|---|---|
| Verified current | Issuer, revision and applicability checked against the named equipment or entity within the stated period | Technical and compliance decisions for that configuration | Other models, revisions or dates |
| Representative | Typical data for a product family or application, not matched to a specific serial number | Preliminary sizing, budgeting, orientation | Final selection, parts ordering, compliance |
| Historical | Genuine at the time of issue, not confirmed as current | Statements about the period and entity named | Present capability, present registration, present ratings |
| Pending verification | Document or claim held but checks not completed | Identifying what to verify next | Any decision that depends on it |
| Restricted | Held under licence, confidentiality or customer ownership | Work by authorised personnel | Public download or redistribution |
A status applies to a specific revision of a specific file matched to a specific machine or claim. Revised copy, changed equipment or a new claim needs a fresh assessment, and the reviewer, date and accepted scope are recorded so that approval cannot quietly transfer to a different version.
What different records actually prove
Inspection records
An inspection proves the condition of the items inspected, on the date inspected, within the scope written on the form. A battery and charger inspection that records a healthy float voltage says nothing about whether the set will accept load. An ATS inspection checklist with every box ticked does not prove transfer readiness unless a transfer was actually performed and recorded.
Test records
A load test proves that the set carried the recorded load for the recorded duration under the recorded conditions, with the voltage, frequency and temperature observations written down. It does not prove performance at a higher load, on a hotter day, or after another year of standby. A load bank test is strong evidence precisely because it is bounded, and a good report states its boundaries.
Service and repair records
A fault diagnosis is a hypothesis supported by measurements. It becomes proof of correction only when the repair has been made and the function retested. A record that says the AVR was replaced proves the AVR was replaced; the retest record proves the voltage regulation is now correct.
Photographs and video
A photograph is evidence of the observed condition at the moment it was taken. It shows a set positioned for temporary power, or a panel under review, and nothing more. We publish media only with a visible scope, an evidence status and a claim boundary, and only after a confidentiality and safety check. A photograph of a rental set on a site does not claim that the site had uninterrupted production, and a photograph of an ATS does not prove it transferred.
Certificates and registrations
A certificate supports a statement about the entity it names, for the scope it names, between its validity dates. Check the dates and the legal identity. Where records use different business names or legal forms over the years, establish which entity the record belongs to before linking it to a current statement. We do not publish a corporate certification unless it exists, is valid, belongs to the relevant entity and is described with its true scope.
Claim boundaries in practice
A claim boundary is a one-line statement of what a document or page does not establish. Examples from our own records read as follows.
- A rental deployment record confirms that a set was supplied for the stated period; it does not establish that fuel, cables, distribution or an operator were included unless the scope says so.
- A commissioning report confirms the functions tested on the date tested; it does not guarantee future automatic start, which depends on battery, fuel and maintenance after handover.
- A test result applies only to the defined load, date, duration and ambient conditions recorded on it.
- A project description summarises an approved category of work without naming the customer or site unless the customer has agreed in writing.
The projects pages follow these boundaries. Where a project is described, the evidence behind it is stated, and where a customer has not approved disclosure the description stays general. The quality, safety and compliance philosophy explains why we work this way.
Applying the same discipline to documents you receive
The same five questions apply to any document a supplier sends you. Who issued it, which revision is it, which equipment or entity does it name, what did it actually test or certify, and when does it stop being valid. A supplier who can answer all five quickly, and who tells you which of their claims are pending verification, is usually the supplier whose equipment will behave as described. The technical library and the datasheets and brochures guide apply these checks to specific document types, and the fire and site safety page shows how statutory evidence differs from manufacturer evidence.
Common mistakes
- Treating a no-load start as proof of standby readiness, which hides fuel delivery, cooling and load acceptance problems until the first real outage.
- Using a historical brochure to establish a current rating or capability, which leads to tenders written against equipment that is no longer built to that specification.
- Accepting an inspection checklist as proof of ATS readiness, which leaves the transfer sequence untested until mains fails.
- Linking an old certificate to a current entity without checking the dates and the legal name, which can invalidate a compliance submission.
- Letting an approval carry over to a revised document without review, so that a changed figure goes unnoticed.
What to send us
If you need us to confirm what a document proves, send the file with its issuer, revision and date visible, the nameplate photographs of the equipment it is meant to describe, and the decision it has to support. If you need a test or inspection record created, tell us the scope you need proven, for example a four-hour load test at 75 percent of rating or a full mains failure transfer test, and the hours run and last service date of the set. Contact us with the details and we will state the evidence status plainly.
Questions engineers ask
What is the difference between an inspection report and a test report?
An inspection records observed condition without operating the function under load. A test operates the function and records the result against stated conditions. For a standby generator you need both: inspection for readiness items such as battery, fuel and coolant, and a test for load acceptance and transfer.
Does a successful load bank test prove my generator will survive the next outage?
It proves the engine and alternator carried the tested load on that day. It does not test the mains failure sensing, the ATS or the real plant load’s starting behaviour unless those were part of the test. A full mains failure simulation covers the whole chain.
Why do you label some data as representative?
Because it is typical for a product family and useful for early planning, but it has not been matched to a specific serial number and build. Final selection and parts ordering need verified data for the exact machine.
How long is a certificate or test record valid?
A certificate is valid between the dates printed on it, for the entity and scope named. A test record is valid as evidence of the condition on the test date; its usefulness as a predictor declines with time, use and any change to the equipment. Annual retesting is a common and sensible interval for standby sets.
Why do your project descriptions not name customers?
Customer identity, exact site details and load information are confidential unless the customer agrees in writing to disclosure. We describe the category of work and the evidence behind it, and we state the claim boundary so the description is not read as more than it is.
Technical content reviewed by D. Srinivas Reddy, Managing Partner and Service Engineer, Reddy Generators. Last updated 19 October 2026.