Skip to content

Processo Team Rules

Elbert Jean edited this page May 14, 2026 · 1 revision

Team Commitment & Performance Rules

1. Overview

The goal of the Retention Criteria is to ensure high performance, consistent communication, and commitment within the team. This system tracks professional engagement through a point-based penalty structure. Reliability is a core value of our workflow; therefore, adherence to these standards is mandatory for all team members.

2. Penalty Framework

Points are accumulated based on infractions related to attendance, responsiveness, and delivery. Each action has a defined penalty and a maximum frequency allowed before immediate review.

Action Penalty Limit
Absence from In-Person Daily (With justification/prior notice) 10 pts Max 8
Absence from In-Person Daily (Without justification/prior notice) 25 pts Max 3
Absence from Review/Planning (With justification/prior notice) 20 pts Max 4
Absence from Review/Planning (Without justification/prior notice) 50 pts Max 1
Staying 24h without responding when requested 25 pts Max 3
Holding the task, not asking for help, and making no commits 50 pts Max 1
Not delivering on time and not communicating difficulties in advance 35 pts Max 2

3. Scoring Thresholds

The system operates on a cumulative basis. It is the responsibility of the team member to monitor their standing.

  • Total Capacity: The maximum allowable threshold is 100 accumulated points.

  • Critical Alerts: Upon reaching 75 points, the team member will be formally notified in the team's WhatsApp group.

  • Termination Clause: Exceeding 100 points or hitting the Max Limit of any specific action results in the immediate expulsion of the member from the team group.

4. Communication Guidelines

To avoid the heavier "Unjustified" penalties, team members must:

  1. Notify the Lead: Provide notice at least 4 hours before a Daily or 24 hours before a Review/Planning session.

  2. Unblock Tasks: If a task is stuck, communication must happen immediately. Silence for over 24 hours is considered a breach of the responsiveness policy.

Clone this wiki locally