From the invoice on your desk to a packet you have reviewed
Five steps we do with you, then one step that is yours alone. We do not submit on your behalf, and knowing exactly where the handoff sits is the point of this page.
Bring in the job
Customer, address, invoice, equipment. Reading values off the invoice is a convenience — every value keeps its dotted “extracted” treatment until a person confirms it.
Confirm what goes on the form
Extracted values sit beside the page they came from. Conflicts, such as two installation dates on one invoice, block the review until someone decides.
Run the requirement checks
Pass, does not meet, unknown, or not applicable — each with its inputs, its source link and the date a person reviewed that source.
Clear the blockers
Missing nameplate photo, unsigned authorization, unconfirmed deadline. Each becomes a task with an owner, or a scoped link you can send the homeowner.
Build and review the packet
Forms filled, attachments in the program’s order, version recorded. You complete an explicit final review before the packet is released.
Record what the program does
Submission, approval and payment are three separate records with their own dates and amounts. Attach the letter or the confirmation and the record shows as evidence-backed.
You file it. We do not submit on your behalf.
The packet lands in your downloads. You sign it, upload it to the program’s portal or email it to the address on the program page, and paste the confirmation reference back into the job. That step is deliberate: the program’s relationship is with you, the licensed contractor, and a submission made on your behalf would be a claim we are not entitled to make.
- Sign the certification page
- Upload to the program’s portal in the order shown
- Record the date, channel and reference
The job then moves to “waiting on the program” with nothing on your list until they reply.
We do say
- Your job was checked against rules a person read on a stated date
- The packet contains the forms and attachments that program asked for, in order
- Anything missing is named before you pay
We never say
- That approval, an amount, or a payment date is guaranteed
- That we found every rebate available for the job
- That we are affiliated with, or speak for, a utility or program
How we read your documents
Reading an invoice is done by software, including a language model running on Cloudflare Workers AI — the same account that already stores your documents. No third party outside Cloudflare receives them, and your documents are not used to train any model. That is Cloudflare's published commitment for Workers AI, not our characterisation of it.
What that software produces are proposals, never decisions. Every field is confirmed by your office before it reaches a packet. A proposed value must quote the text it came from, and we check that quote appears in the document you uploaded — anything we cannot find there is discarded rather than shown to you, so a value the software invented cannot reach a form.
Extraction is measured field by field rather than as one accuracy score, because an aggregate would hide a wrong installation date behind six correct model numbers.