Overview
An Off-Specification is a reference to an omission or error of a product or its specification and requests that it now be added or corrected.
Off Specifications can be recorded by the Project Manager in the Issue Log as part of CS3 Capturing Project Issues or by anyone involved with the project. These are then passed onto CS4 Examining Project Issues for analysis and further actions if necessary. If required each product description should be updated.
It is important to make the distinction between a Request for Change and an Off-Specification due to the possible funding implications. Both of these types of Project Issues are, however, dealt with in the same way. As with all Project Issues impact analysis must be carried out, and if the change falls within the stage's Tolerance margins the Change Budget can be used to undertake the Off-Specification without the need for a Project Board decision. If not the Off-Specification must be brought to the Project Board's attention via CS8 Escalating Project Issues, to be addressed in DP4 Giving ad hoc Direction.
Accepting an Off-Specification without any corrective action is called a Concession.
An Off Specification should include:
- Date
- Issue Log number
- Status
- Description
- Impact
- Allocation details
- Date allocated and completed.
Tips
Notes
- It is a Project Issue
- Something that must be provided by the project that is not currently or adequately provided for
- Could be a missing product or the failure of a product (i.e. not meeting its specification)
- An Off-Specification includes:
- Issue Log Number
- Class, status and date
- Description and impact of the fault/omission
- Priority assessment
- Decision taken to address the Off Specification (Project Issue)
- Allocation details
- Date allocated and completed
- Derived from anyone within the project
- Gathered in CS3 Capturing Project Issues.
Case studies and examples
Related links
| 
