Automated outreach
Each owner receives the current composition of their team at the beginning of the cycle.
Automation of the recurring team-composition validation process, reducing individual follow-ups, standardizing changes and keeping the main roster continuously updated.
The process was redesigned so each team’s current composition is sent automatically, validated in a structured way and reflected in the main roster without relying on manual follow-ups and adjustments each cycle.
Each owner receives the current composition of their team at the beginning of the cycle.
The owner validates the composition and only flags cases where a change is needed.
Interprets the action, applies process rules and routes the update in a standardized way.
Final execution happens in the main roster, keeping team composition ready for consultation.
The main gain was moving roster maintenance from an informal, repetitive process into a structured routine.
Individual messages, waiting for replies, free-text corrections and manual updates person by person.
Automated outreach, structured validation, centralized rules and final execution directly in the roster.
The automation turns team-composition updates into a predictable, standardized routine with far less manual intervention.
Team composition needed periodic validation, but the process was manual: contact by contact, reply by reply and update by update.
Each owner received the current team composition individually. When changes were needed, corrections arrived as free text and the main roster had to be adjusted manually — including searching for additional information for new joiners.
The value of the solution lies in separating communication, validation, rules and execution into clear layers while preserving the roster already used by the team.
Validation becomes recurring, without relying on someone remembering who needs to be contacted each period.
Confirmations, joiners and leavers stop arriving as free text and follow defined paths.
Power Automate and Microsoft Lists centralize validations and decisions before final execution.
The automation ends in the Excel roster, preserving continuity with the process already adopted by the business area.
The current team composition is automatically sent to the person responsible for validation.
Confirmations, joiners and leavers follow defined paths instead of free-form messages.
Rules and references are checked before a change reaches the main roster.
Execution ends in the operational roster already used by the business area, preserving continuity.
Instead of validating through individual conversations and handling each change manually, the automation organizes the cycle, routes changes and maintains a single final roster.
The automation gives each tool a clear responsibility without unnecessarily replacing the operational roster already in use.
The flow connects communication, forms, validations and update rules so each action follows a predictable path.
Microsoft Lists acts as a reference and validation layer, while the final update remains in the Excel roster.
understand the context · structure the problem · build a reliable solution