Help / Team

Schedule and bookings

Schedule answers a question the timesheet cannot: not what did we do, but what have we already promised, and who has room for more. It sits at /schedule and is open to managers, admins and owners — seeing everybody's workload is a management view rather than a personal one.

Reading the schedule is part of the base product. Creating bookings requires the Schedule add-on, enabled under Settings → Add-ons, and is part of the paid plan. The split is deliberate: knowing your current position costs nothing because the data already exists, while planning forward is the paid half.

The three sections

Capacity — each person's booked hours against the capacity they actually have for the window.

Capacity and Planned vs tracked each open with totals for everybody shown, so the team's position is one glance before the rows:

  • Available to schedule — working hours in the dates, less approved leave and public holidays.
  • Scheduled — confirmed bookings in those dates.
  • Unassigned — the spare hours, added person by person. One person's overbooking does not free anybody else's time, so it is shown separately as hours over, rather than cancelling another person's spare hours out.
  • Capacity used — scheduled as a share of available. Each person's row measures against their working hours before leave, so a person on leave can read lower on their row than their share of the total.
  • For planned vs tracked: total planned, tracked, and the difference, in hours and as a percentage over or under plan.

The totals follow the dates and every filter: pick a group and they are that group's.

Planned vs tracked — per project, the hours booked against the hours logged, with the variance in hours and as a percentage. This is the comparison a standalone scheduling tool structurally cannot make: it plans against estimates, while your tracked hours are in the same database.

Bookings — the individual commitments, filed under the person each is for (or under the project — see below), with the controls to add, edit and remove them. Somebody on three projects is one group with three lines, and their booked and unassigned hours for the dates on screen sit beside their name. The list opens with everybody closed — names, counts and hours — so it reads as an overview. Click a name to open that person, or Expand all / Collapse all at the top right to do every one at once. When you add a booking, that person's group opens so you can see it land. Placeholder bookings group under the role they reserve, after everybody with a name.

What counts as capacity

Capacity excludes everything the person will not be working:

  • Weekends.
  • Approved time off, shown separately as leave hours. Schedule reads only the dates — never the leave type or the reason — so an absence never reveals that somebody was off sick.
  • Public holidays, from the calendar assigned to that person under Time off → Setup. Two offices on two calendars each get their own, so a UK bank holiday does not mark a New York colleague as unavailable. If your workspace has exactly one holiday calendar it applies to everybody; with several, a person observes only the one their leave assignment names.

This is the same calculation the Team page uses for utilization, so the two pages agree about what a person's week was worth. See capacity and utilization.

Part-time people

Schedule works out a part-time pattern from two values you have already set: Capacity (hours per week) on the person's Team page, and Hours per day on their leave assignment. Somebody contracted for 20 hours a week with an 8-hour working day works two and a half days.

Both halves matter. Without the day length, 20 hours a week gets spread across five days as four-hour days, and booking that person for a normal working day looks like a 200% overload. With it set, their booked day reads as a full day and their weekly total is measured against the 20 hours they are contracted for. People on a part week are labelled Part-time in the capacity list.

One limit worth knowing: Time Trakkr records how many days a week somebody works, but not which days. Their weekly total is therefore exact, while day-by-day availability assumes any weekday could be one of their working days.

Filtering the schedule

Under Dates shown are three filters, which combine:

  • Group — one of your member groups, such as a pod or a team. Groups are set up under Settings → Groups; until there are some, the filter says so.
  • Team member — type part of somebody's name. Accents and capitals do not matter, so "ruiz" finds Ruíz.
  • Project — pick one from the list, grouped by client and searchable, the same picker as the booking form. It is that one project: two clients' projects called "Site Build" stay apart.

The filters narrow the whole page, so the figures always describe the same people and projects:

  • Capacity shows only the people who match. With a project picked, it shows the people allocated to it — booked on it in the dates shown — the way a group shows its people. Each person's row then leads with their hours on that project ("10h on Site Build"), and the bar and percentage measure that project against their capacity. Their whole schedule follows underneath ("40h of 40h booked in total"), because that is still what tells you whether they can take on more of it. The totals above add a Scheduled on figure for the project, beside the whole-schedule totals for the same people. A project typed into the search rather than picked from the list counts every project it matches.
  • Bookings shows only the matching bookings.
  • Planned vs tracked follows the project. Its figures are whole-project totals for everybody, so the group and team member filters do not narrow it, and the page says so while they are on.
  • Unassigned work is hidden while any filter is on. It is booked against roles rather than people or one project, so no filter can narrow it honestly.

A group or team member filter also leaves out placeholder bookings, which are for a role with nobody assigned yet. Clear filters puts everything back. The filters are remembered if you reload the page, and forgotten when you close the tab.

They are for looking, not booking: the booking form still offers everybody.

What each booking adds up to

Each booking shows its dates, its hours a day and what that comes to — for example 2026-10-01 to 2026-10-31 · 8h/day · 176h. The total counts weekdays only, less the public holidays the person observes, the same rule capacity uses, so a month at 8 hours a day is 176 hours rather than 248.

When a booking runs past the dates shown, the line also says how much of it falls inside them: 72h (40h in these dates). Part-time people are not scaled down: nothing records which days they work, and a booking is a commitment for the days it names.

Who is on a project

By project, above the bookings list, files the same bookings under each project instead of each person: client and project, how many people are on it, and the confirmed hours booked in the dates shown, with tentative hours apart. Open a project to see everybody allocated to it, with their dates, hours a day and totals. By person goes back.

Making a booking

Pick a project, a team member, a date range and hours per day.

Dates. The form opens on the current month. This week, Next week, This month and Next month set both dates in one click, and you can still edit either date afterwards — a booking that starts mid-month is a preset plus one changed date. Weeks run Monday to Sunday; weekends are never counted, so including them costs nothing.

Adding several in a row. After you add a booking, the person, the dates and the hours stay as they were and only the project clears, ready for that person's next project. The dates are also remembered if you reload the page. Changing the dates shown at the top of the page moves the booking dates with them, so what you add next appears in the list you are looking at.

Time remaining. Once you have picked a team member, a panel under the form shows how much of their time is still unassigned for the booking dates — capacity, less approved leave, less what is already booked — and what the booking you are typing would leave. If it would take them past their capacity, it says by how much. It never blocks the booking: overbooking somebody is sometimes the plan, and the point is to do it knowingly. Tentative bookings do not count against the figure.

If the project has an hours budget, the panel also shows how much of that budget has not been booked to anybody yet. This compares the budget with bookings, not with tracked time — it answers "how much of this have we planned", and the project page answers "how much have we spent". A monthly budget is compared with what is booked inside the booking dates; a total budget with everything booked on the project.

The capacity list at the top shows the same unassigned figure for everybody, for the dates on screen.

The same booking twice is refused. A person already booked on a project for exactly those dates cannot be booked again for them — edit the existing booking to change its hours. Different dates on the same project are fine.

Tentative or confirmed. A tentative booking is pipeline — work you are discussing but have not committed to. It appears in the bookings list but is deliberately excluded from capacity, so a shortlist of maybes cannot make somebody look fully booked.

Copying a week or a month

When next month looks like this month, do not re-enter it. Copy from another period… above the booking form copies one period's bookings into another.

Choose where to copy from (last week, last month, or any dates) and where to copy into, and optionally one person. Before anything is created you see the list of bookings it will make, re-dated, and you can untick any you do not want.

How the dates move:

  • Month to month, a booking keeps its days of the month. A booking for the whole of October becomes the whole of November — not 1 November to 1 December, which is what moving it 31 days would give. A booking that ran to the end of the month runs to the end of the new one.
  • Any other pair of periods moves each booking by the gap between the two start dates, so a week's bookings stay on the same weekdays.
  • Only the part of a booking inside the period you copy from is copied. A booking that ran September to November contributes its October days when you copy October.

Hours per day, tentative status and placeholder roles all carry over. A booking that already exists in the target for the same person, project and dates is skipped, so copying twice does not double anything. Copying never changes or removes an existing booking, and the two periods cannot overlap.

Placeholder bookings. Leave Select team member unchosen (or pick No one yet — book a role) and pick a role instead — work you know is coming before you know who will do it. A placeholder needs a role: it is the whole point, because the role is what the demand is for.

Roles are managed under Team → Assignments, and the same roles are what you assign to people. That link is what makes the next section work.

Unassigned work: the hire you need

When placeholder bookings exist, an Unassigned work section appears, listing per role:

  • needed — hours booked against that role with nobody assigned;
  • spare — unbooked hours across the people who hold that role;
  • short — demand the current team cannot absorb.

A shortfall is the useful number. "We are overcommitted" is a feeling; "you are 40 hours short of a Developer in April" is a hiring decision, or a reason to decline the work. Nothing else in Time Trakkr can say it, because it needs planned demand and current spare capacity in the same place.

Two details worth knowing:

  • Only people who hold the role count as supply. Somebody with no role set contributes to nobody's spare capacity — otherwise every shortfall would dissolve into a pool that cannot actually do the work.
  • Only confirmed placeholders count. Tentative work is pipeline; counting it would have you hiring for a project you have not won.

The section is hidden when no placeholder work exists, rather than showing a table of zeroes — which would read as "nothing needed" when it really means nobody has planned anything.

Overbooking

A day is flagged as overbooked when confirmed bookings exceed what the person has available that day, after leave. Booking somebody during approved leave is the clash most worth catching, because it looks perfectly reasonable on a timeline.

Reading planned vs tracked

Projects are listed under their client, in name order, with a subtotal for each client. Project names repeat across clients — most agencies have several called "Site Build" or "Monthly Retainer" — and the client is what tells them apart. Clients start closed, showing only their totals. Click a client's name to open its projects, or Expand all / Collapse all above the table for every client at once.

Every figure opens what it is made of:

  • A project's name opens the project.
  • Tracked hours open the detailed time report for that project over the same dates. A client's tracked subtotal opens it for every project that client has.
  • Planned hours open, in place, the bookings that add up to the figure: who, which dates, how many hours a day.

Planned counts confirmed bookings only; tentative ones are pipeline.

Positive variance means more was worked than planned. Where nothing was scheduled, the percentage is shown as blank rather than as infinity — work tracked against nothing planned is an interesting case in its own right and deserves a real answer rather than a divide-by-zero.

One project, by role

The Schedule page compares plan and actual across projects. To see one project by the people on it, open the project and choose its Team tab. Scheduled vs reported sits above the team list, for the same dates as the rest of the project page — a month, a custom range, or all time.

Each role on the project's team (Engineer, Project Manager, and so on, as set under Edit project → Team) is one row: its scheduled hours and its reported hours as two bars on one scale, with the figures and the difference beside them. Click a role, or Expand all, to see its people with the same figures.

  • Scheduled is confirmed bookings on the project, counted exactly as Planned vs tracked counts them: working days only, less public holidays, clipped to the dates shown. Tentative bookings are not counted.
  • Reported is every time entry on the project in those dates, so the total matches the project's Total hours. Time recorded by coding agents is included, as it is in the project total, and a person's row says how much of theirs it was.
  • A placeholder booking — a role reserved with nobody assigned — counts under that role as Unassigned.
  • People with no role on the project, and anybody who booked or reported time on it without being on its team, are grouped under No role, so nothing drops out of the totals.
  • A person's reported hours open the detailed report for that person, project and range; the total opens it for everybody.

On All time, scheduled counts every confirmed booking in full, including weeks still ahead, so expect it to run ahead of reported on a project in progress.

Who sees it: anyone who can see everybody's hours on the project — managers and admins, whoever has Manages this project ticked on it, and everyone when the project's report is shared with everyone. The scheduled half is for managers, admins and owners only, as on this page; anyone else sees the reported figures by role. If the Schedule add-on is off and nothing is booked on the project, the view says scheduling is not in use rather than showing a column of zeros. It shows hours only, never rates or cost.

Asking the assistant

For managers and admins, the assistant can:

  • report planned work for a date range — who is booked to which client's project, for how long, and what each booking adds up to — narrowed by group, team member or project like the page ("who in Pod A is on Northwind next month?");
  • say how much of each person's time is still unassigned, with the team's totals as the page shows them ("who in Pod A has room in October?", "how many hours does the team have free next month?"), and, for one project, how much of each person's schedule is on it ("how much of Ana's October is on Site Build?");
  • compare planned against tracked, per project, per client and in total, optionally for matching projects only;
  • break one project down by role and person, scheduled against reported, as on the project's Team tab ("are the engineers on Northwind over plan this month?");
  • copy one period's bookings into another, showing you the list before it creates anything.

It does not create, edit or remove individual bookings: a booking is a commitment of somebody else's time, and that belongs in the app where the capacity picture is in front of you.

Two of these depend on how you are connected. The unassigned-time answer needs a signed-in person, because it reads approved leave dates; and copying a period is an action, so it is not offered to a read-only API-key connection.

Updated 2026-11-08. Still stuck? Contact support or return to the Help Center.