Track your work with tasks
Create tasks linked to a request or bid, assign them to teammates, set due dates, filter by what is overdue or due today, and mark work complete, so nothing in your sourcing slips.
What you'll learn
- Create a task and link it to a request or bid
- Assign it to a teammate and set a due date
- Filter by overdue, due today, or upcoming, and mark work done
Sourcing is full of small commitments that are easy to lose. Call the supplier back about lead times. Chase the missing document before the deadline. Review the three bids that came in overnight. Remind a teammate to approve the award. None of these is hard on its own, but spread across a dozen open requests and a shared mailbox, the one that slips is always the one that mattered.
Tasks give you a single place to capture that work and tie it to the request or bid it belongs to. You can assign a task to a teammate, give it a due date, and then see at a glance what is overdue, what is due today, and what is coming up. When the work is done, you mark it complete, and the record stays attached to the request so anyone reviewing later can see what happened.
Why this matters
A request that stalls rarely fails because of a big problem. It fails because a small follow-up fell through the gap between people. Linking tasks to the request or bid they belong to closes that gap: the next person who opens the request sees what is outstanding, who owns it, and when it is due, instead of relying on someone's memory or a buried email.
What a task can carry
Every task has a title and a due date. Beyond that, you can give it three things that make it useful in a busy team:
| Add this | So that |
|---|---|
| A link to a request or bid | The task shows up in context, and a teammate can jump straight to the request or bid it concerns. |
| An assignee | A specific teammate owns it, and it appears in their view of the work. |
| A type (call, meeting, email, review, deadline, and more) | Each task reads at a glance, so a call stands out from a document review. |
Due dates are date-only: a task is due on a calendar day, not at a specific time. This keeps "due today" reading the same for everyone on your team, wherever they are.
Creating and organising your tasks
Create a task and link it to your work
Go to Tasks in the sidebar and select New activity. Give it a title and a due date. To tie it to your sourcing, search for a request or bid in the Linked to field, then pick a Type and assign it to a teammate. Add a note if there is context worth capturing.
Once a task is linked, opening it lets you jump straight to that request or bid, so the work and the thing it concerns are always one click apart.
See what needs attention first
The top of the page shows four numbers: open, overdue, due today, and done. The tabs below let you focus on exactly one of those slices. Open Overdue at the start of the day to clear what has slipped, then Due today to plan what is next.
Use the My activities only toggle to switch between your own tasks and everything across the team. Search by keyword, sort by due date or any other column, and page through longer lists.
Mark work done, or reopen it
When a task is finished, use Mark complete from its menu. You can add a completion note describing what happened, which stays attached to the task as a record. Need to clear something that no longer applies without completing it? Use Dismiss. If you ever need a completed or dismissed task back, Reopen returns it to your open list.
To close out several at once, select multiple tasks and mark them complete together, with an optional shared note.
A task in context
Scenario
A supplier's bid is missing its delivery terms, and bidding closes in three days. You create a task, "Ask Orion Steel to confirm delivery terms", link it to that bid, set the due date to tomorrow, and assign it to the colleague who owns the request. It shows up in their Due today view, they open it, jump straight to the bid, and message the supplier. When the terms come back, they mark it complete with a note. The whole exchange is now part of the record on that request, not lost in a one-to-one chat.
What good looks like
Teams that stay on top of their sourcing tend to use tasks the same way:
- Every follow-up that matters becomes a task with a due date, instead of living in someone's head.
- Tasks are linked to the request or bid they concern, so context travels with the work and the next person is never guessing.
- Work is assigned to a person, not left ownerless. An unassigned task is everyone's job, which means it is no one's.
- The day starts on the Overdue and Due today tabs, so nothing ages quietly past its deadline.
- Completed tasks carry a short note, so the record explains not just that something was done, but what the outcome was.
Next steps
Related guides