# How to include a step for a range of numbers

Use a starter rule to include an optional block's steps when a count on the order is between two numbers.

Source: https://help.smartfact.ai/manuals/worksteps/how-to-include-a-step-for-a-range-of-numbers

Review edition: 13 November 2026

Roles: author, reviewer

Some steps belong to a middle band of sizes. The starter rule **Include a block for a range of numbers** includes an optional block when a whole-number option on the unit's order is between the two numbers you set, both included.

## Use the starter rule

You need the Author role, and the procedure needs a saved draft revision: a procedure you have only just created has nothing for the blanks to offer yet. The rule goes into the next draft revision. Units keep the instructions of the release they were issued with, and new units keep following the published release until a Reviewer publishes a new one.

1. Open **Procedures** and open the procedure.
2. Under **Starter rules**, find **Include a block for a range of numbers**. It is in **Counts**. You can also type a word from its title in **Search starter rules and Help**.
3. Fill in the blanks in the card's sentence, "Include … when … is from … to ….":
   - **Optional block**: one of the procedure's optional blocks.
   - **Count**: one of the procedure's required whole-number options.
   - **Smallest number** and **Largest number**: both inside the range the option allows, and the smallest no larger than the largest. The same number twice means exactly that count.
4. Choose **Use this rule**. The button waits until every blank has a value.

WorkSteps saves the next draft revision with the rule in it, with the note "Began from the starter rule Include a block for a range of numbers (version 1)". No AI is asked, and nothing is published, assigned or issued. The page then says the revision began from this starter rule and what to check next.

If **Draft definition** has changes you have not saved, the cards wait: a starter rule always starts from the saved revision. Save your changes or reload the page first.

Where SmartFACT Automation is connected to WorkSteps, you can also arrive here from **New requirement** there, which offers the cards of the procedure whose draft was saved most recently. Its **Use this rule** makes nothing: it opens that procedure's page with this card alone and its blanks filled in, and the page names the procedure. Check the procedure and the blanks, then choose **Use this rule** on the page. **See every starter rule** shows all the cards.

Where describing a condition in words is switched on for your site, the card also offers **Reword with AI**. It sends nothing: it puts the card's sentence into **Describe this condition in words** under **Slot conditions**, where you read it and choose **Propose a condition** yourself. That request counts against your limits like any other. Where describing in words is not available, the card offers **Use this rule** alone.

## What the rule does

The rule replaces the block's condition: the block's steps are included when the count is from the smallest number to the largest, and left out outside that range. A unit whose order has no value for the count cannot be issued.

In the Instrument enclosure EN-400 procedure, "Include the panel support block when Number of panels is from 4 to 8" gives Fit the centre support bar to units with 4 to 8 panels.

## Check the examples

A starter rule saves no example, because an expected route is yours to state from the approved method: WorkSteps never works it out for you. Before you lock the revision, save examples under **Examples** that show the rule working:

- one unit at each end of the range, whose expected routes include the block's steps;
- one unit just below the range and one just above it, whose expected routes leave them out.

Beside the new revision the page offers **Start an example** for each of these. It puts a unit's options in **Example JSON** and leaves the expected route empty for you to complete; then choose **Add example**. Check every option and enter the expected steps, requirements and parameters from the approved method before you save it.

Your existing examples are run again against the new revision. An example written for the old rule may now fail, and that is the point: decide whether the rule or the example is wrong before you change either.

## Publish it

Under **Review**, choose **Lock revision … and verify**, which names the revision the starter rule made. Every saved example is run, and the proof also needs each optional block both included and left out by some example. Then hand the candidate to a Reviewer. [Verify and publish a procedure](/manuals/worksteps/proof-and-publication) describes the review. A rule from a starter rule is reviewed like any other, and an author who publishes their own revision must have the Reviewer role and give a reason.

## Change it later

Nothing about a starter rule makes its rule permanent. Under **Slot conditions**, choose the block and change either number or the whole condition, or use another starter rule on the same block. Save the change as a new draft revision and publish it in the same way. Units already issued keep the instructions they were issued with.

## If the card is refused

- **This starter rule has changed since the page was opened.** WorkSteps has a newer version of the starter rule. Reload the page and fill the card in again.
- **Someone saved a newer revision.** Another author saved the draft after you opened the page. Reload it, check what they changed, then use the card again.
- **The draft already has this rule, so nothing was saved.** The card would make exactly the rule the draft has now.
- **The number is outside the range the option allows.** Choose numbers the option can have.
- **The smallest number is larger than the largest.** Swap them, or give the same number twice for exactly one count.
