Is the job ahead or behind, under or over?

Earned Value answers two questions about a job, in dollars, on one page:

• Time — is the work ahead of the schedule or behind it?
• Money — for the work that is done, have we spent more or less than we allowed?

Then it uses the answer to the second question to forecast what the job will cost in the end.

You will find it under Construction › Earned Value once a job is selected.

Where the numbers come from

Nothing on this page is typed in. It reads three things you already keep:

Column	Comes from
Budget	The estimate — the same figure as the Cost Centres grid — plus any accepted variations
Should be done	The schedule: how far along each task ought to be by today, on the job’s working days
Actually done	The schedule again: the % complete on each task (a task with an actual finish date counts as 100%)
Spent	Supplier invoices (expenses) — an invoice line counts against the item it names, or the cost code it is coded to

That last one is deliberate. Purchase orders are commitments, not spend; the page only counts money that has actually been invoiced. If you also want your own people’s wages in the picture, tick Include approved timesheets in Spent and the approved hours × cost rate from Timesheets are added, the same way the Cost Centres grid does it.

Reading the tiles

Seven tiles across the top, in the order the story is told:

1. Budget — what the job should cost.
2. Should be done — the slice of the budget the schedule says ought to be finished by today.
3. Actually done — the slice the schedule says is finished.
4. Spent — what has gone out.
5. Money — Actually done minus Spent. Positive (green) means the work done so far cost less than allowed; negative (pink) means more. The small number is “dollars earned per dollar spent” — 1.00 is on budget, 0.90 means every dollar bought 90 cents of work.
6. Time — Actually done minus Should be done. Positive means ahead of the schedule, negative means behind, both in dollars of work rather than days. The small number is “done per planned” — 1.00 is on time.
7. Forecast final — if the rest of the job goes the way the first part has, this is what it will cost. Underneath: how far under or over budget that lands.

If you know the classic terms, they are in the column tooltips: PV, EV, AC, CV, SV, CPI, SPI, EAC and VAC.

The table

Every cost code on the job, in the same tree as Cost Centres, with the same seven figures per row. Parents roll their children up. Click the arrow to open a code; Open all / Close all do the lot; the page remembers what you had open.

By cost code / By item switches the detail. At item level each BOQ item appears under its code with its quantity × rate, its own invoices, and the same progress as its code (the schedule is connected to codes, not items). Two extra rows can appear under a code so the items always add up to it: Invoiced to the cost code (no item named) and, when ticked, Approved timesheet labour.

Find a code or name filters the tree and opens whatever matches.

Drag the edge of a column heading to make a column wider or narrower; double-click the edge to put it back. The widths are remembered on that computer.

The tags

• 2 tasks — progress comes from tasks on the schedule connected to this code. This is what you want.
• job avg — nothing on the schedule is connected to this code, so it follows the whole job’s average progress. It is a fair guess, not a measurement.
• mixed — a parent with some of each underneath.
• not required — the code was switched off in Cost Centres; its budget is zero.

A note above the table tells you how many codes are on the job average. To sharpen them, open a task on the schedule, open its cost and choose Connected to a Cost Center — the task then drives that code. A task can be split across codes with a percentage.

Behind a row

Click a cost code’s name (or an item’s, at item level) and a panel opens beside the table with what is behind it:

• Progress — the tasks on the schedule connected to that code, with their dates, how far along each should be, how far along it is, and its share of the code if it is split. Click a task and the schedule opens on it. A code with no connected task gets a Connect a task on the schedule button instead.
• Spend — every supplier invoice with a line against that code (or that item), the supplier, the date, and how much of the invoice belongs to this row. Click one and the expense opens. The list adds up to the row’s Spent; if timesheet labour is not ticked, the panel says how much there is anyway.

A group row (a code with codes underneath) rolls its children up, so open one of the codes inside it to see tasks and invoices.

Export

Export CSV downloads the whole table at the current level, every row opened out, with the figures as plain numbers and the classic names (PV, EV, AC, CV, CPI, SV, SPI, EAC, VAC) in the column headings, ready for a spreadsheet.

History and the S-curve

Enterprise plan. History is the one part of Earned Value that is not in Builder; the free trial shows it too, so you can see it before deciding. On Builder the History view explains what it adds and shows today’s figures; the daily point is still recorded for every job, so an upgrade has the curve from the first day the page was opened.

Switch the view from Table to History and the page draws the job over time: three lines for Should be done, Actually done and Spent, against the budget as a dashed line. A healthy job has Actually done riding on or above Should be done, and Spent below both.

• Hover a day to read its figures; click to pin it and the row of tiles above the chart becomes As at that day — the job as it looked then. Back to today unpins.
• All / 90 days / 30 days zoom the range. Show as table lists every recorded day.
• One point is recorded per job per day. It is written each night for every live job with a schedule or invoices, and again every time somebody opens this page, so the curve starts the first day the page is opened. Take a snapshot now writes today’s point on the spot.
• A job opened for the first time today has one point and no line yet; come back tomorrow.

What it needs to work

• Cost codes and an estimate. No codes, and the page says so.
• A schedule with dates. Without one, only Budget and Spent are filled in and the page tells you why. Tasks with no date (the engine has not run) stay out of Should be done.
• Invoices coded to the job. Uncoded expenses do not appear in Spent — the Expenses page shows which ones still need coding.

What it does not do yet

• Per-code history. The S-curve and “as at” are for the whole job; the table is always as at today.
• Sorting. Rows stay in cost-code order; use the search to narrow the table.