All Collections
Doc basics
Doc use cases
Organizing your project tracker
Organizing your project tracker

Learn a few best practices for project structure in Coda

Updated over a week ago

Coda Tips!

An organized project tracker gets you one step closer to a successful project. We find that no matter what you're working on, every great Coda doc has the following core pieces:

  • A Welcome to this Doc Page highlighting what the doc is for and how to use it. It's a good first impression, and sets the tone for your awesome doc.

  • A Core Tables Page which houses the underlying tables that power the rest of the doc. 

  • A Team View Page which gives your team their own workspace so they don't step on anybody's toes and can customize to their hearts' content.

  • A Meetings Page to house a running list of meeting notes.

With these core principles in mind, our recommended structure for a project tracker doc looks like this:

Page 1 - About this doc
This page acts as an introduction for any new team members or stakeholders. This is your chance to explain how to use the doc, and how it fits into your team's workflow.

Page 2 - Base Data
Having a base data page as a top-level page is a great way to highlight the core of your doc - the table that runs it all. 

  • Subpage A - Teams and Tasks - This page should hold your core task table . You'll be pulling all your views from this table. 

  • Subpage B - Urgent Tasks - It can be helpful to highlight all of the urgent tasks in one space. Here you would create a view from the core table filtering by however you are depicting urgency. Keep in mind, this view could be anything - tasks by week, tasks by person, and the list goes on!

Page 3 - Team/Phase - If your project is made up of multiple committees or phases, you can create pages for each of them to give people the freedom to work with your core data on their own terms while still keeping everything unified. 

  • Subpage A -  Vision - Just like the core project vision, this page can act as the guidelines and information for the team or phase.

  • Subpage B - Tasks - In this subpage, create a view filtered by tasks assigned to this team or phase. Then, the view can be customized based on the team's preferences. 

  • Subpage C - Meetings - Everyone needs a place for meeting notes, and this subpage can act as a repository. Note, that you can stick with the basic text editing aspects of Coda, or build a table here as well.

Page 4 - Summary and Email Update
Inevitably, you'll need to share your progress and stats with people outside of your team. This page can act as your report out to the wider organization. You can even connect this to the Gmail Pack or Automations to handle this process automatically. Here, you'll use formulas to show what's been completed, what's incomplete, and any other data that's important for folks to know about.

With this as the backbone of your tracker, you can then customize, add, and subtract based on your team's preference and style. Remember, no one knows your team or workflow better than you - make it your own!  

Did this answer your question?