Time entries are decoupled from contracts on purpose

Time entries are logged against a module — an entity (client), a project, a task, or a task group. They're not billed directly to a contract. Instead, when a retainer period recalculates, the system looks at the contract's scope (its entity and optional project) and pulls in time entries that fall under that scope.

Why this matters: One client can have multiple contracts. A time entry against the client's project doesn't need to know which contract it belongs to — the contract pulls it in based on scope. This keeps time tracking simple and avoids forcing the time logger to think about billing.

What counts toward usage

FilterWhy
billable = trueNon-billable time isn't part of the retainer.
Status is eligible for retainer usageDraft, Submitted, and Changes Requested time contributes to live burn alongside approved/completed financial actuals. Rejected, Cancelled, and On Hold time does not count.
Within the period's date rangeEach period only sees entries with entryDate inside its bounds.
Module belongs to the contract's scopeEither directly the contract's entity, or a project (or task / task group under a project) that belongs to the entity. If the contract is project-scoped, only that project counts.

Pending hours affect live burn

The Pending approval chip identifies billable time in Draft, Submitted, or Changes Requested status. Those hours are already included in the period's used hours so capacity and overage warnings reflect work in progress. If an entry is later rejected or cancelled, it drops out on recalculation.

Unallocated billable hours: logged but not in scope

The Unallocated on entity chip is more subtle. It appears when:

  • The contract is scoped to a specific project.
  • The client (entity) has other projects too.
  • Approved billable time exists on those other projects.

That time won't count toward this retainer because it's outside scope. The chip surfaces it so you can decide whether the contract scope needs widening, whether a separate contract should cover that work, or whether it's correctly out of scope (and probably needs its own invoice).

The "Counts toward" chip on time entries

When logging time, the module picker shows a small chip indicating which active retainer (if any) the entry will count toward, with that retainer's current usage percent. This is purely informational — it doesn't change behavior, just makes the routing visible to the team.

Module hierarchy in detail

  1. If the contract has projectId set, only entries under that project (its tasks and task groups) plus the entity itself count.
  2. If the contract has no projectId, all entries on the entity, all entity projects, and all their tasks / task groups count.
  3. Entity-level module entries always count (assuming entity match).
  4. When both an active project-scoped retainer and an active client-wide retainer could match project work, the more specific project-scoped retainer takes precedence.

Forecast

The Forecast tile uses period-to-date burn rate to project usage at the end of the retainer period. It assumes a linear pace from elapsed days, so it is most volatile early in a period.