Work management
Things to do, boards and plans.
Base
Tracking
Process
Control
Layers
Layers build on each other and each one works on its own: turn on the next layer when you want it, turn it off when you don't. Turning off deletes no data.
Base
“Let me keep my list in order.”Work items, status, templates and recurrence
- Up to 10 tags per work item, matched regardless of case and used in filters and search
- Decisions are recorded on a work scope; a decision is never edited, a correction is a new decision
- Dependencies between work items can never form a loop: the database refuses it, whatever screen or script writes it
Tracking
“Let me not miss what happens when.”Work templates and recurrence
- Recurring work opens its own work item weekly, monthly, quarterly or yearly, with an owner and a due date
- Missed runs open one item, for the latest due day, never two for the same day; day 31 means the month's last day
Process
“Let the work follow a rule.”Boards, sprints, plans, milestones and dependencies
- Work-in-progress limits on board columns that warn by default or can be set to block
- A weekly resource schedule with tentative and confirmed bookings; overbooking is flagged, not blocked, and a booking copies to up to 26 weeks
- A 12-month resource horizon: capacity after holidays and approved leave, with confirmed, tentative and free hours; employees and business partners included
- A planned hire is scheduled like a person, with role, start and monthly cost; once hired, their plans move to the person
Works with
With both modules on, their records link to each other; with one off, a record is complete without the link.