Skip to main content

The review queue

Route: /review · Roles: reviewer, finance, admin

The review queue is where submitted time becomes approved (billable) or rejected. Approving is the gate that lets work flow into Billing.

What appears here​

Only entries in the submitted state. Each card shows the project and customer, the engineer, the date, the duration, the billability, and the description. Two badges can appear:

  • possible duplicate — the entry may duplicate another (for example one captured from Slack and again by hand).
  • A source badge — slack or jira when the entry was not logged on the web. Web entries show no badge.

Summary chips show how many are awaiting review, the total pending time, flagged duplicates, and lifetime approved/rejected counts.

Approve an entry​

  1. Open Review queue.
  2. Check the project, duration, and description.
  3. Click Approve.

The entry becomes approved, is stamped with the approver and time, and — if it is billable — the customer's billing month is recalculated automatically.

Reject an entry​

  1. Click Reject on the card.
  2. A reason field appears. Type why (required), for example "wrong project" or "missing detail".
  3. Click Reject entry.

The entry becomes rejected, returns to the engineer's My time, and the reason is recorded in the audit trail.

Approve everything​

When the queue is clear of surprises, click Approve all (N) in the header to approve every pending entry in one action.

Bulk approval is unforgiving

Every pending entry is approved, including flagged duplicates. Skim the queue for duplicates first if precision matters.

Handling duplicates​

Duplicates are flagged, not blocked. Decide which copy is correct, then:

  • Approve the one you want to keep.
  • Reject the other with a reason such as "duplicate of <date>" so the engineer can delete it.

See Statuses and states for how duplicate_of works.

Rules and side effects​

  • Only submitted entries can be reviewed; a stale card returns "Entry is no longer awaiting review."
  • Rejection always requires a reason.
  • Approving a billable entry triggers a billing recalculation for that customer and month.