Keeping Track of Client Decisions

I’m a custom home builder and use Coda to communicate with information about their project via a dashboard. We mostly give them a peek into the tasks that we’re working on, statuses of various budget items, and provide them with a to do list of things we need from them (like faucet selections, etc.)

I’d like to add the ability to let them communicate decisions regarding things. For example, we’re about to do some demo work and we’d like clarification on a couple of items. This is something we could do in emails but as we move through a project, there can be hundreds of little decisions like this and it’s easier to go back later and find them all in one place, especially if you’re on a job site and just want to pull up the info without searching and scrolling through emails.

My initial thought was a doc like this but there are some inherent problems with the checkbox, so I’ve moved to a table with a list of the “issues” thinking I might filter them by a topic field (photo below the dashboard of the table concept).

Here’s the table that maybe I integrate via filtering

I would love to hear other people’s thoughts on this and if they have a better option that I should consider implementing. I want it to be:

  • Easy to communicate with clients
  • Easy for us to go find the decisions later if needed
  • A permanent record stating who made the decision and when

Thanks!

Hi @Lynn_Currie

Looks like you’re just about there.

What I would add is to make use of the sub item functionality. That will allow you to keep track of “evolving” decisions.

And yes, you DO NOT want these floating around emails, where nobody knows what the most recent decision was.

What did you mean with “integrate via filtering”?

P

Thanks @Piet_Strydom

Can you point me in the direction of either an example doc or description of how to implement the sub-item functionality?

RE: “integrate via filtering” - In the table I added a “for filtering” column so I could put the response to choose from directly under the relevant paragraphs/section like I initially did with the checkboxes.

Ah, apologies, subitems is still in beta, and it seems there is a backlog of beta applicants at the moment.

What it allows you is, for a row, to add a subitem row that is linked via a parent child relationship. (You can do that yourself via a relation column type. (By linking the table to itself.) But the Coda version gives you a prettier, indented user interface.)

Perfect for projects and tasks

I’ve got the beta of subitems implemented in my system so I can use them.

Are you thinking that whenever there is a change to a selection, the table creates a new subitem of the “Approval”, “Responder”, and “Date” records?

I have made a short video of how I use something very similar in my daily job. (I mention in the video you can create a table spanning all projects, I should have said view.)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.