Task ownership
Task ownership in project management: one clear owner at a time.
Task ownership means knowing who is responsible for moving the work forward. Relay separates owners, reviewers, and requesters, so giving feedback does not make someone the owner. Team requests stay unowned until someone accepts.
One owner at a time. Everything else is a role, not ownership.
Definition
Ownership means accountability for the next step.
An owner is the person responsible for moving a piece of work forward. Not the person who requested it, not the person reviewing it, not everyone attached to it — the person whose action is next.
Defined that way, ownership can only belong to one person at a time. The moment two people hold it, neither does.
Why it blurs
Most tools overload one field.
A single assignee field gets used for four different meanings: this is yours to do, please look at this, I need this from your team, and I want to keep an eye on it. Each of those is a different kind of accountability, so the field stops meaning anything.
Then the work compensates for the model. People add "(with Sarah)" to titles, comment to be noticed, and hold status meetings to reconstruct who has what.
- Owner
- One person is accountable for moving the work forward.
- Reviewer
- Has the work in hand to look at it. The owner does not change.
- Requester
- Asked for the work. Sees it under Waiting until someone accepts.
- Team ask
- A request pointed at a team, with no owner until a person accepts it.
Reviews
Review should not cost you ownership.
Sending work for review moves the action to the reviewer while ownership stays with you. The reviewer sees it under Needs you. Requested changes return to you. Approval moves the work forward. At no point does a review turn a reviewer into an owner by accident.
Tuesday, September 8
Good morning, Maya.
Here’s what needs you, what you chose, and what is moving with someone else.
Needs you
0Today
1Homepage copy
Website refreshplanned for todaydue Friday
MS
Waiting on someone else
0Upcoming
0Homepage copy sits under Today because Maya planned it for today. Due Friday.
States
Waiting and Needs you are the honest pair.
If you own something but another person has the ball, it is in your Waiting on someone else — still yours, not your move. If something is genuinely your move, it is in Needs you.
Those two sections replace most status questions. "Is this on me?" has a visible answer at all times, for both people.
- Needs you
- Your action is the next one.
- Today
- What you chose to do today, not what happens to be due.
- Waiting on someone else
- You own it, someone else has the ball.
- Upcoming
- Everything else you own.
Team asks
Work with no owner should look like it has no owner.
When you ask a team instead of a person, Relay does not pretend an owner exists. The request stays unowned and visible to the team until someone accepts it, and that acceptance is what creates ownership.
Tuesday
Requests · Design
Work your team has been asked to pick up.
New request
not sentLaunch graphics for the spring drop
Spring launchMarketing → Designnobody owns it yet
The launch graphics request is ready to send to Design.
Common mistakes
Where ownership usually goes wrong.
These patterns show up in almost every team, regardless of tool. Naming them is most of the fix.
- Shared ownership
- Two owners usually means nobody moves first.
- Reviewer as owner
- The person giving feedback ends up holding the work.
- Requester as owner
- Asking for something is not the same as doing it.
- Unowned but assigned
- Work assigned to a group looks owned when it is not.
- Owner by default
- Whoever created the task keeps it long after it moved on.
Example
One brief, four roles, one owner.
A marketing lead requests a product one-pager. A writer drafts it, a designer lays it out, and the lead approves it. Four people are involved, but at each moment only one of them has the next step.
Early on the writer owns it and the lead is the requester. When the writer sends it for review, the lead has the action but the writer still owns it. When the writer passes it to the designer, ownership moves. Asked at any point, the question "whose move is it?" has one answer.
Explore Relay
Keep reading
- Project management without status updatesWhy work events, not manual updates, should keep a project current.
- Work handoffsHow ownership moves deliberately between people.
- Approval workflowsSign-off that moves work without moving the owner.
- Marketing teamsOwnership across cross-functional campaign work.
See ownership stay clear in your own work.
Start free, and let every piece of work answer who has it without anyone asking.
Free for solo use. Team starts with 14 days free — no card required.