Hey Christina! Financial Services compliance is a real bear, isn't it?! I used to work for an independent BD and our compliance of public facing assets went through a global relay product that in no way was integrated with Marketo. So everything was pretty manual. First, during our on-boarding we had our implementation manager set up a BCC so that every email we sent was also sent to a compliance email box, so we had a record of everything we ever sent that could be recalled. Although this isn't ideal, it's what we were able to accomplish with limited engineering support. Then for every email we sent out, we were given a compliance approval number, that I added the footer of every email so if a compliance team member ever asked for the approval I could reference the right record in their system. These numbers were long and ugly, so I usually made the text very small and the color the exact same as the background (like white on white) so it was more or less invisible to the end user. Or you could use HTML ( e.g. <!-- approval info here -->)to comment out the approval number, date, etc. The commenting out would also be helpful if you're using Marketo LPs. Next, for disclosures, where the language ALWAYS stays the same (like your broker/dealer disclosure or paragraphs of variable annuity disclosures) we put all of those into snippets and then pulled them in where ever they were needed. That way if they changed say annually, we could update them in once place and have them propagate everywhere. You might also consider using tokens for this purpose as well. Finally, we used dates in our program naming convention, and those dates were the approval dates of any materials, so that we knew with by the same time the following year, the content would no longer be valid. Anyway, if you have other specific questions feel free to ask! We were a small B/D with limited resources, so some of this might not be super relevant to you. Good luck! Julia Good looking out Christina Zuniga!
... View more