Source attribution is recording where a file came from at the moment of first contact and carrying that record through to the invoice. For an adjusting or inspection firm the sources are specific: a restoration contractor, a roofer, an attorney, a prior client, a carrier’s approved vendor list, or a paid channel. Attribution fails when the source is captured as free text, captured after the fact, or lost at the point where a file becomes a billing record.
Why the source disappears
Source is a free-text field and everyone types it differently
Mike. Mike R. Mike at ABC Restoration. ABC. Referral. Five entries meaning one person, and no report can group them without someone cleaning the list by hand. The cleanup gets done once, then the field drifts again.
It gets captured after the fact
Nobody asks on the first call, so at month end someone reconstructs where files came from by reading notes and asking adjusters what they remember. The reconstruction is a guess dressed as data, and it is the version the principal reads.
The file changes hands and the source does not survive
The source was captured on the intake record. Then a claim file or order record is created and the source stays behind, because nothing copied it forward. Every downstream report is built on records that never had the field.
Referrers are people, and the model only has companies
Three project managers at the same restoration firm send work, and one of them sends most of it. Company-level attribution hides that it is one person, who takes the referrals when they move.
Nothing connects the source to what was billed
You can count files by source because the field exists on the file. You cannot see billing by source, because the invoice was created in the accounting system and the source never made the trip.
Attribution chain from first contact to invoice
Attribution is not one field. It is a chain of points where the source is written, copied, protected, or handed to another system, and the chain is only as strong as its weakest handoff. This is the model we build to.
| Point in the file | What is captured | How it is stored | What it makes reportable |
|---|---|---|---|
| First contact | Source type from a fixed list, plus the referring person where there is one | Source type as a controlled value; the referring person as a link to a contact record, not typed text | Files by source type and by individual referrer, with no cleanup step |
| Referring organization | The company behind the individual, where one exists | The referrer contact belongs to an organization record, and both stay queryable | Roll-up by company while the individual stays visible underneath |
| Campaign or channel detail | For web-originated contacts, the specific form, page, or campaign | Written into the same source fields from the submission, not a separate marketing system | Web and referral sources compared in one report instead of two |
| File creation | The source fields copied onto the claim or order record at creation | Stored on the file record itself, so later edits to the contact do not rewrite history | Attribution that stays accurate after a referrer changes companies |
| Assignment and work | Nothing new. The source rides along untouched | Read-only after creation, changeable only by a named role with the change logged | A file’s source cannot quietly become a more convenient source at close |
| Invoice or fee record | Source fields carried onto the billing record at creation | Synced to the accounting system as a class, customer field, or tag | Billing by source, referrer, and period, produced from the ledger rather than a spreadsheet |
| Referrer view | What that referrer has sent and the current status of each file | A filtered view by referrer, exposing only the fields you choose to share | A conversation based on the referrer’s actual list |
How attribution gets wired in
A fixed source taxonomy agreed before anything is built
Eight to fifteen values, decided in one meeting with the people who answer phones. Forty is a list nobody uses correctly and five tells you nothing. Changing it later becomes a deliberate act.
Referrers exist as contact records with an organization behind them
The individual is the record that matters, with a company attached. That structure survives the common events: the referrer changes firms, two referrers work at the same company, or work arrives with no named person.
Web forms write the same fields as the phone script
A contact form submission and a call taken at the desk populate identical source fields. Where a web form cannot know the source, it captures the page and campaign and sets the type to the web channel rather than leaving it blank.
The source is copied onto the file, not referenced from the contact
At file creation the source values are written onto the file record itself, so if the referrer’s contact is later edited or merged, historical files keep what was true when they came in.
The accounting handoff carries the source with it
When the invoice is created, source and referrer travel to the accounting system as a class or custom field. That is what lets billing by source come out of the ledger, where the numbers already reconcile.
Where attribution has to reach
- CRM automation for contacts and referrers — Referrers exist as contact records under an organization, each carrying the list of files they have sent.
- QuickBooks automation for billing records — Source and referrer are written onto the invoice as a class or custom field so reporting comes out of the ledger.
- intake and web form automation — Web and phone intake write the same controlled source fields, so both channels land in one report.
Is this a fit for your business?
A good fit when
- A meaningful share of your work arrives through contractors, vendors, attorneys, or prior clients
- More than one person takes first-contact calls
- You want to see billing by referral source out of your accounting system
- Your current source field is free text and nobody trusts the report built on it
Probably not a fit when
- Nearly all your work comes through one channel and the mix does not change
- You want a marketing attribution platform for high-volume paid advertising
- You want advice on whether a referral arrangement is permissible in your state
What to have ready
- The list of sources you would actually want to see on a report
- Your main referring individuals and the companies they work for
- The accounting system you invoice from and how its class fields are used
Questions we get asked
Can we use this to pay referrers?
The system can show what a referrer sent and what was billed against those files, which is the record such an arrangement would need. Whether a referral source may be compensated, and on what terms, is a licensing and legal question for your firm and its counsel. Several states restrict compensation to unlicensed persons in public adjusting work.
What about a file with more than one source?
One primary source, with optional influencing sources recorded alongside it. Only the primary rolls into billing reports, because a report where files can count more than once is a report nobody can reconcile. The influencing sources stay visible on the file.
How far back can we reconstruct attribution?
As far back as there is evidence. Historical files can be backfilled from intake notes, email, or recollection, and we mark reconstructed values as reconstructed. Mixing the two produces a history that looks more certain than it is.
Does this require a CRM?
Not necessarily. It requires a contact record with a stable identifier and a file record that can hold a copied value. If you already run HubSpot that is the natural home; if not, the referrer table can live with your files.
Related
- claim intake and adjuster assignment
- broker and referral intake for appraisal firms
- QuickBooks automation for billing and reporting
- workflow automation for appraisal and adjusting firms
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.