Provisional Sums in Deep Space

1The 60-second brief

A provisional sum is money the head contract sets aside for work that cannot be priced when the contract is signed. Deep Space keeps that money in two layers, and almost every question a customer asks comes down to which layer they are looking at.

The lifecycle in one line

Allowance is created (from the estimate or by hand) → the allowance is approved onto the head contract, which puts a line on the Schedule of Values → the team records drawdowns as the work is instructed → each drawdown is approved, directly or through an internal approval route → when approved drawdowns exceed the allowance, Deep Space raises a head contract variation for the over-run → when the work is finished the allowance is closed, and any saving goes back to the client as a credit variation.

Status words

A tour of the register

Commercial → Head Contract (Client) → Provisional Sum Register (it carries a BETA tag in the menu) opens the register. The subtitle says what it is: the drawdown register — spend recorded against the allowances attached to each head contract. Four cards across the top total the project: Total Allowances, Drawn, Remaining and the number of Drafts still to be dealt with. Two tabs switch the table between the two layers.

Click an allowance ID on either tab and its drawer opens on the right. Everything about one provisional sum is in that drawer, top to bottom:

1. Header — ID, title and status, then Allowance / Drawn / Remaining and the blended margin of the allowance's lines. Close Allowance sits here and is only available once every drawdown is settled.
2. Drawdowns — one card per drawdown with Add Drawdown above them. Each card shows the drawdown's lines (cost code, quantity and rate, cost, sell, margin) and its totals; a card in an approval route carries the amber approval panel.
3. Adjustment Summary — the six lines from the original allowance to the net adjustment to the contract sum, under the contract's margin basis.
4. Allowance Breakdown — the allowance's own lines as priced into the contract.

2One-time setup

Four things are decided before the first drawdown. Two of them (the margin basis and the contract's margin rate) are the settings that make one customer's provisional sums behave differently from another's, so get them right on day one: the basis locks on the contract at the first drawdown approval.

2.1 Choose the house default for the margin basis

The margin basis says where the builder's margin is applied when a provisional sum is adjusted. Both bases use the contract's provisional sum margin rate; they differ in what the rate is applied to.

A worked example with the same allowance under both bases is in section 9. A margin rate of 0 is legitimate: it models contracts that pay the actual cost with no margin.

1. Deep SpaceSet the house default
   Admin → Company Settings → Commercial tab → the Provisional Sums card → Provisional Sum margin basis (house default). Pick On actual cost or On variance and save. Every head contract that does not choose its own basis follows this. The card also states the instrument rule in one line: every drawdown that moves the contract sum raises a Head Contract Variation.

2.2 Make sure the cost codes exist

Every allowance line carries one cost code, and drawdown lines inherit it. The code is what the Budget Register keys on, so it must exist before the allowance is approved onto the contract.

1. Deep SpaceCheck the workspace cost codes
   Admin → Finance → Financial Model → Cost Codes tab. Confirm the trades the customer expects to run provisional sums against are present and not archived. The allowance form offers these codes in a picker (section 4 shows it); free text is not accepted.

2.3 Set the basis and the margin rate on the head contract

The contract carries the contractual provisional sum margin percentage (the Annexure figure) and may override the house default basis. Both fields sit in the head contract form.

1. Deep SpaceOpen the contract form
   Commercial → Head Contract (Client) → Head Contract Register → New Contract, or the pencil icon on an existing contract to open Edit Head Contract. Both fields sit in Contract Basics.
2. Deep SpaceProvisional Sum Margin Basis
   Leave Workspace default (…) to follow the house default, or pick On actual cost / On variance for this contract only. Once the contract has an approved drawdown the select is disabled and reads Locked — a drawdown has been approved on this contract.
3. Deep SpaceProvisional Sum Rate (% on cost)
   Enter the contractual percentage for profit and attendance. The label says it: the rate is applied on cost, so 20 means sell = cost × 1.20 (a 16.7% margin on sell). On actual cost it prefills every new allowance and drawdown line; on variance it grosses up the over-allowance difference. The estimator can still change a line's rate before approval.

2.4 Optional: route drawdown approvals through Delegation of Authority

By default anyone with access to the register approves a drawdown with one click. Customers who want authority limits switch the internal approval route on by configuring a workflow; nothing else needs turning on.

1. Deep SpaceCreate the workflow
   Admin → Finance → Delegation of Authority → Approval Workflows tab → Add Workflow with Entity Type PS Drawdown (the entity type cannot be changed after creation). Each step is either a Fixed role or DoA-driven, where the engine routes by the drawdown's sell amount through the Approval Thresholds matrix; the threshold simulator on the right previews which steps a given amount activates. Only one PS Drawdown workflow can be Active per scope.
2. Happens automaticallyThe gate is now on
   From the moment the workflow is active, Approve on a drawdown answers Internal approval required and offers Submit for approval instead. Workspaces without a PS Drawdown workflow keep one-click approval. Section 6 walks the route.

3Where allowances come from

An allowance reaches the register by one of two roads. Most arrive from the estimate: a BOQ line typed as a provisional sum becomes a Draft allowance the moment the budget is pushed. The rest are typed in by hand, either in the register or on the head contract. Both roads end in the same place: an Unapproved allowance that still needs a head contract and an approval (section 4).

3.1 From the estimate

1. Deep SpaceType the BOQ line
   In Estimation, when adding or editing a BOQ item, set Item Type to PS, PC or Contingency (the default is Lump Sum). The line then carries an amber type chip in the BOQ, and the estimate's Allowances card counts it: "{n} PS / PC / Contingency items".
2. Happens automaticallyZero margin by default
   Typed lines price at cost with no margin, because the contract normally states profit and attendance on provisional sums separately. Bulk pricing skips them ("20 items updated · skipped 4 PS / PC / Contingency") unless the estimator ticks "Also price the … PS / PC / Contingency lines in this selection"; pricing one by hand is recorded as an Override.
3. Deep SpacePush the budget
   Estimation → Push to Budget Register, or Commercial → Budget Register → Generate Budget Register. The success toast ends with the seeding result: "PS sync: 3 created, 0 updated, 1 skipped, 0 orphaned."
4. Happens automaticallyOne Draft allowance per typed line
   Each typed BOQ line becomes its own allowance: title = the BOQ item name, type = the item type, one line carrying the BOQ quantity, unit, cost rate and sell, and the BOQ line's cost code if it had one. The description reads "Seeded from Estimation Budget push." No head contract is set, so the register shows the allowance as Unassigned and the head contract's Provisional Sums tab lists it under Unassigned Draft Provisional Sums.
5. Happens automaticallyKept out of the budget until approved
   Typed lines are excluded from the Original Budget. The Budget Register shows an amber banner, "Draft Provisional Sums not in budget: $… · n drafts · n unassigned", and a Draft Provisional Sums table on the cost code's Variations tab. Their money enters the budget only through approved drawdowns (section 8).

3.2 By hand

1. Deep SpaceOpen the form
   Provisional Sum Register → New Allowance, or open the head contract → Provisional Sums tab → Add Provisional Sum (this one pre-selects the contract). Either way the form creates a Draft; the header says so: "Creates a Draft. Approve it from the drawer or the head contract's Provisional Sums tab to add it to the contract sum."
2. Deep SpaceTitle, Type, Head contract
   Title is the only required field. Type offers Provisional Sum, Prime Cost, Contingency or Other. Head contract can be left on Assign later, but until a contract is chosen the form warns "No head contract yet — lines stay unpriced until one is chosen"; once chosen it shows the contract's terms, e.g. "Rate 20 % on cost · margin on actual cost", and new lines prefill that rate.
3. Deep SpaceDescription (optional)
   + Add a description opens a note for the team. It is not printed on the SOV, the claim or the PDF; the line description is what the client sees.
4. Deep SpaceLines
   Each line card has a cost code button (Select cost code opens the picker; free text is not accepted), a description ("the line's name on the contract SOV, claims and the claim PDF"; with a single line it defaults to the title), and the money row Qty · Cost rate · Cost · Markup % · Margin % · Sell rate · Sell. Type any two of cost, markup or margin and the rest follows. + Add line starts the next line on the same cost code: "One cost code per allowance by default."
5. Deep SpaceCreate Draft
   The footer totals show Cost, Sell and Margin ("0 % · passthrough" for a cost-only allowance). Create Draft → toast "Draft provisional sum created". The allowance appears as Unapproved and can be edited freely until it is approved.

4Approving an allowance onto the contract

Approving an allowance answers one question: is this money part of the contract? It is a single action on the whole allowance, it needs no approval route, and it does not spend anything. Spending is what drawdowns are for (section 5).

1. Deep SpaceCheck the three prerequisites
   A head contract is assigned, there is at least one line, and every line has a cost code from the picker. Without a contract the button is disabled ("Assign a head contract first"); without a code Deep Space refuses with "Allowance line 2 needs a cost code from the project's cost structure before it can be approved".
2. Deep SpaceApprove Allowance
   Open the allowance's drawer (register) or find it on the contract's Provisional Sums tab and click Approve Allowance. There is no confirmation dialog; the toast reads "Allowance approved — it now counts toward the contract sum" and the chip turns Approved.
3. Happens automaticallyLines land on the Schedule of Values
   Each allowance line becomes a row on the head contract's Schedule of Values at its sell value, tagged as a provisional sum. In the SOV preview the row carries an amber PS badge; it turns green PS · ACTIVE once the first drawdown against it is approved. The allowance is now in the contract sum, but the row cannot be claimed until a drawdown activates it: the claim forms show it as Pending approval with a claim value of zero.
4. Happens automaticallyThe drawer becomes read-only
   The Edit Allowance panel disappears; the drawer now shows Drawdowns with Add Drawdown, the Adjustment Summary and the Allowance Breakdown. Lines and pricing are fixed on the contract from here on.

Declining instead

Decline Allowance on an Unapproved allowance marks it and its lines Declined (toast "Allowance declined"). A declined allowance stays in the register for the record and cannot be revived; if the money is needed after all, create a new allowance. An approved allowance is not declined but closed (section 7), and only once every drawdown on it is settled.

The margin basis override

While an allowance is Unapproved, Edit Allowance → Advanced — margin basis override lets it depart from the contract's basis: Contract default, Override: on actual cost or Override: on variance, with a reason that Deep Space insists on. The drawer then shows a chip such as "Margin basis override: on variance — {reason}". Use it for the odd clause that treats one allowance differently; the setting cannot be changed once the allowance has produced an adjustment.

5Recording and approving drawdowns

A drawdown is the priced request to spend part of an approved allowance. It is born as a Draft, can be edited until it is approved, and only its approval moves money: into Drawn, into the Budget Register and onto the claim. Everything in this section happens in the Provisional Sum Register.

5.1 Record a drawdown

1. Deep SpaceOpen the form
   Register → New Drawdown opens New Drawdown — pick an allowance: every approved allowance with its head contract and "{remaining} remaining of {allowance}". Or open the allowance's drawer and click Add Drawdown. The form's header restates the target: "Against PS-Asher1-0019 · COM-805 Test 2 — remaining $216.00 of $300.00 · CON-Asher1-0010 · rate 20 % on cost".
2. Deep SpaceTitle and lines
   Title is required ("What this drawdown pays for"); the description is optional and shows only on the drawdown card. Each line has the same money row as an allowance line: Qty · Cost rate · Cost · Markup % · Margin % · Sell rate · Sell, plus a checkbox "Additional procurement cost — freight, craneage, storage; feeds summary lines 4 / 5" for costs that are not the work itself.
3. Happens automaticallyCost code and rate are inherited
   The line carries the allowance's cost code without asking: "Cost code: inherited from the allowance (CC-7142 - Asher Test Cost Code 001)." A link, "Code this drawdown to a different cost code", exposes the picker for the exception. Under On actual cost the line prefills the contract's rate; under On variance it prefills as cost passthrough (sell = cost), because that basis adds margin only on the over-allowance difference.
4. Deep SpaceRead the totals, then Create Drawdown
   The footer shows Cost, Sell, Margin and Remaining after — what the allowance will have left once this drawdown is approved. If the sell exceeds what is left, it turns into "Over the remaining allowance by $…" with the warning "A Head Contract Variation will be raised for the over-run when this drawdown is approved." Create Drawdown → toast "Drawdown created"; the drawdown is Draft, numbered DD-01, DD-02 … within its allowance.

5.2 While it is a Draft

The drawdown card offers Edit (opens Edit Drawdown #n, Save Changes) and Delete (no confirmation; toast "Drawdown deleted"). Both exist only while the drawdown is a Draft: once it is Pending it sits with the approver, and once Approved it is part of the record.

5.3 Approve or decline

1. Deep SpaceApprove
   On the drawdown card, or in the Drawdowns tab's Actions column, click Approve. No confirmation; toast "Drawdown approved". On a workspace with a PS Drawdown approval workflow, this click answers Internal approval required instead — section 6.
2. Happens automaticallyWhat one approval does
   The drawdown's sell joins Drawn and Remaining falls. Its lines reach the Budget Register on their cost code as approved provisional sum cost. The allowance's SOV row turns PS · ACTIVE and becomes claimable up to what has been drawn. The contract's margin basis locks if this was its first approved drawdown. And if cumulative approved spend now exceeds the allowance, the over-run variation is raised (section 7).
3. Deep SpaceDecline
   Decline marks a Draft or Pending drawdown Declined (toast "Drawdown declined"). It stays on the ledger for the record. An approved drawdown cannot be declined: "Approved drawdowns cannot be declined; the revoke flow is not available yet", and one whose over-run is already carried by a variation points you to that variation instead: "dispute that variation instead; it reverts the drawdown automatically."

6Internal approval through Delegation of Authority

On a workspace with an active PS Drawdown workflow (section 2.4), a drawdown is not approved by whoever clicks first. It is submitted, routed to the approver the workflow names for its amount, and the final approver's sign-off is the approval: nobody comes back to click Approve a second time.

1. Deep SpaceSubmit for approval
   Click Approve on the drawdown as usual. Deep Space answers with Internal approval required: "This workspace routes PS drawdown approvals through the Delegation of Authority workflow. Submit this drawdown for internal approval? The final approver's sign-off will approve the drawdown." Confirm with Submit for approval → toast "Drawdown submitted for internal approval".
2. Happens automaticallyThe route opens
   The drawdown becomes Pending with an amber In approval chip; Approve, Decline, Edit and Delete disappear. The amount routed is the drawdown's sell total. A DoA-driven step picks its approver from the Approval Thresholds ladder; a fixed-role step goes to that role. Approvers are notified.
3. Deep SpaceThe approver acts from the register…
   The card and the Drawdowns tab show the approver "Awaiting your approval — approving here approves the drawdown" and a green Review & approve. It opens the Approval Route: the steps, who is on each, a Comment (optional) box, and Approve / Reject.
4. Deep Space…or from My Approvals
   The My Approvals icon in the top bar (its badge counts the requests waiting on you) opens the approvals inbox as a side panel; the same inbox is a page at /auth/horizon/my-approvals. The request is listed as "PS Drawdown DD-01" with the project and date, and the notification email's link opens the allowance's drawer in the register with the card in view.
5. Happens automaticallyApproved: the drawdown approval runs
   When the last step is approved, Deep Space executes the drawdown approval itself, with every effect from section 5.3: Drawn, budget, SOV activation, basis lock, over-run variation. The register refreshes to Approved. The approver's name is recorded as the one who approved the drawdown.
6. Happens automaticallyRejected: back to Draft
   A rejection returns the drawdown to Draft with a red Approval rejected chip. Edit it and click Approve again to submit a fresh request; the earlier one stays in the approval history.

Everyone else sees the card read-only: "Awaiting internal approval — the final approver's sign-off approves this drawdown", a View approval route button and the route's progress line, e.g. "Step 1 of 1 · Test · Asher DoA Test Project Manager" (figure under section 1). While the request is open, Decline is refused with "This drawdown has an internal approval in progress — revoke or resolve it in the approvals centre before declining."

7Over-runs and close-out

A provisional sum changes the contract sum in exactly two moments, and Deep Space records both with the instrument the client already knows: a Head Contract Variation. Spending inside the allowance raises nothing. The moment approved spend crosses the allowance, an over-run variation is raised; when the allowance is finally closed under, a credit variation hands the difference back. Neither is typed by anyone: the drawdown approval and the close-out create them.

7.1 The over-run variation

1. Happens automaticallyRaised at the approval that crosses the line
   When a drawdown approval takes the allowance's net adjustment above zero, Deep Space raises a variation on the head contract for that net figure — not for the whole drawdown. It is born Submitted (the drawdown approval is the submission) and titled "PSO · PS-Asher1-0018 · DD-04 — Test COM-805", with the description ending "provisional sum over-run — net over-allowance drawdown (AS4000 cl.3 / NZS3910 cl.12 treatment)".
2. Happens automaticallyLater drawdowns revise it, or add to it
   While that variation is still unapproved, the next over-run drawdown revises it to the new cumulative figure. Once the client has approved it, the next drawdown raises a delta variation for the increment only. Either way the sum of the variations equals the allowance's net adjustment — the drawer's footer says so: "Carrying the full +$120.00 net adjustment to the contract sum".
3. Client-facingThe client approves the variation
   From here the variation lives its ordinary life in Commercial → Head Contract (Client) → Variations (Client-Side): it is issued, and the client approves or disputes it. Only Approved moves the contract sum. The variation document carries a Provisional Sum Adjustment section with the six-line build-up (or a folded version on sell-only templates).

Where the link shows

• Allowance drawer — a Variations raised by this allowance block: one row per variation with the HVO link, its status pill (Submitted / Approved / Disputed), the signed value and the drawdown that raised it (DD-04). The drawdown card itself reads Raised HVO-Asher1-0022.
• Head contract → Provisional Sums tab — the Variations column: HVO-Asher1-0022 · +$120.00, or 3 variations · +$….
• Variations register — PS-born rows carry an emerald PSO (over-run) or PSC (close-out credit) pill with From PS-Asher1-0018 · DD-04 under the HVO number. The Source filter separates From provisional sums (PSO / PSC) from Client-raised only, and the search matches the PSO reference.
• Variation sidebar — Raised from allowance with a link back to the allowance and the drawdown number, and the same Adjustment Summary card underneath.

7.2 If the client disputes

Disputing a PS-born variation does more than mark it: Deep Space reverts the drawdown that raised it from Approved back to Pending, recomputes Drawn and Remaining, and the variation stops carrying any adjustment. The drawer says "Reverted to Pending — its variation was disputed" on the card, and the variations block strikes the value through with the note "Disputed — its drawdown was reverted to Pending". Because of this link, two things are refused: declining an approved drawdown whose over-run is already carried ("dispute that variation instead; it reverts the drawdown automatically"), and reverting a PS-born variation to Draft ("This variation was generated by a provisional sum drawdown and cannot be reverted to Draft. Dispute it instead.").

7.3 Closing the allowance

1. Deep SpaceSettle every drawdown first
   Close Allowance (drawer header, or Close on the contract's Provisional Sums tab) stays disabled with "Resolve {n} outstanding drawdowns first" until no drawdown is Draft or Pending.
2. Deep SpaceConfirm
   The dialog Close allowance: "Close this allowance? No further drawdowns can be recorded, and if it closed under, the difference is credited back to the contract sum." Confirm → toast "Provisional sum closed"; the chip reads Closed and Add Drawdown disappears.
3. Happens automaticallyThree possible outcomes
   Closed under (net adjustment negative): a credit variation is raised for the difference, titled "PSC · PS-Asher1-0017 — Allowance D" with a negative value, and shown in the register as Close-out credit · PS-Asher1-0017. Exactly on (net zero): nothing is raised. Already over: the over-run variation already carries the adjustment, so closing only fixes the status.

8Budget Register and progress claims

Provisional sum money reaches the rest of the Commercial module through two doors: approved drawdown lines feed the Budget Register on their cost code, and activated allowance rows on the Schedule of Values feed the progress claim up to what has been drawn. The over-run itself travels as a variation and is claimed like one.

8.1 Budget Register

Expand a cost code and open its Variations tab for the detail: a Provisional Sums (n) card lists the allowances contributing to the two columns with their Approved Cost and Pending Cost, and an amber Draft Provisional Sums (n) card lists Unapproved allowances that are visible for tracking but "excluded from Revised and Projected Budget totals until attached". The over-run variation does not add its cost a second time under head contract variations: the drawdown lines are the cost's only home.

8.2 Progress claims

1. Deep SpaceSection C in a new claim
   Commercial → Head Contract (Client) → Progress Claims (to client) → New Claim. After the SOV and the variations, Section C · Provisional Sums lists the allowance rows with a Provisional Sum chip and the count "{n} active, {n} pending".
2. Happens automaticallyClaimable only up to what is drawn
   An allowance row can be claimed up to the lesser of the allowance and the approved drawdowns against it — Drawn is the cap. A row with no approved drawdown yet shows the chip Pending approval, a disabled tick and the claim cell "Zero until approved". Anything above the allowance is claimed through the approved over-run variation in the Variations section, not here — and only once the client has approved that variation; while it is Submitted the Variations section lists it as Pending (needs approval).
3. Deep SpaceEdit, detail, PDF
   The edit form has the same Provisional Sums section ("{x} of {n} claimed · GST excl.") and a Provisional Sums subtotal; the claim detail shows Provisional Sums ({n} items) · Allowances & adjustments · GST excl.; the claim PDF prints a Provisional Sums section with Cost Code · Description · Allowance · Previous · This Period · Total · Status and rolls it into summary row C · Provisional Sums. The grand total caption reads Contract SOV + Approved Variations + Provisional Sums.

Forecasting and the Financial Summary have no provisional-sum view of their own; they read the budget columns and the claims above.

9The money math

Every figure in the Adjustment Summary, every over-run variation and every close-out credit comes from one formula. Knowing it lets you predict what Deep Space will raise before the customer asks.

Actual cost is the cost of the approved drawdowns. Allowance is the allowance's sell value as priced into the contract. Rate is the contract's Provisional Sum Rate (% on cost), or the allowance's override. A positive result is an over-run and raises a variation the moment it turns positive; a negative result is a saving and is credited only at close-out; zero raises nothing. A rate of 0 models contracts that pay the actual cost with no margin.

One allowance, both bases

The allowance is PS-Asher1-0022's: $1,000 cost priced at 20% on cost, so $1,200 on the contract. The rows are four different totals of approved drawdown cost.

Read the two "exactly on" rows: under On actual cost the allowance is spent when its cost is spent ($1,000), because the margin is added on top of every dollar of cost. Under On variance the allowance is spent when its sell is spent ($1,200), because the contract sum already carries the margin and only the difference is marked up. That is also why drawdown lines prefill with the contract's rate under one basis and as cost passthrough (sell = cost) under the other (section 5). The $1,500 row is the over-run you captured in section 5: the form warned Over the remaining allowance by $600.00 for exactly this reason.

Reading the six lines

The footer Effective margin 20.0% vs contractual 20.0% compares the margin the drawdowns actually carry with the contract's rate; it turns red when the drawdowns were priced below the rate, which is the same signal the Margin check dialog gives at save time.

10Dialogs & guardrails

Every message a customer may quote back to you, what triggered it and what to do. Server messages reach the screen word for word.

11Known limits and what is next

Not in this release

• No client-facing document per drawdown. A drawdown is an internal record; the client sees the over-run or credit variation only. The Provisional Sum Order document and client approval of drawdowns are scoped as COM-1048.
• No evidence links on an approval (client instruction, superintendent's or architect's instruction, RFI). The drawdown carries a client instruction id field but no UI for it — COM-803.
• The variation document does not yet quote the allowance, the drawdown and the remaining balance beyond the six-line build-up — COM-1050.
• No "contract value net of allowances" reporting view. The allowance is part of the contract sum everywhere; a revenue view that strips it out is not built.
• No undo of an approved drawdown other than disputing its variation. A wrongly approved within-allowance drawdown needs a correcting entry or support.

Known issues being worked

• Multi-line allowances can be over-claimed. The drawn cap is stored per SOV row, so an allowance with two lines offers its drawn amount on each row (PS-Asher1-0019: $84 drawn, two rows each claimable to $84). Single-line allowances are unaffected — COM-1109. Until fixed, check the Provisional Sums subtotal of a claim against the register's Drawn.
• Budget Register cost-code drill-down lists allowance lines by allowance status and ignores the View As lens, so it does not reconcile to the Approved / Pending PS Cost columns; the Draft table shows a raw contract id — COM-1106.
• Wording: the create modal says New Provisional Sum while the button says New Allowance; "attached" survives in the Budget Register and in server messages; the SOV badge abbreviates to PS — COM-1107.
• Guardrails: no confirm on Delete drawdown or on disputing a PS-born variation; nothing editable after an allowance is approved though title and description could be — COM-1108.
• Legacy records: allowances created before the drawdown ledger (August 2026) may show a green Approved chip where newer ones show amber, or a Scope Lines block with per-line Approve / Decline instead of Allowance Breakdown. Do not use the per-line buttons; add a drawdown to move the allowance onto the ledger, or leave it. Older PS-born variations keep their original description format — COM-1088.
• Re-pushing the budget after typing a line as PS can double the head contract SOV — COM-1001, under investigation. If a customer reports duplicated SOV rows after a push, stop and escalate.
• PO cost code picker shows $0.00 for a code whose budget is entirely provisional sums — COM-813.
• Orphaned Draft allowances (BOQ line untyped or removed after seeding) are reported but not removed, and cannot be deleted from the register — COM-844.

Recognising a legacy allowance

Its drawer shows Scope Lines rather than Allowance Breakdown, the Drawdowns section may read "This allowance predates the drawdown ledger — approve or decline its scope lines below, or add a drawdown to switch it to the ledger", and Drawn is the sell of its approved lines. In customer workspaces these are test records; in doubt, ask before touching them.

Appendix · Figure index

Every figure in the guide and where it was captured, in reading order. All captures are from the Asher1 demo project, September 2026.