Operating design · Synthetic example

What a Source-to-Signed-Case Record Needs to Capture

A count of inquiries cannot show whether a firm completed intake, held a consultation or recorded a signed engagement. This proposed record design makes those steps visible. It is an educational example for firm operators, not a claim that InjuryOS has deployed the workflow.

Give each event an explicit meaning

Start with a shared description of what an inquiry, completed intake, consultation, signed engagement and closed record mean in the firm’s own process. A marketing form submission should not silently become a qualified opportunity. A scheduled consultation should not be reported as a consultation held.

Record the event time, the time it was entered and the owner responsible for the next step. Corrections should remain distinguishable from the original record. An operator should be able to explain why an item appears in a total without reconstructing it from private messages.

The firm defines its review standards and representation decisions. A tracking design does not supply a legal qualification rule or decide which matters the firm should accept.

Keep a stable identity across the journey

The same person may submit a form and call later. If both contacts become independent opportunities, the source count can be inflated. Preserve each contact event while connecting it to a stable internal record through an authorized process.

Record the original known source separately from later touchpoints and the attribution rule used for reporting. Unknown is a valid state. Do not manufacture a campaign source when there is no evidence. A source field describes a recorded relationship; it does not establish that a campaign caused a signed engagement.

Public analytics and marketing inquiry forms should not contain an injured person’s case narrative. The simplified record below uses invented identifiers and contains no personal or incident information.

A synthetic record set

The following three records are invented. The event names illustrate a reporting design and do not represent real firms, real inquiries or product telemetry.

RecordRecorded sourceObserved progressCurrent state
EX-101Campaign AInquiry, contact, completed intake, consultation, signed engagementSigned outcome recorded
EX-102Campaign AInquiry, contact attemptWaiting for next contact step
EX-103UnknownInquiry, completed intake, firm reviewClosed by firm review

What this small example can and cannot report

There are three distinct records, two completed intakes and one recorded signed outcome. Campaign A appears on two inquiries, one of which has a signed outcome in this snapshot. The unknown-source record must remain visible rather than being redistributed to the known campaign.

That is not enough information to estimate campaign quality, predict future conversion or decide a budget. The waiting record is still unresolved. The time elapsed since each inquiry differs, and a later signature could change the snapshot. A larger comparison needs a defined inquiry cohort and a consistent outcome cutoff.

If a duplicate is found, keep the source events and record the merge. If a signed status is corrected, preserve that correction. A clean-looking final total is less useful when nobody can trace how it changed.

Add costs only after the record basis is clear

Suppose the invented Campaign A spending is $2,000 for the same agreed acquisition window. Dividing it by two recorded inquiries gives $1,000 per inquiry. Dividing it by one currently recorded signed outcome gives $2,000 per signed outcome in this snapshot.

Those figures answer different questions. The second can change as unresolved records mature. It excludes other costs and says nothing about eventual case value, collected fees or firm profitability. The example is arithmetic, not a benchmark or performance promise.

Before comparing sources, confirm the spending window, duplicate treatment, eligible records, signed-status definition and follow-up cutoff. Show unresolved records alongside completed outcomes.

The next operating conversation

Ask the intake owner where a record currently changes hands, which statuses are ambiguous and who confirms an outcome. Then test the definitions on a small set of permitted records inside the firm’s appropriate environment.

InjuryOS is a concept under development. The public materials describe an operating direction and invite workflow discussion; they do not offer legal representation or demonstrate a live firm deployment. Do not send case files or sensitive personal details through the general inquiry route.