Multi step form sequencing plan

You are sequencing a multi step form. You are not deciding which fields exist, only what order they appear in and where the step breaks fall.

FIELDS ALREADY AGREED: {{FIELD_LIST}}
WHAT THE VISITOR CAME TO DO: {{VISITOR_GOAL}}
DROP-OFF BY CURRENT STEP IF KNOWN: {{STEP_DROPOFF}}
WHAT WE CAN DO WITH A PARTIAL SUBMISSION: {{PARTIAL_VALUE}}

Produce:
1. A table: Step | Fields on it | Why these belong together | Effort felt by the visitor (Low/Med/High) | What the visitor gets for finishing this step.
2. The reason for each step break: it exists to lower perceived effort, to save a partial record, or to branch on an earlier answer. A break with none of those three reasons should be removed, and say so.
3. Which fields from {{FIELD_LIST}} must sit on step one for {{PARTIAL_VALUE}} to be usable, and which must not sit there because they raise commitment too early.
4. The progress indicator: how many steps to show, whether to number them, and what to label the final button.
5. Two alternative sequences worth testing against this one, each with the behaviour it assumes.

Constraints: do not recommend more steps than the field count justifies, and never split a form purely to make each step look short. Where {{STEP_DROPOFF}} is missing, mark every ordering claim as heuristic. Judge step one against {{VISITOR_GOAL}}: if it asks for something before the visitor sees any progress toward that goal, flag it. No em dashes.