Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.
Work BoardThe plan people actually work in
Phases, workstreams and deliverables are tickets with owners, a priority from P0 to P5, labels and due dates, moving through statuses you define. Because the team works the board, moving a card is the status update. There are no dependency links, swimlanes or sprints.
- Custom statuses from kickoff to closeout
- A Blocked or Waiting-on-client status that makes stalls visible
- Change requests tracked as their own tickets
Work BoardTasksOwners, dates and what is actually assigned
Every commitment is a task with one or more assignees, a due date, labels and a checklist. Filter the list by assignee to see what each person owns in this project. The due date lands on the project calendar with a reminder, and assignees are notified in the app, by push, by email or on WhatsApp where it is enabled, per their settings.
- Assignments with due dates on the project calendar
- Checklists inside a task for the steps it needs
- Recurring tasks for weekly reports and reviews
TasksCalendarMilestones, gates and the critical dates
Put milestones, review gates, steering meetings and launch dates on the project calendar, with attendees from the team, RSVPs and reminders. Task and ticket due dates appear in the same month, week, day or list view, so a crowded week is visible before it arrives.
- Milestone and review-gate schedule for the project
- Steering meetings with RSVPs from the team
- Due dates and milestones in one view
CalendarNotesDecisions, risks and meeting records
Meeting notes, a decision log and a risk register live as notes on the project instead of in a personal notebook, with labels, owners and due dates. A note can be turned into a draft task or ticket in one step, and anyone in the project can find it later.
- Decision log with the reasoning written down
- Risk register kept as a labelled note
- Action items turned from a meeting note into draft tasks
NotesBacklogScope requests without scope creep
New asks land as tickets in the Backlog, the Work Board's list of work not yet started, instead of becoming commitments in your inbox. You decide what moves onto the board. Stakeholders outside the project cannot add to it directly: someone on the team logs the request, or Smart Tickets drafts it from a pasted email for review.
- One list for requests that are not yet approved work
- Triage into the board, later or not now
- A parked list you can point to when scope is renegotiated
BacklogAtty ChatAsk the project instead of the people
Atty reads the apps of the project you are in, so you can ask what closed this week, what is overdue, what is waiting and what belongs in the update, and get an answer built from the records. It drafts notes, tasks and tickets, and every change waits for your approval.
- Weekly status drafted as a note from what moved
- Overdue and blocked sweep before a steering meeting
- A first task breakdown from a project brief, each task approved by you
Atty ChatSharing HubStakeholder updates by link
Share a specific note, task, document or the calendar by public link, with a view count and a switch to turn the link off. Partners who need to work in the project can join as external collaborators on Team plans and above; limited access covers only the apps you grant, and they see everything in those apps.
- The weekly update note shared with a sponsor by link
- A document shared with a client instead of attached to an email
- External partners working in the apps you grant them
Sharing HubDashboardThe project at a glance
Each project has a Home dashboard of widgets built from its apps, such as tasks, calendar, tickets, notes and documents, arranged the way you want. There is no single portfolio screen across projects: you switch projects, and each Home shows its own work.
- Due tasks and upcoming dates on one screen per project
- Widgets arranged around what you get asked about
- A quick check before the Monday meeting
Dashboard