Stark's Fidelity accounts in the Fiduciary Oversight Report — 2026-06-10

Teams 1:1, 9:03 AM to 4:51 PM ET, twenty-eight messages. Brandon asked for an updated Fiduciary Oversight Report; the day's work was getting Brian Stark's Fidelity-custodied TTAMP accounts into it (Stark is matched by surname to the roster; Brandon and JT wrote "Stark", "Starkey's", and "Starks").

Summary

• Brandon: all of Stark's accounts are in the TAMP except possibly two tiny ones. JT: if only two small accounts sit outside the TAMP, it is more efficient to treat them as TAMP accounts than to build another lookup that can break; pulling by his g-code would pull all of them. Brandon: "tomorrow is fine for those."
• JT's design: for Fidelity, drive Stark's accounts off the TTAMP field in Black Diamond rather than the rep code, leaving Schwab on the rep code, so a Black Diamond flag triggers them; four accounts were flagged Fidelity. The model allocation was the open question because Fidelity has no models or sleeves recorded for them.
• Brandon: with so few at Fidelity he would do those four manually; he allocated them from the MAP with a spreadsheet, "old school", because they do not have iRebal there. JT should take the model from the TTAMP MAP for those four accounts.
• Brandon: iRebal settings "are so messed up" he cannot use it and would call the iRebal department that day.
• 12:31 PM: JT sent a fresh report with Stark's Fidelity accounts added (MAPs and agreements pulled, model allocations entered for four accounts), a new Custodian column on the TTAMP tab, and a previously unpushed update to the RMD Schwab download report (remaining required RMD for the year, current-year totals, grouped at the end); Brandon can ask for it to be removed if it is noise.
• The IAR state registration session slipped again: JT had to leave before 4:00 PM, Brandon had been out all morning; agreed on "Manana."
• Golf banter: Brandon played "Terrible... Been off for a while."

Decisions

• JT: Stark's Fidelity accounts are pulled by the TTAMP field in Black Diamond; Schwab stays on the rep code.
• Brandon: the four Fidelity accounts are allocated manually from the TTAMP MAP; no Fidelity model is created.
• Both: states session moves to 2026-06-11.

They asked me for

• Brandon Drespling: an updated Fiduciary Oversight Report. Status: done 9:16 AM and again 12:31 PM with Stark's Fidelity accounts.
• Brandon Drespling: add the two small non-TAMP accounts later. Status: open, "tomorrow is fine."

I asked them for

• Brandon Drespling: whether pulling all of Stark's accounts by g-code is acceptable versus another lookup table. Status: answered (do the four Fidelity ones manually, treat the rest as TAMP).
• Brandon Drespling: where the Fidelity model allocations live. Status: answered (the TTAMP MAP).

Concerns and frustrations raised

• Brandon Drespling: iRebal settings unusable; calling iRebal support.
• JT: extra lookup tables add "more things that can break."

What they are focused on

• Brandon Drespling: the Fiduciary Oversight Report as his daily working file; iRebal; the state registrations.
• JT: making the report's account selection data-driven (TTAMP flag, rep code) and keeping the repo's report updates pushed.

Doable / not doable / needs a decision

• Fidelity model allocations from the MAP → doable manually for four accounts; a Fidelity custom field was offered and not taken up.
• iRebal fix → Brandon's call to the vendor; not JT's.
• RMD columns in the report → doable; Brandon to say if they are noise.

Action items

Mine

• Add Stark's two small non-TAMP accounts to the report if Brandon still wants them — target 2026-06-11 — (Notion: not pushed)
• Fresh Fiduciary Oversight Report with Stark's Fidelity accounts, Custodian column, RMD update — done 2026-06-10 12:31 PM

Theirs

• Brandon Drespling: call the iRebal department about the settings — 2026-06-10
• Brandon Drespling: say whether the RMD columns should stay — no date

Suggestions for me

• Brandon's preference is the manual path when volume is small ("do those 4 manually"); offer automation only where the count justifies it.
• He asks for a "fresh one" most mornings; the report is his working file, so a scheduled morning send would remove the ask (this is what the later Options Report daily send did).

Notable quotes

"iRebal settings are so messed up that I can't even use it at this point." — Brandon Drespling "There will be so few at Fidelity (at least for now) that I would just do those 4 manually." — Brandon Drespling "They don't have iRebal...so had to just do it old school." — Brandon Drespling "I can figure it out building another lookup table or something but just ads more things that can break if its not a big deal" — JT