Weights & rollups: how the percent is calculated

Every number above a task in Fieldcurve is computed. That single rule is what makes the tracker trustworthy: nobody can hand-tune a milestone the night before a review, because milestones don’t take input at all.

The formula

parent % = Σ(child.weight × child.%) / Σ(child.weight)

Applied bottom-up: tasks → activities → milestones → phases → project, recomputed in the same transaction as the edit that caused it. There is no refresh step and no overnight batch; the project header is current the moment a task saves.

Weights

A weight is a relative share among siblings, default 1. Weights only matter within a parent: three tasks weighted 2/1/1 split an activity 50/25/25. The worksheet shows the resulting share next to each weight, and the rebalancer preview shows every sibling’s share as you adjust — so a weight change is never a surprise.

Every computed number shows its work

Click the ∑ on any computed percent for its contribution breakdown: each child’s weight, share, percent, and what it adds to the parent. This is the answer to the steering-committee question — “why is mechanical completion only at 46.7?” — as a table instead of an argument.

Calibrating a task percent

Task percent is free-form 0–100 — but calibration is a judgment call, so the editor helps: type it directly, nudge in steps of five, or use the slider against a live projection of what the rollup will become. Status is independent of percent: a task can be blocked at 40%, and blocked-ness is first-class on the dashboard rather than hidden inside a percent.

What history remembers

Every percent, status, weight, and structural change lands in the audit trail — who, what, before, after, when. When a number moves unexpectedly, the answer is a lookup, not a hallway investigation.