New feature ideas

Vote for ideas you would like to see in the product.
If you don't see your idea, add it below 👇
Include in your description how your idea would benefit you (e.g. save you time or increase accuracy)
Salaried Staff Costing Logic in Timesheets
It would be great if Tanda could introduce an additional costing logic for salaried employees in timesheets. At the moment, salaried employee costs can be difficult for restaurants to understand when reviewing actual labour after the shifts have been worked. The roster forecast is one part of the process, but once the timesheet is completed, it would be helpful if the cost could be calculated using the employee’s actual clocked hours, while still respecting their contracted salary. For example, Tanda could calculate a salary equivalent hourly rate based on the employee’s weekly salary and contracted weekly hours. The timesheet cost would then be calculated using the actual clocked hours for each day or week, but capped at the employee’s contracted weekly salary. Also make the calculation based on their contracted date pro-rate from roster and actual from timesheet If the employee works above their contracted weekly hours, those additional hours could be shown separately as “above salary” or “above contracted hours”. If the employee works below their contracted weekly hours, this could be flagged as “under contracted hours”. This would give restaurants much better visibility when reviewing actual labour costs, especially where salaried employees do not work the same number of hours each day. For example, someone may work 6 hours one day and 10 hours another day. From a timesheet perspective, the actual cost allocation should ideally reflect the hours they worked, rather than spreading the salary evenly across days or relying only on roster allocation. The intention is not necessarily to change the current roster allocation options, as those are useful for forecasting. This would be an additional timesheet-based costing option to help businesses understand the actual labour impact after shifts have been worked. This would also make it easier to identify direct on timesheet: Salaried employees working above their contracted hours Salaried employees working below their contracted hours More accurate daily or weekly labour cost allocation Better visibility between rostered cost and actual timesheet cost Overall, this would help restaurants and payroll teams review salaried labour more accurately and reduce confusion around how salaried staff costs are allocated in timesheets.
3
Let Managers Fix Last-Minute Shift Changes from Mobile App
Managers and admins should be able to fully manage published shifts from the mobile app, especially for last-minute roster changes. Currently, managers can view team schedules on mobile, but published shift management is limited compared to desktop. This creates issues for frontline managers who are not always at a workstation, especially in healthcare, hospitality, retail, F&B, aged care, security, and other shift-based industries. The mobile app should allow users with the correct permissions to: * Edit published shift start and end times * Edit or add breaks * Add or update shift details * Add notes or reasons for shift changes * Delete published shifts that are no longer needed * Move a shift to another employee * Convert an assigned shift into a vacant shift * Assign a vacant shift to a staff member * Publish vacant shifts for shift claiming * Review updates before publishing * Notify affected staff when changes are published * Require staff acknowledgement for updated shifts * Respect existing shift clash or duplicate shift prevention rules This is important because managers often need to make changes while on the floor, not from a desktop. If an employee’s shift changes and the old shift cannot be deleted or updated from mobile, the outdated shift may still appear in the schedule. This can cause duplicate shifts, shift clashes, staff confusion, and missed updates. This feature would help keep the schedule as the source of truth, reduce manual communication through WhatsApp/SMS/calls, and ensure staff receive accurate schedule notifications in real time. This is different from timesheet corrections because the goal is to update the roster before the shift happens, not fix attendance after the shift has already occurred.
0
Separate Internal Position Template & Location Data from Candidate-Facing Job Advertisements in Hire Module
As part of reviewing functionality for the proposed implementation of the Tanda Hire Module, we have identified a significant limitation. Currently, Tanda controls Manager access to recruitment advertisements and applications through: Position Templates and reporting hierarchies Operational Location permissions This approach is preferable from a governance and access-control perspective, as it ensures Managers only have visibility over the roles and applications relevant to their area of responsibility. However, the issue is that Tanda uses these same internal structures as public-facing recruitment information. The internal Position Template and Location names currently used in Tanda contain operational and payroll-related information unsuitable for Candidates to see publicly and lack the necessary details for a job advertisement. Our Position Template Names are configured as Position Name – Location – Award – Employment Type – Business Unit Our Location names ae similarly configured for use in Workforce Management, are not designed to be public facing and do not always contain a physical location which would indicate where a job was based Tanda currently requires either the internal Position Template or operational Location to be attached to a job advertisement for application routing and Manager access and these internal labels also appear publicly on recruitment advertisements. For the Recruitment Module to be viable for us to use, Tanda would need to separate internal operational data from Candidate-facing recruitment content. Specifically, we require the ability to: Continue using internal Position Templates and operational Locations behind the scenes in Hire for workflow routing, payroll conditions, document management, and Manager access controls Assign applications to the correct hiring Managers internally using those existing structures Hide internal Position Template and Location names from public job advertisements Display simplified, candidate-friendly job titles (manageable with existing functionality) and locations instead Optionally allow specific Manager(s) to be manually assigned directly to a job advertisement to provide access where required (in addition to resolving the Position Template and Location display issue) This would preserve the benefits of the current permission structure while allowing recruitment advertisements to contain accurate Candidate facing data. As a client with 70+ Locations and 350+ Position Templates across two countries, we are currently unable to implement and utilise the Hire module of Tanda due to these issues
0
Load More
→