Workspace table
Tasks
The Tasks table stores discrete units of work someone has to complete: onboarding steps, service tasks, care logs, inspections, forms, and acknowledgements. Completed tasks become structured records instead of disappearing into chat.
Illustrative example
From tasks to a useful workspace
- 01
Start with a table
Tasks
- 02
Build a workspace
Onboarding pipeline
- 03
Focus the view
Overdue
A suggested way to organize your information. This diagram is not a product screen.
What belongs in this table
- 1Onboarding checklists assigned to new hires.
- 2Service work and care logs completed during a shift.
- 3Inspections and quality checks tied to locations.
- 4Forms and acknowledgements workers submit from mobile.
Fields to understand
Your account may use different field names and permissions. Use these examples to understand what each field contributes.
- Task name
- What needs to be done, in operator language.
- Assignee
- Link to the User responsible for completing it.
- Due date
- When the task must be done; drives overdue queues.
- Status
- Not started, In progress, Completed, or Blocked.
- Linked records
- The shift, location, or document the task relates to.
- Form content
- Checklist items or form fields captured on completion.
Ideas for your team
List
Onboarding pipeline
Tasks per new hire, grouped by stage.
List
Overdue tasks
The exception queue managers work first.
List
Daily reports
Shift tasks and logs submitted from the field.
Example tabs
- Overdue
- Due today
- In progress
- Completed