When multiple people collaborate on goals in Teamflect, it’s natural to wonder whether the original goal creator receives notifications whenever updates occur.
However, not every change triggers a notification. Teamflect is designed to keep goal owners informed about meaningful interactions without overwhelming them with constant alerts.
This article explains which goal updates send notifications, which ones do not, and how this approach helps keep communication clear while preventing notification fatigue.
Actions That Do Not Trigger Notifications
Progress updates: Changing the numeric or percentage progress of a goal.
Status changes: Marking a goal as On Track, At Risk, or Off Track.
Actions That Trigger Notifications
Comments: Adding a comment sends a notification to the goal creator.
Closing a goal: Marking a goal as completed also notifies the creator.
Use Cases
Maintain Goal Progress Privacy
HR teams or managers can adjust progress without overwhelming goal creators with constant alerts. This is especially useful in high-volume initiatives where progress changes frequently.
Encourage Open Feedback
Comments generate notifications, which makes them the best channel for requesting clarification, giving recognition, or highlighting issues directly to the goal creator.
Manage Goal Closure Transparently
Closing a goal is a milestone moment. Notifying the creator ensures alignment on completion or termination decisions.
Best Practices
OKR Check-ins
Use comments to notify employees only when feedback or redirection is needed.
Project Wrap-Ups
Ensure closing goals always notify creators so accountability is transparent.
✅ Best Practice: Use comments for communication and alignment, while reserving progress updates and status changes for behind-the-scenes tracking. This prevents “notification fatigue” and keeps alerts meaningful.