Included on every plan
Find out a standard was revised before your client does.
Tell TRACE which codes and standards your programs depend on. It checks the publishers every week and tells you when one of them publishes a new revision.
What it does
Code Watch, in detail.
Your watch list, not a generic feed
Add the standards that actually matter to your programs — SNT-TC-1A, NAS 410, ASTM E1444, and the rest — each with the revision you currently hold on file.
Checked every week, automatically
A scheduled job reads each standard's watch page every Monday — the publisher's where it allows it, an authorized reseller's where it doesn't — and compares the published revision against the one you have recorded. No one has to remember to look.
Told, not left to notice
When a revision changes, the standard is flagged and consultants get both an in-app notification and an email — so the first you hear of a new edition isn't from a client.
Acknowledge and move on
Review what was detected, then acknowledge it to record the new revision as the one you hold. The standard returns to a clean state until the next change.
Fails loudly, never silently
If a publisher blocks the check or redesigns their page, that standard shows as a failed check with the error — rather than sitting there looking current when nothing has actually been verified.
How it works
Day to day.
- 1
Add the standards you depend on
Record each code, the revision you hold, and the page to watch.
- 2
Let the weekly check run
TRACE reads each watch page every Monday and compares what's published against your recorded revision.
- 3
Get told when something moves
A change flags the standard and notifies your consultants in-app and by email, with the detected revision alongside yours.
- 4
Acknowledge the new edition
Confirm the update to record it as the revision you now hold, and the watch resets for next time.
What the weekly check can and can't reach
Code Watch reads publicly reachable pages. Several standards bodies actively block automated requests, so those are watched through authorized reseller pages that are fetchable rather than through the publisher's own storefront — and any watch that stops working is reported as a failed check instead of quietly going stale. A few documents have no fetchable source anywhere; those are held as manual entries, and TRACE reminds you quarterly to re-verify them by hand instead of letting them go quietly stale. It tells you a revision exists; obtaining the document itself is still a purchase from the publisher.
Want to see it on your own program?
Tell us how your NDT program runs today and we'll show you how this fits it.