Dashboard
Hours
Log Time
Record hours against a project, or as upskilling.
Entries
Logged time. Locked entries are read-only.
| Date | Member | Dept · Team | Type | Project | Category | Description | Hours | Billable |
|---|
Reports
Filter and group hours; export to CSV.
| Project | Hours | Billable hours |
|---|
Daily Roster
Assign planned hours and notes per person per project. Daily cap 8. Edit the cells, then Save.
Each cell: planned hours (top) and what they'll work on (notes). The small number is actual hours logged so far. Green means on or under plan, red means over.
Export roster history (CSV)
Daily Variance
Where each person logged hours versus their roster plan for the day, and any extra hours taken. Off-roster work is flagged as unplanned.
| Member | Scheduled | Actual | Overage | Where they logged |
|---|
People Insights
See what your team is good at and how their time is spent. Every figure is worked out from skill ratings, the roster and time logs. New to a term? Open the People Insights guide in the sidebar.
Projects
Propose a project
| Project | Type | Client | Proposed by | Status |
|---|
Departments & Teams
Departments are the broad unit; teams sit inside them. Brand and working-day settings moved to Account.
Departments
Teams
Batches for interns
Interns are grouped by intake batch instead of a team.
Team
Add and manage members. Login is their work email.
Add member
| Name | Title | Role | Department | Team / Batch | Shift | Assigned projects | Edit exceptions | Missed |
|---|
Logging & fair play
Keeping logs current is a team habit. Here's how it works and what to do if life gets in the way.
Why timely logging matters
Your logged hours are how your effort gets seen and credited and how we plan work fairly across the team. When everyone keeps their logs current, planning is accurate, nobody's work goes unnoticed, and no one ends up quietly carrying more than their share. It's a shared habit, not a spotlight on any one person.
The two deadlines
15 minutes to edit. After you save an entry you can tweak it for 15 minutes; then it locks so hours can't be quietly changed later.
16 hours after your shift ends to log. Time for a given day should be logged within that window (for a standard 9-6 day, that works out to 10am the next day). After that the day locks. Different teams/shifts have their own deadline based on their own shift end, the rule is the same for everyone.
These windows keep everyone's records honest, including yours, so your effort can't be edited away.
Missed a deadline? There's a fair way through
Life happens. If you missed the window, use Request edit on the entry (or the prompt when logging a past day). You give a short reason, it goes to an admin or HR, and they can reopen that day for you. Reasonable requests are expected and get approved, that's what the process is for.
What happens if logs are repeatedly missed
To be transparent: working days with no time log are counted (you may well have worked, this is only about the log being missing), and 3 or more working days without a logged entry past your shift's log deadline flag a 1 day pay adjustment, visible to your manager, HR, and the founder.
Please read this as a gentle nudge to keep logs current, not a gotcha. It only ever counts from the day you joined (and from the day NerdRota went live), non-working days never count, and an approved edit request clears a missed day. If you're ever struggling to keep up, the right move is to raise it early, not to let it pile up.
The short version
Log your hours the same day where you can, definitely within 16 hours of your shift ending. If you slip, raise a quick request. Do that and you'll never see a penalty, and the whole team gets a fair, accurate picture of the work.
Notifications
Updates for you in this organisation.
Edit requests
Members asking to log or edit time past the lock window.
| When | Member | For | Reason | Status |
|---|
Roles & Permissions
Tick a box to grant a permission to a role. Changes save instantly.
Audit log
Every change, hash-chained and tamper-evident.
| When | Who | Activity |
|---|
How this works, and why
Full transparency on what NerdRota measures and what it is for.
Our promise first
NerdRota exists to make your effort visible and fairly recognised, and to make sure no one is quietly overworked. It is not a surveillance tool. You can see exactly how every number is produced, because the same rules apply to everyone, including the people who run the company.
What we calculate
Hours per entry. You log a start time and an end time (for example 9:00 to 10:30). We simply subtract the two to get the duration. There is no rounding up and no hidden maths, 90 minutes is 1.5 hours.
Billable vs non-billable. Each entry is flagged as billable or not. Non-billable work still counts as real work, it is just funded differently.
Projects vs Upskilling. Time is logged either against a project, or as Upskilling when you are learning. Learning is treated as valuable time, not as a gap, because growing your skills benefits you first.
Daily, weekly, monthly, and annual views. We add your entries into the day, then roll days into weeks (Monday to Sunday), months, and years. Department and team views simply add up the people inside them. The maths is plain: nothing is secretly weighted, every total is just the sum of the hours you logged. (Logging on time does matter, see Logging & fair play in the sidebar for how deadlines and missed logs work.)
The daily colour, and why 8 hours
A typical full working day is about 8 focused hours, so that is the benchmark the daily colour uses:
- Under 2 hours logged
- 2 to 4 hours
- 4 to 6 hours
- 6 hours and above, hitting the mark
The point is a healthy, sustainable day, not a race to the highest number. Green means a solid day and you are done, not a reason to push further.
Protecting you from overwork
The same data that shows whether a day was full also shows when someone is consistently over the line. If your logged hours are regularly high, that is a signal for your manager to rebalance the load, not to ask for more. Sustainable pace beats burnout every time, for you and for the work. Rest, breaks, and time away are expected and healthy.
Why your hours can be trusted
Every change is recorded in a tamper-evident log, and once a period is reviewed your entries are locked so they cannot be quietly altered. That protects you: your effort is recorded accurately and cannot be edited away.
Account
Your password and, for the super admin, this workspace's settings.
Change your password
Platform
Every workspace on this deployment, regardless of which one you're currently signed into. Platform admin only.
Add organisation
Organisations
| Name | Slug | Domain | Members | Super admins | Entries logged | Created |
|---|
People Insights guide
What each number means and where it comes from. Visible to super admin, HR, and admin.
The big idea
Everything here is read-only and computed from data already in NerdRota: the skill ratings you record, the roster, and time logs. Nothing about tasks, tickets, or bugs is tracked, so those are never shown. If a number is blank, it means there is no data to compute it yet, not zero.
How ratings work
Every rating is a dated record and is never overwritten. The "current" level is always the most recent rating, so the full history stays intact for growth and trends. A skill that has never been rated is blank, not zero.
- Proficiency scale
- 1 Theoretical only · 2 Basic knowledge · 3 Works solo with minimal support · 4 Individual contributor · 5 Expert. "Strong" means level 4 or 5.
- Validation
- How a rating is backed: self assessed, manager validated, or evidence backed. Evidence backed is the most trustworthy. It is shown as a signal; it does not secretly weight any score.
- Review due
- A person is flagged for review when their most recent rating is more than 180 days old. "No data" means they have never been rated.
The views
- Overview
- The landing view. Headline counts, the latest ratings (visible from the very first one), and the most recent level change per person and skill. A downward change is shown neutrally: it can mean the bar was raised (new tech, higher standard) as much as a real gap to close.
- Skill Matrix
- A people-by-skill grid of current levels. A quick "who knows what" read.
- Dashboard
- Per person: skills assessed (distinct skills rated), strong skills (level 4+), validated ratings, and when they were last assessed.
- Growth
- For skills rated more than once, the change from a person's first rating to their latest. One-off ratings do not appear (nothing to compare).
- Project Fit
- Pick the skills and minimum levels a project needs. Each skill is OK (2+ people meet the bar), TIGHT (exactly 1), or GAP (none). The overall verdict is READY, DELIVERABLE but thin, or NOT READY, based on the weakest skill. Uses current levels.
- Hiring Gaps
- Every skill, sorted worst first: how many distinct people are rated, how many reach level 4+, and the current best person. Flags are GAP (no one at 4+), THIN (a single person, so a single point of failure), or COVERED (2+).
Productivity (all worked out from time logs)
- Available (hrs)
- How many hours the person could work that week: this workspace's working days multiplied by 8. There is no leave model yet, so holidays are not subtracted.
- Logged (hrs)
- Total hours the person logged that week.
- Billable (hrs)
- Of the logged hours, the ones marked billable.
- Utilisation %
- Billable hours as a share of available hours. How much of the person's time turned into billable work.
- Logged %
- All logged hours as a share of available hours, billable or not. A low number usually means missing logs, not idle time.
- Days logged
- Days with at least one log, out of the working days that week (for example 3 out of 5).
- Project work (hrs)
- Of the logged hours, the ones spent on an actual project (client or internal work).
- Learning (hrs)
- Of the logged hours, the ones logged as Upskilling: time spent learning rather than on a project. Project work plus Learning add up to the total logged hours.
- Top category
- The work category the person spent the most hours on that week.
- Weeks active
- In the rolling window, how many weeks had any logged hours.
- Trend
- Compares the most recent active week's logged hours to the average of their active weeks. More than 5% above is Improving, more than 5% below is Declining, otherwise Steady. "Stale" means no logs in the window.
- Free capacity %
- Over the next couple of weeks, the share of working days with nothing rostered. Higher means more free time coming up.
- Current project
- What the person is rostered on today.
- Free from
- The next upcoming working day where they have nothing rostered.
Reading the colours
- Utilisation % and Logged %
- Red below 70%, amber from 70 to 99%, green at 100% or above. 70% is the "healthy" line.
- Proficiency levels
- Warmer (red) at level 1 through to green at level 5.
- Free capacity %
- Higher is greener: more free time coming up reads as good.
- Trend
- Improving green, Steady amber, Declining red. A 5% band around a person's own average stops a flat trend from flickering week to week. "Stale" means no logs in the window, which is a logging gap, not a real dip.