Variables can be added throughout the project (and master) specifications, and changing the value will change the variable everywhere it has been added. So, for example, if your role as ‘Architect’ has changed to ‘Employer’s Agent’, this can be done automatically by changing the variable value.


Note: if you have a variable in the editor or spec and org notes on-screen, refresh your browser to see the value change.


Please note: 'Variables' are available with 'Premium'.


Changing org-level variables

  • Changing the variable value at the organization level will apply the change to all projects and master specs that contain that variable. This will happen unless the variable value has been changed in the project/ master ‘Edit variable’ area and you are notified that the ‘Inherited value has been overridden at this level’.
  • Changing the variable name at an org level will cause all existing variables to become missing. It is recommended that you avoid changing the name of org-level variables once a variable has been added to specifications and org and spec notes.
  • For information about what happens when a variable is missing and how to fix it, see Missing variables.


Changing project/ master-level variables

Changing variable values at a project or master level is recommended. Changing a variable value in the context of a project:

  • This means that org-level variables are no longer inherited. The variable will show the message ‘Inherited value has been overridden at this level’. If the org-level variable value has changed, the changes will not be applied to the project.
  • Will not change other projects or masters. Changing variables in a project or master does not change the same variable in any other projects or masters. Project and master variable changes affect the contents of that project/ master and do not change any other projects or masters.


Changes that should be avoided

  • Avoid renaming or deleting org-level variable names once the variable is in use.
  • Correct spelling mistakes as you set up new variables. Think about naming conventions.
  • Avoid changing the org-level variable value once the variable is in use unless the change is intended to apply to all projects and masters where the variable is being used. Changing the org-level variable value will change all instances of that variable in every project and master unless the variable’s inherited value has been overridden in projects and masters using it.
  • Avoid renaming or deleting project-level/ master-level variable names once the variable is in use.
  • ‘Variable in use’ refers to a variable added to an article, clause, spec note, org note or table.


Copying variables

  • Org-level variables can be copied with specifications into different projects and masters. However, it is important to check the project or master-level variables to ensure that the values match the stage of the project.
  • Org-level variables copied with spec content to another organization must be set up in the other organization. Otherwise, the variable will become missing. Please see the ‘Missing variables’ section.
  • Project/ master level variables copied with spec content to another project or master must be set up in the other project or master. Otherwise, the variable will become missing. Please see Missing variables.


Deleting variables

Deleting a variable will affect any instances where the variable has been used. Missing variables can be fixed; please see Missing variables.