Lone Star Document Management LLC v. DocuSign Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Lone Star Document Management, LLC (Delaware)
  • Defendant: Docusign, Inc. (Delaware)
  • Plaintiff's Counsel: Devlin Law Firm LLC
• Case Identification: 1:26-cv-07801, N.D. Ill., 07/02/2026
• Venue Allegations: Venue is alleged based on Defendant Docusign maintaining a "regular and established place of business" in the district, specifically an office in Chicago that was established following its acquisition of SpringCM, Inc.
• Core Dispute: Plaintiff alleges that Defendant's content management systems, acquired through its predecessor SpringCM, Inc., infringe a patent related to the collaborative proofing and version management of electronic documents over a network.
• Technical Context: The technology addresses challenges in networked document collaboration by providing a centralized system to manage document versions, track comments, and control reviewer access in a pre-cloud computing era.
• Key Procedural History: The complaint alleges that Plaintiff offered to license the patent-in-suit to Defendant's predecessor, SpringCM, Inc., in October 2017. Defendant subsequently acquired SpringCM, Inc. in September 2018, which may form the basis for allegations of pre-suit knowledge and willful infringement.

Case Timeline

Date	Event
1998-12-17	'082 Patent Priority Date
2005-07-12	U.S. Patent No. 6,918,082 Issues
2017-10-13	Plaintiff offers to license '082 Patent to SpringCM, Inc.
2018-09-04	Defendant Docusign acquires SpringCM, Inc.
2026-07-02	Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 6,918,082 - "Electronic Document Proofing System"

• Patent Identification: U.S. Patent No. 6,918,082, "Electronic Document Proofing System," issued July 12, 2005.

The Invention Explained

• Problem Addressed: The patent's background section describes the difficulties of collaboratively proofing electronic documents over a network at the time of the invention (c. late 1990s). These problems included the need for collaborators to use the exact same software version and operating system, the use of proprietary file formats, and the lack of integrated features for tracking multiple document versions or comment histories Compl. ¶16 '082 Patent, col. 1:32-36 '082 Patent, col. 1:51-54 Even with the advent of "portable document formats," managing concurrent review by multiple parties and tracking versions and comments remained challenging Compl. ¶21 '082 Patent, col. 2:13-17
• The Patented Solution: The invention proposes a centralized, network-based system to manage the document proofing lifecycle '082 Patent, abstract A central computer receives and stores multiple versions of portable format documents in a database, associating them with authorized "proofer identifiers" '082 Patent, col. 3:60-64 The system is designed to receive comments from proofers and store them with the corresponding document version '082 Patent, col. 4:6-11 A key feature is the system's ability to receive a request from a proofer, retrieve the document and its associated comments, and format them for "simultaneous display" '082 Patent, claim 16 The system also describes a specific method for locating documents by assembling a URL from data stored in a database record '082 Patent, col. 5:22-33
• Technical Importance: The invention aimed to provide a structured, managed environment for collaborative document review, moving beyond the simple, ad-hoc file exchanges common at the time.

Key Claims at a Glance

• The complaint asserts infringement of at least independent claim 16 Compl. ¶14 Compl. ¶37
• The essential elements of independent claim 16 include:
  • A system for proofing electronic documents over a network.
  • A database storing portable format documents with at least one proofer identifier.
  • A computer that receives comments regarding the documents.
  • A program that associates and stores the comments with the documents.
  • The computer receives a review request from a proofer presenting the identifier.
  • The program retrieves a record for the requested document and assembles a URL pointing to it.
  • The program retrieves and formats the document with its associated comments for simultaneous display.
• The complaint reserves the right to amend its infringement contentions Compl. ¶38

III. The Accused Instrumentality

Product Identification

• The complaint identifies the "Accused Instrumentalities" as the "SpringCM, Inc. systems," which include "one or more hardware and software products for content management and related services" Compl. ¶37 These systems were acquired by Defendant Docusign and are now Docusign products Compl. ¶13

Functionality and Market Context

• The complaint alleges that the accused systems are used for content management and that they were implemented in "network architectures having features which utilized the patented invention" Compl. ¶14 Compl. ¶37 The complaint does not provide specific technical details on the operation of the accused systems, instead referencing an "Exemplary infringement analysis" in Exhibit 2, which was not publicly filed with the complaint Compl. ¶38 It is alleged that these systems provide "convenience and efficiency for its customers" Compl. ¶14

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint alleges that the Accused Instrumentalities directly infringe at least claim 16 of the '082 Patent Compl. ¶37 A detailed infringement analysis was reportedly provided in Exhibit 2 to the complaint, which is not available for public review Compl. ¶38 The infringement theory articulated in the complaint itself is that the accused "SpringCM, Inc. systems" for content management perform the functions recited in the elements of claim 16 Compl. ¶14 Compl. ¶37

'082 Patent Infringement Allegations

Claim Element (from Independent Claim 16)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a database of portable format electronic documents stored together with at least one proofer identifier;	The complaint alleges the Accused Instrumentalities include a database storing portable format documents with proofer identifiers Compl. ¶28	¶28; ¶37	col. 3:60-64
a computer connectable to the network for receiving a plurality of comments...;	The complaint alleges the Accused Instrumentalities include a computer on a network for receiving comments Compl. ¶28	¶28; ¶37	col. 4:6-8
a program executing on said computer for associating and storing the received plurality of comments...;	The complaint alleges the Accused Instrumentalities include a program for associating and storing comments with the documents Compl. ¶28	¶28; ¶37	col. 6:65-67
said computer for receiving a request, from a proofer presenting the proofer identifier, to review a particular portable format electronic document;	The complaint alleges the Accused Instrumentalities' computer receives review requests from identified proofers Compl. ¶28	¶28; ¶37	col. 3:65-col. 4:2
said program for retrieving a record corresponding to the requested document and assembling a URL pointing toward the document from data in the record; and	The complaint alleges the Accused Instrumentalities' program retrieves a record and assembles a URL to display the document Compl. ¶12 Compl. ¶29	¶12; ¶29; ¶37	col. 5:29-33
retrieving and formatting the requested document together with the associated plurality of comments for simultaneous display to permit review.	The complaint alleges the Accused Instrumentalities' program retrieves and formats the document with comments for simultaneous display Compl. ¶12 Compl. ¶28	¶12; ¶28; ¶37	col. 4:11-17

• Identified Points of Contention:
  • Technical Question: A central factual question will be whether the accused Docusign systems, which operate in a modern cloud environment, actually perform the specific step of "assembling a URL pointing toward the document from data in the record" as described in the patent '082 Patent, col. 5:10-22 The defense may argue that modern systems use different object-addressing or API-based methods that do not meet this limitation.
  • Scope Question: The meaning of "simultaneous display" of a document "together with" its comments will likely be disputed. The analysis may turn on whether a user interface that presents comments in a separate but concurrently visible pane or window satisfies this limitation, or if a more integrated presentation is required.

V. Key Claim Terms for Construction

• The Term: "assembling a URL pointing toward the document from data in the record"

• Context and Importance: This term appears to describe a specific technical implementation for locating a document file. Its construction is critical because if interpreted narrowly, it may not read on modern cloud-based storage architectures that may use different resource locators or identifiers. Practitioners may focus on this term as a potential non-infringement defense.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: A party could argue that this term should be interpreted functionally to cover any method of generating a unique, addressable link to a specific document version based on stored metadata, consistent with the patent's overall goal of providing access.
  • Evidence for a Narrower Interpretation: A party could point to the specification's detailed description of creating a directory tree and "past[ing] together as a string the , , , and ... to assemble on the fly a URUpath [sic]" '082 Patent, col. 5:29-33 This language suggests a specific, hierarchical file path string construction that may be narrower than a modern object URI.

• The Term: "simultaneous display"

• Context and Importance: This term is central to the user-facing functionality of the claimed invention. Whether the accused product infringes may depend on how its user interface presents documents and associated comments.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The term's plain meaning could support any presentation where the user can see both the document and comments at the same time on one screen, even if they are in separate frames, panes, or windows.
  • Evidence for a Narrower Interpretation: The claim requires formatting the document "together with" the comments for "simultaneous display." A party could argue this implies a single, unified view, rather than merely adjacent but separate interface elements. The specification's example describes viewing comments "in the same window as the proof" '082 Patent, col. 8:23-24, which could support a narrower construction.

VI. Other Allegations

• Willful Infringement: The complaint alleges that Defendant Docusign has had knowledge of the '082 Patent since at least September 4, 2018, the date it acquired SpringCM, Inc. Compl. ¶13 This allegation of knowledge is based on a letter sent by Plaintiff to SpringCM on October 13, 2017, offering to license the patent Compl. ¶13 These allegations of pre-suit knowledge may be used to support a claim for willful infringement and the request for enhanced damages and attorneys' fees under 35 U.S.C. § 285 Compl. p. 13, ¶C

VII. Analyst's Conclusion: Key Questions for the Case

• A core issue will be one of technical implementation: Does the architecture of Docusign's modern, cloud-based content management platform map onto the specific, late-1990s client-server mechanics recited in claim 16, particularly the requirement of "assembling a URL" from record data, or is there a fundamental mismatch in operation?
• A second key question will be one of claim scope: Can the term "simultaneous display," in the context of formatting a document "together with" comments, be construed broadly enough to cover the user interface of the accused Docusign product, or does the patent's language and specification require a more specific, integrated presentation that the accused product does not provide?
• Finally, an evidentiary question regarding knowledge and willfulness will be significant. The case will likely examine what knowledge of the '082 Patent Docusign inherited through its acquisition of SpringCM, Inc. and whether its subsequent actions constitute willful infringement.