Start an internal tool with the workflow you already know

Existing forms, spreadsheets, and email threads reveal how work currently moves. They can inform a brief, but copying every workaround into a new screen preserves the old confusion.

This is an illustrative workflow to adapt and test, not a timed product benchmark or a verified customer case study.

Define the information and the work

Name the request, its owner, its possible statuses, and the decision that moves it forward. Separate required information from fields collected only because an old sheet had room for them. Start with one queue and a readable detail view.

Write these decisions into a brief before polishing the interface. A useful brief explains what someone can do, what should be saved, and how another person picks up the result. Keep the original material available while reviewing the first version so differences can be checked rather than guessed.

Try a concrete review scenario

Follow one request from creation to completion. Check a reassignment, a missing detail, and a rejected request. Ask a second person to complete the same journey without an explanation from the builder.

Record the steps, expected result, and any difference you find. Ask for one focused correction, then repeat the same scenario. Include an empty state and a failure as well as the successful path. This gives the first version an acceptance test and later changes a practical regression check.

Give the result a home in your App Cloud

Use structured records to keep the queue and its history understandable. Authentication and ownership rules define who handles each request. Add email only at meaningful handoffs. An agent can propose a summary or a next action for review, while staff retain a clear view of the original request and the resulting change.

Create and refine this experience in Studio. Keep the first version focused enough to test with the scenario above.

Publish and keep learning

Check the account’s current allowance and the usage of the capabilities you selected. Publish the reviewed app from Studio, then repeat the essential task on the shared link.

Follow what people actually do with the app. Use observed problems and measured usage to decide the next change; completion times, savings, and business outcomes depend on your own workflow.

Continue with the related guide · Explore the building blocks · Understand your App Cloud