One of the elements we've worked on is what the deputy minister at Transport talked about, which is something technical called the program activity architecture. That's his foundation for reporting. We have worked on making sure that we have a clear description of what program activities we have, based on the framework of how we articulate that story.
We've gone from a 150-page report that was quite long and without concise information on where you can get further information if you have a particular interest in a particular topic. It was difficult to do before, whereas now we have links throughout the document. If you're interested in a particular topic, you can drill down, and we keep that information ever green. We've actually been working with Treasury Board Secretariat. They've asked us to work with them as a case study for guidance when the next round of guidance for departmental performance reports is to go out.
As I said before, we've also gone above and beyond in providing on the lower level online. So if you take some of the sub-activities.... Again, I know it sounds quite technical, but it becomes the work that we do, and how we determine if we're meeting that result or not is available and transparent to all.
We've also included our financial information by program activity in graphical format as well as tabular format, so you can see what we're doing, what results we're trying to attain, and how much we're spending or not spending in that particular area, in quite a concise format, with available references should you want more information in that area.