The short answer: track a register, not a folder

A polyphosphate supplier file almost never fails because a document is missing. It fails because a document that was valid when it was filed quietly expired, and nobody noticed until a customer audit, a customs query, or a tender submission forced a last-minute scramble.

The fix is not a better folder structure. It is a dated document register: a single table in which every certificate, report, declaration, and licence is a row with its own expiry or review date, the exact product it covers, an owner, and a status. The folder stores the files; the register tells you which ones need action this quarter.

This matters more for polyphosphate and siliphos-type crystal supply than for commodity purchases, because the documents are product-specific. A certificate issued for one grade does not automatically cover another, and “polyphosphate crystal”, “phosphate glass”, “siliphos-type media”, and generic scale-inhibiting media are not interchangeable descriptions. If your register does not record the exact grade a document refers to, you cannot tell later whether you are still covered.

Which documents in a polyphosphate supplier file actually expire

Different documents “expire” in different ways, and treating them all as simple dated certificates creates both false alarms and blind spots. The table below separates printed expiry dates from documents that go stale in practice.

One caution that belongs in the register itself: a food-grade statement is not evidence of drinking-water suitability. Suitability for potable water must be verified for the exact product, the application conditions, and the destination market’s rules. If a supplier sends a food-grade certificate in response to a potable-water question, that is a documentation gap, not a solved requirement.

Use two dates per document, not one

Most tracking systems fail because they record only an expiry date. Add a second field: review-by date. The expiry date is what the issuer printed. The review-by date is when you must look at the document again — earlier than expiry, and it applies even to documents with no expiry at all.

For a test report or an SDS, the review-by date is the only date that exists. For a certification, it is the date by which you start chasing the renewal, so the renewed document arrives before the old one lapses.

Minimum fields for each register row

• Document type — certificate, SDS, test report, declaration, licence, audit report.
• Exact product and grade covered — not just “polyphosphate”; record the supplier’s product name and grade exactly as printed on the document.
• Issuing body — the organisation that can confirm or renew it.
• Document reference number — so a copy can be matched to the original.
• Issue date and expiry date — with “no expiry stated” recorded explicitly rather than left blank.
• Review-by date — set by you.
• Status — valid, expiring soon, expired, superseded, or under renewal.
• Owner — one named person, not a department.
• File location — the exact path or document ID of the current version.
• Applicable market or regulation — the destination and framework the document is meant to satisfy.

A row without a named owner tends to sit untouched until it becomes urgent. A row without a market field tends to be reused in the wrong destination.

Set lead times by consequence, not one global reminder

A single “remind me 30 days before expiry” rule is too late for anything that depends on a third party. Renewal of a management system certificate, a product listing, or an overseas licence can involve an external audit, laboratory scheduling, or a translation and legalisation step — none of which you control.

A more practical approach is to rank documents by the consequence of lapse:

1. Stops a shipment or a sale — product listings, import registrations, licences: longest lead time, earliest trigger.
2. Stops a customer approval — management system certificates, audit reports, market declarations: medium lead time.
3. Weakens an argument but rarely blocks — older test reports, SDS revisions: handled at your normal review cycle.

The specific lead time is a business decision. What matters is that it is written down and applied consistently, so the trigger does not depend on who happens to open the file.

Run a fixed monthly review, and keep the output short

Tracking works when the review is boring and repetitive. Once a month, filter the register for rows whose review-by date falls within the next 60–90 days, and record three things only: what needs action, who is chasing it, and the date the request was sent. Anything longer than a page is unlikely to be read.

Add two exceptions to the monthly routine:

• Any new document received is entered into the register the same day it is filed. Documents that arrive by email and are never registered are the most common source of gaps.
• Any revision notice from a supplier triggers an immediate check of every row that references that document, because a new edition may supersede several linked files at once.

Handle documents without expiry dates deliberately

Test reports, technical data sheets, SDS files, and specification sheets often carry no expiry date. Do not leave the expiry field blank — blank fields are indistinguishable from forgotten ones. Instead:

• Enter “no expiry stated” in the expiry field.
• Set a review-by date based on risk and on how much the document’s content could change between revisions.
• Record the revision number or date printed on the document, so a later revision can be detected.
• Note any assumption the document depends on — for instance a test report produced for a specific production site or a specific water condition.

Supersede, don’t delete

When a new certificate or SDS arrives, mark the old row superseded with the date and the reference of the replacement. Deleting the old file destroys the audit trail that shows what was valid at the time a shipment was made. If a customer asks which document covered an order placed fourteen months ago, a supersede history answers the question in seconds; a deleted file cannot.

Red flags worth checking in any polyphosphate supplier file

• A certificate that names a product family or a “series” rather than the exact grade you buy.
• A food-grade statement presented as evidence of drinking-water suitability.
• A test report with no sample date, no production site, or no identifiable sample reference.
• An SDS whose revision predates a known regulatory change in your market.
• A product listing that cannot be found on the issuing body’s own public register.
• The same expiry date appearing on several unrelated documents — often a sign of copy-paste filing rather than genuine tracking.
• A register that lists documents but not the destination market each one is intended to satisfy.

Frequently asked questions

Do I need a database, or is a spreadsheet enough?

A spreadsheet with the fields above is sufficient for most importers and equipment manufacturers. The limiting factor is discipline, not software. Move to a database or a document-management module when more than one person edits the register, or when you need to prove what was valid on a specific past date.

How often should an SDS be reviewed?

There is no universal expiry period. Review whenever a regulatory change, a formulation change, or a new hazard classification occurs, and otherwise adopt an internal interval. Record the interval you choose, and treat any supplier revision notice as an immediate trigger.

Is a Certificate of Analysis an acceptable substitute for a third-party test report?

No. A CoA documents a specific batch against the supplier’s own specification. A third-party report provides independent verification. They answer different questions and should be filed as separate rows.

Can I use one document set for several markets?

Sometimes, but only after checking the requirements of each destination. Certifications that satisfy one national scheme may not satisfy another, and a document accepted by one buyer may be insufficient for a different customer in the same country.

If you need documents for a specific grade

Document requirements follow the product, not the supplier’s general catalogue. If you are building or refreshing a supplier file for a polyphosphate or siliphos-type crystal product, tell ENVO CHEMICAL the exact grade or specification you are evaluating, the application (for example scale inhibition in a specific equipment type), the destination market, and the document types your customer or regulator requires. With that information, the relevant technical and compliance documents for that grade can be identified and any gaps stated clearly, rather than assumed.