Help

One base or multiple project bases for a project and task management design

Topic Labels: Base design
506 2
cancel
Showing results for 
Search instead for 
Did you mean: 
jwendt65
4 - Data Explorer
4 - Data Explorer

Hello all. I'm new to Airtable and I have been charged with setting up project and task management for our team. We have a team of about 10 with multiple projects and tasks that are randomly assigned based on availability and skill level. Each project has a timeline with tasks, start and end date, status and assignee. The assignee can have multiple tasks on multiple projects at any given time. My question is, do I create one base with each project as the master table or do I create a separate base for each project and sync the tasks, assignee and status. I need to have a calendar view for each assignee with all of their upcoming task due dates and ideally an overall calendar view for the team director who can see all upcoming tasks, due dates, etc. 

We also want to share the status with groups outside our team for each project, so the outside team can see the status of tasks and overall project status.

There is another wrinkle in that help desk tickets also create tasks that are assigned for projects. Those also need to be incorporated into the calendar view.

Any guidance on whether I should start with one base or multiple bases would be greatly appreciated.

 

 

2 Replies 2

Hello,

I do not see any reason to do this with several bases.

All projects have the same properties, hence it makes sense to have a "projects" table. It will be much easier to integrate a new project by just creating a new record rather than creating a new base.

Maintenance will also be easier. If you need to add an information, for example "project cost", you will need to do it only in one place rather than having to modifiy each separate base.

Furthermore, having a single base will enable to have an interface where you can see all projects in the same view.

Regards,

Pascal

+1 for using a single base