TIMESHEET REVIEW
Approve the submitted work, with its details in view.
A designated human reviewer inspects the submitted timesheet and decides whether to approve it or return it for correction.
Approval should describe a decision on identifiable work
A weekly total alone does not explain which tasks were completed or what the reviewer accepted. Tsumira’s approval flow works with a submitted timesheet and its included entries. The reviewer can inspect the period, member, time and billing context, then approve or reject the current version. Recording and approval remain separate steps, so a running timer or saved draft cannot quietly become an approved financial input.
Read the work that was actually submitted
The approval view lists the submitted week and its entries, with total time, billable effort and relevant flags. Review descriptions, dates and work references where a quantity needs explanation. The underlying submission identifies a specific set of work, so the decision has a defined basis. If a record changes concurrently, the current version and integrity checks prevent the reviewer’s stale screen from deciding on a different unnoticed state.
- Submitted week and included entries
- Total and billable effort
- Current-version and integrity checks
Use the person designated to review
The submitted timesheet identifies its reviewer. The decision flow checks that the acting person is that designated reviewer, along with the applicable permission. Being able to see a review queue is not itself blanket authority to decide every timesheet. Self-review is restricted to the implemented solo-owner exception, rather than being the normal path for a team. This makes responsibility for the decision explicit.
- Designated reviewer
- Permission-controlled decision
- Restricted solo-owner exception
Approve or return the work with useful context
The supported decisions are approved and rejected, with an optional note. A rejection gives the person a clear reason to correct the week through the appropriate entry flow. Approval can make eligible billable work available for the connected finance process, but it is not equivalent to issuing an invoice. A financial colleague still needs to review pricing, customer context and the relevant commercial document before billing the customer.
- Approved or rejected decision
- Review note for clarification
- Separate financial pricing and issue steps
A concrete workflow
Open the submitted week
Confirm the member, period and entries rather than approving a total without its context.
Check the effort
Read dates, descriptions, work references, billable time and any exceptions that need explanation.
Decide on the current version
As the designated reviewer, approve or reject with a useful note and the required permission.
Follow the result
Let rejected work return for correction, or continue eligible approved work into its separate billing review.
An illustrative working example
Illustrative workflow: return an unclear customer entry
A reviewer opens a consultant’s submitted week and sees a customer-work entry whose description does not explain the task. Instead of changing the employee’s work silently, the reviewer rejects the timesheet with a note asking for clarification. The consultant corrects the eligible entry and resubmits the current preview. Once the work is understandable, the designated reviewer can decide on that version.
Questions about this topic
Can any manager approve any timesheet they can see?
The decision checks the designated reviewer and permission. Queue visibility or a management role alone should not be treated as authority to approve an unrelated submission.
Can a team member approve their own week?
Self-review is not the normal team flow. The implemented exception is limited to a solo owner who is the only active human member and the designated reviewer.
What happens after rejection?
The rejected work can be corrected through the supported entry and resubmission workflow. A useful reviewer note explains what needs attention.
Does approval issue an invoice?
No. It approves the submitted time. Eligible billable work can continue into connected finance, where pricing and document issue remain separate controlled actions.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
