• Inspections can now be completed from push notifications • Added search and sorting for inspections • Tasks can be assigned to chat members where they were created

• Location search — quickly find the one you need in the list • The request list now remembers your sort order. Choose the order that works for you — it will still be there when you come back, so there's no need to set it up again • Faster performance and fewer crashes

More freedom in working with requests   Now you can reject a request at any step — both the assignee and the manager can do it, not just at the moment it comes in. And any employee with the right permissions can delete a request — right from their phone or from the web version.   Update the app to get everything working. As always, we look forward to your feedback.

We’ve updated the app interface for iOS 26. On devices running the latest version of iOS, screens, buttons, and navigation now better match the updated operating system design. Familiar flows remain in place, so you can keep using the app just as before.

We’ve updated the app interface for iOS 26. On devices running the latest version of iOS, screens, buttons, and navigation now better match the updated operating system design. Familiar flows remain in place, so you can keep using the app just as before.

We’ve updated the app interface for iOS 26. On devices running the latest version of iOS, screens, buttons, and navigation now better match the updated operating system design. Familiar flows remain in place, so you can keep using the app just as before.

We’ve updated the app interface for iOS 26. On devices running the latest version of iOS, screens, buttons, and navigation now better match the updated operating system design. Familiar flows remain in place, so you can keep using the app just as before.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Closed requests are now easier to find — the Archive is available alongside all other request lists. We’ve added even more transparency to performance tracking: request lists and details now show the automatically calculated completion duration — e.g., “closed in 2h 15m.”

Closed requests are now easier to find — the Archive is available alongside all other request lists. We’ve added even more transparency to performance tracking: request lists and details now show the automatically calculated completion duration — e.g., “closed in 2h 15m.”

Now it’s easier to navigate the list of requests. Instead of showing only the location name, the full location path is displayed — for example: Building → Floor → Kitchen. If you have similar names on different floors or in different buildings, there’s no need to open a request to find out where exactly the issue occurred — the relevant information is visible right away. For large facilities, you can expand or collapse the full path as needed.   In addition, when assigning executors or assistants manually, you’ll now see not only their names but also their job titles. This is especially useful for large company with many employees — it helps you quickly find the right person for the request.

Request analytics are now more accurate. Previously, requests could be closed immediately, skipping the ‘In-progress’ stage. Now the workflow is unified: before closing, the assigned employee must first start the request. This ensures that reports reflect more accurate request timelines.

Request analytics are now more accurate. Previously, requests could be closed immediately, skipping the ‘In-progress’ stage. Now the workflow is unified: before closing, the assigned employee must first start the request. This ensures that reports reflect more accurate request timelines.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”. • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”. • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”. • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.