Create and manage a project
The project is the container everything else attaches to. One project per thing you would want a profit figure for — not one per client, and not one per phase unless you would bill the phases separately.
/
Projects
Projects is delivery work that has a budget and a record of the time spent against it. Tasks, logged time, budget and change requests all hang off the project, which is what lets you answer whether a job made money.
Try it in the demoproject · 5 tasks
Before you start
- A decision on who approves time. Unapproved time is not cost, and a project without cost is not a budget.
- The customer or account the project is for, so the work can be traced back to the sale.
What Projects does
Delivery work with a budget and a record of time spent.
Create and assign tasks within it
Tasks inside a project are the same tasks the Tasks module holds, so a person’s list is one list rather than one per project.
Log and approve time
Logging is the person’s record; approval is what makes it count. Approve weekly — a month of unapproved time is a month of unknown cost.
Manage the budget
The budget is per project and is what the logged, approved time is read against. A budget nobody set reads as unlimited.
Approve change requests
A change request is the record that the job grew and somebody agreed to it. It is the difference between an overrun and a variation.
What it claims to do
The capability list this guide is written against, unabridged. Nothing above adds to it.
Projects on the Services page- Projects created and managed
- Tasks created and assigned within them
- Time logged and approved
- Budgets managed per project
- Change requests approved
Where it connects
The modules Projects hands work to, or takes it from. Most problems that look like one module are a handover between two.