/product-fieldpulse/b/product-news/posts/why-we-rebuilt-the-scheduling-engine-from-scratchToday, we are sharing a look behind the curtain at one of the most significant engineering efforts in FieldPulse history: a complete rebuild of our scheduling engine from the ground up. This project has been eighteen months in the making, and it is nen-US14.0.0.622 14https://verint14-pre-04.socialedgeconsulting.io/product-fieldpulse/b/product-news/posts/why-we-rebuilt-the-scheduling-engine-from-scratchSun, 05 Apr 2026 16:45:00 GMT9b51ca3f-ea30-4ce0-acc7-41a30a3e64f6Keiko Tanaka1<p>Appreciate the transparency on the eighteen-month timeline. From an operational planning perspective, can you share whether the automated scheduling suggestions you mention will require opt-in configuration, or will they be surfaced automatically to dispatchers?</p><img src="https://verint14-pre-04.socialedgeconsulting.io/aggbug?PostID=76^AppID=21^AppType=Weblog^ContentType=0" width="1" height="1">https://verint14-pre-04.socialedgeconsulting.io/product-fieldpulse/b/product-news/posts/why-we-rebuilt-the-scheduling-engine-from-scratchSun, 05 Apr 2026 14:22:00 GMT9b51ca3f-ea30-4ce0-acc7-41a30a3e64f6Brandon Okafor0<p>We have 340 technicians and the load times were killing us. This is exactly what we needed.</p><img src="https://verint14-pre-04.socialedgeconsulting.io/aggbug?PostID=76^AppID=21^AppType=Weblog^ContentType=0" width="1" height="1">