What happens when I give one task to thirty people?

Everyone gets their own copy, with their own deadline, attempts and history. Giving the same task to two groups is fine as well: anybody already on it is skipped rather than given it twice.

Can somebody see another person's submission?

No, unless they review that person's group or have workspace-wide access. The comment thread on a piece of work is only between that person and their reviewers.

What if the deadline passes?

If you allowed late work it still goes through and is clearly marked as late, so nothing is lost and nothing is hidden. The deadline it started with is kept even when you extend it.

Can I change the words to match how we talk?

Yes. Pick General, Education, Operations or Professional services, or change a single word on its own. It only affects labels, nothing you have already created, and you can switch back at any time.

Do people need to download files to review them?

No. Images, PDFs, Word, Excel, video, audio and plain text all open in the browser. Anything else downloads rather than failing.

Can approved work be reopened?

Yes. You have to say why, the person is told, and it goes back to in progress. It also shows in their record, so repeated rework is visible rather than quietly absorbed.

All apps

OperationsLive now

TasksGive work out, and see it come back

Write a task once and give it to one person or a whole group. They tick off the steps and send it back with whatever you asked for, in any file format. You read it in the browser, approve it or ask for changes, and every handover, deadline change and reopened item keeps its reason on the record.

Start freeView pricing

Give it to one person or a whole group at once
Any file format, read in the browser without downloading
Approve, request changes, mark it, or reopen it later
Wording that fits a school, a shift rota or a client team

API endpoints

Webhook events

Ready-made vocabularies

Everything it does

Explore every feature

Tap a category to see what is inside. Nothing hidden, nothing bloated.

The full round trip

One task, given out, worked on, sent back and decided. Nothing lives in an inbox or a spreadsheet on the side.

One person, a group, or bothGive a task to named people, to every member of a group, or both at once. Anyone already on it is skipped rather than given it twice.
Say what has to come backA note, files, both, or nothing at all. Set a minimum number of files and a limit on how many attempts somebody gets.
Steps to tick offBreak the work into a checklist so the person doing it knows what is left, and you can see how far along they are before it arrives.
Built for a phone firstThe screen the assignee uses is designed for a phone, because the work is usually done away from a desk.

How it works

Live in a few steps

Pick your wording

Choose the vocabulary that fits your workspace, then set up the categories your work falls into.

Put people into groups

Say who reviews and who gets given work. One person can be a member of one group and a reviewer of another.

Write it and give it out

Set the brief, the deadline and what has to come back, then hand it to a person, a group, or both.

Decide and move on

Work arrives in one queue. Approve it, ask for changes, or reopen it later, and the record builds itself.

Where it shines

Made for real work

Teaching and training

Set work for a class, take it back in any format, mark it with a rubric or letter bands, and see each learner's record by subject.

Shift and site operations

Give the same checklist to everyone on a shift, get photos and signed sheets back, and see what was done on time without marking anything.

Client delivery

Track deliverables per engagement, approve them or send them back with written feedback, and keep the reason for every deadline change.

Repeating rounds of work

Onboarding a new starter or a monthly compliance round: build the steps once as a template and run it against a group whenever it comes round.

For developers

Embed it, or drive it from code

API scopes

service.tasks.viewservice.tasks.manageservice.tasks.assignservice.tasks.submitservice.tasks.reviewservice.tasks.groups.manageservice.tasks.templates.manageservice.tasks.export

Webhook events

tasks.assignedtasks.reassignedtasks.delegatedtasks.startedtasks.submittedtasks.changes_requestedtasks.completedtasks.reopenedtasks.cancelledtasks.due_date_changedtasks.overdue

Product guide Developer reference

Questions

Frequently asked

No. Marking is off by default. Leave it off and you still get completion, timeliness and rework figures for everyone, which is how most operations teams use it.

Better together

Pairs well with

AI WorkflowsCreate work automatically on a schedule or after an event.

FormsUse the same field builder to ask for structured answers.

AppointmentsTurn a completed visit into follow-up work for the team.

One subscription covers every service.

Ship Tasks on your site today

Create a free workspace, install Tasks, and go live in minutes. 14-day trial on paid plans.

Start free View pricing

TasksGive work out, and see it come back

Give it to one person or a whole group at once

Any file format, read in the browser without downloading

Approve, request changes, mark it, or reopen it later

Wording that fits a school, a shift rota or a client team