Feature requests

ability to drag and reposition goals as they appear within a review.

Users will be able to carry over their shared notes into recurring meetings. This helps teams retain important context like shared documents, links, and decisions without needing to re-add them manually each time.

It would be great to see tasks in a calendar view with a potential link into Microsoft outlook

Clickable buttons for each competency in the Required competencies column that will give a description of the competency. This will allow for quick review related to a specific role. Another suggestion is to have a roles archive instead of having to delete unassigned roles.

I have a number of tasks that require several checklist items that have due dates. It would be super helpful to have the ability to set those dates and have the related Goal roll up from task progress from the checklist items.

Hi Teamflect team, I’d like to suggest adding native support for the RACI methodology inside Teamflect, specifically at the level of OKR Initiatives / Tasks. In our OKR setup, an initiative is often not just a simple task—it can be a cross-functional project involving multiple teams. Teamflect already helps with accountability because we can define the Owner of an initiative. However, in multidisciplinary initiatives we also need clear governance and collaboration roles beyond the owner: R — Responsible: Who executes the work day-to-day (can be one or several people). A — Accountable: Who approves decisions and is ultimately answerable for the outcome (ideally one person). C — Consulted: Who must be consulted and provide input before key decisions are made (two-way communication). I — Informed: Who should be kept informed of progress and outcomes (one-way communication). Today, the Owner concept covers part of this, but Teamflect doesn’t clearly capture who approves (A), who must be consulted (C), and who must be informed (I)—which creates ambiguity in approvals, decision-making, and when/why certain stakeholders should participate. A RACI capability could be implemented as: A dedicated RACI section within each Initiative (people picker for R/A/C/I), Optional rule: enforce single “A” per initiative, Integration with updates/notifications: auto-notify I on milestone updates, and prompt C when input is requested, Visibility in dashboards to quickly understand governance and dependencies across teams. This would materially improve cross-team execution, reduce bottlenecks, and make initiatives easier to scale across the organization. Thanks for considering it — happy to share examples or use cases if helpful.

It would be helpful to have the ability to decide whether one or both people need to answer the questions on the check-in template, similar to the configuration of the review templates. Right now, both the supervisor and the employee are required to answer, and some questions only make sense to be answered by the employee.

Option to view tasks associated to a goal in order of due-date to improve clarity and visualization

Add a new goal's metric option - Due Date - for objectives that must be completed by a specific date (e.g., “Deliver X by May 31”). For such goals, the system should automatically calculate progress over time based on the current date versus the period to the due date. This complements the existing “Start–End date” (duration) model and better reflects deadline-driven goals. Currently, goals are tracked primarily with a start and end period (e.g., Jan 1–Jun 30). However, many business objectives are binary and deadline-driven (“do X before a given date”). Without a due-date-based progress metric, users see 0% progress until manual updates, which: Obscures urgency and time remaining. Creates inconsistent tracking vs. duration-based goals. Increases manual maintenance by managers and employees.