An inspection plan states the approved method and how context selects its checks. Obtain expert-approved source requirements before entering values. Do not ask a proposed rule to invent tolerances, uncertainty policy, methods or source approval.
Define supported context
On Plans, use New plan or Edit draft. Under Supported context, declare exact family, drawing revision, supplier status, customer group and finish values. Supplier status uses the supported approved or newly_approved values. Unknown context must refuse selection rather than guess a method.
Under Required checks, define each approved check with its identity and revision, instructions, method reference and source. Depending on type, enter exact numeric limits and precision, pass/fail criterion, allowed choices, instruction acknowledgement or evidence purpose and permitted files. Required repetitions and instrument requirements are part of the method.
Bind and add requirements
Under Family and drawing bindings, select the base checks for each supported pair and whether Supervisor must release. Under Additional requirements, add conditions, selected extra checks, explanation and required supervision. A conditional rule must not silently remove protected base acceptance or mandatory supervision.
Write Proof examples from the intended method. State the exact expected checks and supervision, or the expected refusal. Include ordinary, additional, boundary and invalid-context situations. A ready outcome alone is insufficient if the selected method is wrong.
Choose Save draft and inspect its revision and differences from the last retained release. Resolve validation problems. Reload and compare a stale editor before another save.
Review new methods explicitly
Where new expert-supplied definitions are pending, they remain non-executable until an independent Reviewer approves the exact definition and expert statement. Pending definitions block selection and full proof, even if currently unused. Approval revises the draft and invalidates earlier proof; it does not activate the plan.
Hand over the whole plan
Run proof examples on the saved draft and inspect every difference. Tell the Reviewer which contexts, methods and decisions changed. Plan activation requires a Reviewer who has not contributed a saved draft to that plan.
Continue with proof and approval. A later draft does not rewrite a retained release or an inspection already started under frozen requirements. Coordinate operational changes with the Supervisor.
Propose a condition without changing its fixed actions
For an existing saved rule, expand Describe a rule condition. Select Existing rule, read Fixed actions and enter When should the fixed requirement apply?, then use Propose condition when the authoring service is available.
Read Proposed condition and Actions that will stay fixed before choosing Adopt condition into this draft. Adoption updates the draft and clears its previous proof. It cannot replace the independent definition or plan review. Rerun proof examples and obtain the required separate review before activation.
If the authoring answer is uncertain, use Check or retry the same request for the retained request. Do not create another intention to conceal a missing outcome. Keep using the structured editor when no authoring connection is available.