Overview
Tasks is the to-do list for the project. It is intentionally minimal — title, assignee, due date, status, optional link back to the artefact that spawned it. The point is not to replace your PM tool; it is to make sure work captured inside AI Noven (in Meetings, RFIs, LoE) does not fall on the floor.
Most tasks are not created by hand. They appear automatically when a meeting produces actions, an RFI closes with a follow-up, or a row is added to the LoE.
When to use it
- Tracking actions out of meetings without re-typing them into a separate tool.
- Following up on RFI responses that need work before the loop is closed.
- Splitting a deliverable from the LoE into trackable pieces of work.
How it works
1. Auto-creation
The most common path: a meeting generates action items, you tick them, they become tasks. RFI closures and LoE rows behave similarly.
2. Manual entry
Add a task by hand from the project board when something comes up between artefacts.
3. Statuses
Open, In progress, Blocked, Done. Configurable per project if you really want to.
4. Filters & views
By assignee, by source artefact, by overdue. Email digests roll up tasks per person daily or weekly.
Tips
- Trust the auto-creation; do not also re-type the same action into a separate tracker.
- Put a due date on everything. Tasks without due dates never close.
- Keep titles short and specific — "Send updated SLD to client" beats "Drawings".