Projects & Job Costing
One Projects table, two different screens to view it from, and a separate rate-calculator tool that feeds it — untangled.
On this page
Two things named "Project"
The word "Project" is overloaded in this platform, and that's the single biggest source of confusion here. Two unrelated things share the name:
- The Projects table. A single set of records — one landscaping job or contract each — used for cost tracking. There is only one
projectstable in the database. It has two screens onto it: Purchasing > Projects (this module — procurement-focused: Materials and Other Costs) and CRM > Scheduling > Projects (client-focused: Milestones, Billing, Analysis). Open a project from either screen and you're looking at the same underlying record — just a different set of tabs layered on top depending on where you came from. - "Project" as a CRM Job type. A CRM Job (a scheduled visit for a client) has a
typeofrecurring,one_time,waiting_list,package,snow, orproject. This is a scheduling classification — it just marks the job as one-off project work rather than recurring service. It is a completely separate field from the Projects table above. A CRM Job of any type — including one whose type happens to be "project" — can optionally be linked to a Project record for cost tracking, via aProject IDfield on the job. The two are independent: a recurring job can link to a Project, and a job typed "project" doesn't have to.
Creating a Project
From either screen, click + New Project. The dialog is the same form either way, since it's writing to the same table.
| Field | Notes |
|---|---|
| Project Name | Free text — e.g. "Smith Residence Backyard Renovation." |
| Customer / Client Name | Free text field (not a dropdown of CRM Clients). A project can separately carry a Client ID for billing — see below. |
| Address / City / State / Zip | Job site location. |
| Status | Sold, Scheduled, In Progress, On Hold, Complete, or Canceled. Cancelling removes the project's milestones that haven't been invoiced yet and offers to cancel its upcoming visits. A canceled project can't approve change orders or invoice milestones. Reopening it (back to Sold) asks whether to bring back the milestones the cancel removed. |
| Start Date / End Date | End Date defaults to "TBD" until set. |
| Contract Price | The editable field here is the ORIGINAL contract price, entered BEFORE tax (converting an estimate seeds it from the estimate subtotal minus discounts; milestone invoices add tax at the estimate/client rate, so a percent milestone is a percent of the pre-tax price). Projects created before this change keep their tax-inclusive price and are billed as before. The Revised Contract Price shown elsewhere (Analysis, Change Orders, Milestone billing) is derived — original plus every approved change order — and is maintained by the database, not editable directly. Changing an existing project's contract price needs the Projects permission (Add/Modify Projects); without it the field is locked and every other field stays editable. |
| Budget Hours | Planned labor hours, compared against Actual Hours for a variance once logged. |
| Notes | Optional free text. |
A project's status runs through a flow — Sold → Scheduled → In Progress → Complete — with On Hold and Canceled as side branches, shown as a step indicator on the Details tab.
Cancelling and reopening. Cancelling a project removes the billing milestones that haven't been invoiced yet, so nothing more can be billed from its schedule; invoiced milestones, invoices and purchase orders are kept. While a project is canceled, its change orders can't be approved and its milestones can't be invoiced — reopen it first. Clicking Reopen on a canceled project puts it back to Sold and, if the cancel removed any milestones, asks whether to bring them back. Choosing yes restores exactly the milestones that cancel removed. If the contract price changed while the project was canceled (for example the original price was edited or a change order was reversed), the difference is spread across the restored milestones in proportion to their amounts, so the schedule covers the contract the same way it did before the cancel. Choosing no reopens the project without them. Only the most recent cancel's milestones can be restored, and reopening this way needs the Projects permission (Add/Modify Projects); without it, Reopen just changes the status.
Users with the Equipt Viewer or Requestor role can see projects but not change them: New Project, Edit, Archive, Delete, the status buttons and the Materials / Other Costs actions are hidden, and the database refuses writes from those roles. Purchasers keep full access so they can track job costs.
Assigning costs to a Project
Projects don't hold costs directly — they roll them up from other records. When adding a line item to a Requisition or a Purchase Order, each line has an optional Project field. Setting it assigns that line's cost to the project.
Materials can also be added straight from the project itself — the Materials tab's Add Material button lets you send items directly onto the project (a "direct" line with no source document), onto an existing Requisition or PO, or into a brand-new Requisition or PO pre-filled with those items and this project already set on every line.
Worked example: Smith Residence Backyard Renovation
A project pulls cost together from however many source documents touch it:
- Create the project: Smith Residence Backyard Renovation, customer "Smith," a Contract Price, and a start date.
- PO #1 — a paver order from the hardscape supplier. Two line items (category
project_material) are each tagged with this project. - PO #2 — mulch and plants from the nursery, placed a week later. Its line items are tagged with the same project.
- PO #3 — a follow-up order for extra edging once the crew realized more was needed. Tagged the same way.
- Open the project and switch to its Materials tab: all line items from all three POs appear in one table, each showing its item, quantity, unit cost, and which PO it came from (a clickable badge that opens that PO). The Subtotal, Sales Tax, an allocated share of each PO's Shipping cost, and a grand Materials Total are computed live underneath.
- As each PO is received, the same numbers keep reflecting committed vs. received spend — there's nothing further to do on the project itself to keep the rollup current.
If a subcontractor also poured a patio slab for this job, that cost has no PO — it goes on the project's Other Costs tab instead, as its own line (vendor, description, cost type, amount), separate from the Materials rollup but included in the project's total cost on the Details tab.
The Materials & Other Costs tabs
The Materials tab merges three kinds of line items into one view: Requisition lines, PO lines, and "direct" lines added straight to the project (no source document). Requisitions that have already been converted into a PO are excluded, so a converted requisition's items don't show up twice.
Rows behave differently depending on where they came from:
- Direct items can be edited or deleted right from the project.
- Requisition / PO items can only be viewed here — editing quantity or cost, or removing the line, has to happen on the source Requisition or PO itself. The row's Source badge opens that document directly.
The Materials Total is built from:
- Subtotal — quantity × unit cost, summed across every line.
- Sales Tax — each line's source document's tax rate, applied only to lines still marked taxable (non-taxable items like pallet deposits or delivery fees are excluded).
- Shipping — a PO's shipping cost is allocated across every project it touches, proportional to that project's share of the PO's subtotal.
The Other Costs tab is a flat, manually-entered list — no product catalog involved — grouped into Materials, Labor, or Other, each optionally tied to a Vendor. Its own subtotal by type feeds into the project's overall cost on the Details tab, alongside the Materials Total.
When you add a cost entry, the Vendor picker lists your shared vendors. If the vendor isn't there, choose Add New Vendor at the bottom of the list — it opens the same new-vendor form used on purchase orders (it needs Equipt write access) and selects the vendor on the entry when you save. Enter a negative amount for a vendor credit (hover the Amount label for the reminder).
The CRM view of a Project
Opening the same project from CRM > Scheduling > Projects shows one dialog with every tab: the Purchasing side (Details, Materials, Other Costs, Tickets, Notes, Files, Comments & Audit Trail) and the billing side (Milestone, Change Orders, Warranties when the project has a client and you can view warranties, Billing, Analysis). Details shows the same status flow, hours, labor rates and contract / cost / net-profit summary as the Photos > Projects panel, and the project's total cost is computed the same way in both places. Same underlying projects row either way.
Milestone is a real, working billing-schedule editor, not a placeholder — it defines what percentage of the Revised Contract Price gets invoiced and when. Invoicing a milestone from here creates a draft invoice on the project and marks the matching milestone on the Estimate the project came from as invoiced, since the project's schedule and the estimate's schedule are the same rows. It requires the project to have a Client ID; without one it shows a message asking you to link a client first instead of the editor.
Converting more than one estimate into a project. The first estimate converted into a project is the one it came from: its price fills the contract (when it isn't set yet), its cost fills the EAC, and its percent milestones are percentages of the contract. Any later estimate converted into the same project is an add-on. It is added as an approved change order — the contract goes up by the add-on's price before tax and the EAC by its cost — and its milestones bill against the add-on estimate's own total, not the project contract. A 50% deposit on a $3,656 add-on bills $1,828 (plus tax), however large the project is. The convert dialog says so when you pick a project that already came from another estimate. If the add-on estimate has no milestones, its change order gets a milestone of its own.
Change Orders is its own tab alongside Milestone, not folded into it. It runs scope changes through a real approve/reject/reverse workflow (statuses: draft, pending approval, approved, rejected). Approving a change order raises the Revised Contract Price by its amount and, based on the billing treatment chosen when it was created — spread across the remaining milestones, given its own new milestone, rolled into the final milestone, or left off the schedule entirely — adjusts only the milestones that haven't been invoiced yet. Anything already billed is left exactly as it was. Reversing an approved change order runs the inverse through the same guarded path, and is refused once a milestone it touched has already gone out on an invoice.
A canceled project can't approve change orders — the Approve button is hidden and the database refuses it — until the project is reopened. A change order can still be reversed while the project is canceled; it comes off the removed milestones too, so restoring them on reopen doesn't bring its amount back. Change orders on a Complete project can still be approved, but you're asked to confirm first, because the work has already been signed off. Approving a change order and invoicing a milestone on the same project at the same moment can't interfere: one waits for the other, so a milestone is never re-priced after it was billed, or billed at a stale amount.
Analysis shows the project's labor and overhead the way the WIP report counts them. Actual Man Hours are the crew hours on the project's completed visits plus any hours entered on the project; Actual Labor Cost is those hours at the project's Loaded Labor Rate (LLR); Overhead to Date applies the overhead share the estimate was priced with. Invoiced is before tax, matching the contract price, and an invoice that was combined into another invoice still counts on this project (it shows on Billing as "Invoice (combined)"). Invoices can only be merged with invoices of the same project, contract and estimate.
Billing and Analysis both depend on the project having a Client ID set — a link to a CRM Client record, separate from the project's free-text customer name field. Without a Client ID, Billing shows nothing at all (by design, so it doesn't show unrelated org-wide activity), and Analysis has no invoices or payments to total. Both are scoped to this project's invoices and payments specifically — not every invoice the linked client has — since billing-by-client used to pull unrelated invoices into a project's numbers.
Notes & Attachments is, today, just a notes textarea saved to the project — no file upload exists under that tab yet. Audit Trail is a static "coming soon" placeholder with nothing wired up behind it.
A Warranties tab also appears next to those when the project has a client. Warranties added before the project is finished wait as "Not started" and begin automatically the day the project is marked Complete. See the Warranties guide.
The Job Costing Dashboard
Separate from Projects entirely, Job Costing is a labor rate calculator — it computes a break-even hourly rate and a bid rate from wage, overtime, payroll burden (FICA, Workers' Comp, SUI, FUI, PFML), overhead, and target profit inputs. It is a season-level pricing tool, not a per-project cost record — it has no concept of an individual job or project.
This is a live, current tool with a direct, working connection into Projects:
- The Rate Calculator tab shows Bid Rate, Break-Even rate, and Billable Hours as you adjust inputs, with a chart breaking the bid rate down into Direct Labor, Payroll Burden, OH Payroll, Other OH, Liabilities, and Profit per hour.
- Clicking "Set as project rates" saves two org-wide rates at once: the Break-Even Rate (
breakevenLaborRateCents) and the Loaded Labor Rate (LLR) (burdenedLaborRateCents). LLR is burdened labor plus the non-billable uplift, with no overhead recovery, and is shown on the Rate Calculator under the Break-Even card. The same two rates can be edited directly in Settings. - Each project stores its own copy of both rates, taken when the project is created. Saving new org rates therefore only affects new projects. After saving you are asked whether to also update open projects (sold, scheduled, in progress or on hold); you can decline. Completed projects are locked — their rates cannot be edited or bulk-updated, and show a lock icon on the Details tab. Reopen a project to change its rates.
- The Scenarios tab holds your saved input sets (e.g. "2026 Budget — Landscape Season"). They are saved to your organization. A new organization starts with no scenarios and a blank calculator; star one scenario to make it the default, and the Rate Calculator loads it each time it opens. Use Save as Scenario to store the current inputs, or Update to save changes back to the scenario you loaded.
- Overtime is a true weighted average. Overtime hours are paid at 1.5× the wage, and the calculator weights each wage by the share of all hours worked at it (overtime hours ÷ total hours). A crew with 400 regular and 100 overtime hours blends to 20% overtime, not 25%. Fixed overhead is still spread over regular hours only, so extra overtime never dilutes it. After this changes a scenario's numbers, open the Rate Calculator and click Set as project rates again to apply the new rates.
- SUI and FUI only apply to each employee's first dollars of wages (for example Massachusetts SUI is the first $15,000 per year, and federal FUI the first $7,000). Enter the SUI wage base and FUI wage base (taxable wages per employee in the scenario's period) and the calculator applies the rate only up to that base, showing the resulting effective rate. Leave them at 0 to apply the rate to all wages.
- Changes to organization settings, including these labor rates, are recorded. Admins and managers can see who changed what, and when, under Settings → Organization → Change history.
Field & tab reference
Every tab available on a Project record, and which screen surfaces it:
| Tab | Surfaced in | What it shows |
|---|---|---|
| Details | Purchasing & CRM | Status flow, budget vs. actual hours, labor rates, and the Contract Price / Cost / Net Profit summary. Material & Other Costs is the same figure as the Projects list total. |
| Materials | Purchasing | Every Requisition, PO, or direct line item assigned to this project, with running Subtotal / Sales Tax / Shipping / Total. |
| Other Costs | Purchasing | Subcontractor costs entered manually — Materials, Labor, or Other — each with an optional linked Vendor. |
| Milestone | CRM | A real, working billing-schedule editor — percentages of the Revised Contract Price (an add-on estimate's milestones are percentages of that estimate's own total), each invoiced independently. The last milestone not yet invoiced takes any rounding cent, so 50% + 50% always adds up to the contract exactly. Invoicing a milestone creates a draft invoice on the project and marks the matching milestone on the source Estimate as invoiced (they're the same schedule). Requires the project to have a Client ID, or it shows a "link to a client first" message instead. |
| Change Orders | CRM | Its own tab, not folded into Milestone. Full create / approve / reject / reverse workflow with statuses draft, pending_approval, approved, and rejected. Approving one raises the Revised Contract Price by the change order's amount and, per its chosen billing treatment (spread across remaining milestones, its own new milestone, added to the final milestone, or left off the schedule), adjusts only the milestones not yet invoiced — anything already billed stays put. Reversing an approved change order undoes exactly that (contract price and schedule both drop back); it's blocked once a milestone it touched has already been invoiced. A change order created by converting an add-on estimate can't be reversed while that estimate's milestones are still on the project. A canceled project's change orders can't be approved until it is reopened; approving one on a Complete project asks you to confirm first. |
| Billing | CRM | Invoices, payments, and credits scoped to this project specifically — not every invoice on the linked client — filtered by type (All / Invoice / Payment / Credit). Requires the project to have a Client ID; without one this tab shows nothing rather than unrelated org-wide billing. |
| Analysis | CRM | Project-scoped Original Contract, Revised Contract, Invoiced (before tax), Payments, Amount Due, and Remaining to Bill, plus Budgeted vs. Actual Man Hours, Budgeted vs. Actual Labor Cost and Overhead to Date — the same figures as the WIP report. Voided and draft invoices are excluded from Invoiced; an invoice combined into another still counts on this project. |
| Notes & Attachments | CRM | Despite the name, just a free-text notes field saved to the project record today — there's no attachment upload here. |
| Audit Trail | CRM | Not built yet — the tab renders a static "Audit trail coming soon" placeholder. |
| Comments & History | Purchasing | Comment thread plus the full audit trail for the project record. |
| Files | Purchasing | Attachments. |
Good to know
- Change orders keep the tax. On a project priced before tax, milestones re-priced or created by an approved change order are invoiced with sales tax added on top, so the client is billed the full taxed amount. Milestones already invoiced keep their amount when a change order is approved, even if that invoice is later voided.
- Milestones carried from a taxed estimate. When the schedule is checked against the contract price, flat milestones carried from a taxed estimate count at their pre-tax share, so a complete schedule doesn't block invoicing.
- Figures stay current. The project window updates as soon as a change order is approved, without closing and reopening it.
- Drafts don't count yet. Project cost leaves out draft purchase orders and requisitions, and Invoiced, Amount Due and Remaining to Bill leave out draft invoices, matching the WIP report. In the WIP report, only POs actually ordered count as cost to date; requested or pending POs and open requisitions show as Committed. A requisition split into POs by vendor is counted once: each line moves to its PO as soon as that PO exists.
- Crew material requests. Materials a crew requests from a project job's stop are tagged to the project, so they count toward its cost.
- WIP cost includes labor and overhead. In the WIP report, Cost to Date is materials & other costs plus labor (crew hours on completed visits and hours entered on the project, at the project's LLR) plus overhead at the estimate's overhead share. % Complete and Earned Revenue follow from it.
- Delete vs. Cancel. A project that has invoices, open purchase orders or invoiced milestones can't be deleted — cancel it instead, which keeps its billing and purchasing history. Cancelling removes the milestones that haven't been invoiced yet and asks whether to cancel the project's upcoming visits (visits already started, completed or invoiced are kept). Reopening a canceled project offers to bring those milestones back. A deleted project can't be restored.
- Crew logins don't see project financials. Crew app logins can't read projects, their costs, change orders or billing milestones. Creating or editing change orders needs the Projects permission (Add/Modify Projects).