Construction stage shares refused or the plan splits equally: shares must add up to 100%
Project-wide stages share one 100% and each tower's own stages share their own; a share that pushes its bucket over 100% is refused, while shares that do not reach 100% make the pricing preview split the plan equally and leave revenue progress with nothing to measure.
Messages this explains
- “Project-wide stages cannot exceed 100%.”
- “Stages of <Tower> cannot exceed 100%.”
- “Project-wide stages would add up to <n>%, above 100%”
- “Stages of <Tower> would add up to <n>%, above 100%”
- “percent_of_total: The project-wide stages would add up to <n>%, more than 100%”
- “percent_of_total: This tower's stages would add up to <n>%, more than 100%”
- “The stages carry no "% of total" that adds up to 100, so the preview splits the plan equally across the <n> stages; a real payment plan sets its own percents.”
- “This project has no construction stages yet; add them on the Construction Stages tab.”
- “No construction stages with a share”
- “<n> of <m> stages achieved”
Construction stage shares refused or the plan splits equally: shares must add up to 100%
Saving a stage's Share of total was refused, a stage import failed on the share column, the pricing preview says it is splitting the plan equally, or a revenue run reports "No construction stages with a share".
What you see
- Under the Share of total field of the stage panel, after Add stage or Save changes: "Project-wide stages cannot exceed 100%." or "Stages of <Tower> cannot exceed 100%." The field's hint reads "Of its bucket: project-wide stages total 100% (e.g. Tower A 20%, Amenities 20%); each tower's own stages total 100%". Outside the screens (through the AI assistant, for example) the refusal gives the total: "Project-wide stages would add up to <n>%, above 100%" or "Stages of <Tower> would add up to <n>%, above 100%".
- In the Import dialog's row results: "percent_of_total: The project-wide stages would add up to <n>%, more than 100%" or "percent_of_total: This tower's stages would add up to <n>%, more than 100%". Those rows are marked failed, and nothing from the sheet is imported until every row passes.
- The summary line "Shares (each bucket up to 100%): project-wide X% allocated, Y% completed · <Tower> X% allocated, Y% completed" shows each bucket in red above 100%, green at exactly 100% and amber otherwise.
On Unit Pricing, in Preview on a unit under Payment plan preview with Construction-linked (project stages) chosen: "The stages carry no "% of total" that adds up to 100, so the preview splits the plan equally across the <n> stages; a real payment plan sets its own percents." With no stages at all, both the preview and the Save stage links section show "This project has no construction stages yet; add them on the Construction Stages tab."
On a Revenue run whose policy recognises revenue Over time (stages achieved), each booking line's note reads "<n> of <m> stages achieved" or "No construction stages with a share".
Why it happens
A stage's Share of total says how much of the construction it represents. The shares live in independent buckets: the project-wide stages (those with no tower) share one 100% between them, and each tower's own stages share a separate 100%. The buckets are never added together. Each bucket may add up to at most 100%, so a share that would push its bucket above 100% is refused, counting the shares already saved on the other stages of that bucket. The import applies the same rule to the sheet's rows and the stored rows together.
A bucket is not forced to reach 100%, which is why the other messages exist:
- The pricing preview on the Unit Pricing tab is a quick illustration of how a plan would be collected. It uses every stage of the project, project-wide and tower stages together, and takes their own shares only when every one of them has a share above 0 and they add up to exactly 100. Otherwise it has no percentages to trust, so it divides the plan equally across the stages and says so. A project whose towers have their own stages therefore always gets the equal split in the preview, since each bucket carries its own 100%. A real payment plan, drafted on an estimate, sets its own percentage per stage and is not affected.
- Revenue recognised over time by stages measures progress as the shares of the achieved stages divided by the total shares in the bucket: a tower's own bucket when the tower has stages with a share, else the project-wide bucket (or, when there are no project-wide stages with a share, every stage with a share). "<n> of <m> stages achieved" is that measure; when the bucket's shares add up to zero there is nothing to divide by, the note reads "No construction stages with a share" and the booking recognises nothing for the period.
How to fix it
- For a refused share: lower this stage's share, or lower another stage in the same bucket first, so the bucket stays at or below 100%. Check which bucket the stage is in: the Tower field showing "Whole project" means project-wide; a tower name means that tower's bucket. Saving needs the Edit permission on Construction Stages (in the default roles the Administrator, the Project Manager, the Compliance Officer and the Site Engineer); adding a stage needs the Create permission (the same roles except the Compliance Officer).
- For a failed import row: correct the percent_of_total cell so the bucket's total, sheet and saved rows together, is at most 100, and import the whole sheet again. A blank cell leaves a saved share as it is.
- For the equal-split note: when every stage is project-wide, give each stage a share above 0 so that together they add up to exactly 100; the summary line on Construction Stages shows the current total. When towers have their own stages the preview cannot use the shares, so ignore the note and draft the real plan on the estimate.
- For "No construction stages with a share": on Construction Stages, give the stages a Share of total (in the tower's bucket for a tower with its own stages, else project-wide) and mark the achieved ones Completed, then Recompute the revenue run (the Create permission on Revenue Recognition). If the project should not recognise by stages at all, change the method under Revenue policy or on the project.
Related
Related
- Construction StagesScreen
Plan the project's construction stages (plinth, slabs, possession…) with their shares and dates, record commencement and completion, and keep the certificates and photos for each stage.
- Unit PricingScreen
Keep the project's pricing plans, one per unit type: the sale charges by charge group with GST per line, how each charge group is collected, and a preview of the price and payment schedule on a real unit.
- Revenue runScreen
One period close: what each booking and member offer recognises, the journals and cost moves it posts, the subjects it left out, and the actions to recompute, post, reverse or delete it.
- Revenue policyScreen
The CA's effective-dated choices on how the books recognise sale revenue and the costs that go with it: framework, method, possession trigger, OC rule, cost treatments and judgement areas.
- Construction stages and share bucketsConcept
A project's construction stages (plinth, slabs, possession) each carry a share of a 100% bucket, one bucket for the project-wide stages and one per tower; completing a stage dates the installments waiting on it and moves the revenue progress.
- Unit Pricing: no plan for the unit type, or the stage links refuse to saveTroubleshooting
An estimate loads a pricing plan only when the project has an active plan for the unit's type; otherwise price by hand, giving each manual line an amount and every override a reason; on the Unit Pricing tab the stage links save only once the plan has charges and something changed, and the Unit Base Price group always stays on the payment plan.
- Construction stage cannot be deleted: payment schedules reference itTroubleshooting
A construction stage that installments on a booking's payment schedule are waiting on cannot be deleted; those schedule rows would lose the event that dates them.