You prepare the configuration production will use. Your saved drafts and checks remain separate from the live release. Freezing a candidate hands a particular saved revision to a Reviewer; it does not make that work live.
Start with an explicit requirement
Write down what must change, the inputs that decide it and examples of both matching and non-matching work. Agree the expected labels, values, quantities and refusals before checking the proposed behaviour.
Use exact customer codes and field values. A requirement such as “use the export label for overseas jobs” needs an agreed definition of overseas and the correct supported input field.
Choose the right editor
- Templates: label objects, text, barcode placement, size, stock and orientation. See layout editing.
- Rules: conditions and supported actions selecting or deriving label behaviour. See rule authoring.
- Operator forms: reviewed questions and permitted corrections at preparation time. See forms and data.
- Data and mappings: maintained reference values and the interpretation of imported source fields. Use the checks for the particular editor.
Changing one part can affect the others. Check the complete label outcome, not only the field you edited.
Save, check and freeze
- Open or create the appropriate draft based on the intended configuration.
- Make the change and check that the saved revision contains it. An unsaved edit is not the reviewed source.
- Inspect the proof where the editor provides one. Check the real label dimensions as well as its fitted screen preview.
- Save independent examples and verify them. Include expected refusals and boundaries, not just successful output.
- Resolve every relevant failure. Freeze the saved revision with a useful change note and hand its candidate reference to the Reviewer.
Read examples and release review for the distinction between a successful check, a frozen candidate and a live release.
If another person changes the draft
A stale page cannot overwrite newer work. Reload the current revision, compare it with your intended change and deliberately save again. Do not repeatedly submit an old browser form or assume that a failed save changed production.
Your authority ends at the handover
Author alone cannot publish a release. A person who also has Reviewer may have additional actions, subject to the site's release controls. Where a second approver is required, use the required independent person and exact candidate. Do not treat combining roles as a way around those controls.