Authors prepare what production may use in Materials and policies. This role does not authorise physical stock movements or activation of a release. A reviewer makes the activation decision.
Begin with the intended behaviour
For material reference data, check the item code, base unit, permitted precision, aliases, conversions and any lot or expiry requirements. Once an item identity is in use, changing its quantity basis or tracking model can be refused. Do not create a new alias that redirects an existing identity to a different material.
For a policy, write the operational question before editing: where should this material go, which stock may be allocated, or when should a review be raised? Use materials and policies and examples and releases for the complete path.
Save, prove and hand over
Save a draft, reopen the retained revision and check that it contains the intended content. Prove this exact draft checks that revision. A later edit, changed dependency or changed operational impact can invalidate the proof. Passing an earlier revision does not prove the current one.
Where plain-language condition authoring is offered, treat the returned condition as a proposal. Read it, check the examples and adopt it only if it says what you meant. Adoption changes the draft; it does not release the policy.
Prepare examples with independently chosen expected outcomes, including refused or held work. Do not copy the proposed result into the expected result simply to make a proof pass. Give the reviewer the purpose, exact draft revision, relevant examples and the reason for changing production behaviour.
Finish cleanly
Keep a page with an uncertain save open and reconcile its original request. Private authoring wording is not necessarily retained after refresh. If the current draft has changed since you loaded it, reopen and review it before making another edit.