Evaluate suitability before proposing automation

Document the trigger, necessary information, steps, approval points and the person who handles an uncertain result. Identify which actions affect external records or customers and what permissions those actions require.

Compare a proposal with the current process and include setup, checking, maintenance and recovery in the assessment. A small test is a hypothesis, not a guarantee of future performance.

A bounded assessment should include the effort of reviewing and correcting uncertain results. If required data or decision rights are unclear, the next step may be to resolve those questions rather than propose automation.

Before implementation, identify who monitors the workflow, how staff resume manual work and how errors are reported. Confirm product capabilities and third-party dependencies rather than assuming them.

These are planning questions for a possible discussion; the local site itself does not accept applications or create a partner relationship.