Work types
Map typed work to the relevant project workflow.
Feature
Give every piece of work the structure it needs, and no more.
Typed work items connect ownership, workflow, relationships, discussion, and history to the surrounding project.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Configure work types
Map a project work type to the workflow used by the team.
- 02
Add a custom field
Create a typed field with the label, help text, and options the work needs.
- 03
Inspect activity
Review a focused feed of dated work-item history.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Custom fields
Create the exact typed properties required by the team.
Subtasks and relationships
Inspect populated subtasks and typed links without leaving the work item.
Activity history
Keep dated status, estimate, dependency, and creation events together.
Control point
AI follows the same boundary.
Where AI is enabled, accessible context and review-oriented flows apply to the surrounding workspace rather than bypassing its controls.
- Scoped context
- Configured provider
- Visible proposals
- Human decision
Deployment and security
Control the deployment and the boundary.
Use TOW Cloud, run TOW on controlled infrastructure, or operate an air-gapped Docker Compose deployment. Permissions, identity settings, exports, and AI provider choices stay visible to administrators.
Explore self-hosting
FAQ
Questions worth answering clearly.
Current product, deployment, and commercial boundaries.
Is work types implemented in TOW?
Yes. Work types, Custom fields, Subtasks and relationships, Activity history are part of the current product surface and are backed by the linked implementation evidence.
Can this be self-hosted?
Yes. The capability is available within the TOW application in a configured self-hosted deployment.
See TOW in your environment