Brandon 1:1 on Teams: compliance change log — 2026-09-03

Eleven messages between 9:18 and 10:44 AM ET. Brandon opened with a message he deleted a minute later (JT's reply says he downloaded something and saved it to his Desktop); the substance is JT's two updates on the Compliance Manual work and Brandon's note that he is unwell.

Summary

• 9:21 AM, JT: updating the AI portion of the Compliance Manual after research the night before; the change log and manual would be updated shortly; most changes answer the items Brandon raised in his review, plus a few more JT found and noted for him.
• 10:14 AM, JT: the compliance change log is ready for Brandon's review. If it is good, JT packages everything, posts it to the public drive, finishes the training modules, and sends the advisors a notification to complete the training and sign off. JT added a column to the right of Brandon's with responses to each of Brandon's items, and notated other items found on a second pass.
• 10:43 AM, Brandon: under the weather, heading home; will dive into all of it tomorrow or over the weekend. JT: sounds good, feel better.
• Donut chatter in between (Brandon debating an order; JT: "The $20 Donuts?").

Decisions

• JT: the rollout sequence after Brandon's sign-off is package, post to the public drive, finish the training modules, then notify advisors.
• Brandon: review slips to 2026-09-04 or the weekend of 2026-09-05.

They asked me for

• Nothing raised.

I asked them for

• Brandon: review the compliance change log (and the manual updates) and say whether everything looks good. Status: open, expected 2026-09-04 or the weekend.

Concerns and frustrations raised

• Brandon: unwell; left the office mid-morning.

What they are focused on

• Brandon: the Manual and change-log review when he is back.
• JT: closing the manual updates so the training modules and advisor notification can go out.

Doable / not doable / needs a decision

• Advisor notification Friday 2026-09-04 → not doable if Brandon's review lands over the weekend; Monday 2026-09-07 is the realistic soft-launch date (the 2026-09-02 email to Derek already named Friday or Monday).

Action items

Mine

• After Brandon's sign-off: package the change log and manual, post to the public drive, finish the training modules, send the advisor notification — target 2026-09-07 — (Notion: not pushed)

Theirs

• Brandon: review the compliance change log and manual updates — 2026-09-04 or the weekend

Suggestions for me

• Brandon's review gates the soft launch and the Zakir complaint referral; he is out sick. Do not stack a third ask on him this week unless it is the Zakir contact.
• The deleted 9:18 AM message is the only gap; whatever JT downloaded is on his Desktop, not in the record.

Notable quotes

"The compliance change log is ready for you to take a peek at and review." — JT "Can dive into all of this tomorrow or this weekend." — Brandon Drespling