Describe a ReclaimStation reuse rule in plain English

Type a reuse rule in plain English, answer the AI’s question about missing details, inspect the complete proposed rule and save it deliberately as a draft.

For authors

Type a reuse rule in plain English, answer the AI’s question about missing details, inspect the complete proposed rule and save it deliberately as a draft.

Read these instructions on any device. Watch or practise a chapter on a desktop or laptop, with a desktop or mobile application layout. Demonstrations use sample data and simulated scanners.

Plain English to a checked draft

  1. Load the current recovery policy

    Load the current recovery policy

    Load the PM-200 recovery policy from ReclaimStation. Its examples were agreed in advance and include a module with two recorded reuse cycles that should go for review.

  2. Choose Add reuse gate

    Choose Add reuse gate

    Choose Add reuse gate. A reuse gate rule can admit a recovered component as a candidate, block it or send it for review.

  3. Type the requirement in plain English

    Type the requirement in plain English

    Type the requirement as the team wrote it: send a recovered component for review when it has two or more recorded reuse cycles in this register.

  4. Ask for a proposal

    Ask for a proposal

    Ask for a proposal. The AI replies with a question instead of guessing: what should the rule be called, and which reason code should it record?

  5. Add the details the AI asked for

    Add the details the AI asked for

    Keep the requirement and answer the question: call the rule review-repeat-reuse and record the reason code repeat_reuse_review.

  6. Ask for the complete proposal

    Ask for the complete proposal

    Ask again. The AI now returns a complete reuse gate rule. Nothing is saved until you choose to save it.

  7. Read the restatement of the rule

    Read the restatement of the rule

    Read the restatement. It says in plain words when the rule applies, when the number of recorded reuse cycles is at least 2, followed by the change it saves.

  8. Inspect the proposed condition

    Inspect the proposed condition

    Inspect the condition in the same controls ReclaimStation uses: the number of recorded reuse cycles is at least 2.

  9. Check what will be saved

    Check what will be saved

    Read what the rule will save, field by field. Every value has its name, and the reuse outcome is shown in plain words with its code.

  10. Check the rule identifier

    Check the rule identifier

    Check the rule identifier is review-repeat-reuse.

  11. Check the reuse outcome and reason code

    Check the reuse outcome and reason code

    Check the outcome: Send for review, with the reason code repeat_reuse_review.

  12. Confirm you checked the whole proposal

    Confirm you checked the whole proposal

    Confirm that you checked the condition and every value. ReclaimStation still validates the whole policy when it saves.

  13. Save the proposal as a draft

    Save the proposal as a draft

    Save the proposal as a draft. Saving does not approve, release or run the rule: the proof and an independent review come next.

Watch or practise this chapter

Only a draft was saved. The proof and an independent review come next.

Contact SmartFACT support · Explore the suite