Sunday , June 16 2019
Home / Impact Evaluations / Capturing cost data: a first-mile problem

Capturing cost data: a first-mile problem

Summary:
Before we bought our house, my husband and I knew the price. The real estate agent wasn’t allowed to give us a back-of-the-envelope estimate right at the end of the process. She wasn't allowed to just declare that the house was low cost, affordable, or sustainable for our budget. We knew the exact price of ...

Topics:
Alaka Holla considers the following as important:

This could be interesting, too:

European Central Bank writes Luis de Guindos: Interview with Corriere della Sera

Amol Agrawal writes 100 years of first transatlantic flight..

Amol Agrawal writes From Harvard vs Hard work economists to scoot and shoot economists..

Swiss National Bank writes 2019-06-14 – Minutes – 22nd Meeting of the Working Group, 13 June 2019

Before we bought our house, my husband and I knew the price. The real estate agent wasn’t allowed to give us a back-of-the-envelope estimate right at the end of the process. She wasn't allowed to just declare that the house was low cost, affordable, or sustainable for our budget. We knew the exact price of each house she showed us, not just how many bedrooms each had, what the walls were made of, or the quality of the public schools in the neighborhood. There are even laws that stipulate how transparent she and the bank offering us credit needed to be about the total cost of buying a home.

Somehow we don't hold ourselves to the same standard when we're asking a government to invest in a particular program or policy (which, by the way, are way more expensive than a house, even a house in the DC metro area).  We spend a great deal of our efforts making sure our estimates of benefits are valid and precise; then we either present some quick estimate of costs in the final section of our papers or reports or we avoid this altogether and just declare from the outset that we are testing something is low-cost or scalable. Then, for some mysterious reason, we feel we're in a position to offer policy advice.

I have blogged about the absence of cost estimates before, and Dave Evans has also offered some hypotheses for why we don’t regularly feature costing analyses in our impact evaluations. JPAL provides guidance for conducting cost effectiveness analysis, and USAID has cost reporting guidance for its education programs.  At the Strategic Impact Evaluation Fund (SIEF), we require that teams that receive funding collect cost data and present a costing analysis in their end line reports.

Despite all of this, we still find ourselves in a situation where we have sloppy estimates of costs (if we have them at all) that play a very minor role in our overall assessment of whether a program or policy was successful. What's going on?  I believe we have a first-mile problem. We don’t know how to get started.  While there's plenty of guidance on how to conduct a costing analysis, all of it assumes that you have already collected the cost data. The cost data, you need, however, isn't just lying around all in one place waiting for you to pick it up; you somehow have to go capture it, and there's very limited guidance on how you should go about doing this. There are some templates in the form of complicated spreadsheets with macros that are sure to give you an awful headache, but again, they assume you know how to find the data that must be filled in.

To remedy this, we at SIEF – in coordination other groups interested in supporting greater use of costs - are developing guidance and case studies on capturing cost data. We want to describe the process that takes you from a from a blank spreadsheet to a final estimate of total cost. With the International Rescue Committee, we have already published a brief note that outlines some of the basic ideas. The first point is that cost data needs to be disaggregated. It's not enough to know how much was spent on salaries in total, for example. You want to know how many people were needed to make an intervention happen and what their rates were. This isn’t important just for verifying the accuracy of more aggregate data; it’s also necessary for estimating costs for a scaled-up version of the program or for implementation in another geographic area where labor costs might differ. Disaggregation can also help identify opportunities to save money in future iterations of the program.

Second, cost data should be intervention-specific. The data must include the costs of all inputs that were required to make an intervention happen and must not include the costs of inputs that served other related programs. This turns out to be complicated for inputs like management and labor that are often shared across multiple programs. You want to capture the time and effort people have spent on the program you're costing and not the time and effort they spent on other programs. You also don't want to say , "Oh, these are fixed costs; these people would be paid anyway in the absence of my program, so I'm not going to count the costs of their time." When they're working on your program, they're not working on something else. Unless you assume they would otherwise do nothing in the time they're working on your program, then it's important to count their time as a cost. Similarly, if delivery of your program requires vehicles and fuel and other programs also use these inputs, it will be important to apportion of fraction of these costs to the cost of your program.

Therefore, a third point we make is that cost data cannot be limited to financial data. To get disaggregated and intervention-specific data, you may need to interview people, to get out and see the program in action, and to rely on regular monitoring and evaluation data. You might even need to collect time and effort data to accurately apportion expensive inputs like management and labor to your program. Rarely is this kind of information waiting for you neatly in the budget or financial records of program implementers. My colleague Sam Fishman blogged about his experience in Bangladesh costing an additional year of preschool. He first asked for the implementer's financial records, and by the time he stepped everyone through the process of disaggregating the data and making it intervention-specific, the estimated total cost of the program had quintupled.

To do all of this, we argue, planning for cost data collection ideally starts before implementation of an intervention and data gets collected in real time. There are some expensive inputs like staff and management time that suffer from significant recall bias and thus asking people to remember how much they worked on something a year or more later can't be a good idea (see Kathleen Beegle's illuminating blog on the challenges of measuring labor in surveys). Collecting data in real time also allows you to take advantage of other data collection efforts that might accompany a project like regular monitoring. It's much easier to add some fields to a monitoring instrument than to conduct an entirely separate survey just on costs.

We hope to show by example in our guidance. If you have good case studies in mind (that show what can go right and what can go wrong when trying to estimate costs), please send them our way (write to [email protected] and use the word "Costs" in the subject line). Please also get in touch to let us know what challenges you have faced when trying to capture cost data or when trying to get started.

As a starting point, here a few challenges that researchers have noted that can come up when costing the programs they are evaluating and our suggested ways of dealing with them:

  1. Government officials and program officials may be reluctant to share their salaries, or to have them made public.  
    Suggested solution: Government salaries, as well as program officials paid by aid agencies, are often public information, so there’s no need to ask people themselves to reveal their salaries. If an individual’s salary is not publicly available, then a schedule of average salaries by grade could provide a reasonable substitute. Moreover, as with any data, costing data when published typically does not have names attached but rather roles – for example, senior trainer – and this confidentiality should be emphasized at the time of data collection.
     
  2. How should the time of researchers designing and monitoring a program be counted? Many impact evaluations involve substantial time from field coordinators, university professors, and other researchers. Some of this time concerns program design and implementation (e.g. how to ensure take-up, actual supervision and monitoring in the field), while some relates to the impact evaluation. Sometimes all of these costs are paid by one source, but sometimes they are the responsibility of different funding streams. It is often unclear how much to include in program costs. 
    Suggested solution: This is a more general problem related to allocating costs when resources are shared – in this case, researcher time is shared across about program design, program supervision, and evaluation. Typically, we leave out the costs of evaluation when costing programs because most interventions do not come an evaluation (particularly when they are scaled). Thus, we need to identify how much researcher time has gone into the design and implementation of the intervention itself. To do this, researchers will need to keep track of this, ideally monthly. For example, during the design phase, we might spend 80 percent of our working hours on the project, with half of the time spent on the design of the program and half on the design of the evaluation. During other phases like implementation, we might spend considerably less time on the project overall and most of this might be on supervision tasks. Keeping track of the activities, the overall percentage of time, and the allocation of time across activities would not only help with an accurate estimation of costs but would also help with costing a version of the program in which non-researchers take on some of the activities.
     
  3. Concerns about how the cost data will be used. Many funders have  budgeting rules that could make it much harder to give a $20 take-up subsidy to a program participant or to buy a $1,000 laptop than to spend $300,000 on salaries, or they might have other limits on how funds can be spent that don’t match the needs of program implementation. Bundling these items into lump-sum delivery contracts allows for programs to be implemented efficiently, but researchers may be concerned that very disaggregated cost data will leave them vulnerable to line-item audits. 
    Suggested solution: The good news (which is really bad news for the costing agenda) is that typical financial reporting to donors is not that helpful for costing a program. Costing data that includes all of the ingredients required to make an intervention happen, their quantities and prices, and their timing usually must be tracked separately. Since we are advocating starting the costing process early – before program implementation even begins – this could be a good way to start a conversation with a donor about the financial reporting you will have to do and whether the budgeting rules are realistic for the intervention that is being implemented. Moreover, in the guidance, we hope to include messages to donors so that their financial reporting does not just aid their fiduciary oversight but also contributes to global public goods like a set of costing estimates and necessary ingredients for an intervention implemented in different contexts.

Leave a Reply

Your email address will not be published. Required fields are marked *