Tempo Ideas

Problem

When a user recalls an already approved timesheet and then changes hours, the Project Time Approval block for that project, user and period goes back to pending. The approver of that project is not told that this happened, nor that the hours had already been approved by them.

We capitalise only hours approved by the project approver. While the block is pending, those hours are excluded, including the hours that were already approved before the change.

Current behaviour (verified with controlled tests on our Cloud tenant, 2026-08-06)

Two points from those tests:

• The recall notification is sent only to the approver of the global timesheet. Approvers of the individual projects affected receive nothing.

• When the project approver later receives the approval request, it looks like any other request. There is no indication that they had already approved that block, or which hours changed.

Requested enhancement

When a user recalls a timesheet, notify the approver of each project whose hours are then modified, and only those approvers. If a user works on four projects and changes hours on the third one, only the approver of the third project is notified.

Two variants, either of which would help:

1. Let the user choose, at recall time, which project approvers are informed and state a reason.

2. Notify automatically when a previously approved block returns to pending because its hours changed, including previously approved hours and current hours in the notification.

Why it matters

The shorter the block stays pending, the smaller the gap between hours worked and hours available for capitalisation at month end. Today the project approver has no way of knowing that a block they already approved has reopened, so the gap depends entirely on when the user happens to resubmit and the approver happens to notice.