Define draft, submission and review
Specify what must be complete for submission and what may be missing in a draft. State who can read each version. A fictional startup workflow might collect contact roles today and approved content sources later.
Decide which version the reviewer receives and what a request for more information means. A status label without an owner is insufficient as an expected outcome. Save the step definition and version before testing.
Test incomplete saving and return visits
Fill the first step and leave a later required step empty. Save, close and return through the agreed access route. Compare values, step status and actual stored information. An incomplete draft may be allowed without being labelled finished.
Simulate a failed save and expired resumption access in the test environment. The interface must distinguish a failed attempt from a valid saved version. Check that renewed access does not reveal another person's information.
| Test | Check | Expected outcome |
|---|---|---|
| Incomplete draft | Save and reopen | Values retained under the model; missing steps shown |
| Save failure | Feedback and remaining input | No false storage promise |
| Expired access | Return route | Private information stays protected |
| New required field | Old draft against new step definition | Requirement change explained without silent data loss |
| Submitted version | Receiver's review material | Same marked version reaches its owner |
Test changed steps and corrected information
In the controlled test version, add a required field after creating a draft. Decide how the old version migrates or requests completion. Previously saved material must not silently count as approved under new requirements without an agreed rule.
Go back, correct an entry and continue using the keyboard. Check conditional fields do not retain information that has lost its valid context. Readable errors should lead to the right step without losing the rest of the work.
Follow submission to the named reviewer
Submit the marked version and verify that the same information appears in the agreed receiving view. A notification alone does not establish correct receipt. Try a later draft edit to confirm it cannot silently change the review version.
Request a specific correction and follow it to the right person and step. Record version, state, owner, evidence and retest. Final review means the decision you defined rather than automatic agreement, payment or activation of every system.