At the latest, when you're handling multiple deliverables for the same client within a similar timeframe, you'll find yourself asking the question: Is this one project or three?

Typically, it's best to consider the following questions:

1. Would it be beneficial to maintain three separate project histories?

   • If the assets provided by your client are the same for all three projects, it might be more efficient to combine them into a single history to avoid redundancy and have a single search location.

   • On the other hand, if you believe that a single timeline would become too cluttered with information, and you want to keep notes and conversations separate, having three timelines might be a better approach.

2. Would it be beneficial to manage three separate task boards?

   • If the workload for each deliverable is substantial, and organizing tasks on a single board would be overwhelming, consider splitting them.

   • If you prefer having one comprehensive task board with all tasks across all deliverables, it may make sense to stick with one project.

3. Would it be beneficial to assess the health of individual deliverables in the project overview?

   • Do you want to track the efficiency of each deliverable in terms of budget versus spent time separately?

   • Do you wish to monitor time usage for each deliverable individually? In that case, it's wise to split them into multiple projects.

If you're still uncertain, we recommend splitting it into multiple projects. This offers greater flexibility, albeit at the potential cost of a more detailed overview and some duplication.