How to track employee attendance in Notion

Attendance is the piece most teams try to solve with a spreadsheet, and it is the piece a spreadsheet is worst at. Someone has to remember to fill it in, nobody can see it at once, and the moment you want "hours worked by person last month" you are writing a pivot table.

Notion handles it better, not because it is clever, but because the data entry and the reporting are the same object. This guide builds the whole thing from an empty page.

What you are building

One database, six properties, three views. That is genuinely all of it:

Step 1: Create the Attendance database

Add a new page, type /database and choose Table — Full page. Name it Attendance.

Delete the default Tags property. Add these:

• Employee — type Person. Not Text. Person links to a real Notion account, which is what makes filtering by "me" possible later.
• Date — type Date, time off.
• Clock In — type Date, time on.
• Clock Out — type Date, time on.
• Notes — type Text.

Turning time on for Clock In and Clock Out matters. Without it the subtraction in the next step has nothing to subtract.

Step 2: Add the hours formula

Add a property called Total Hours, type Formula, and paste:

if(
  empty(prop("Clock Out")),
  0,
  round(dateBetween(prop("Clock Out"), prop("Clock In"), "minutes") / 60 * 100) / 100
)

Three things are happening. dateBetween returns the gap in minutes; dividing by 60 turns that into hours; the round(x * 100) / 100 trims it to two decimals so you get 7.53 rather than 7.533333333.

The empty() guard is the part people skip. Without it, a row where someone has clocked in but not out shows a large negative number, and any sum built on top of it is wrong for the rest of the day.

Step 3: Add clock in and clock out buttons

This is what makes the database usable by people who do not care about Notion.

Add a property of type Button, name it Clock In. In the button editor:

1. Choose Edit pages
2. Target: This page
3. Set Clock In to Now

Repeat for a second button called Clock Out, setting the Clock Out property to Now.

An employee now opens the database, finds their row, and taps a button. No typing, no format to get wrong, and the timestamp is real rather than remembered.

Step 4: Build the calendar view

Add a view, type Calendar, and set Show calendar by to the Date property.

A month of attendance in one screen is the single most useful view in the system. Gaps are visible without filtering, patterns show up on their own, and "who was in on the 14th" stops being a question you run a query for.

Step 5: Group a board by employee

Add a view, type Board, and set Group by to Employee.

Each person becomes a column. This is the view you open during a review, or when someone asks how often a specific person has been in this month. Sort each group by Date descending so the most recent entry sits at the top.

Step 6: Roll hours up to an Employees database

The board view answers "how often". It does not answer "how many hours". For that you need a second database.

Create an Employees database with a Name property and a Relation to Attendance. Then, back on Employees, add a Rollup:

• Relation: Attendance
• Property: Total Hours
• Calculate: Sum

Filter the rollup by date range and you have monthly hours per person, computed rather than tallied.

Common mistakes

Letting employees create their own rows. They will forget the date, or set it to today when the entry is for yesterday. Create the day's rows yourself with a repeating template, or use a Notion automation on the database to generate them.

One database per month. It feels tidy and it destroys every rollup you built. Keep one database and use filters; archive to a second database once a year if performance suffers.

Trusting Clock In without Clock Out. People remember to arrive and forget to leave. Add a filtered view — Clock Out is empty and Date is before today — and clear it once a week. Five minutes, and it keeps the hours honest.

Making attendance mandatory before anyone wants it. If nobody was tracking attendance before, a new daily obligation lands badly. Start with the calendar view visible to everyone and no enforcement, and let the usefulness make the case.

When to stop building

This tracker is complete for a team of up to about fifty. Past that, view performance and the lack of row-level privacy both start to bite, and dedicated HR software earns its per-seat cost.

What it does not cover is leave. Attendance tells you who was in; it says nothing about who is approved to be out next Thursday. That is a separate system with its own approval flow, and it is the natural next thing to build.