Skip to main content
In all cases, guidance provided in the Isometric Standard, Protocols and Modules is authoritative.

​
What is an Explanatory Note?

An Explanatory Note is a document that records how a Protocol, Module or Standard requirement applies to your project when your project doesn’t fit that requirement exactly. It explains why a requirement doesn’t apply to your project, or explains the alternative approach you have taken and that Isometric has agreed to. Isometric approves and publishes the Explanatory Note as part of your project record, so the VVB, buyers and anyone else reviewing the project can see what was agreed and why. An Explanatory Note can be used in three situations:
  1. A Protocol update is planned. Your project doesn’t currently meet a requirement, but a planned update to the Protocol or Module will bring it into compliance.
  2. You will comply at a later date. Your project doesn’t currently meet a requirement, but you will meet it by a defined point, such as your next verification. This is recorded as a Forward Action Request (FAR), and the note states the deadline.
  3. You are taking an agreed alternative approach. Your project doesn’t meet a requirement, or the requirement doesn’t directly apply, and you are using an alternative approach that Isometric has accepted. Isometric uses this route only as a last resort.
For the third situation, you must give Isometric a written explanation of your approach and why it is a sufficient alternative before Isometric approves it. That explanation forms the context section of the note. Explanatory notes are only issued as exceptions and at Isometric’s discretion; where a project is able to comply with a requirement, it must do so.

​
Still need help?

If none of these answers solve your problem, contact support.