Hints and tips for Framework applicants

published on

I've been asked for my hints and tips on preparing a submission for the 2010 Framework Innovations funding.

All I can do is to note a few things based on my past Framework experience but priorities and requirements change each year so my list is certainly no more than a rough guide to supplement advice from the Framework team.

It's a pretty painful process to trawl through around 100 applications in a short amount of time. It never ceased to amaze me how organisations (nameless) would send in 10 applications with content and budget pretty much identical! And some of the budgeting was, to be kind, inventive. The selection panel are highly experienced e-learning and project management leaders

So here's my list...

  • Research what has been done before in Framework projects
  • Build on from, and acknowledge, past projects
  • Describe your current practice and what works well and what doesn’t – fill the gaps and accentuate what works – think of what can be done to make your program better still
  • Research other Framework research work, Toolboxes etc – you won’t get funded to replicate
  • Narrow your project right down – don’t try to do too much
  • Treat your project as a model from which you can extend
  • Describe how you will roll out, extend and embed your project
  • Describe how your project will survive long term – it must be sustainable
  • Have senior management buy-in
  • Don’t be a one person show
  • Make business partnerships REAL – build on existing relationships rather than establishing new ones
  • Involve students – get their input and feedback
  • Photograph and document each step – these are really useful for your report•    Don’t be afraid to take risks, make mistakes and ask for help .... early
  • Be realistic in your budget – don’t overcharge and don’t make up items – the selection panel reads them carefully and know what things cost
  • Make connections with other Framework teams, in and beyond your RTO
  • If your RTO is submitting more than one application allow each ‘owner’ their own look and feel – don’t copy/paste unless standard RTO data/info

What else would you add? Leave a comment