What the documents look like
Price and display checks take place during day-to-day operations, and the emphasis is on sustained execution of standards rather than a one-time launch exercise. The material for this category comes from supervisor systems, POS price lists, store cameras and head-office promotion calendars. The working documents are store-visit photos, price-tag lists, display standards and rectification notices.
For copy drafting, these documents serve as evidence. A price-tag list and a promotion calendar state the price and activity status of an item for a defined period. A display standard states where material is to be placed. A store-visit photo states the observed condition on site. A draft sentence is supported only when the material states the same subject, object, period and status. Any status the material does not state remains unknown.
Constraints at the interactive forms step
The form input node is a user-interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and execution continues after the user completes the interaction. After submission, the node collects the information the user filled in and passes it to later nodes. The user selection node also enters an interaction state and executes a branch according to the user's choice.
Neither node carries business database functions. Field validation, approval, write-back and batch operations need to be implemented in an external system or in later nodes. For price and display copy drafting, the draft sentence and the source text of the material are submitted together. The interactive nodes collect and branch; they do not decide whether a draft sentence is supported by the material.
Hypothetical paper exercise: a chain operator's operations department is preparing to finalize a promotion sentence for one store. The source text supplied for comparison reads: "The price-tag list (hypothetical identifier PL-001) states that item A carries a promotional price of 19.9 yuan from 1 March 2025 to 31 March 2025; the head-office promotion calendar (hypothetical identifier PM-007) states that item A falls under the 'Spring Special' slot for that period; the display standard (hypothetical identifier CL-012) requires the price tag for item A to be placed at the front left of the shelf." The draft sentence to be assessed is: "Item A Spring Special price 19.9 yuan, activity ends 31 March." A separate handover request reads: "Please confirm whether this copy can be used directly on the store poster." The material does not state the poster approver or the poster validity period.
Configuration and implementation checks
| Configuration item | Value or check item on this page | Basis and explanation |
|---|---|---|
| Interactive node type | Form input or user selection | The official documents state that both trigger an interaction state and continue after completion |
| Required form fields | Draft sentence, source text, material identifier, period range | Hypothetical starting point for this page, so that subject, object, period and status are complete for assessment |
| Material identifier field | Text input, filled in by the submitter | The official documents do not specify an identifier format; the identifiers are self-defined for the hypothetical exercise |
| Branch decision | Execute the "yes" branch according to the user's choice | The official documents state that the user selection node executes a branch according to the choice |
| Downstream processing | Field validation, approval and write-back are implemented in an external system or later nodes | The official documents state that the node does not carry business database functions |
| State recording | The interaction state is recorded by the node, and execution continues after the interaction completes | The official documents state that the node records the workflow state |
Three common errors
- Treating a status the material does not state as confirmed. In the hypothetical exercise the material does not state the poster approver. If the draft sentence says "approval obtained," that sentence is unsupported and must be recorded as pending verification, not as confirmed.
- Treating an interactive node as a business judge. Form input and user selection only collect information and execute branches. They do not judge whether a draft sentence is supported by the material. Placing the assessment responsibility on the node itself omits the manual comparison step.
- Mixing evidence from different periods. In the hypothetical exercise the promotion period is 1 March to 31 March. If the draft sentence says "continues in April," that sentence is inconsistent with the material period and is unsupported. It is not a conflict and not a negation.
How to verify the setup
- Enter the hypothetical draft sentence "Item A Spring Special price 19.9 yuan, activity ends 31 March" together with the source text, and compare whether the price, activity name and end date in the draft sentence match what the price-tag list and promotion calendar state. When all three match, record the sentence as supported by the material. When any item differs or is not stated in the material, record it as unsupported or pending verification.
- Enter the handover request "Please confirm whether this copy can be used directly on the store poster," and compare whether the request contains approver information that the material does not state. When the request does not contain the approver and the material does not state one, record an evidence gap and do not judge the request as executable.
- Enter the hypothetical material identifiers PL-001, PM-007 and CL-012, and compare whether the submitted content matches the material corresponding to each identifier. When an identifier does not correspond to the content, or an identifier is missing, record it as pending supplementation and do not proceed to a later branch. All of the above are paper expectations and do not indicate that testing has been performed.