Asana Auto Assign Tasks with Round Robin Rules and Workload Based Assignment

The three native ways Asana assigns a task

Every automatic assignment in Asana is a rule: a trigger such as a task being added to the project, a form being submitted, a task moving to a section or a custom field changing, followed by one or more actions. The action that matters here is Set assignee. Rules are included from the Starter plan up, and the monthly rule action caps that Starter (250) and Advanced (25,000) used to carry were rolled back, according to the community maintained list of Asana limits.

• Fixed assignee. When a task is added to the Design requests project, assign it to Dana. Simple and reliable, and it turns Dana into a human router who forwards half of what she receives.
• Assignee by field value. One rule per option of a dropdown such as Request type, Region or Client. Asana documents this pattern in its help article on assigning work automatically with custom fields. It routes by category well and says nothing about who in that category is free.
• Round robin. Added to Set assignee in August 2026. The rule rotates new tasks through an ordered list of teammates you pick.

All three answer the question which person for this kind of task. None of them answers which person can take this task right now, and that second question is the one a team lead answers by hand every morning.

What the new Asana round robin does, in its own words

The launch post in the Asana Community on 27 August 2026 describes the feature in one sentence: you can rotate tasks automatically through an ordered list of teammates right inside Set assignee, on Starter, Advanced, Enterprise and Enterprise+. For a team that has waited years for this, it is a real step. The original community request had been open for years, a partner built rotation was deprecated in June 2024, and admins spent most of 2025 trying to make AI Studio keep a rotation.

What the announcement does not say is just as useful to know before you rebuild intake on it:

• No workload signal. The rotation is an ordered list. The next task goes to the next name, whether that person holds 3 open tasks or 33.
• No availability signal. There is no mention of skipping people who are out of office. One admin in the thread said skipping absent teammates would make sense, which is a request, not a feature.
• Gradual rollout. Admins replied on 27 August and 1 September 2026 that they did not see the option in their rule builder.
• Coverage gaps users reported. One user wrote that it does not seem to apply to repeating tasks, and asked for subtask support because all of their use cases are subtasks.

If your intake is light and your team is always fully staffed, the native rotation is enough. If people take time off, carry very different loads, or need to explain to a client why their request went to a junior designer, it is not.

Why equal turns stop being fair after a week

Round robin is fair on day one. By day five it usually is not, because tasks are not the same size and people are not equally available. Three patterns show up in almost every team that switches it on.

• The vacation pile. A designer leaves for two weeks. The rotation keeps handing them every fourth request, and when they return they face 15 tasks that clients have been waiting on, while the rest of the team had a lighter fortnight than usual.
• The fast closer penalty. The person who finishes quickly gets exactly as many new tasks as the person who never finishes, so the open queue grows on the slowest desk and nobody sees it until a deadline slips.
• The new hire flood. Teams that wrote their own least loaded script on Enterprise met the opposite problem. A user in the round robin thread wrote in July 2025 that a new team member receives all tasks until their count catches up with everyone else, so counting open tasks alone is not the whole answer either. You need a cap per person as well.

Fair assignment needs three inputs at the moment of assignment: who is available, how much each person already has open, and which tasks need a specific skill. A rotation has none of the three.

Building least loaded assignment with script actions

Asana does offer a way to code real logic. Script actions let a rule run a Node.js script that calls the Asana API, and the developer documentation states that script actions are available to Enterprise and Enterprise+ customers. A script can count each teammate open tasks in a project, pick the lowest, and set the assignee.

Three costs come with that route:

• The plan. Enterprise is priced by sales. A team on Starter at $10.99 or Advanced at $24.99 per user per month billed yearly has to move to a quoted plan to get scripts at all.
• The upkeep. Someone writes the script, handles time off (Asana keeps out of office in user settings, which the script must read), caps the new hire flood, and fixes it when a project is duplicated or a teammate leaves. That is usually one ops person who is also on the rotation.
• The explanation. Unless the script also writes its reasoning to a field, the task shows a rule ran and nothing more.

For a few teams this is the right answer. For most it is a project nobody budgeted, and it stops working the week its author changes jobs.

Setting up Asana auto assign tasks the right way

Whichever method you pick, the same setup decisions decide whether automatic assignment works:

1. One intake project per team. Point the request form at a single project, so every rule fires from one place and nothing arrives through a side door.
2. Classify before you assign. Make Request type and Priority required form fields. A rule cannot route by a field the requester skipped.
3. Separate who from what. Use field rules for the category (design versus copy), then choose the person inside that category with rotation or load. Mixing both into one rule is how teams end up with 40 rules per project.
4. Decide what happens when nobody is free. Leave the task unassigned in a Needs owner section with a rule that alerts the lead, rather than letting it sit with someone on leave.
5. Review the spread weekly. Group the intake project by assignee and look at open counts. If one person carries twice the median, the method is wrong, not the person.

How Assigner assigns Asana tasks fairly

Assigner is task assignment software that sits beside Asana and decides who takes each new task. Your projects, forms and rules stay where they are. A rule or webhook sends the new task to the Assigner intake endpoint, Assigner picks one available person and records why, and a signed webhook sends that decision back so the task gets its assignee.

• Rotation with real availability. Round robin or weighted round robin that skips people who are out, off shift or over the cap you set.
• Load before turn. Load balanced routing sends work to the person with the most room, with a per person cap so a new hire is not flooded.
• Skills and priority. Route by request type, client, language or region, with urgent work jumping the queue.
• A reason on every assignment. Each assignee comes with the rule that chose them, for example skill match plus lowest load plus available, which is the answer a lead needs when someone asks why.
• One engine for every queue. The same rules route Asana intake, help desk tickets and CRM leads, so ops, support and sales stop maintaining three setups.

Pricing is per user: Starter is $7 per user per month billed yearly, Team $18 and Business $36, each with a 5 user minimum, and you license only the people who receive work. Load balanced routing starts on Team. Try the routing studio at the top of this page with your own team before you change a single Asana rule.

Can Asana auto assign tasks?

Yes. Asana auto assigns tasks with Rules that use the Set assignee action. A rule can assign a fixed person when a task is added or a form is submitted, assign by custom field value, or rotate tasks through an ordered list of teammates with the round robin option added in August 2026. Rules are included from the Starter plan up.

How do I auto assign tasks in Asana?

Open the project, choose Customize, then Rules, and add a rule. Pick a trigger such as Task added to this project or Form submitted, then choose Set assignee as the action and select a person, or the round robin option if it is available in your workspace. Save it and test it with one submission.

Does Asana have round robin assignment?

Yes, since 27 August 2026. Asana announced round robin inside the Set assignee rule action on Starter, Advanced, Enterprise and Enterprise+, rotating tasks through an ordered list of teammates. The rollout is gradual, and several admins reported they did not see it yet in early September 2026.

Does Asana round robin consider workload or time off?

The launch announcement does not mention either. It describes rotation through an ordered list, so a teammate with many open tasks or one who is on vacation still receives the next task in turn. Balancing by open load or skipping absent people needs a script action on Enterprise or an outside router such as Assigner.

Can Asana automatically assign subtasks?

Not reliably with round robin. Users in the August 2026 launch thread asked for subtask support because their intake work lives in subtasks, which suggests the rotation targets tasks. Teams that need subtasks spread across people use a script action on Enterprise or an outside router, so test the current behavior in your own workspace first.

Why is my Asana rule not assigning tasks?

Check the trigger first. Rules fire on an event such as a task being added, moved or changed, so tasks that were already in the project before the rule existed are not assigned. Also confirm the assignee is a member of the project, that the rule is turned on, and that repeating tasks are not involved.

Which Asana plan includes rules?

Starter, Advanced, Enterprise and Enterprise+ all include rules, and the Asana pricing page lists unlimited automations from Starter. The free Personal plan does not include rules. Script actions, which run custom code inside a rule, are limited to Enterprise and Enterprise+.

How much does Asana cost per user for automatic assignment?

Starter is $10.99 per user per month billed yearly or $13.49 monthly, and Advanced is $24.99 yearly or $30.49 monthly, per the Asana pricing page in October 2026. Both include rules and round robin. Enterprise, needed for script actions, is priced by sales.

Can Asana assign a task to multiple people?

No. An Asana task has one assignee by design. Teams add other people as collaborators, use a People custom field for a second owner, or split the work into subtasks with their own assignees. Any automatic assignment method, including round robin, writes one person.

How do I bulk assign tasks in Asana?

Select several tasks in list view with Shift or Ctrl and use the multi select bar to set one assignee for all of them. That is a manual one time action. For new tasks arriving every day, a rule with Set assignee or an outside router keeps assignment automatic.

Can Asana assign tasks based on a schedule or rotation by week?

Not natively. An admin asked in March 2023 for weekly on call style assignment and the request was merged into the round robin thread. The August 2026 round robin rotates per task, not per week, so schedule based assignment still needs a script or an outside tool that reads availability.

How much does Assigner cost for Asana task assignment?

Starter is $7 per user per month billed yearly with round robin, capacity caps and availability skip. Team is $18 and adds load balanced and priority routing across all work types. Business is $36 with territory rules and weighted round robin. Each plan has a 5 user minimum.