How to review agency code before launching your app

Agree on what customers must be able to do, then ask your agency to show that it works in the exact version you intend to launch. You can lead the acceptance review and give a technical reviewer specific questions to verify.

Define the customer journeys that matter

For a booking app, try booking, rescheduling, cancellation, and confirmation messages. Use two separate test accounts and confirm each sees only its own bookings. Record the expected result and the version tested.

Ask for evidence you can hand to another developer

Request the GitHub repository and branch, the commit planned for release, the test results for that commit, and known issues. When a code report flags a finding, ask which user flow it affects and how someone can reproduce it.

Sort issues by impact

A customer seeing another customer’s records or a payment being taken twice needs immediate investigation. A maintainability concern can have a different deadline. Ask the reviewer to document severity, reachability, owner, and the evidence needed to close each issue.

Check the fix against the release candidate

Ask for the updated commit and rerun the affected journey in staging. If you rerun an automated review, compare findings against that same commit. Assign a person to approve the launch and document how they would roll it back.

Related guides