Transparency

Supported. Bounded. Clear.

See what to expect and what needs clarification.

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

Not something to assume without checking

  • A full public API platform
  • Webhooks as a standard product
  • Custom enterprise integrations without an agreement
  • That every surface always has complete parity at the same time
  • That features under development count as shipped

Parity across surfaces

The goal is high parity, but some features arrive on one surface before they are fully even everywhere.

Under development

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.

Agreed solutions

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.

Supported and not supported

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.