Using the allocation engines to commit allocations

Using the allocation engines to commit allocations


The allocation engine provides for a simple approach to allocate children, either individually or in bulk to a service or a programs. The allocation engine recommendations ensure that

  • Capacity Management is in place to ensure that no service / program is over allocated, and
  • The highest priority child is always allocated first. 


Allocating children will update their status and ensure that details related to the allocation are auto updated on the child record. The process of allocation children does NOT result in notification to families, to notify families of allocations you will need to send relevant email templates. 



To use the allocation engine to commit allocations

  • Access Allocation Engine  as described here and remain on the Review / Commit Allocation view. 
  • Apply relevant Parameters to the allocation engine, once selected click "Refresh" 
  • Make any required changes in to a child's "Recommended Allocation" using the dropdown lists displayed (note, these lists include all preferences held for a given child). 
  • Select Child/(ren) to be allocated and click "commit allocations" to allocate the selected children
  • Click "yes" on the pop up window to confirm
  • You will then be returned to a refreshed view of the allocation engine with children who have just been committed reflected as allocated in the Allocation Summary tab (and no longer available for allocation on the Allocation Details tab). 


Please note: Some EnrolNow CRMs may still be utilising v1 of the allocation engine which is accessed from quick action buttons in the children tab. If you are unable to see the Allocation Engine in the main menu bar, please refer to this help article for more details about v1 of the allocation engine which is being progressively updated.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article