Is it possible? One day based table for vacation days and employee sickness for all team members

Dear Community,

I’m getting a bit desperate with this task and hope someone can help me!

I would like to create a kind of attendance calendar or table where 17 team members can enter their vacation days and sick days. So the table would have to be day based. There should be a column with the employee’s name, one with the vacation entitlement (30 days), one with the remaining vacation from last year (e.g. 3) and one where the remaining vacation days is automatically calculated when a team member enters vacation in the table. In addition, sick days are to be entered in the calendar, and a checkbox would be needed next to it in order to manually check whether the sick note is available.

What is the best way to implement this? With a table or a calendar? Would the sum of the remaining vacation days be a view of the other table? What formula would you suggest?

I would be really happy if someone could help me.

Hello Patricia,

Coda is certainly suited for this project. That said, I understand it can get complicated in a hurry.

In order to build a doc/app like this, you have to understand how Coda works, or be willing to learn how it works. Based on what you are asking, I kind of doubt you are there yet.

Just start with a simple table and add more tables and features as you go. You are asking what formula to use, but that’s a tough one to answer if we can’t see what you have done so far. Dates are really just numbers and you can calculate with them by adding and subtracting numbers or other dates. But dates are not the easiest type of data to deal with, you have to consider working days, weekends, holidays and perhaps a few more exceptions.

For the record: a Coda table is a the same as a Coda calendar - it is just a different way of looking at the data. I have many tables that show as a table on one page and show as a calendar on another page. You can even use the calendar as a place to input your data, although Coda is not always the best tool for that.

Consider also wether every member is going to enter their own vacations (because that is what you say), and also their own sick days? It makes a difference, because you would use user() to identify the person if everyone does their own thing, but if that’s not always the case, you would have a lookup from a team-member table.

If you need help building this, you are looking at a commercial job, because this goes beyond a support question.

Last: start with a dummy doc with just a few (dummy) member names. Try a couple of things and when you get stuck, you can share your doc with the community - usually someone will help you really quick.

If you want someone to build this for you, there are quite a few people in this community that can do this for you (myself included).

And one piece of advice: always check if a commercial solution is available that already does what you need. Building it in Coda gives you a lot of design and feature freedom, but if you can’t do it yourself you really have to consider if you need a custom doc/app.

Enjoy Coda,
greetings, Joost


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