Change Order Catcher
Catches the parts and labor your techs gave away, before closeout.
Bill the work your tech already did.
Change Order Catcher takes the approved scope from the sale and the tech's end-of-day record, diffs one against the other, and flags every part and every hour that was done on site but never sold. Then it drafts the change order so you bill it while the memory is fresh, not discover it at closeout. Runs on Claude and Cowork from a plain conversation, no connectors needed.
Download the skillThe problem
Profit does not disappear on the proposal. It disappears in the gap between what you sold and what the field gave away. A tech works a job all day. The client says "while you're here, can you look at this other TV." It needs an HDMI cable, an Apple TV, and a small surge protector. The tech has the parts on the van, so he uses them.
He is not stealing. He had a long day. He forgot to log it, or he logged two of the three items and missed the surge protector. That work was real, the parts were real, and none of it reached an invoice. Multiply the forgotten cable and the unbilled hour across every job, every tech, every week, and you are running a business that gives away product and labor as a habit nobody tracks.
The fix is not asking your techs to remember better at the end of a ten-hour day. It is a system that already knows what was sold and catches everything that was not.
What you get
How it works
Load the approved scope. First thing every run: the scope of work from the sale. If you ran the Proposal Builder or the Scope of Work Builder on this job, that document is exactly what it reads. The scope is the baseline that makes the catch precise.
Drop in the tech's end of day. Paste the voice memo transcript, the day-end notes, the text thread, whatever he sent. Include client messages from the day and it catches the "while you're here" asks too. Messy is fine.
The diff. It goes line by line through what the tech did and sorts every action and part into sold, not sold, or unclear. The tech never has to decide what counts. The scope decides, and anything outside it gets flagged whether he mentioned it or not.
The flag list, for your review. It surfaces every out-of-scope item before it drafts a single billable line, each one tagged AI-caught or tech-declared. You say which to bill, which to write off, which need a client conversation first.
Change order draft. For the flags you approve, it builds the change order: parts by line with your prices, added labor with the assumption behind the number, and any schedule impact, plus the client-facing paragraph ready to send.
Nothing bills itself. Every change order is a draft you approve. The tool catches and drafts. You decide what bills.
Example output
Flag List: Riverside Media Room, Aug 4
Change Order Draft (flags 1 and 2 approved):
Parts: 1x HDMI cable [PLACEHOLDER: confirm price], 1x Apple TV [PLACEHOLDER: confirm price], 1x surge protector [PLACEHOLDER: confirm price]. Labor: 0.75 hr at your service rate. Schedule impact: none.
Client summary: "While on site for your media room install, at your request we set up the guest bedroom TV, including the Apple TV, cabling, and surge protection. That work is billed below as a change order to the original scope."
How to trigger it
Works with
Install + download
Click the download link below and save the file.
In Claude: go to Settings, then Skills, and upload the file.
In Cowork: open the Skills panel and upload the file.
Test it: say "run the change order catcher" and paste a scope plus a tech's end-of-day notes.
The core prompt
Use this if your platform has no Skills support. Paste it into custom instructions.
# Change Order Catcher You catch parts and labor a technician did on site but never billed, then draft the change order. The user is an AV integration owner. STEP 0. Load the approved scope of work from the sale. Ask for it first, once. If it is missing, run blind and say so, then work only from clearly out-of-scope work in the field record. STEP 1. Take the tech's end-of-day record: voice memo transcript, day-end notes, or texts, plus any client messages from the day. STEP 2. Diff the field record against the scope. Sort every action and part into: in scope (sold), out of scope (candidate change order), or uncertain. The tech is never the judge. Flag out-of-scope items whether or not he called them a change order. Tag each flag AI-caught or tech-declared. STEP 3. Present the flag list first for the owner to approve: out of scope caught, uncertain needs a call, and in scope accounted for. STEP 4. For approved flags only, draft the change order: parts by line with prices from the price book or [PLACEHOLDER: confirm price], added labor with its assumption, and schedule impact. Write a plain, confident client-facing paragraph, never apologetic, because the client asked for the work. STEP 5. End with open questions: anything the field record left unclear that could change what gets billed. Rules: never invent a price or model number. Nothing bills automatically, every change order is a draft the owner approves. Uncertain items become questions, never forced into billed or written off. Small parts on every job are the whole leak, so never drop a flag for being small.
Feed it the scope straight from the Proposal Builder and the two skills become one loop: Proposal Builder sells the job and defines the scope, Change Order Catcher makes sure nothing you deliver on top of that scope walks out unbilled.
This is a template, not a finished product. The skill knows the diff, not your shop. Load your price book and the caught items come back in your numbers instead of placeholders. Load the approved scope from your own Proposal Builder run and the catch gets sharp. Run it once on a real day-end from one of your techs, tune it, save your version.