---
name: target-value-delivery
description: Support Target Value Delivery / Target Value Design (TVD) - set the allowable and target cost from the owner's business case, split the target across cluster teams (structure, envelope, MEP, interiors, sitework), track estimates against targets at every design iteration, keep an ideas log and show the trend. Use when the user works on an IPD or collaborative project, mentions target cost, "diseño al costo objetivo", "costo meta", "valor objetivo", value engineering done early, cluster teams, or asks why the design estimate keeps going up.
---

# Target Value Delivery

In TVD the target cost is a design criterion, like the program: the team designs to it instead of estimating after design and cutting later.

## Inputs
- The owner's business case: what value the project must deliver and the allowable cost (the most they can spend and still meet it). If it does not exist, help the owner write it; do not set it.
- The target cost agreed by the team (usually below the market estimate) and the cluster breakdown.
- Estimates from each design iteration, by cluster, with date and basis (drawings, model, assumptions).
- The ideas log (proposed changes with estimated impact on cost and value).

## Procedure
1. Write the value definition with the owner: functions, performance, operating cost goals, carbon or energy goals, schedule. These are the conditions of satisfaction every idea is checked against.
2. Split the target by cluster (structure, envelope, MEP, interiors, sitework, general conditions) using the team's numbers; show the sum equals the target.
3. At each estimate cycle, build the target vs estimate table by cluster: target, current estimate, gap, trend vs last cycle. Use the user's estimates only.
4. Keep the ideas log: idea, cluster, owner, estimated cost impact (range), value impact (against the value definition), status (proposed / analysing / accepted / rejected), decision date. Decisions between options go to `choosing-by-advantages`.
5. Show the trend chart data: estimate by cycle vs target line, and the "gap to close" by cluster.
6. Prepare the cluster meeting: where the gap is, the ideas waiting for analysis, and the decisions due before the next cycle.

## Output
- Target vs estimate table by cluster, trend data (CSV), ideas log, meeting agenda.

## Never
- Never set the allowable or target cost; the owner and the team do.
- Never "close the gap" by reducing scope silently; any scope or value change is an idea with an owner and a decision.
- Never mix estimate bases between cycles without saying so (escalation, contingency, scope).