On Wednesday night at 9:30pm Zambia time we got a call from Grand Challenges Canada to say that our bid to them for scale-up funding had not been approved by their Investment Committee (IC). This leaves a 1 million dollar hole in our 3-year scale-up plan. As well as being a significant amount of money it’s strategically important too, as a large proportion of this money was ear-marked for undertaking operational research to capture and share the learning that we will generate during the scale-up process.
We are grateful to Grand Challenges Canada for their support for the trial – they contributed $CAD100,000.
Given the results of our trial (see below) and GCC’s aims we thought we were a great fit for the follow-on scale-up funding which supports:
Bold ideas and integrated innovation – the co-ordinated application of scientific/technological, social and business innovation – with a strong likelihood of achieving substantial and measurable health gains in an under-resourced setting
So just when we thought it was “safe” to take some leave(!) we find ourselves searching for another funding partner. Help and suggestions in this regard would be gratefully received.
Finally, we are also grateful for all the enthusiastic support we have received from GCC on social media over the last couple of years. Here’s a sample:
The key headlines from the ColaLife Operational Trial in Zambia (COTZ) – Sep-12 to Aug-13:
Request access to ColaLife’s Findings and Learning
The data contained in this blog post: Findings in this blog post are unpublished and based on initial analysis of data from the ColaLife Operational Trial in Zambia (COTZ). Final calculations may vary and will be published in peer reviewed literature in due course. In the interim, the following citation may be used: Ramchandani, R. et al. (2014). ColaLife Operational Trial Zambia (COTZ) Evaluation. Johns Hopkins Bloomberg School of Public Health, Baltimore. Related correspondence should be sent to Rohit Ramchandani (firstname.lastname@example.org) and copied to Simon Berry (email@example.com).