Allocating Stock to Projects
An allocation is the link that puts a stock to work: it assigns a registered piece of land to a project so the project can be developed and carved into units. Because allocation moves real inventory into development, it isn't a one-click action — it goes through a small review workflow (submit → approve / reject) before it counts.
Before you allocate
- The stock must be in Registered (or Partially Sold) status. You can't allocate something you don't yet own.
- The project you're allocating to must already exist.
- You need the allocate stock to project permission.
The allocation workflow
An allocation is a record with its own status, separate from the stock's status. It moves through these stages:
| Stage | Meaning |
|---|---|
| Draft | The allocation has been created but not yet sent for review. You can still edit it. |
| Submitted | Sent for approval. Awaiting a decision. |
| Approved | A reviewer accepted it. The stock's availability is now updated. |
| Rejected | A reviewer turned it down. You can revise it back to Draft and resubmit, or cancel it. |
| Posted | Finalized. Terminal — no further changes. |
| Cancelled | Withdrawn. Terminal. |
Only an approval updates the stock's availability. A rejection leaves the stock unchanged — nothing is consumed until someone says yes.
Step 1 — Create the allocation
- Open the stock and go to its Allocations section.
- Click Add Allocation.
- Fill in:
- Project — the destination project (required).
- Allocation date (required).
- Allocated area, and optionally length and width dimensions.
- Allocation type — Full or Partial.
- Reason and any custom fields.
- Save. The allocation is created in Draft with an auto-generated allocation number (
STK-001-ALLOC-001,STK-001-ALLOC-002, …).
While in Draft (or Rejected), you can edit the allocation's date, area, dimensions, type, and reason.
Step 2 — Submit for approval
When the draft is ready, submit it. Its status moves to Submitted and it waits for a reviewer. A remark is required when submitting.
Step 3 — Approve or reject
A user with approval rights reviews the submitted allocation and either:
- Approves it — the allocation becomes Approved and the stock's available area is updated. A remark is required.
- Rejects it — the allocation becomes Rejected and the stock is untouched. A remark explaining why is required.
A rejected allocation can be sent back to Draft, corrected, and resubmitted — or cancelled outright.
Step 4 — Post (finalize)
An approved allocation can be Posted to finalize it. Posted is a terminal state.
Cancelling an allocation
You can cancel an allocation from most stages (Draft, Submitted, Approved, Rejected) — but not once it's Posted or already Cancelled. A remark is required. Cancelling is terminal for that allocation record.
How allocation affects the stock
- Creating a full allocation against a Registered stock sets it up to move to Allocated (you confirm the stock-level status when ready — see the stock lifecycle).
- Removing the last allocation from an Allocated stock reverts the stock to Registered.
This two-way link keeps the stock's status truthful: a stock is only Allocated while it actually has a live allocation.
Removing an allocation
Deleting an allocation is a soft delete — it's hidden from future views but kept for audit. If it was the only allocation on an Allocated stock, the stock automatically reverts to Registered.
Allocation and deletion guardrails
A stock that has project allocations can't be deleted. The system blocks it and tells you how many allocations (and units) reference it, suggesting you change the status to Cancelled instead. For the full set of rules on what blocks a delete, see Delete guardrails.