Skip to content

Use cases

Use cases

ProTask is generic on purpose: workspaces, projects, lists, and tasks can mean different things in different companies. These pages explain how to map real work onto those objects, not only which butt…

Last updated Aug 20, 2026 · 2 min read

ProTask is generic on purpose: workspaces, projects, lists, and tasks can mean different things in different companies. These pages explain how to map real work onto those objects, not only which button to click.

Each use case follows the same shape:

  1. What you are trying to achieve
  2. How to structure workspaces and projects
  3. Day-to-day loop (where people live in the UI)
  4. Reporting and notifications

Read First week after install if the database is still empty. Then pick the closest match:

Situation Start here
Several clients, retainers, or brands Agency / client work
One product, sprints, bugs, and roadmap In-house product team
You are the only (or main) worker, hours matter Freelance and solo work
Recurring checklists, shifts, or SOPs Operations and recurring work

Shared rules that prevent mess

  • One workspace per boundary of people and confidentiality. Client A should not see Client B’s boards. A department that must not see another department’s work gets its own workspace.
  • One project per body of work you want to close or report on. “Website redesign” is a project. “The whole company” is not.
  • Lists are workflow, not categories. Categories belong on labels. Lists are stages (Inbox → Doing → Review → Done).
  • Time lives on tasks. If you need a timesheet, people must start/stop the timer (or you accept that the report will be empty).

Feature how-tos (create workspace, move a card, filter by due date) live under Using ProTask.

← All ProTask – Project Management Software with Time Tracking & Team Collaboration documentation

We use cookies to understand how visitors use this site. Cookie Policy