Comply v2 - Launch Day Checklist

Right? Like, I've been living in the Comply v2 ticket queue for what feels like six months.

It basically has been six months, so you're not wrong. Okay, I want to run through the launch day checklist today — make sure we're all aligned, flag any blockers, and just kind of do a final gut check before Tuesday.

Perfect. So let me just start from the top — QA sign-off. Nina, where are we on the final regression suite? Last I saw there were like three open items.

Yeah so, two of those are already closed as of this morning actually — the SOC 2 report generation timeout issue and the, um, the framework toggle bug in the multi-report view. Both resolved and verified.

Yeah Dev pushed fixes last night and I ran through the test cases first thing this morning. The third one — the edge case with PCI DSS report download on Safari — that one's still open but engineering flagged it as low severity, cosmetic only, doesn't affect report content.

Okay, so is the call there to ship with it or hold? What's your gut, Nina?

I mean, honestly, ship it. It's a minor UI rendering thing, the PDF is correct, the data is correct. I'd document it as a known issue and patch it in the next minor release.

Yeah I agree with that, and from the design side the Safari issue is — I actually know exactly what it is, it's just a flexbox rendering quirk in the download modal. I can drop a one-line CSS fix, it's not even worth delaying for.

Can you do that before Tuesday though? Like I don't want to be merging stuff day-of.

Oh totally, I'll have it in a PR by end of day today. It's literally one line.

Okay, perfect. Nina you good to verify that today or tomorrow?

Absolutely, just ping me when it's merged and I'll run it through the test suite, should take maybe twenty minutes.

Great, okay. That feels really clean. Moving on — Jordan, the on-demand reporting UI flow, are we good? The walkthrough I saw last week looked amazing by the way.

Thank you! Yeah, I'm really happy with how that turned out. The framework selector, the report preview panel, the download options — it all feels cohesive. I incorporated the feedback from the internal beta users, the ones who said the framework descriptions were too jargon-heavy.

Exactly, so the copy is much more plain language now. Like instead of just saying 'ISO 27001 framework' we have a little tooltip that explains what it covers, who it's typically for. It makes the whole thing feel a lot more accessible, especially for folks who aren't compliance experts themselves.

That was kind of the whole point, right? Like the whole pitch of Comply v2 is that compliance shouldn't require a specialist to operate the tool. So the UX has to back that up.

A hundred percent. Okay, let me — let me jump to something that I want to make sure we're thinking about given the, uh, the Detect outage earlier this month.

So obviously Comply and Detect are separate modules, the outage shouldn't touch us at all. But I just want to make sure our comms are tight in case any customer asks on launch day whether the new Comply features are somehow connected to any recent stability issues. Like I don't want anyone conflating the two.

That's a really smart thing to flag. I'd say from a QA perspective, Comply's infrastructure is totally independent — we don't share the event ingestion pipeline at all. The Comply report generation runs on its own processing layer.

Right, and I think if we can get that in the launch announcement — even just a line that says something like 'Comply v2 operates on dedicated infrastructure' — that kind of proactively addresses any concerns without making it weird.

Yeah I love that, I'll work that into the announcement copy. Okay, let me — what else. Oh, the HIPAA reporting module. Are we still confident that's fully validated? That's the one that was in flux the longest.

Yes, fully validated. And honestly I'm most proud of that one from a QA standpoint. We ran it through like forty different customer data configurations to make sure the report output was accurate across edge cases. It's solid.

No, absolutely not. Okay — last big thing on my list, the in-app guidance. Jordan, the tooltips, the empty state copy, the onboarding flow for first-time Comply users. Where does that stand?

All done and in production. The empty state for when you haven't run any reports yet — I'm actually really happy with it, it's got a clear call to action, explains the four frameworks, and has a 'run your first report' button that takes you right into the flow. It doesn't feel like a dead end.

Thank you! That one took a few iterations. The first version was way too busy. But I think where we landed is clean and it gives people a clear path forward.

Alright, I think we're in genuinely great shape. Like, better than I expected three days out if I'm being honest. I'll update the launch checklist in Notion this afternoon, get sign-offs from all three of us, and then we should be good to go for Tuesday. Anyone have anything else?

Nothing from me. I'm excited. Let's ship it.

Same. Tuesday cannot come fast enough. This is going to be a good one.