Tasks combines manually created follow-ups with work generated by workflow events. Recruiters always see a personal task scope; managers and owners can switch between their own work and team-wide work.
Use the Tasks workspace
- 01
Open My Work
Review total, open, overdue, and completed-today counts before choosing a view.
- 02
Choose Priority, List, or Board
Priority ranks work across tasks, communications, pipeline SLAs, and compliance. List shows a selected due bucket. Board shows overdue, today, this week, future, and completed columns.
- 03
Create a task
Select New task, enter a title, choose low, normal, high, or urgent priority, and add an optional due date and time.
- 04
Set the work scope
Use Only mine to keep the view personal. Recruiters remain scoped to their own work even when a broader request is made; managers and owners can view team-wide work.
- 05
Update or complete work
In List, select the checkbox to mark a task done or reopen it. In Board, drag a task between due columns to update its state and due date.
- 06
Open related records
When a task is associated with a candidate, job, or client, use the linked name to open that record and complete the work in context.
How board moves affect dates
Dragging to Completed marks the task done. Other columns keep it open and assign a due time within the selected overdue, today, this-week, or future window.
Turn the next action into a specific task
Write a title that tells you what must happen. “Confirm Maya's start date for Cedar Hospital” is a fictional example of a useful action; “follow up” gives much less context. Choose a due date based on the real commitment or workflow need, and select a priority that reflects the agency's shared definitions.
Keep separate actions separate when they have different owners or due dates. Reviewing a candidate reply and checking a client requirement may belong to different people. A single broad task can hide the unfinished part when one person marks it complete. Use the associated candidate, job, or client record to establish context where that link is available.
Choose a view for the question you have
Use Priority when deciding what needs attention across the available work signals. Use List when you want to complete individual tasks in a selected due bucket. Use Board when reviewing how open work is distributed across time. These views help organize the work; changing a view does not complete the underlying action.
Check the scope before comparing counts with a colleague. A recruiter's personal view and a manager's team view cover different work. Owners and managers should verify whether Only mine is selected before using totals in a team discussion. A smaller number in a personal view is not evidence that tasks are missing from the agency.
Understand a board move before making it
Moving a task between due columns can change its due date as well as its position. Use that action when you intend to reschedule the work. If an external commitment cannot move, do not drag the card merely to make the current column look clear. Confirm the new due information after the move.
Dragging to Completed marks the task done. Before doing that, open any related recruiting record and check that the required action actually succeeded. Writing an email draft, for example, is different from sending an approved message when sending was the assigned task.
Investigate missing or apparently completed work
Check the selected view, due bucket, and scope first. A task moved to another date may no longer appear in the bucket you were using. Review completed work if someone may have finished or accidentally checked the task. Reopen a task when the work remains outstanding and your workflow permits that correction.
If an update failed, inspect the saved task before repeating it. Ask a manager to review assignment or visibility when necessary. A useful support report includes the task's purpose, selected view, approximate update time, and visible error; avoid sending an unrestricted list of candidate tasks in an initial message.
Troubleshooting
A due bucket is empty.
Likely cause: No tasks in the current scope fall inside that due window.
Check Only mine, choose another bucket or view, and confirm that the task has a due date.
A board move is reverted.
Likely cause: The task update could not be saved.
Read the error banner, dismiss it after noting the problem, and retry. The board restores the previous state when the save fails.
Priority work cannot be loaded.
Likely cause: The work-queue request failed.
Select Retry. If the failure continues, use List or Board to review saved tasks while support investigates.