Lost-income claims are straightforward when payroll records show an hourly rate, missed shifts, and a matching reduction in wages. They become much harder when the plaintiff is self-employed, earns through multiple platforms, or has revenue that moves sharply from month to month. In those files, the demand cannot simply multiply an asserted daily rate by the number of missed workdays. The attorney must build a traceable economic story that separates gross receipts, avoided expenses, net loss, seasonality, and the effect of the injury on the plaintiff’s actual capacity to work.
This article lays out a documentation workflow for presenting self-employed and gig-worker lost income in a personal injury demand without overstating what the records prove.
Why self-employed lost income is an evidence problem before it is a writing problem
A W-2 employee usually has a third-party payroll system that can confirm compensation and attendance. A rideshare driver, independent contractor, sole proprietor, or small-business owner may instead have tax returns, payment-app statements, invoices, calendars, bank deposits, mileage logs, and customer messages—none of which answers the damages question alone.
California’s civil jury instructions distinguish lost earnings from lost profits. CACI No. 3903C addresses past and future lost earnings, while CACI No. 3903N addresses lost profits. The correct theory depends on what the plaintiff is claiming and how the business operates. A solo consultant’s reduced billable work may look different from a retail business whose revenue continued through employees. The demand should not blur personal labor income, business revenue, and business profit merely because they appear in the same account.
That distinction matters because gross revenue is rarely the same as compensable economic loss. Some expenses continue despite the injury, such as rent, software subscriptions, commercial insurance, or vehicle financing. Other expenses may fall when work stops, such as fuel, transaction fees, subcontractor costs, or materials. A credible analysis identifies both categories rather than presenting gross receipts as though every dollar would have become personal income.
Volatility creates a second problem. One weak month after the incident proves little if the plaintiff’s business regularly swings between strong and slow periods. The file needs a defensible baseline, a clear loss period, and an explanation of other variables that may have affected revenue.
Build the claim from source records, not a single summary number
The best workflow begins with an evidence map. For each component of the claim, identify the proposition to be proved, the record that supports it, and any limitation in that record.
Establish how the plaintiff actually earns money
Start by documenting the business model. Does the plaintiff bill by the hour, project, delivery, appointment, or completed sale? Is compensation paid immediately or weeks later? Can work be rescheduled, delegated, or performed remotely? Does the business rely on the plaintiff’s physical labor, personal license, customer relationships, or management?
This operating description gives meaning to the numbers. A delayed deposit may reflect work completed before the incident. A post-incident payment may therefore coexist with a real loss of working capacity. Conversely, a cancelled appointment is not automatically lost income if it was moved to the following week and completed later. The demand should distinguish deferred revenue from revenue that was actually lost.
Create a baseline that accounts for normal variability
For a stable operation, 12 months of pre-incident records may provide a useful baseline. A seasonal business may require 24 months or a year-over-year comparison for the same weeks. A newer business may have too little history for a reliable average, requiring more emphasis on booked work, accepted engagements, platform activity, or contemporaneous projections supported by actual performance.
Useful baseline records can include:
- Federal and state tax returns, including relevant schedules;
- 1099 forms and platform annual summaries;
- Profit-and-loss statements and general ledgers;
- Business and payment-processor statements;
- Invoices, contracts, appointment books, dispatch logs, or project calendars;
- Mileage, trip, delivery, or billable-hour reports; and
- Records showing refunds, cancellations, subcontracting, or replacement labor.
Tax returns are important, but they should not be treated as a complete answer. They report annual figures, may combine several income streams, and may not reveal the timing of a short disability period. Monthly source records connect the annual picture to the weeks at issue.
Define the loss period with medical and work evidence
The claimed period should track the actual functional restriction. Identify dates when the plaintiff could not work, returned on reduced hours, declined physically demanding assignments, or needed replacement labor. Tie those periods to treatment notes, work-status documentation, and the demands of the occupation without converting a medical restriction into a broader economic claim than the evidence supports.
For gig workers, platform data can be particularly useful. Compare online hours, accepted jobs, completed trips, cancellations, geographic coverage, and earnings per active hour before and after the incident. For a business owner, compare billable production, owner draws, payroll, outsourced work, and operating results. The right measure is the one that follows the way the plaintiff’s labor produces income.
Convert the records into a transparent damages analysis
A persuasive demand lets the reviewer reproduce the calculation. A spreadsheet or schedule should identify the baseline period, injury-related period, gross shortfall, avoided variable expenses, added mitigation costs, and resulting claimed loss. If the analysis uses an average, explain why that average is representative.
One practical framework is:
- Measure expected activity. Use comparable pre-incident weeks, year-over-year periods, booked engagements, or another supported baseline.
- Measure actual activity. Capture completed work and revenue during the claimed period, including delayed payments attributable to earlier work.
- Separate revenue from loss. Deduct expenses that would have been incurred only if the missing work had occurred.
- Add supported mitigation costs. Identify replacement labor, subcontracting, transportation, or other costs reasonably incurred to keep work moving.
- Reconcile the result. Compare the schedule against tax records, bank deposits, platform statements, and the plaintiff’s declaration.
Avoid false precision. If the evidence supports a range more reliably than an exact figure, explain the assumptions and preserve the underlying records for attorney review. The point is not to manufacture certainty; it is to show why the claimed methodology is reasonable and where judgment was required.
Address the predictable challenges before the adjuster raises them
Self-employed claims commonly draw questions about unrelated market changes, seasonality, duplicate revenue, cash payments, unreported income, business expenses, and the difference between inability to work and lack of available work. The demand should address material issues directly.
For example, if revenue fell before the incident, do not use an earlier peak period without explanation. If several client cancellations occurred for unrelated reasons, remove them from the claimed loss. If work was delegated, identify the replacement cost and any revenue preserved through that mitigation. If deposits continued after the incident, reconcile them by invoice or service date instead of ignoring them.
This is also where a concise plaintiff declaration can help. It should describe the work, physical demands, interruption, mitigation efforts, and recordkeeping system. It should not substitute for objective documentation that should exist.
A practical pre-demand checklist for the firm
Before finalizing the lost-income section, the attorney and case team should be able to answer the following:
- What damages theory is being presented: lost earnings, lost profits, added mitigation expense, or a documented combination?
- What period is claimed, and what medical or functional evidence supports it?
- How was the baseline selected, and does it account for seasonality or business growth?
- Are payments tied to the date earned rather than merely the date deposited?
- Which expenses continued, which were avoided, and which increased because of the injury?
- Were postponed jobs separated from permanently lost jobs?
- Do tax records, bank activity, platform reports, invoices, and the plaintiff’s account reconcile?
- Are assumptions and data gaps stated clearly enough for another reviewer to audit?
Use the same discipline applied to the rest of the demand package. The firm’s pre-send demand package review should confirm that the economic-loss schedule matches the narrative and exhibits rather than existing as a disconnected spreadsheet.
How Legal Power AI fits
Legal Power AI’s demand-letter workflow can help organize uploaded records, surface inconsistent dates or figures, and carry an attorney-approved lost-income analysis into the draft narrative. It does not decide the correct damages theory or cure incomplete business records. Counsel remains responsible for selecting the methodology, protecting confidential and health information, verifying every calculation and citation, and approving the document before it is sent.
Conclusion
A self-employed or gig-worker lost-income claim becomes credible when the demand shows its work. Define how the plaintiff earns income, select a representative baseline, connect the loss period to supported restrictions, separate gross receipts from net economic loss, and reconcile the result across source records. That method gives the adjuster a reviewable claim while helping the attorney identify weak assumptions before they become negotiation problems. AI can reduce the clerical burden of organizing records and maintaining consistency, but the economic theory and final judgment must remain with counsel.
See a more structured demand workflow.
Built for plaintiff PI teams that want faster record organization without giving up attorney control. See Legal Power AI in action →