Using Q4 PRESS to Satisfy Reg FD for Blog Content
Yesterday I posted about the importance of the controls over the vehicle in which corporate disclosure is distributed.As I mentioned, it wasn’t supposed to be about plugging our products, but as I was creating the post using Q4 PRESS I took a few screen shots throughout to be able to demonstrate how simple it was. Read more to see how simple it is to satisfy Reg FD for blog content with Q4 PRESS.
After I created the first draft, I broadcasted the document to the Q4 management team for approval and then I checked the dashboard to see who looked at it or responded:
Next up I reviewed the suggested changes from Catherine and Darrell:
Both Catherine and Darrell approved the document, so I finalized it and generated an ‘exposure report’:
After the document was finalized, I was able to go in and generate a full historical report of exactly how my document evolved – what happened, when it happened and who did what:
As you read this, the post from yesterday was blasted out through our RSS feed, Twitter, Technorati, Facebook and our corporate website (via an inbound RSS module in Q4 WEB). All of this distribution came for free through 1 simple process that has given us a full audit trail of how the content was created along with a ‘post once, distribute everywhere’ model.
The vehicle is the easy part and demonstrating that implementing proper controls isn’t as hard as the FUDDERS are making it out to be.
Related posts:
- Who’s reading insider email? Nobody with Q4 PRESS!
- GE uses corporate blog to disclose information to investors
- Q4 Press New Spring 08 Features!
- Q4 PRESS for Blackberry
- Barrick Gold Goes live with Press Release RSS feeds
Related posts brought to you by Yet Another Related Posts Plugin.