Trace and set a cost allocation

Of a cost this project already carries, how much each participant owes, with every rule, basis and adjustment shown rather than a blended percentage.

Some cost codes are shared: an entry road, an amenity centre, anything three builders split between them. This page answers who owes what, and shows the whole derivation rather than a single figure somebody has to trust.

Each code with a rule shows its basis, its denominator and every participant's share. A group participant (a bundle) shows its own share and then, if a second rule divides it further, each member's share underneath, with both rules named. A named adjustment appears beside the share it changed, with the reason on it.

A project can also carry a default rule, which applies to any code that has no rule of its own and no ancestor with one. Those codes are shown, and their panel says the derivation came from the project default rather than from a decision made about that line, so a share is never quoted as though somebody had set it deliberately.

A roll-up code is left out when its children are on the page. The money is on the lines underneath it, and allocating the heading as well as its lines would have every participant owing the same dollar twice.

At the foot, every entity's total across every code, and whether the totals reconcile to what was allocated. When they do not, this page says so instead of hiding the gap. That is a finding about the rules on record, not a page error.

Why it also lives here

The budget tab is already large. This split off onto a page of its own so the derivation could be shown in full rather than summarised down to fit beside the working ledger.

Setting a rule

Rules on record lists every rule: what it governs (one cost code and everything under it, the project default, or a bundle of a wider rule that it subdivides), how it splits, when it took effect, and who takes what share. Add a rule opens the form. A fixed percentage rule reads each ticked participant's share as a percentage and the shares must sum to 100; the form refuses a set that does not foot and says what it came to. A direct assignment reads each share as dollars. Every other basis, lot count, unit count, acreage and frontage, computes the split from the lots and takes no stated share. Saving re-derives every panel above from the rules on record; nothing is cached.

Edit on a rule rewrites who takes a share and how much, its effective date and its note. The basis and the scope are fixed once a rule exists: to split another way, remove the rule and add one with the basis you mean. Remove refuses a rule that carries a nested rule or a named adjustment, because both would go with it.

Writing a rule needs money and schedule access at edit, both: a rule decides where dollars land, and the rule row itself is schedule-class. Participants lists who can hold a share. Add a participant puts an entity from the party register on the roster under the label the rules will use; it needs schedule access at edit.

Once a draw has gone out

A rule whose scope reaches a cost code on a submitted or funded draw is fixed, and the register says which draw. The draw asked the lender for dollars under the split in force that day, and a rule rewritten afterwards would restate what the lender was told. Editing or removing such a rule is refused, not versioned: the way forward is a change order or a reallocation. A draft draw has not gone out and does not fix anything.