The Bank Draw Is Due Friday and Nobody Has 31 Lien Waivers Yet. Claude Cowork Hands Back the Whole Packet.

You tried this in 2024 and it wrote you a paragraph about draw requests

That is a fair objection and it was a fair experience. In 2024 you asked an assistant to help with the monthly bank draw and it explained what a schedule of values is. Useful to a first-year, useless to your controller, who did not need a definition — she needed 31 conditional lien waivers back from trade partners, a percentage-complete figure for every budget line on nine active lots, the invoices that support them, and the whole thing in the format your regional bank's construction department accepts, by Friday.

That is the difference 2026 made. The assistant stopped being a chat box. Anthropic shipped Claude Cowork on 12 January 2026 and OpenAI shipped ChatGPT Work on 9 July 2026, and both work the same way from an owner's point of view: you give it a goal, it connects to your files and your systems, breaks the job into steps, works on its own for hours, and hands back a finished thing. A completed spreadsheet. A packet. Not advice about a packet.

A goal-based agent is one you hand an outcome to — "assemble February's draw for all nine active lots" — and it works through the steps by itself for hours and returns the finished packet, rather than telling you how to build one. Both products were aimed at people who do not write software, which in a homebuilding office means the controller, the closing coordinator and the office manager.

What a draw request is made of, and why it takes six days

If you build with a construction line rather than cash, you know the shape. Every month, per lot: a draw request form on your bank's template or an AIA G702 and G703 if your lender is old-fashioned, percentage complete against each budget line, supporting invoices from every trade who billed, conditional progress lien waivers from each of those trades matched to the exact dollar amount, unconditional waivers covering the previous draw, current certificates of insurance, progress photos, and in some states a sworn statement listing every party who furnished labor or material.

Your controller starts on the 25th. She exports job cost by lot from Sage or QuickBooks, cross-checks purchase order status in Buildertrend, and then begins the part that consumes the week: emailing waivers to trade partners and waiting. The drywall contractor's office manager is out. The plumbing supplier sends a waiver for the wrong amount because they billed two lots on one invoice. Two trades send back an unconditional when you asked for conditional. She chases, she re-requests, she assembles, and somewhere around the 4th the packet goes to the bank, which then takes its own five business days and its own inspection.

Meanwhile you are floating those subs on the operating line, because the trades got paid on the 10th and the bank funds on the 12th of the following month. That gap is the whole point of this article.

Wednesday, 9 a.m.: you give it the goal and go to a site meeting

The instruction is one sentence. Assemble the February draw for lots 4, 6, 9, 12, 18, 22, 27, 31 and 33. Then it works, for a couple of hours, without you.

flowchart TD
  A["Owner sets the goal: February draw, 9 active lots"] --> B["Pulls job cost by lot and PO status"]
  B --> C["Builds percent complete for every budget line"]
  C --> D["Requests conditional waivers from each trade who billed"]
  D --> E{"Waiver missing or amount does not match?"}
  E -->|Yes| F["Names the trade and the dollar gap for the controller"]
  E -->|No| G["Assembles packet: draw form, invoices, waivers, photos, COIs"]
  F --> G
  G --> H["Controller reviews and signs, sends to the bank"]

What comes back at 11:40 is a folder, not a suggestion. Nine draw request forms filled to your bank's template with percentages that tie to job cost. Every invoice attached under the right budget line. Twenty-eight of the 31 waivers collected, matched to the penny. Three exceptions listed by name: the framer's waiver is for $18,400 against an invoice of $18,940, the electrician sent an unconditional when the draw needs a conditional, and the flooring contractor's certificate of insurance expired on the 19th. Progress photos pulled from the superintendent's daily logs, dated, sorted by lot.

Your controller spends forty minutes on the three exceptions and signs. That is the change: she moves from assembling to reviewing exceptions. It is the same shift a good superintendent made years ago when he stopped counting lumber and started checking the load against the list.

The arithmetic is cash timing, not payroll

Nobody is laying off a controller over this, and you should be suspicious of anyone who pitches it that way. The money is in the calendar. Assumptions stated so you can substitute your own.

There is a second benefit that does not appear on that table and matters more to some builders: trade partners who get paid on a predictable date price you better and answer the phone in July. If your best framer knows your check lands on the 8th every month without fail, you are a different customer to him than the builder who pays whenever the bank funds.

To measure it, write down two dates for the last six draws — the day the packet went to the bank, and the day funds hit. Then track the same two dates for six months after. If the first date moves five days earlier and the second follows, the arithmetic above is yours.

The part you cannot hand over: signing, and the sworn statement

You sign the draw request. Your controller signs the draw request. Not the agent, not ever. That form contains a representation to a lender about the state of work in place, and if the percentage complete on lot 22 says 68 percent and the plumbing rough is not in, that is a problem with your name on it, not a software error. Someone who has walked those lots reviews the percentages before anything is transmitted.

Lien waivers deserve the same caution in the other direction. In several states the statutory waiver forms are prescribed word for word and a modified form is worthless; California, Texas, Arizona and others each have their own. Have the agent collect and match waivers, and have a person — your controller or your construction attorney once, up front — confirm the form itself is the right one for your state. Same for a sworn statement in the states that require it.

It will also fail in the ordinary way: a trade partner who does not answer email, a supplier whose accounting system emails a scanned image with no numbers in it, an invoice that covers two lots. Those are exactly the exceptions it should hand back rather than guess at. If you ever see it resolve an amount mismatch on its own, turn that behavior off.

Frequently asked questions

How is this different from just having a better draw template?

A template does not chase the drywall contractor. The assembly work — requesting waivers, matching amounts to invoices, noticing an expired certificate, pulling the right photos out of daily logs — is where the six days go, and that is the part a goal-based agent actually does. The template was never your problem.

Our bank has its own portal and its own forms. Does that break it?

No, and it is common — most regional construction lenders have a portal with their own draw form. The agent fills the form and assembles the supporting file; a person uploads it. Some builders let the agent do the uploading too, using the controller's own login, which works but is a decision to make deliberately rather than by default.

What has to change about how I assign work?

This is the real answer to the question. You stop writing task lists and start writing outcomes with the boundaries attached: what "done" looks like, what it may decide on its own, what it must bring back. "Assemble the February draw, all nine lots, bank template, flag any waiver that does not match to the dollar, do not transmit." That sentence is a management skill, and the first month of using it feels awkward for exactly the same reason delegating to a new project manager feels awkward.

Which one should I use, Cowork or ChatGPT Work?

Either does this job. Pick based on where your files already live and which one your controller finds less annoying after a week. Run the same draw through both once, with real lots, and let her choose. That is a better selection process than a feature comparison.

Start with one lot, not nine

Next draw cycle, pick a single lot in the middle of construction and give the goal for just that one, three days before your controller would normally start. Let her build the other eight the way she always does. Then put the two versions of that lot's packet side by side on the conference table and mark every difference. If the agent's version is right on the percentages and honest about the waivers it could not get, you have your answer, and you have spent one afternoon finding it.

The draw cycle also generates a week of phone traffic that nobody plans for: trade partners calling about waiver requests, suppliers calling about which lot an invoice belongs to, the bank's inspector calling to schedule. CallSphere builds AI voice and chat agents that answer the office line through that week, take the caller's question with the lot and invoice number attached, and book the callback with your controller — so the days you pulled out of the draw cycle do not go straight back into returning voicemails.