Best Practices for Requested App Review

Requested app review is the bridge between intake and formal application onboarding. A good review process helps teams avoid provisioning too early or delaying good requests for the wrong reasons.

Best practice 1: Confirm whether the app fits the standard model

Requested apps should be used for applications that match a standard onboarding approach. If the request is unique or unclear, it may belong in custom discovery instead.

Best practice 2: Review notes before changing status

Do not change a requested app's status without first reviewing its notes, comments, and attachments. This reduces back-and-forth later.

Best practice 3: Assign a clear owner

If more review is needed, make sure the requested app is assigned to a specific person. Unassigned intake items are easy to overlook.

Best practice 4: Explain non-obvious decisions

If you defer or reject a request, leave a short comment explaining why. This makes follow-up easier and improves transparency.

Best practice 5: Provision only when the next team has enough context

Provisioning should happen when the request is clear enough to support real onboarding work.