Non-promotable tasks can keep a small company running while contributing little to the career progress of the person doing them. Before asking the usual volunteer again, review the upcoming work alongside existing commitments and opportunities to develop. Make the allocation yourself, explain the trade-off and check who actually does the work.
What you'll learn
- Identify low-promotability work using the criteria for the actual role.
- Allocate necessary helping and developmental work together, with a real workload trade-off.
- Check whether the agreed distribution survives contact with the work.
Which work counts as non-promotable tasks?
Meeting notes, onboarding help, organising an internal event or repairing a shared document may be non-promotable tasks in one role and central responsibilities in another. Keeping operating records accurate could be a recognised outcome for an operations specialist. The same maintenance work could repeatedly displace the project evidence a designer needs for their next role.
Ask what good performance in this role is meant to demonstrate, then check which work gets mentioned in reviews and development decisions. If helping is formally valued but routinely disappears from those conversations, the issue may be recognition or evaluation as well as allocation. Do not describe essential work as worthless to the people who rely on it.
Keep the distinction visible to the employee: "This needs doing, but it will take time away from the work we agreed would demonstrate your next-level skills. Let's decide what moves and how your contribution will be recorded." This is an illustrative manager invitation, not a research-tested script.
Why the usual volunteer needs another look
The experiment involved 150 University of Pittsburgh undergraduates in ten anonymous, three-person rounds. An investment benefited the group but paid the volunteer less than the other members. Women invested an average 3.4 times and men 2.3; the authors reported a 48% difference. A separate experiment with single-sex sessions did not show that gap. These are laboratory results, not current employee rates or evidence about a particular colleague's preferences.
A different mechanism appears in Bae and Woolley's 2026 research: managers allocated more additional tasks to employees they perceived as intrinsically motivated. Managers assumed that enjoying the main job meant enjoying the extra task too. Perceived motivation is not the same as reliability, skill or available time.
Cornell's explanation of that research describes an intervention in which managers considered multiple allocations together rather than deciding one request at a time. It reduced the preference for giving extra work to the more intrinsically motivated employee in the tested setting. The small-team process below is a practical adaptation; the research does not establish its effects in your company.
Make the next allocation together
- 01
Identify the work and its recipient
Describe the needed output, when it is due and who depends on it. Check whether the task can be removed or simplified before distributing it. Include the preparation and follow-up, not just the visible meeting or handover.
- 02
Check who can take it on
Compare relevant skills, access, current commitments and agreed working time. Ask what learning or responsibility the person wants next. A quiet colleague is not automatically available, and an enthusiastic colleague is not automatically willing.
- 03
Choose a workable trade-off
Assign the necessary work to an owner, with support and a check of the finished output. Change a competing commitment explicitly. Consider who receives the developmental assignment too; moving routine duties does little for career access if the promising work still goes elsewhere.
- 04
Explain and review the decision
Record who owns each output, why any exception is needed, what moved and when you will review completion. Tell affected stakeholders about changed dates or scope yourself.
Suppose a four-person operations team has three upcoming assignments: a customer handover record, materials for a new starter and a chance to lead a customer briefing. This is a hypothetical allocation, not a Cooperly customer case. Alex usually tidies records and helps new starters, while Jordan usually gets the customer-facing work.
| Assignment | Owner and support | What changes elsewhere |
|---|---|---|
| Customer handover record | Sam owns the record using the existing format. Alex answers a bounded set of handover questions; the manager checks the finished output. | Sam's non-urgent internal report moves to the next agreed window. Alex is not kept as an unlimited fallback. |
| New-starter materials | Jordan owns the materials and checks them with the manager before the starter arrives. | One internal improvement task waits. The preparation work does not quietly return to Alex. |
| Customer briefing | Alex wants to practise this responsibility, has the required customer access and leads with the manager available for agreed support. | Alex's routine work is reduced so preparation fits. Jordan shares existing briefing notes rather than taking the assignment back. |
Discuss those choices with the people involved before treating the table as settled. If Sam needs much more help than expected, account for Alex's support time and reduce scope or find another arrangement. A transfer that leaves Alex doing the work invisibly has not changed the distribution.
When the problem is more work than the team can carry, use the team overload review to reduce commitments. Reallocating non-promotable tasks cannot create time that nobody has.
When a rota would make the work worse
Confidential records, specialist checks and urgent customer work may need a particular owner. Do not distribute them by task count or put an unqualified colleague on a rota. If one person must carry the assignment, remove other work where possible, recognise the contribution through the appropriate process and make any training or backup plan concrete.
Use the guide to an employee ready for promotion when no role is available if the unresolved issue is a real organisational constraint. Changing the allocation will not create a vacancy or approved pay decision.
If you keep rescuing assignments despite adequate support and agreed boundaries, inspect your own delegation pattern. That is a different problem from deciding who receives non-promotable tasks in the first place.
Check who actually did the work
In the hypothetical team, Sam completes the record but Alex spends more time helping than the manager allowed for. Jordan prepares the starter materials. The customer briefing is postponed, and Alex uses the released time to catch up on routine requests instead. The necessary work moved, but the developmental opportunity did not happen.
The manager should now account for Alex's support work, clarify what Sam needs for the next record and decide whether Alex still wants the briefing. Rebook it with preparation time protected, or agree a different opportunity that is available. Do not mark development complete because a promising assignment once appeared in the plan.
Keep a short shared work record: agreed owner, actual contributor, rough effort, changed commitment and next decision. Use appropriate access and avoid collecting private explanations for someone's availability. Review the work with the people involved; do not turn helping into a public league table.
Cooperly's Fundamentals can support the conversation about commitment and accountability. Current working preferences can help you ask better questions, but they do not measure spare capacity or decide a fair allocation. Keep the task record and the manager's decision grounded in the actual work.