Time Tracking & Planning

Runnit keeps planning (the time you expect work to take) separate from tracking (the time work actually took). Holding both lets you schedule capacity ahead of time and compare your estimates against reality for accurate budgets, billing, and reporting.

	Resource planning	Time tracking
Purpose	Allocating future work	Recording actual work
Created	During project planning	During or after the work
Precision	Hour and day blocks	Minute-level accuracy
Editable	Yes, until work starts	No. It is a historical record.
Used for	Capacity planning, scheduling	Billing, payroll, analytics

Planning future work

Projects are broken down into tasks, each with an estimate, an assignee, and a planned start and end. From there, estimates are allocated into calendar time slots based on each person’s availability.

For example, a 10-hour wireframe task for one designer might be spread across three days, with four hours on the first, three on the second, and three on the third. It is not booked as a single block. Slots can be marked as confirmed or tentative, and carry a utilisation percentage so you can see how dedicated a person is to that work.

Tasks that span multiple days are captured as one calendar segment per day, so they render cleanly on calendars (and overdue segments can be highlighted) while the task itself stays the single source of truth for status and progress.

Tracking actual time

Time entries record the real work performed. You can capture time in two ways:

• Timer: start a timer when you begin work and stop it when you’re done.
• Manual entry: add time after the fact by entering a start and end time with a short description.

Each entry can be marked billable, carries the rate that applied at the time, and records what was done.

Tip

Completing a task from the Tasks page asks you to confirm your actual hours and records a time entry for you automatically, so your planned-versus-actual figures stay accurate without running a timer.

Approval workflow

Time entries move through a clear lifecycle:

draft → submitted → approved → invoiced
            ↓
         rejected → draft

Submit entries for review, and a manager can approve them or reject them with a reason. Approved time can then flow through to invoicing. Corrections are kept as separate adjustments with a reason and an audit trail, so the original entry remains intact.

Comparing planned vs actual

Because planned slots and actual entries are stored side by side, you can compare estimated, planned, and actual hours per task or across a whole project. This feeds budget tracking and profitability reporting, so you can see where work is running over or under what you forecast.