DraftIndicative placeholder for the section owner — amend, replace, or confirm as the first definitive version.

Doc owner: COS

Procedures

Procedures are how-to execution steps — more volatile than policy, created only when repeated friction or risk exists.

Procedure domains

Procedures mirror the policy domain structure:

Domain	Path	Scope
Enterprise	enterprise	Company-wide baselines
Engineering	engineering	Physical engineering
Production	production	Manufacturing and supply chain
Digital	digital	Software/platform/data
People	people	Conduct, ethics, training

See policy-index for cross-domain navigation (policy · procedures · templates).

When to add a procedure

Add a procedure only when the same activity is being performed repeatedly, inconsistently, or with unacceptable risk. Procedures reduce friction and error; they are not written pre-emptively.

Do not create procedures pre-emptively.

Relationship to policy

• Policy = mandatory constraints ("what must be true")
• Procedure = how we do it
• Procedures support policy; policy references procedures when needed
• Policy does not depend on procedures to remain valid