How should multi-visit jobs and progress billing be handled in revenue reporting?
Attribute the whole job to one source and one origination date, then let revenue land as it invoices. The common mistake is treating each visit or invoice as its own job, which multiplies job counts, deflates average ticket, and credits later visits to whatever source happened to touch them most recently. Roll invoices up to the job, and jobs up to the original opportunity.
The rollup hierarchy is the whole design
There are four levels and they have to stay distinct: the opportunity, which is the customer's need and carries the source; the job, which is the work sold against it; the visit, which is a dispatch event; and the invoice, which is a billing event. A remodel might be one opportunity, one job, six visits and three invoices.
Most reporting problems in project-heavy trades come from a system or an export that flattens these into one row. Preserving the hierarchy is standard integration modeling, and it has to happen before any metric is computed on top.
What breaks without the rollup
- Job count inflates. Six visits become six jobs and your completed job count is meaningless.
- Average ticket collapses. A large project divided across visits reports as several ordinary jobs.
- Attribution drifts. Later visits get whatever source is on the most recent record, which is often the office or nothing.
- Close rate distorts. Change orders can register as new sold opportunities that never had a corresponding quote.
Recognizing revenue that spans periods
Long jobs straddle reporting periods, so a rule is needed and it should be written down. Two are defensible: recognize revenue as invoiced, which matches the books, or recognize the full job value at completion, which matches operational thinking. Mixing them within one report produces totals nobody can reconcile.
Whichever you choose, keep the origination date on the job so cohort reporting still works. That preserves the ability to judge the channel that produced the opportunity, which is discussed further in revenue reporting.
Deposits complicate this further. Money collected before work begins is cash, not earned revenue, and treating it as completed revenue overstates a period and then leaves a hole in the next one.
Change orders deserve their own treatment
Change orders and add-ons are additional revenue on an existing opportunity, not new opportunities. Counting them as new sales overstates both close rate and job count while understating average project value.
They are worth reporting separately, though, because change order revenue as a share of original job value is a genuinely useful operating metric. It tells you about estimating accuracy and about how well crews identify additional work in the field — both coachable, and both invisible if the change order is buried inside the job total. See custom dashboards for how these levels get presented without flattening them again.
Topics: multi-visit jobs · progress billing · rollups · attribution · data modeling
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.