Assign trusted team members to manage your OKRs while you retain ownership and accountability. Your delegates update progress, maintain details, and keep information current, freeing you to focus on strategy while ensuring your objectives, key results, and initiatives never go stale.

Rhythms now supports multiple delegates per OKR and chat-based delegate assignment for faster, more flexible team management.

Senior leaders need to own strategic OKRs to drive them forward and maintain accountability. However, these same leaders often face time constraints that make regular updates difficult. When executives can't provide frequent status updates, OKRs become outdated, showing stale information during business reviews and preventing teams from aligning with current leadership priorities.

Separate ownership from operational updates. You remain the visible owner (your name, your accountability, your control over who helps). Your delegates keep the OKR current by updating progress, maintaining details, and managing alignment based on their proximity to the work.

OKR statuses stay current without requiring you to provide detailed updates. You maintain full visibility and control over who manages updates. With multiple delegates, you gain flexible team coverage for continuity and distributed responsibility. You can step in anytime (delegation supplements your access, it doesn't replace it).

Clear responsibility eliminates "who should update this?" confusion. You have permissions to keep OKRs accurate without constantly requesting changes. When multiple delegates collaborate on complex initiatives, you can share the workload. The system tracks your updates, giving visibility to your contributions.

Strategic OKRs remain reliable for decision-making. Business reviews work with current data. Teams confidently align with leadership priorities. Coverage is maintained during absences, vacations, and time zone differences.

Rhythms supports unlimited delegates per OKR, enabling flexible team management. Assign backup delegates to maintain momentum during vacations or leave. Share responsibility across team leads for department-wide OKRs. Add delegates from Product, Engineering, and Marketing for cross-functional launch OKRs. Assign delegates in different regions for 24/7 time zone coverage. Use primary plus backup delegates for succession planning.

When multiple delegates are assigned, the system displays the first two avatars plus a "+N delegates" indicator for additional team members.

Delegates have broad permissions to keep OKRs well-maintained. They can update OKR details (title, description, team assignment, time period, labels). They can connect to parent OKRs to show strategic alignment. They can create new check-ins as well as edit or delete check-ins made by the OKR owner or previous delegates. They can view complete history including all previous updates by any user.

Three restrictions preserve your strategic control. Only you can transfer the OKR to someone else. Only you can add, change, or remove delegates. Only you can delete the OKR entirely.

⚠️ Delegates cannot see or manage other delegates. Only owners have visibility into the complete delegate list and can modify delegate assignments.

When delegates are assigned, they receive immediate notification with a link to the OKR. Multiple simultaneous assignments are consolidated into a batch notification. When removed, delegates are notified they're no longer responsible for managing the OKR. If a delegate leaves the company, you receive notification for each affected OKR.

Navigate to the OKR details page. Click the delegate management section. Select multiple team members from your organization (owners are automatically excluded). Save your changes.

The system prevents duplicate assignments (each person can only be added as a delegate once per OKR).

Use natural language commands in chat for faster bulk operations.

⚠️ Chat commands replace the entire delegate list rather than appending. To keep existing delegates while adding new ones, include all desired delegates in a single command.

When you're assigned as a delegate, you receive notification with the check-in frequency for the OKR. You can immediately begin updating the OKR details, creating check-ins, and managing alignment.

If multiple delegates are assigned, coordinate timing of updates to avoid conflicts and establish clear communication protocols about who updates what.

You receive notification for each affected OKR. The system automatically removes them as a delegate. Assign new delegates promptly or handle updates yourself.

Make updates yourself anytime as the owner (you retain full access). Discuss obstacles with the delegate (training needs, unclear expectations, competing priorities). Remove the delegate or assign a different person if the relationship isn't productive.

While there's no technical limit on the number of delegates, consider practical management. Maintain clear ownership despite multiple delegates (keep a clear primary owner accountable for results). Establish protocols for who updates what when multiple delegates are active. Coordinate timing to avoid conflicts by communicating about update schedules. Periodically review and update delegate assignments as team needs change. Use chat for efficiency when managing bulk delegate operations.

Delegation is different from ownership transfer. To make someone the new owner, change the Owner field (not Delegate). Delegates remain unchanged when ownership transfers (the new owner can then modify delegates as needed).

The owner is accountable for success, maintains strategic control, and their name appears prominently on the OKR. Owners can do everything including delete the OKR and change ownership. A delegate keeps the OKR current on the owner's behalf with extensive permissions for updates but cannot delete the OKR, change ownership, or modify the delegate assignment.

No technical limit exists. Add as many delegates as needed for your use case. However, consider practical management (clear communication and coordination become more important with larger delegate teams).

No. The system prevents this to avoid permission conflicts. If you own it, you already have full permissions. Delegation is specifically for when the owner wants someone else keeping the OKR current.

The system automatically prevents duplicates. Each person can only be a delegate once per OKR.

Chat commands replace the entire delegate list. To add new delegates while keeping existing ones, include all names in your command.

No, only owners can view and manage the full delegate list. This maintains clear accountability while delegates focus on OKR maintenance.

Delegates remain unchanged when ownership transfers. The new owner can then modify delegates as needed.

No, all delegates have the same permissions. For different access levels, consider using ownership or viewer permissions instead.

Delegates see everything about their assigned OKRs (descriptions, all historical check-ins, alignment, and details). Only assign people you trust with complete visibility.

All existing check-ins remain with original authorship preserved. New delegates can see the full history and can edit or delete prior check-ins made by other users.

No. Assigned delegates can update OKR details as well as provide check-ins. However, they cannot change the OKR owner or delete the OKR.

You can edit the OKR anytime to modify or revert changes. The system tracks who made each change. Discuss expectations directly if issues recur, and remove the delegate if the relationship isn't productive.

No. OKRs count toward the owner's statistics for coverage, alignment, and other reports. Delegation is operational support, not ownership transfer.

Yes. The audit trail shows who made which updates and when, supporting accountability while crediting delegates for their work.

Use the filter options in OKR views to show "Delegated to me." You can also search for OKRs delegated to you using the search functionality.