Put the consequence beside the action
On November 9, I clarified two existing controls in Seasonal.Work: the preview before a CSV import and the optional expiry date for a shortlist report. Neither needed a new workflow. Both needed the interface to explain what the existing action would do before someone committed to it.
The CSV screen previously described where parsing happened and how rows reached the application. I replaced that implementation-focused explanation with the practical distinction between Preview and Import. Preview checks the file without importing it. The valid-row count and errors were also moved above the action buttons, so the information appears before the decision it supports. Import remains unavailable until a preview exists without errors, and changing the CSV or import type clears the old preview.
The shortlist form had a different ambiguity. Its expiry field was optional, but leaving it blank still had a defined consequence. I added help text beside the field explaining the existing default of fourteen days after creation and the UTC cutoff for a selected date. The help is associated with the input for assistive technology. This was a disclosure of existing behaviour, not a change to the report's lifetime or the way its date is interpreted.
Together, the changes put useful information where it affects a decision. A person checking an import should see the result before choosing Import. A person leaving an expiry blank should know that blank does not mean unlimited. The November 9 edits were incorporated into the workspace update merged on November 11, preserving the existing handlers and their rules.
Reflection
Good form copy answers the user's next practical question. For Seasonal.Work, the useful improvements were a clearer preview boundary and an explicit date default. Both make existing controls easier to understand without asking people to learn the implementation behind them.