I've been unable to find a good guide for naming steps in a workflow (status labels).
What are some principles / best practices?
If you're curious, my specific case is:
I have a system where users submit payment requests. If the user does not cancel the payment request by the time our Customer Service team sees it, Customer Service reviews the request and either marks it as "fraud" or approves it. After approving dozens of requests, the CS employee can press a button to upload all of the approved ones to a 3rd-party payment system. Then time goes by (the response is not immediate), so these items are in a limbo status (which I'm thinking of calling "uploaded_for_processing"). The 3rd-party payment system eventually returns "success" or "failure" for each request; in the success case, we set the status to "complete" (in our local system). The failures need to have their statuses set to something that lets the CS rep review those (e.g. failed_to_process). For each, the CS rep needs to contact the user to inform her that her payment request failed and that she needs to try again. Then the CS rep would mark the request as "reported_failure_to_user".
Something doesn't feel right about my choices for these status labels though, so I'm wondering if there is a good framework for thinking about how to name them well.
Also, these status labels are for internal (Customer Service) use. Our customers won't see them.