Codes and Standards Compliance

A codes and standards register with the right editions, an applicability matrix, controlled deviations, vendor and inspector checks, and compliance dossiers that stand up to a regulator.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Codes and Standards Compliance, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help you organise your own work. It does not replace your professional judgement, the rules of your regulator or professional body, your firm's policies, or advice from a qualified lawyer, accountant or other adviser. Where a law, code or standard applies, use the current official version for your country, and get qualified sign-off on regulated or safety-critical work.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🔧 Engineering Practice

Codes and Standards Compliance

Working to the codes and standards a design must meet: ASME, API, IEC, BS EN and local codes, keeping editions current, recording deviations and compliance records.

  1. Project codes and standards register
  2. Fixing the edition and date of applicability
  3. Order of precedence between law, codes and client specifications
  4. Standards library subscription decision
  5. Code applicability matrix by equipment item
  6. Deviation and concession register
  7. Statutory requirements map for the project location
  8. Compliance responsibility split between owner, contractor and vendor
  9. Statement of compliance format for deliverables
  10. Monthly standards update watch
  11. New edition impact assessment routine
  12. Vendor deviation request review routine
  13. Compliance matrix upkeep for each specification
  14. Material certificate and traceability checks
  15. Code interpretation and query log
  16. Quarterly project compliance status report
  17. Annual register audit and withdrawn standards sweep
  18. Third-party inspector and notified body coordination
  19. Reading a code's scope, definitions and mandatory language
  20. ASME Boiler and Pressure Vessel Code structure
  21. Comparing piping codes B31.3, B31.1 and EN 13480
  22. API standards for oil, gas and petrochemical equipment
  23. IEC and BS EN electrical standards family
  24. European conformity under PED, ATEX and CE marking
  25. Welding and NDE code requirements
  26. Using code cases, interpretations and errata
  27. Choosing a design code when the client leaves it open
  28. Equivalence justification for an alternative standard
  29. Bringing company specifications up to current editions
  30. Cutting duplication between client specs and international standards
  31. Choosing a standards management tool
  32. Code compliance check before issuing deliverables
  33. Hazardous area classification compliance review
  34. Preparing for an Authorized Inspector shop visit
  35. Code pressure test witnessed and recorded
  36. Regulator or certifying authority design submission
  37. Code compliance dossier at handover
  38. Preparing for a client or insurer compliance audit
  39. Working to an unfamiliar national code overseas
  40. Standards compliance for a small consultancy
  41. Vendor compliance documentation that buyers accept
  42. Owner's engineer verification of contractor compliance
  43. Modifying plant built to superseded code editions
  44. Code literacy plan for a new team member
  45. Writing a company engineering standard
  46. Joining a standards committee or working group
  47. Submitting a formal code interpretation request
  48. Compliance strategy for modules built abroad
  49. Performance-based alternative to a prescriptive code
  50. Compliance basis for technology with immature codes

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Project codes and standards register

Every design claims compliance with something, but on most projects the list of governing codes lives in five specifications, two contracts and somebody's memory. One register listing each code and standard, its edition, its scope on this project and the documents that invoke it is the base every later compliance statement depends on.

First tasks

  • Collect the contract, basis of design and discipline specifications in one folder
  • List every code and standard each document names, with its edition
  • Flag any standard cited at two different editions
  • Issue the register at revision A with a named owner

Fixing the edition and date of applicability

Specification clauses that say "latest edition" sound safe and are a trap: ASME pressure vessel and piping codes are reissued about every two years, and an edition published mid-project can change allowable stresses or test rules. Freezing each code at a named edition on a stated contract date stops the target moving under the design.

First tasks

  • Search the specifications for latest edition wording and list each hit
  • Propose an edition cut-off date to the client's lead engineer
  • Update each register entry to the edition in force on that date
  • Add the edition rule to the next revision of the basis of design

Order of precedence between law, codes and client specifications

When a client specification asks for a thinner wall than the code allows, or two standards give different test pressures, someone has to know which one wins. Statutory law sits above everything, but the ranking between the contract, project specifications and international codes has to be written down before the first conflict, not argued during it.

First tasks

  • Find and copy the precedence clause from the contract
  • Draft a ranked list from law down to recommended practices
  • Agree the tie-break rule for conflicts at the same level
  • Brief the discipline leads on the agreed order

Make it yours.

Install Codes and Standards Compliance, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.