Naming workflow inputs so operators know what belongs there

Use names that describe what a person provides: “Source CSV,” “Target time zone,” or “Report deadline.” Add units and accepted formats where confusion is likely.

Avoid names based on internal transformations, such as “Step 3 payload,” unless the operator genuinely works with that concept. Show a safe example and mark required fields. Test the form with someone unfamiliar with the workflow; their first question reveals a weak label.

Which input name gets interpreted two ways?