You have a project in your head. Maybe a documentary series you've wanted to start for a year, maybe something you're about to pitch to a fund, maybe an exhibition you want to propose to a gallery. The idea is clear, the plan isn't. The moment you start writing down what you're actually going to make, how you'll get there, and what happens to it afterwards, you notice that a good idea and a good project plan are two different things. I saw how funds, galleries and photographers themselves structure project plans, and a few patterns kept coming back. Here are seven of them.
Start your project plan with your own reason for making it
A project plan that opens with a general subject reads differently from one that opens with a personal reason. The reason this story needs to be told, and why by you specifically, belongs in the first few lines. Your own background, position or access shapes how you approach the subject. Write that down explicitly instead of leaving it out. 'I want to document the fishing community of Urk' says less than 'I grew up in a fishing family myself, and I'm watching the next generation walk away from it'. The second version gives a reader a quicker reason to keep reading. A good reason doesn't need to be dramatic. A long-standing fascination, a chance encounter, or simply something you notice every day in your own surroundings works just as well, as long as you explain why it caught your attention and not someone else's.
Show how you'll get there, not just what it becomes
A project plan often describes the end result at length and the process towards it barely at all. Some photographers research beforehand, others work from a fixed location or travel around instead, alone or together with the people they're photographing. Whether it's a fund panel, a gallery owner, or yourself six months from now: that process is just as interesting as the subject. It also shows you've thought through the practical side, not only the artistic one. A project plan that only describes the result leaves the reader guessing how realistic that result actually is. A few sentences on your approach take that doubt away.
Name concrete milestones, not broad phases
'Research in spring, shooting in summer' sounds like a plan, but says little. A milestone only becomes useful with a concrete deliverable marking when a phase is truly finished: a first selection ready, a test shoot with the main subject, a confirmed location. Deliverables like these make a timeline credible, and give you something to hold onto to see if you're on track. It also helps when explaining your planning to others: 'sometime in summer' invites a follow-up question, 'first edit finished in August' doesn't.
Know when it's finished
For a project with a hard deadline, like a grant round or an exhibition date, this is clear by default. For a long-running, self-initiated project it's harder, and that's exactly where a project often stalls, because there's no clear endpoint. A number of images, a timeframe, or a substantive criterion like 'when I've told this family's story in full' gives you something to hold onto. It can still shift along the way, but a vague endpoint isn't an endpoint. Without that point, a project can easily keep running until it stalls on its own from lack of time or motivation, instead of being wrapped up deliberately.
Think through what could go wrong
Access falling through, a participant dropping out, a location no longer available, weather dependency on an outdoor project. You don't need to foresee everything, but a short paragraph on risks and what you'd do about them shows you've thought beyond the optimistic scenario. For a fund or gallery, that reads as professionalism. For yourself, it's a useful reference point if something goes sideways along the way. A couple of lines are usually enough: which risk you see, and what your alternative is if it happens. A location falling through, for example, can be covered by a second option you've already scouted.
A budget that matches your project plan
A budget of €15,000 for a project that can be shot in three weekends raises questions, even if the project itself is strong. Work out what your line items actually cost: travel, equipment, hours, post-production, presentation. Many funds require a quote above a certain threshold, for example above €1,000 per line item. Specific amounts per item, even if you have to estimate, read as more trustworthy than a couple of generous totals without justification.
Don't forget what happens next
Describe what happens to the work once it's finished: an exhibition, a publication, a presentation, a partnership with a local institution. 'I want to share the work' isn't a plan, it's a wish with no follow-through. Name where possible where, with whom, and preferably also when, even as a tentative estimate. A missing follow-up is often a weakness in project plans, and also one of the easiest to fix. It takes a couple of sentences, and it turns a project that ends at "the photographs are done" into one that's working towards something.
These seven points won't solve your entire project plan, but they're where a plan most often gets stuck. Whether you're writing a grant attachment, proposing an exhibition, or simply want to write a project plan for your own photography project: the project plan tool helps you write this out in your own words, with guidance at every step and a check for vague language at the end. Not a ready-made document, but preparation that makes starting or pitching a project easier afterwards.