SOC 2 Type II - Final Review
Team will submit SOC 2 Type II evidence package to auditors Thursday afternoon.
Ravi, Nina, Tyler, and Diana held a final internal walkthrough of the SOC 2 Type II evidence package ahead of auditor submission. They reviewed availability, change management, logical access, and incident response sections, agreeing to document the March Detect outage transparently along with its remediation arc. Nina's concern about the 99.9% uptime exception was addressed with a cross-referenced incident note. The team committed to Nina's QA sign-off by Wednesday and submission Thursday afternoon, with the audit window scheduled for the week of April 27th. Diana noted three enterprise prospects and two renewing customers are commercially dependent on the report by end of May.
How the call went
This is an internal call with no external-side turns, so sentiment is neutral throughout.
Opening
0Close
0No turn-level sentiment was scored for this call, so only the opening, close, and overall figures above are available.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 13
- Questions they asked
- 0
- Turns
- 44
- Longest silence
- 1s
Who was on the call
Customer
- Internal call
What happened8
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised3?A problem was brought up on the call.
Nina verified that deprovisioning logs from the last Type I gap finding are included in the logical access section, closing out that finding.
Diana asked about the Comply v2 export format; Ravi explained it produces a point-in-time PDF with hash verification and can be regenerated on demand.
Nina flagged that Detect was below the 99.9% uptime SLA during March; Ravi confirmed an exception note with the incident report is cross-referenced in the availability section.
Commitment1?Someone committed to doing something.
The team committed to submit the SOC 2 Type II evidence package Thursday afternoon after Nina's Wednesday QA sign-off and Ravi's Thursday morning final pass.
Decision1?A decision was reached.
The team agreed to frame the March Detect outage transparently in the incident response section, showing the six-hour monitoring visibility loss alongside the full remediation arc.
Risk1?A risk to the account, project, or system was surfaced.
Diana noted three enterprise prospects and two existing customers require SOC 2 Type II for procurement or renewal, making the end-of-May report commercially critical.
Recap1?A summary of what was agreed.
Ravi recapped the action plan: Nina's QA sign-off Wednesday, final pass Thursday morning, Tyler on standby for evidence questions, and Diana holding auditor comms.
Praise1?The customer said something positive.
Nina and Tyler credited Comply v2's on-demand reporting with replacing what used to take two weeks of manual evidence pulling.
What was promised6
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Complete final QA sign-off on the SOC 2 evidence package. | Nina KowalskiAegisCloud | 22 Apr 2026said “by Wednesday” | internal review or investigation?Conduct QA, audit, verification, investigation, post-mortem, root-cause analysis, or assessment, including testing and analyzing to understand or validate something. | ||
| Complete a final pass on the evidence package. | Ravi GuptaAegisCloud | 23 Apr 2026said “Thursday morning” | internal review or investigation?Conduct QA, audit, verification, investigation, post-mortem, root-cause analysis, or assessment, including testing and analyzing to understand or validate something. | ||
| Submit the SOC 2 Type II evidence package to the auditors. | Ravi GuptaAegisCloud | 23 Apr 2026said “Thursday afternoon” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Send Nina the page reference for the availability exception note. | Ravi GuptaAegisCloud | 20 Apr 2026said “after this call” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Notify the three prospects and two renewal accounts that the SOC 2 report is on track. | Diana ReevesAegisCloud | No date given | notify or loop in?Inform, flag, copy, connect, or give a heads-up to a person or team for awareness, including internal alerts and handoffs that are not formal escalations. | ||
| Hold communications with the auditor contact. | Diana ReevesAegisCloud | No date given | notify or loop in?Inform, flag, copy, connect, or give a heads-up to a person or team for awareness, including internal alerts and handoffs that are not formal escalations. |
Themes and issues5
What the call was about, and the specific issue recorded under each theme.
| Theme | As the model phrased it?The wording the model used before mapping it to the shared taxonomy. | Issue | |
|---|---|---|---|
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance | audit evidence preparation | |
| Incident Response?Calls about detecting, responding to, and reviewing incidents, including post-mortems and root cause analysis. | incident response | outage documentation | |
| Reliability?Calls about overall system reliability, availability, resilience, capacity, and performance, excluding specific outages or incident response. | availability | uptime sla exception | |
| Identity & Access?Calls about identity, authentication, authorization, and access management including SSO, MFA, and provisioning. | access control | deprovisioning log evidence | |
| Reporting?Calls about reporting, analytics, dashboards, and data visibility, excluding compliance-specific reporting. | reporting | audit report export format |
Numbers stated on this call6
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Uptime SLA availability target | “99.9%” | uptime | Nina Kowalski | |
| Duration of monitoring visibility loss in the March outage | “six hours” | outage duration | Ravi Gupta | |
| Number of enterprise prospects requiring SOC 2 Type II for procurement | “three” | account count | Diana Reeves | |
| Number of existing customers with SOC 2 Type II in renewal terms | “two” | account count | Diana Reeves | |
| Deadline for the SOC 2 Type II report | “end of May” | date | Diana Reeves | |
| Time previously spent pulling evidence packages together manually | “two weeks” | effort | Tyler Washington |
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
8 min captured of 40 min stated. Anything said in the remaining 33 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
3 participant(s) speak before joining — transcript and events are on different clocks. Do NOT derive absolute timestamps by joining these two sources.
- Partial transcript(warning)
transcript covers 18.0% of a 40.4min meeting; 32.4min after the final turn is unaccounted for
The model's own note: Transcript is partial (7.9 minutes of a longer meeting implied); internal call with no external participants.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 21,876 tokens