A job table may say completed. A service-job collection can show the request, scheduling, visits, work performed and billing. The critical question is which records describe the same job and which describe separate visits. Map those units first so a callback or second technician does not disappear into the final status.
One job, more than one visit
Fictional job J-204 contains visit V-1 on May 7 and callback V-2 on May 10. Completion notes describe each visit, photos are attached to V-2, and invoice I-68 refers to the overall job. A single job row cannot explain that structure on its own.
Compare the job snapshot with the linked collection using the same job and period. Do not count a callback as a separate customer order unless the records actually define it that way.
| Group | Reference to inspect | What it describes |
|---|---|---|
| Job | J-204 | Requested work |
| Dispatch | J-204 and V-1/V-2 | Scheduled visit and assignment |
| Visit notes | Visit reference | Work attempted or completed |
| Photos | Job or visit attachment link | Recorded visual context |
| Invoice | J-204 and invoice lines | Billed work |
Keep arrival, work and completion distinct
Scheduled time, actual arrival and completion are different events. If a note was entered at the end of the day, its creation time may differ from the time the technician worked. Preserve the field meaning rather than merging all dates into a generic job date.
A photo’s timestamp also needs context. It may establish when the image was captured or uploaded, but it does not independently prove which job it depicts. The attachment relationship or an explicit job reference is the stronger connection to inspect.
Test a callback and an incomplete job
Choose one job that required a return visit and one that remained open. Check whether the notes explain what changed, whether the second visit retains the original reference and whether billing reflects the final work. This is a structure check, not a judgment about service quality.
Inventory the evidence before describing a complete job history
Write a separate row for job records, dispatch events, visit notes, photos and invoices. Dates may differ between groups. A photo folder beginning last year does not make earlier jobs disappear; it means earlier jobs have a different collection scope.
- Persistent job and visit identifiers
- Dispatch or assignment event dates
- Completion notes with the relevant visit
- Attachment links and actual file availability
- Invoice reference and any credit or adjustment
- Known gaps in older job history
Ask a specific buyer question
Handshake’s license page names ServiceTitan as a source example. If that is your system, ask about your job records, photos and visit history.
Sources: Handshake
Questions about this comparison
Does completed mean we have the completion note?
No. The status and the explanatory note are separate inventory elements.
Should photos be grouped by date or job?
Keep their original identity and inspect the job or visit relationship. Date alone can be ambiguous.
Can the same invoice cover several jobs?
Yes in a possible collection structure. Inspect the actual line or supporting reference before connecting it to one job.
Sources
- Data Partnerships | Handshake AI (license / interest form page)Handshake · Checked 2026-10-10