What the documents look like
Creator-led sales campaigns depend on external creator performance and commission settlement. Brand business staff confirm terms with MCN agencies or creator managers rather than coordinating internal brand shifts. The copy drafting task draws on four document types: creator cooperation agreements, commission setting sheets, sample dispatch sheets, and livestream performance reports. Data originates from the selected alliance, the creator marketplace, creator historical data, and store transaction details. A new batch of records appears after each livestream, and weekly summaries form stage records.
For copy drafting, brand business staff extract verifiable material from these documents and produce proposed sentences for creator confirmation. Source text may contain the cooperating entity, product object, commission rate, sample dispatch status, or livestream session scope. Any promotional wording in a proposed sentence needs a corresponding basis in the source text. Fields not stated in the material remain unknown; the presence of similar information in another document does not establish that the field exists here.
Constraints at the interactive forms step
The form input node is a user interaction node. When triggered, the conversation enters an interaction state, records the workflow state, and waits for the user to complete the interaction. After submission, the node collects the entered form information and passes it to subsequent nodes. The user selection node is also a user interaction node; when the user makes a selection, the node evaluates that selection and executes the corresponding branch. Neither node includes a business database function. Field validation, business approval, write-back, and batch operations require an external system or subsequent nodes.
Hypothetical paper exercise sample: the source text consists of three sentences. Sentence one: "The cooperating entity for this session is a Hangzhou cultural media company; the cooperation target is the creator account 'Xiaolu Reviews'; the cooperating product is a brand moisturizing essence 30ml." Sentence two: "The commission setting sheet states the commission rate for this product is 18%; the sample dispatch sheet states the sample was dispatched on 10 March 2025 and the receipt status is signed." Sentence three: "The livestream performance report states the livestream date was 22 March 2025 and the transaction amount was RMB 120,000." The proposed sentence to be assessed is: "The cooperating creator 'Xiaolu Reviews' promoted a brand moisturizing essence 30ml in this session, commission rate 18%, sample signed, livestream transaction RMB 120,000."
When checking, compare each field of the proposed sentence against the corresponding field in the source text. The entity name, product name, commission rate, sample receipt status, livestream date, and transaction amount each require item-by-item correspondence. The source text does not state an authorization scope or a promotional wording approval status, so the proposed sentence must not add such statements.
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Form input node | Interaction node | Enters interaction state when triggered; collects entered information and passes it to subsequent nodes |
| User selection node | Interaction node | Executes a branch according to the user's selection |
| Required field checklist | Implementation check item | Lists the entity, product, commission, sample status, and session scope that this task cannot omit |
| Downstream processing division | Implementation check item | Field validation, business approval, write-back, and batch operations are implemented in an external system or subsequent nodes |
| Interaction state recording | Existing node behavior | The node records the workflow state and waits for interaction after triggering, then continues downward after completion |
| Hypothetical exercise starting point | This hypothetical exercise starting point | Compare proposed sentence fields item by item against the source text; this starting point is chosen because it must cover entity, object, status, and scope |
Three common errors
- Writing a promotional wording approval status into the proposed sentence when the source text does not state it. In the hypothetical sample, the source text states only the cooperating entity, product, commission rate, sample receipt status, and livestream transaction amount. It does not state whether promotional wording was approved. If the proposed sentence adds "authorized promotion" or "promotional wording reviewed," that field has no corresponding basis in the source text and is unsupported.
- Merging the commission rate from the commission setting sheet with the transaction amount from the livestream performance report into a single field check. In the hypothetical sample, the 18% commission rate comes from the commission setting sheet, and the RMB 120,000 transaction amount comes from the livestream performance report. The two share an entity and a period but are different fields. Each must be checked against its own source document; appearing in the same proposed sentence does not justify combining them into one judgment.
- Expanding the sample receipt status "signed" into "sample used" or "sample returned." In the hypothetical sample, the sample dispatch sheet states only that the receipt status is signed. It does not state a use or return status. If the proposed sentence writes a use or return status, that field is not stated in the source text and is unsupported.
How to verify the setup
- Input the three source sentences from the hypothetical sample and the proposed sentence to be assessed. Compare "cooperating creator 'Xiaolu Reviews'," "brand moisturizing essence 30ml," "commission rate 18%," "sample signed," and "livestream transaction RMB 120,000" in the proposed sentence against the corresponding fields in the source text. When every field can be matched to a statement in the source text with the same entity, the same period, and the same field, the proposed sentence field check passes. If any field is not stated in the source text, record it as unsupported.
- Input the 18% commission rate from the commission setting sheet and the RMB 120,000 transaction amount from the livestream performance report in the hypothetical sample. Compare whether the two fields come from the same document and whether they are the same field. When the two fields come from different documents and have different field names, check each against its own source. If the two fields are combined into a single judgment, record it as field confusion.
- Input the receipt status "signed" from the sample dispatch sheet in the hypothetical sample. Compare whether the proposed sentence writes "used," "returned," or another unstated status. When the proposed sentence writes only "signed," it matches the source text. If the proposed sentence writes another status, record it as unsupported. When the source text does not state an authorization scope or approval status, the proposed sentence must not add such statements; missing evidence remains missing.