Production planning with Yamdu

We have been using Yamdu for more than two years now and would like to share what we use it for.

The initial reason why we switched to Yamdu was that our previous program was not up to the task when creating shotlists.

We have a CRM system, integrated to our financial system, where we keep track of all projects, both film productions and others, so this system is our master for projects, not Yamdu.

Yamdu is used for all film productions where we have either talent, crew with copyright & rights or locations. For each project we keep track of these master objects.

An additional benefit with one single repository is it’s makes it much easier to manage GDPR for persons who’s been recorded or oart of the crew.

When we schedule productions, we use Yamdu to plan which scene that should be taken each day, where and with whom.

If needed, we also plan each shot, with estimated times. Based on these plans, we make call sheets without the need to re-enter information.

If we make storyboards for the production, they are also saved in Yamdu, so we can show each scene and framing for each shot.

We have now started to use the production schedule feature and aligned it with our standard processes for scripted and non-scripted productions.

For scripted productions, we are using Final Draft and import those scripts, including revisions, to Yamdu. For non-scripted productions will we investigate if the manuscript feature can make the process easier.

We have an old license and the resource feature is not included. I have tried it and found it useful, but we haven’t changed license yet.

Main benefits with Yamdu for us are:

  • Have most of the features we need

  • Active development of the product with new features regularly

  • Work together with others in the crew.

  • Works on all devices, PC, Mac, iPads and mobile phones, wherever you are.

Wishlist for the future is integration with our CRM system and time-reporting to avoid entering the same information in two systems.