Teamflect makes it easy to automate review, survey, and 360° feedback cycles so evaluations happen on time with minimal admin effort. You can set up:
Periodic automation — recurring cycles on a fixed cadence (e.g., quarterly, annually).
New Hire automation — one-time cycles triggered by a hire event.
Anniversary automation — cycles triggered on employee anniversaries based on a chosen date attribute.
This article explains where to create and manage automations, how each type behaves, and the best practices to keep your process clean and predictable.
Audience selection options: When creating automations, you can target Everyone, Everyone who signed, or Filter by attributes (e.g., department, location). These options are available where applicable across Review/Survey/360 templates.
1. Access & Navigation
Go to Admin Center → Modules → Reviews
Click Automation Rules. This page lists all automations created per template and shows the next cycles.
Use filters (template, status, owner, etc.) to find what you need.
Click See cycles on any rule to view active or historical cycles.
Use the ⋯ (ellipsis) next to a rule to edit or delete it.
2. Create a New Automation Rule (Periodic - New Hire - Anniversary)
If you want to start a new automation, click the Create New Automation button.
You will be prompted to:
Name the automation.
Select an automation type (periodical - new hire - anniversary).
Select a template for the review process.
Name the cycle.
Choose the reviewees.
Set the due dates.
After configuring these options and clicking Save Automation, the new automation will be created.
3. Automation Types
1) Periodic Automation
Use this for recurring reviews (e.g., Q1, Q2, Monthly, etc.).
The next cycle and group of reviewees are visible in advance.
Ideal for broad compliance windows or company-wide cadences.
2) New Hire Automation
Use this to trigger a one-time review for employees who recently joined.
Triggered from hire events, future reviewees aren’t always listed in advance.
Good for 30/60/90-day performance check-ins or probation reviews.
3) Anniversary Automation
Use this when you want to automatically send a review on specific anniversary years (e.g., 1st, 3rd, 5th) or every year.
What you’ll configure for the Anniversary Automation
Attribute selection (required)
Field: “Which attribute is the anniversary automation based on?”
Shows only date-type attributes from Admin Center > Users > User Attributes.
Default: Employee hire date.
Note: The data source follows your User Attribute Settings (Azure AD, third-party HR system, or manual entry).
Automation recurrence (required)
Every anniversary or multi-select dropdown for 1–50 years.
Example: selecting [1, 5] sends on the 1st and 5th anniversaries only.
If the selected anniversary year is already in the past for an employee, the rule does not backfill a cycle.
Example: Employee is in year 3; admin selects year 2 → no cycle is created for that employee.
Alternative: Send on every anniversary (toggleable). When enabled, the rule triggers every year for eligible users.
Special date rule for the Anniversary Automation
If the attribute date (employee hire date) is Feb 29, the automation fires on Feb 28 in non-leap years.
4. Manage Existing Automations
Click See upcoming cycles to inspect upcoming/historical cycles.
Use ⋯ (ellipsis menu) to Edit (eligible fields) or Delete.
Remember: Editing does not retro-change already-created cycles.
Use Cases
Annual or Quarterly Reviews
Automate recurring cycles to ensure evaluations are completed on schedule.Onboarding Reviews
Trigger new hire reviews automatically to capture early performance insights.Compliance-Driven Evaluations
Set automation for specific roles or regions to ensure regulatory requirements are met without manual tracking.
Best Practices
Name clearly: e.g., “Q1 2026 Sales Reviews”, “Year-1 Anniversary Check-in”.
Attribute hygiene: Keep date attributes clean, unique, and correctly mapped from your data source. Deleting attributes will break anniversary rules.
Audience filters: For Anniversary, consider pairing with Filter by attributes (e.g., country, function) to control scope.
Leap-year check: If using Feb 29 attributes, confirm that Feb 28 behavior matches your policy.
Change control: Document edits to recurrence so stakeholders know who receives which cycles and when.