The product page has a datasheet button. The button works. A customer downloads a document with a similar product name, but the revision or variant may not match the item on screen. Link integrity alone is not document applicability.
Model the relationship explicitly
A useful document record can carry a stable identifier, title, revision, issue date where supplied, language, status and source. The product relationship should state whether it applies to a family, a specific model, a variant or a serial range. Where the source does not establish that relationship, do not fill the gap with a filename guess.
Preserve revision and replacement history
When a supplier publishes a replacement document, record which file supersedes which and whether the older one remains valid for earlier units. Removing an old PDF may break service workflows; leaving it unlabelled may encourage an outdated selection. Give the page a current document and make status clear to users.
Check the published page
Review representative products and variants. Confirm that the label is clear, the file opens, the revision shown matches the source and the applicability note is visible. Check mobile access and search results too. A correct relationship buried behind an ambiguous label still creates avoidable calls.
A practical inspection
- Give each document a stable record and revision state.
- State whether applicability is family-, model- or variant-specific.
- Keep supersession and archive rules visible to the team.
- Verify the source and the published page agree.
- Test a sample across variants and mobile use.