<aside> ‼️ Taking these steps will allow for smooth, efficient communication between our team and yours.
</aside>
[ ] Identify all points-of-contact from your team that will be available for the entirety of the audit.
<aside> ℹ️ These people should have the technical and non-technical context of the project and enough bandwidth to answer all questions.
</aside>
[ ] Enable notifications for the main communication channel.
<aside> ℹ️ Responsiveness is essential; the quicker questions are answered, the more effective the audit will be.
</aside>
[ ] Plan ahead for the time your dev team will need to implement fixes for any significant audit findings.
<aside> ℹ️ This will allow you to complete your fixes as quickly as possible, which will then let us review your fixes while your code is fresh in our minds.
</aside>
<aside> ‼️ This step is particularly important if you have a firm deadline by which you need to have the final report in-hand (ex: a publicized launch date). Knowing when to expect all of your fixes allows us to pre-book time on our schedule to review them. If you are unable to commit to a deadline for your fixes, we may not be able to review them right away since the auditor may be working on another audit. If this is the case, we will work to accommodate your schedule as best we can but we cannot make any promises.
</aside>
What we need to deliver an estimate
How to get the best estimate and audit