Give agency clients a focused UI decision to review

Ask the client a specific question

A request to approve the whole portal invites conflicting expectations. Instead, identify a bounded decision such as whether the document-upload confirmation communicates the correct next step. State the reviewed build, audience, and previously agreed constraints. Clarify whether the client is commenting on language, confirming scope, or providing formal acceptance under your contract. Those are different responsibilities.

Prepare evidence the recipient can understand

Capture the implemented screen or a short journey using sample documents and names. Review the proposed findings in Retick and remove unrelated internal discussion or unsupported assumptions. Explain unfamiliar terminology in the issue description. Choose the supported sharing target and access level deliberately, then test the recipient experience without relying on your owner session. Never assume a public link is appropriate for confidential material.

Record the approved outcome

For an unclear confirmation, ask the responsible client contact to approve the document naming and next action. Capture that decision in your normal approval record. Keep a new request for a document dashboard separate from the agreed correction. Export selected implementation work to Trello or download a reviewed file only once the decision owner has accepted the scope.

Verify delivery rather than assuming sign-off

After development, ask the appropriate person to inspect the updated flow against the recorded criteria. Opening a shared link does not prove approval, and sending a review does not guarantee participation. Retick provides media and review context; it does not replace contractual acceptance, certify client consent, or resolve disagreements about project scope. Keep those records in your established agency process.