One Check-in per Type Model
Overview of the One-Instance Model
To keep your team's communication streamlined and prevent overlapping workflows, Troopr operates on a "one check-in per type" model. This means that for any specific check-in type - such as a Daily Standup, Weekly Retrospective, or Social Check-in.Each team can create and maintain exactly one active instance.
How it works
When you are setting up a new check-in for your team, Troopr identifies the check-in type you are configuring. If an instance of that type already exists for your team, you will not be able to create a duplicate. Instead, you are encouraged to manage or update the existing instance.
Managing existing instances
If you need to change how a specific check-in functionsβsuch as changing the schedule, the questions asked, or the participants - you should edit the existing instance rather than attempting to create a new one. This maintains the history of your team's check-ins and keeps your configuration clean.
Key benefits
Reduced Noise: Prevents team members from receiving multiple notifications for the same standup or report.
Consistent Reporting: Ensures all data for a specific check-in type is aggregated into one comprehensive report.
Simplified Administration: Makes it easier for team leads to manage workflows without tracking down multiple duplicate configurations.
