We understand how hard modelling can be. Our team see a lot of models, and we know that it’s essential to get the measure of them quickly.
I was recently looking at a set of templates issued by a public sector procurement authority and I was struck by the number of tell-tale signs that this was not all the original work of the ‘author’.
Continuing with our breakdown of the Financial Modelling Code published by the ICAEW late last year; this time we look at ‘User interface and transparency’. There is some overlap with the last blog about ‘Layout and structure’ – both sections are largely about designing a model that makes it easy to avoid errors. In the process, your model will become user friendly.
In the third blog in our series about the ICAEW Financial Modelling Code, we complete our look at Layout and Structure. Following our discussion of structure last time, this week we look at navigation and inputs.
In the second blog in our series about the ICAEW Financial Modelling Code, we look at Layout and Structure. There is a lot in the Code on this subject, so we’ll split it over two blogs, this week, looking at structure, next week at navigation and inputs
This is a new series of blogs in which we will dig into the new ICAEW Financial Modelling Code. Sign up to receive the whole series here. You can also download our whitepaper describing the Numeritas approach to complying with the Code here: download our whitepaper
Carillion had already identified for itself the top two risks that might cause failure. Here’s what they were:
Tim Martin, Wetherspoon’s chairman (and vocal advocate of Brexit) says he’s ready for Brexit and isn’t worried about a ‘no-deal’ cliff edge. How ready are you?
What is the purpose of a model audit?
Would you send an important document, perhaps a proposal or a contract for example, without spell checking it first? Of course not!