# Close-out Call and Walkthrough ## Close-out Call The Close-out call will have all relevant stakeholders including the security review team, core team, and key members from the client. From this close-out call, all parties should come away with a clear understanding of what occurred during the security review period and the vulnerabilities identified by the security researchers. All expectations and deliverables initially communicated during the kick-off should now be met and closed out. Additionally, clear and actionable next steps should be established moving into the remediation of the vulnerabilities identified as the engagement moves into the [Fix Period](/spearbook/anatomy-of-a-spearbit-review/fix-period.md) stage of the review process. \ \ A draft report will be provided for internal usage of the security review containing all valid issues as well prior to the close-out call and after completion of the security review period. {% hint style="info" %} **Note:** If after 1 week of receiving the report the client does not provide any comments or concerns raised, the client acknowledges the report is complete and the report will be considered final. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.spearbit.com/spearbook/anatomy-of-a-spearbit-review/close-out-call-and-walkthrough.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.