Four parties are in motion simultaneously on a factory-built housing project. The factory is running a production schedule that does not pause for site problems. The general contractor is managing site readiness against a set day that is weeks or months away. The municipality is processing permit applications and inspection requests on its own timeline. The utility company is scheduling service connections according to its own backlog and access requirements.
Each party is tracking its own scope. None of them is tracking the interfaces between scopes. That is where projects fail, and it is where Bequall operates.
The factory tracks module production milestones, quality checkpoint sign-offs, HCD inspection scheduling, and shipping logistics. Its window of concern ends when the modules are on the truck and the delivery paperwork is complete.
The GC tracks site work completion, foundation pour schedules, subcontractor coordination, and the crane window. Its window of concern begins when the site is ready to receive modules. What happens between factory and site is not within the GC's contracted scope.
The municipality tracks permit application status, plan check completeness, and inspection scheduling. It does not track whether the applicant's factory documentation is consistent with the site drawings. That is the applicant's problem.
The utility company tracks service connection requests, easement agreements, and field crew scheduling. It does not track whether a factory-built project's electrical stub locations match its connection requirements. That gap surfaces when the crew arrives on site.
Between all four parties, there are document flows that require routing, sign-offs that require tracking, and coordination items that exist in nobody's scope until they become someone's problem.
A factory production milestone triggers a site readiness check in the Bequall coordination workflow. The check is not a formality. It runs against a structured set of criteria: foundation inspection complete, utility rough-in confirmed, crane access radius cleared, permit for permanent power active.
The check surfaces an unresolved utility coordination item. The electrical service connection request was submitted 11 weeks earlier. The utility company assigned an account number and a project manager. No follow-up had occurred since the initial submission. The service connection form requires a second signature from the property owner confirming the meter location, and that form was never routed.
Bequall routes the form to the property owner with the specific account number, the utility contact, and a deadline tied to the production milestone. The form is returned in two days. The utility schedules the crew. The site readiness check closes.
Without that routing, the gap would have surfaced at set day, when the crane is on site and permanent power is required for the final inspection sequence. Scheduling a utility crew after set day adds two to four weeks to the certificate of occupancy timeline.
A consultant advises on process. A coordination function executes within it. Bequall does not recommend that developers track utility service connection status. Bequall tracks it, routes the follow-up, and flags the item before it affects the schedule.
The distinction matters because the factory-built housing delivery model creates a coordination gap that nobody owns by default. The factory is not responsible for utility scheduling. The GC is not responsible for permit package routing. The developer is responsible for the outcome but typically does not have the operational bandwidth to manage 40-plus concurrent items across four parties.
That bandwidth is what Bequall provides. Not advice about how to build. Active management of the work that falls between the parties who are already managing their own scopes.