Section 172 – ever asked why?
by Claire Bodanis, founder of Falcon Windsor and author of Trust me, I’m listed.
First published on the Falcon Windsor blog in December 2019
I had my eyes opened by an auditor recently. I must confess that, while I’ve always known that auditors have much to offer the verification end of reporting, it came as a bit of a surprise that I could learn about communication from an auditor too. Maybe, and with all due respect to any auditors reading this, it’s because we’re not talking about just anyone here, but the incredibly knowledgeable Janice Lingwood, formerly of PwC, now advisor to design agency Superunion, and in big demand when new reporting regulations are being debated.
We shared a client with Janice over the previous reporting year, and during that time gained many very useful insights from her about regulation and compliance. But it was when I decided to consult her about our book that I realised that Janice, like us, sees reporting as principally a communication exercise. And, that she agreed with one of the fundamental
principles of the book which is, if you understand why you are doing something, you’ll do it a whole lot better.
During our conversation, Janice happened to mention that, in support of this principle, she runs a workshop for all new joiners at Superunion about why reporting is the way that it is – where the regulations come from, why they have evolved in the way that they have and so forth. So I asked her if she could run one for our team, which she duly did, and which resulted in a lively discussion.
You can read the fascinating details of the history of reporting and how it can help us produce better reports today in chapter 1 of Trust me I’m listed, but here’s just one point that illustrates the principle of the importance of understanding why you’re doing something – how to deal with the new requirement to include a section 172 statement in the strategic report.
This new requirement drives me bonkers from a comms point of view for two reasons. First, because it’s so utterly ludicrous to have to make a statement telling readers that certain information is in there, when, if they just read it, they’d know that it was. Second, if we accept (which we don’t) that our readers are too dim to be able to work this out for themselves, then it is even more ludicrous to have to include the section 172 statement, which is about directors’ duties, in the strategic report (essentially the report of the management) rather than in the governance report (the report of the directors).
Janice’s insight was invaluable. She explained that this requirement came not from the FRC, which has jurisdiction over the governance report, but from BEIS (Department of Business, Energy and Industrial Strategy). BEIS has jurisdiction over the strategic and remuneration reports, but none over the rest of the governance report. So if BEIS wants to change something, they can only do so through those two parts of the annual report. Which is why this statement about section 172, which should properly be in the governance report, was put into the strategic report. (One wonders why the good people of BEIS didn’t just ask the FRC to put it into the governance report to save all this confusion, but maybe I’d better not go there.)
Understanding this background makes it a whole lot easier to be pragmatic about how to fulfil this regulatory requirement without spoiling readers’ experience of the strategic report – or, worse, confusing them entirely. And what might this pragmatism look like? Simply this: include the weeniest possible comment in the strategic report that fulfils the regulatory requirement of having a statement in there, and refer readers to a fuller discussion in the governance report where this statement truly belongs.