Supported in the standard track
- Geo-verified check-in and check-out
- Employee app for daily use
- Portal for customer administration
- Timesheets, approval and CSV export
- Basic messages, tasks and absence where the modules are activated
Transparency
See what to expect and what needs clarification.
The goal is high parity, but some features arrive on one surface before they are fully even everywhere.
Some work happens internally before it is ready for customers. It does not count as shipped until it is actually available in the product and covered in the release notes.
Customer-specific export and integration setups can be the right call, but they should be described as agreed solutions, not as a generic standard product.
Clear boundaries build trust.
This page defines what TapInn supports today, what is under development, and what should not be expected without an explicit agreement or further product work.
In short. A good product does not just say what it can do. It also says clearly what is not finished, not public, or not yet part of the standard commitment.