TeamCounter guides

Avoiding typical mistakes in lists edited by several people

Counting together works most reliably when it is clear in advance who may change values, what exactly is counted and how corrections are made. TeamCounter deliberately keeps the process simple, but that simplicity does not replace agreement inside the group.

By Maximilian Holstein · Last updated: 6 August 2026

The most common causes of wrong values

  • The management link was given to people who should only read along.
  • Two people count the same event at the same time.
  • An entry is named unclearly or understood differently.
  • After a loading error an action is repeated without checking the current state.
  • An old browser tab stays open and is used again later.
  • Resetting or deleting is confused with a normal correction.

The technical permission follows from the link that is used. TeamCounter has no individual accounts or roles that could enforce such rules.

Before you start counting together

  1. Define the purpose, the period and the unit of the list.
  2. Name entries unambiguously and as briefly as possible.
  3. Choose one or a few responsible people.
  4. Send the management link only to those people.
  5. Use the view link for everyone else involved.
  6. Test the complete process with neutral sample data.

If responsibility changes, the group should not pass the link on publicly. After a mistaken share, a new list can be the safest solution, because individual access cannot currently be revoked separately.

Example: two people maintain a task list

Two coordinating people receive the management link. Each completed task is counted only by the person who signs it off. Before a correction both reload the current state. The rest of the team uses the view link exclusively.

If an update visibly fails, nobody clicks blindly again. First they check whether the value has already arrived on a second device. That reduces the risk of double counting.

Corrections, export and deletion

Small input errors can be corrected through management access. Before a reset or a permanent deletion the affected list should be identified clearly and, if needed, saved as CSV or through the print function. An exported file is only a snapshot and is not synchronised with later changes.

TeamCounter keeps no complete audit-proof change log. For binding settlements, personnel processes or legal evidence a purpose-built application is required. See the export guide and the decision guide.

Data protection and lost access

Use abbreviations or neutral labels when real names are not required. Management links must not appear in public posts, freely accessible documents or search engines. Noindex is not password protection.

What is possible when access can no longer be found is explained in the guide to lost links. Further protective rules are in the data protection guide.

Nach oben scrollen