Which traits make an intake process worth turning into a simulated environment?

An intake process is worth simulating when it shows most of the following traits, because each one gives an environment something concrete to test.

- Submissions arrive through several channels, such as a portal, email and phone notes, each in a different format - Required fields and attachments vary by request type, so completeness is a rule lookup rather than a fixed list - Completeness depends on written policy and also on staff judgement about what is good enough to proceed - Cases can be returned, resumed or withdrawn part-way, which forces the environment to track state over time - Duplicates and identifier conflicts turn up against existing customer, patient or supplier records - Routing depends on category, value, location or risk flags, and the right queue is not always obvious - Handover notes must let the next team act without reopening every attachment or asking the applicant again - Reminders and timers change what the correct next action is, which tests sequencing as well as judgement