Make an HR request's status clear

Saving a timesheet or sending a request isn't necessarily the end of the task. Show who submits, reviews and approves the information in your HR software. One fictional request can explain those roles without touring every module.

Let the review step be seen

Start with the employee's actual entry screen, then move to the supported review role. Show an approved status only after the relevant action. If the example remains pending, keep that state visible. A successful save should not look like final approval simply because the interface displays a positive confirmation.

Prepare a consistent demo

Use demo screens, the actual review process and the names your product gives to each role and state.

Use fictional demo data and record the screens and product version shown. Check who acts in each scene and what the screen actually confirms.

Try it before the next demo

Use it when introducing the feature. Ask whether the request is approved and who still needs to act. A wrong answer points to a label or scene worth revising. Explain the product's behavior without implying legal or payroll consequences that haven't been established for the setup shown.

Related reading

• Show what someone can do with your software
• Help new colleagues find their way