How an audit runs
Engagement process
From intake brief to findings memo — the practical sequence Toolkit Brook uses for mobile app codebase audits and release readiness reviews.
This page is for teams who want to know what happens after they send a brief, before they compare rates.
1. Intake brief
You describe platforms, repository shape, release date, and the decision you need (ship, wait, hire, or brief investors). We confirm language for meetings and whether an on-site day in Taichung is useful.
2. Access & constraints
We agree read-only repository access, build instructions, staging accounts if needed, and explicit out-of-scope areas (for example, a legacy module scheduled for deletion). Work does not begin until access is stable.
3. Review window
For a Mobile App Codebase Audit, expect five to ten working days of deep reading. For a Release Readiness Review, the window is shorter and more checklist-driven. You receive a mid-engagement note only if a blocker prevents progress (broken builds, missing credentials).
4. Findings & walkthrough
You receive a written memo. Optionally we schedule a live walkthrough so your engineers can challenge severity ratings with local context. We revise the document once for factual corrections.
5. Optional roadmap
If findings need sequencing across sprints, book a Remediation Roadmap Session. That session is separate from the audit fee unless bundled in the original quote.
What we need from you
A responsive technical contact, honest release dates, and permission to say “wait” when the build cannot defend a store submission.