Skip to content
Solutions

Redlining Built for Patent Prosecution

Specifications, claims, and office action responses follow conventions most redlining software was never built for. Version Story compares them the way patent practice demands — down to the paragraph number.

[0003] Stays [0003].
Never [3].

Patent specifications number their paragraphs in fixed-width form — [0001], [0002], [0003]. Most redlining software re-parses those as automatic list numbering and rewrites them, so every paragraph shows a phantom change and the USPTO-required format is gone. Version Story preserves your numbering exactly as written, so the redline shows only what you actually changed.

Generic redlining software

[0003][3]Association of a request with earlier traffic is commonly performed using the source network address and using state stored at the client device, such as a session cookie returned to the service on subsequent requests.

[0004][4]Client software of the kind that loads and renders documents retrieved over a network commonly includes a scripting runtime environment. The scripting runtime environment executes script code carried byembedded in or referenced from a loaded document.

Every paragraph is flagged as changed, and the one real edit is buried in phantom numbering churn.

Version Story

[0003]Association of a request with earlier traffic is commonly performed using the source network address and using state stored at the client device, such as a session cookie returned to the service on subsequent requests.

[0004]Client software of the kind that loads and renders documents retrieved over a network commonly includes a scripting runtime environment. The scripting runtime environment executes script code carried byembedded in or referenced from a loaded document.

One real change, shown once. The numbering your filing requires never enters the redline.

Office Action Responses,
Formatted to File

Hand Version Story the pending claim set and your revised claims, and it produces the complete “Amendments to the Claims” listing that 37 C.F.R. § 1.121 and MPEP § 714 require. Status identifiers derived for every claim, underline and strikethrough markup computed against the last entered version, double-bracket form for deletions of five or fewer characters, canceled claims listed without text, new claims taking the next unused number — delivered in Word alongside a standard tracked-changes redline for internal review.

Reconstructing the entered baseline and re-marking every claim by hand each round is a version-control problem — the exact problem Version Story was built to solve.

Request Demo

IN THE CLAIMS

Please amend the claims as follows:

1.(Currently Amended)A computer-implemented method for provisioning a diagnostic report to a technician in a vehicle service platform, the method comprising:

in response to receiving an incoming service request from a vehicle, the incoming service requesting request including a vehicle identifier, i) placing the incoming service request in a queue for assignment to a technician, and ii) initiating [[a]] an asynchronous process to generate a diagnostic report based on telemetry data associated with the vehicle identifier, the asynchronous process executing while the incoming service request awaits assignment in the queue, without delaying processing of the incoming service request, the asynchronous process comprising:

retrieving telemetry data associated with the vehicle identifier;

retrieving maintenance records relating to current and past service visits of the vehicle across one or more service locations; and

generating the diagnostic report from the retrieved data.

2.(Original)The method of claim 1, wherein the incoming service request is received over a cellular network.

3.(Canceled)

4.(Previously Presented)The method of claim 1, wherein the diagnostic report identifies a component predicted to fail.

21.(New)The method of claim 1, wherein the asynchronous process completes before the incoming service request is assigned to the technician.

The Tedious, Error-Prone Tasks Version Story Replaces

1M+

office action responses filed with the USPTO every year

9 in 10

applications rejected at least once before allowance

53,000+

registered practitioners formatting amendments by hand

Precision Through
the Whole File Wrapper

Scanned filings, real redlines

Office actions and file-wrapper documents arrive as scanned PDFs. Version Story's OCR turns them into precise comparisons, no retyping required.

Word and PDF, any combination

Compare the specification you drafted in Word against the PDF the examiner mailed back — or any other pairing of formats — in one step.

Cross-references intact

References to claims, paragraphs, and figures keep their numbering, linking, and formatting through every comparison.

Two lawyers look out over the city from a corner office

See it in action

Enter the epoch of AI with redlining that scales