Write the statements your organisation may make about a product, back each with a test result or written reasoning, send it through approval, withdraw it when it no longer holds, and let Tenders offer only the claims that can still be asserted.
A claim is a statement your organisation may make about a product, such as "IP67 rated", "Qualified to MIL-STD-810H" or "CE marked under MDR Annex IX". In a tender response a claim is a contractual representation, so each one records the exact wording, what backs it and who approved it. Only an approved claim whose evidence still holds is offered to a bid.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Action | Who |
|---|---|
See claims | Anyone with View Products ( |
Add claims, edit them and delete drafts | Manage Product Claims ( |
Approve or reject drafts, and withdraw approved claims | Approve Product Claims ( |
Writing and approving are separate permissions, so the person who drafts a claim need not be the person who asserts it. Admins can do all of these, and buttons appear only for people who can use them.
A claim follows the classification of the version it describes. A claim that applies to all versions follows the most restricted classification any version of the product holds. You see only the claims your clearance allows; see clearances.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Open Products and choose the product in the Product register.
Choose the Claims tab.
The tab lists every claim for the product, whatever version it applies to. Each entry shows the claim text; its kind, version (or All configurations) and market (or All markets); the test it is backed by; Approved by and the approver's name with the date it is valid until; and a status badge.
If any approved claim can no longer be asserted, an amber warning appears at the top: Some approved claims can no longer be asserted, with a count and the advice to update the evidence or withdraw the claim.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Select the version the claim is about, if it applies to one version only.
Choose Add claim.
Complete the fields below.
Choose Save claim. The button is available once Claim has text.
Field | What it does | Rules and defaults |
|---|---|---|
Claim | The finished sentence as a customer would read it. This is the wording the approver accepts. | Required, up to 4,000 characters. |
Kind | What the claim is about; see the next section. | Defaults to Performance. |
Market | Where the claim holds. | Defaults to All markets. Choose a market only when the claim is true there alone; regulatory claims usually are. |
Applies only to configuration followed by the version label | Limits the claim to the selected version. | Ticked by default. Clear it when the claim holds for every version. |
Backed by test | The test result that substantiates the claim. | No test — substantiated in writing, or one of the selected version's passed results that is still valid. |
Reasoning | Why the claim is true: the specification, standard or argument it rests on. | Optional, up to 20,000 characters. |
Validity dates | The date the claim takes effect and the date it ends, when the claim is time-limited. | Optional. The end date cannot be before the start date. |
Substantiating document | A document in a document vault that supports the claim, such as a declaration of conformity. | Optional. |
A new claim is always a Draft. Nothing is offered to a bid until someone approves it.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Kind | Typical claim |
|---|---|
Performance | A rating or capability: "Operates from minus 40 to plus 70 degrees Celsius." |
Safety | "Meets IEC 62368-1." |
Environmental | "RoHS compliant." |
Regulatory | "CE marked under MDR Annex IX." |
Quality | "Manufactured under ISO 9001." |
Security | "Firmware signed and verified at boot." |
Commercial | "Ten-year spare-parts availability." |
Other | Anything that fits none of the above. |
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Back a claim with a test when one exists. A linked test makes the claim lapse visibly when the test does, instead of the sentence quietly outliving its evidence. Only passed results that are still valid on the selected version are offered, and the test must belong to this product. A waived test never backs a claim.
When no test applies, choose No test — substantiated in writing and explain the basis in Reasoning, adding a substantiating document where you have one. A claim substantiated in writing does not lapse on its own; give it an end date if it should.
When your organisation has set it up, Propose claims from evidence opens the assistant. It reads the version's specifications, passed results and authorizations and proposes draft claims, each with the record that backs it. Where nothing substantiates a claim, it says so instead of proposing it. Its proposals appear in the list as Draft and go through approval like any other claim. See the Product Specialist assistant.
With no claims yet, the tab explains A claim needs something to stand on: record specifications, qualification results or market authorizations first.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
A draft shows Approve, Reject and a bin button (Delete claim).
Approve makes the claim available to bids and records you as the approver, shown as Approved by and your name. Approval is refused while the backing test no longer holds, for example "This claim cannot be approved: The test behind this claim has expired. Update the substantiation, or record a current test result, first."
Reject marks the draft Rejected. Only drafts can be rejected.
Delete claim removes a draft after you confirm Delete this claim?. Only a draft can be deleted, and this cannot be undone.
A rejected claim stays in the list as the record of that decision. To put the statement forward again, add it as a new claim.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Approval alone does not make a claim usable. A claim is assertable, and offered to bids, only while all of these hold:
it is Approved;
its start date, if any, has arrived;
neither its own end date nor its backing test's Valid until date has passed;
its backing test, if any, passed.
The until date on a claim is the earlier of its own end date and its test's Valid until date. When an approved claim stops being assertable, its badge changes from Approved to Cannot be asserted in amber, and a line under it says why:
Reason shown | What to do |
|---|---|
This claim has not been approved. | Ask an approver to review the draft. |
This claim was reviewed and rejected. | Add a new claim if the statement should be made. |
This claim has been withdrawn. | None; the withdrawal reason is on record. |
The test behind this claim did not pass. | Link a passed test, or withdraw the claim. |
The test behind this claim has expired. | Record a current result on Qualification, then edit the claim to use it. |
This claim is past its own expiry date. | Edit the dates, or withdraw the claim. |
This claim is not yet in effect. | Wait for its start date. |
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
Holders of Manage Product Claims can edit a claim's wording, kind, market, version scope, backing test, reasoning, dates and document. Editing an approved claim returns it to Draft and clears the approval: the approval was given for a particular sentence with particular evidence, so the changed claim must be approved again before bids can use it.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
An approved claim leaves use only by withdrawal, with a reason.
Choose Withdraw on the approved claim.
In Why is this claim being withdrawn?, say why the organisation stopped making it. The reason is kept permanently.
Choose Withdraw claim. The button is available once the reason has text.
The claim shows Withdrawn and is no longer offered to bids.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender workspace and choose the Products tab.
In a tender workspace, the Products tab (What this tender bids) links the tender to the product:
Choose Bid a product, find the product, and choose the Configuration and the Market being bid into. Choose Bid this configuration. Only a version that is released and in a marketable lifecycle state can be bid, and the bid is refused when the export check for that market does not permit it; see export control.
Under Proposed answers, choose Propose answers. ComplyTrain matches the tender's requirements against what the bound version holds: passed results that are still valid, assertable claims, the marketed name and the placement's authorizations.
Review each proposal. A claim is proposed with its own wording and the attribution "Approved claim", the approver and the backing test. It shows a match percentage. Choose Accept, Edit or Reject.
Only claims for that version or for all configurations, and for that market or all markets, are offered; version-specific and market-specific claims come first. Nothing reaches the response until a person accepts or edits it. A claim's proposal can be accepted only while the claim is still assertable: approved, its backing test passed and in date, and its own dates open. If that changes before you decide, the proposal says "The evidence behind this proposal has lapsed, so it cannot be accepted. Reject it and propose again."
Looking up products from a tender needs the Products module and View Products.
Product location: /products/{productId}/claims (fallback: /products). Open the product in Products, select the version the claim is about, then choose the Claims tab.
The product's version 3.1 passed an IP67 test, valid until the end of 2027.
On Claims, with 3.1 selected, choose Add claim. Enter "The enclosure is rated IP67 to IEC 60529." Set Kind to Performance, leave Market as All markets, keep Applies only to configuration 3.1 ticked, and choose the IP67 result in Backed by test. Choose Save claim.
The quality manager, who holds Approve Product Claims, reviews the draft and chooses Approve. The claim shows Approved by and their name, until 31 December 2027.
A bid manager binds version 3.1 to a tender for Denmark and chooses Propose answers. The claim is proposed against the requirement "State the ingress protection rating", and they choose Accept.
In January 2028 the claim changes to Cannot be asserted, "The test behind this claim has expired.", and stops being offered to new bids until a new result is recorded and linked.
