I’m not sure if this is typical for other consultants, but I spend a lot of time reading through corporate annual and quarterly reports (called 10K’s and 10Q’s, respectively, after the SEC form names). These reports give lots of information, including a description of the business (useful for technology and biotech/pharma companies which can be difficult for the layperson to understand), snapshot of performance for the period that is reported, the relevant historical comparisons for current performance (e.g. the year before, the same quarter from the year before, etc.), and a list of risk factors for the business.
These reports are produced by public companies (and by some private companies, no doubt) for the benefit of investors who no doubt want to know exactly what they are investing in. But, I do also believe that the very process of making these reports is good for management as it forces them to think very hard about their strategy, their competitive environment, and their ability to execute.
This is why, despite scoffing when I first heard about a consultant at my firm who compiles an annual report for himself (complete with a letter to the shareholder — himself), I have recently started compiling these reports. Yes, I know this is incredibly nerdy, but hear me out. Four reasons why everyone should think about making personal annual and quarterly financial reports:
It’s not necessary to copy the form that corporate annual reports come in, and it’s not necessary to do monthly reports or to make them especially pretty. What is important is to pick a schedule which sounds reasonable (I suggest every 3 months as a good balance between having to do it too often, and having to do it not often enough) and to pick a form which is reasonably easy to do but still forces you to write down your past track record and future plans (could even be scribbles on a notepad if that works for you).
Or if you’re more artistically inclined, you can do what Podravka, a Croatian food company, does which is make an annual report that is only readable after you bake it (hat tip: Eric).
But that’s just for extra credit…