Your comments

Hello! In theory, you might be able to use the service as-is today, by avoiding inputting buildings at all. The trick would be to specify enough "post-session recovery" time to allow enough travel time.


However, if your travel time isn't regular, then you might best be suited to wait for this feature to be implemented.


Regardless of what you decide to do, you're welcome to register for a free account (no credit card required). Doing so will give you access to the caseload editor, and you can see if you think you could make it work for your specific scenario.

This is a great idea, thanks for posting!


FYI, the engine does this today--kinda. Most folks have trouble finding a workable schedule because they input so many "Must Not" constraints. (I think the record I've seen so far is around 500!)


If SLPs change all of their "Must Not" constraints into "Prefer Not" constraints, the engine will gladly return to you a non-optimal schedule. It will still try its best to respect all of the "Prefer Not" constraints, but will move away from them when mathematically necessary to find a workable schedule in the first place.


Just this morning, I updated the caseload editor with additional recommendations along these lines. Also, I've added a few more pages to the Knowledge Base this weekend that will also help expose issues more quickly, all while increasing the likelihood of finding a starting-point schedule.


Thanks again!

FYI, your browser's search feature can do this today.

FYI, your browser's search feature can do this today.