You're not a system administrator, but your team depends on four things you do in Tanca. All four together take less than ten minutes a day.
Recommended routine
| When | Task | Time required | Detailed article |
|---|---|---|---|
| Start of the day | Approve pending requests | 2–3 minutes | A4-02 |
| Start of the day | Glance at yesterday's attendance sheet to see who was absent or unusually late | 2 minutes | A4-03 |
| During the day | Assign ad hoc tasks and update progress | 3 minutes | A4-04 |
| End of the week | Schedule next week and check which time slots are short-staffed | 10 minutes | A4-03 |
| End of the cycle | Review employees according to the cycle set by the company | depends on team size | A4-05 |
The most important task on the list is approving requests on the same day. Pending requests lead to incorrect timesheets, incorrect timesheets lead to incorrect payroll — and the people who bear the consequences are your employees.
Whose data you can see
The scope of data you can view depends on the access group HR assigns to you: a Branch Manager sees data for one branch, a Regional Manager sees multiple branches in the region. If you can't see employees who should belong to your team, ask HR to re-check the permissions and department structure.
Three things to avoid
- Approving requests via messages and only clicking in the system later. Employees will follow your example and stop submitting requests altogether.
- Scheduling the whole month at once and never reviewing it. Real-world changes that aren't updated will make timesheets wrong across the board.
- Leaving all reviews until the end of the period. Recording observations throughout the period gives much more accurate results.
