Imagine it’s Thursday afternoon at a modular factory. The production manager tells the owner that all six modules in the first batch came off the line on schedule. The controller has a question. “Can I send the invoice today?” Five modules have signed inspection reports. Somebody remembers seeing the plumber in the sixth one that morning. Nobody in the room knows whether he finished the pressure test.
I’d want that question answered before everyone went home. Under this particular contract, the customer owes a progress payment once all six modules pass inspection. One open test can hold up the draw on a whole batch. And if the lender reviews payment requests on Friday mornings, an hour spent finding the answer on Thursday could cost the factory a week.
That little scene is hypothetical, but it explains why, if I ran a modular company, the controller would have a seat at my production meeting. It also explains where I’d spend my first dollar on factory tracking technology.
Before I promise a slot on the line
Let’s back up to the day the builder walked in with that 20-module order. Sales worked up the price. Production found room on the schedule. Before I signed, I’d ask the controller to put dates beside three things we already know well: when our suppliers expect payment, when our people get paid, and when the builder expects to pay us.
Suppose we’ll spend $450,000 on materials and labor before the first production payment clears. The builder offers a $200,000 deposit. That leaves us carrying $250,000 on this job at that point. We might be perfectly comfortable doing that. But if two other builders need their modules in the same month, I’d like to see all three jobs on the same sheet of paper. The same dollar in our checking account can look available to three different salespeople.
This is when I’d negotiate the progress payments. The deposit lets us reserve capacity and commit to purchases. Progress payments let us collect portions of the contract price as identifiable work gets done. Six inspected modules might make a sensible first billing milestone for this order. On another job, a smaller batch might suit both parties better.
I’d bring the builder and the lender into that discussion. Who can approve the inspection? What records do they need? Will they release funds while the modules are still at our plant? What protection does the buyer have for modules already paid for? A builder can sign our payment schedule in good faith and discover later that the bank’s first draw requires delivery. I’d much rather learn that while we can still change the deal.
What the tag on Module 6 can tell us
Now put an RFID tag on each module and link its number to the job. A fixed reader at the inspection bay records that Module 6 arrived Thursday at 10:42. That saves the foreman a walk through the plant and gives accounting a reliable starting point. Someone still has to perform the pressure test and record the result against that same module number.
That distinction matters. If the plumber signed at 2:15 and the report is sitting in a folder, the controller can assemble the draw request this afternoon. If the test failed, the superintendent needs to assign the repair and arrange a retest. Same module, same location, two entirely different jobs for management.
I’d start with one line and one milestone. For the first few batches, I’d ask the foreman to compare the electronic record with what actually happened, including the box that went backward for rework. In a steel bay, I’d also check whether the reader picked up a tag on the neighboring module. Once the crew trusts the readings, a simple alert can tell accounting the moment all six approvals are in. That alone would earn its keep in a plant where the controller currently has to chase paperwork.
Where I’d give AI a job
The more interesting question comes a day earlier. On Wednesday morning, can we tell that Module 6 is likely to miss Thursday’s inspection? Once the factory has enough reliable history, AI could compare the work remaining on that floor plan with the time similar modules actually took. Add the inspection schedule and open work orders, and the superintendent might get a specific heads-up: the sixth module is likely to reach testing after the inspector leaves.
Now somebody can act. The superintendent can check with the plumber, see whether an earlier test slot is available, or tell the controller to move the expected receipt into the following week. I’d judge the system by how often its warning came early enough to make one of those decisions. Any foreman can tell me on Friday afternoon that we missed Thursday.
The number I’d look at on Monday morning
Every Monday, I’d review a rolling 13-week cash forecast alongside the production schedule. The controller would start with the reconciled bank balance, enter receipts in the weeks we reasonably expect to collect them, and place payroll, taxes, supplier bills, freight and debt payments in the weeks they’re due. I’d go straight to the lowest projected balance and ask what has to happen for that number to hold.
Suppose the builder calls to say the foundations are three weeks behind. If our contract lets us collect on inspected modules in the yard, we can weigh the cost of storage and the carriers we’ll tie up. If the next payment depends on setting those boxes, starting another batch commits more cash while the receipt moves further out. I’d want the builder on the phone before purchasing releases the next batch of windows.
I’d also run the forecast with our largest draw arriving two weeks late. That gives me a basis for deciding how much cash to keep available and how much credit to arrange with our bank. An invoice has a date, payroll has a date, and every owner ought to know what happens when they fall out of order.
Gary’s Observation
If I walked into a factory tomorrow, I’d ask the production manager to pick one module that came off the line last month. Then I’d ask the controller to follow it with me. When did it pass inspection? When did we earn the payment? When did we send the paperwork? What day did the money clear?
I’d pay particular attention to the days between the signed inspection and the invoice. If we lost four days waiting for somebody upstairs to hear what happened downstairs, we’ve found something we can fix on Monday morning. And we can fix it without asking the crew to build a single box any faster.
