# US 2026/0268005 A1 · Transaction Document Management System And Method

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0268005 A1
- Document ID: US20260268005A1
- Status: Published application
- Kind: A1
- Application number: 19/384,712
- Filed: 2025-11-10
- Published: 2026-09-10
- Earliest claimed: 2015-08-07
- Assignees: Workshare, Ltd.
- Applicants: Workshare, Ltd.
- Inventors: Ben Ridgway; Ted Sabety
- Web page: https://patentgrep.com/patent/US20260268005A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 16/93: Document management systems
- G06F 40/169: Annotation, e.g. comment data or footnotes
- G06Q 10/103: {Workflow collaboration or project management}
- G06F 2221/2139: Recurrent verification
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

This invention discloses a novel system and method for transaction document management where personnel from two sides of a business transaction involving one or more documents that constitute the transaction can interact with the system in order to automate the process of tracking executed signature pages associated with the documents. In addition, the system and method automates the tracking of exceptions to at least one of the documents and associating the exception with one or more documents comprising due diligence documents that may also reside on the system.

## Claims

### Claim at position 1

1-21. (canceled)

### Claim 22

A system for managing storage of a document, the system comprising:
a local computer for managing storage of a plurality of versions of a first document, the plurality of versions including a first version and a second version;
a server communicatively coupled with the local computer and having a database configured to:
store a file representing the plurality of versions,
store a data item corresponding to an authorized party,
store a data structure that maps the first document to (a) the authorized party and to
(b) a stored status item that represents two logical states associated with the first document,
determine one or more status flags associated with the first document,
transmit a list of documents that includes the first document and a second document,
cause displaying of (i) the list of documents and (ii) an indication that the first document is (1) ready for signature from the authorized party or (2) signed by the authorized party; and
a data record associated with the first document and including data representing an exception, the data record further including a bookmark that specifies a location reference within the first document.

### Claim 23 (depends on 1)

The system of claim 1, further comprising a remote computer with a display, the remote computer being communicatively coupled with the server and being configured to show on the display (i) the list of documents and (ii) the indication that the first document is (1) ready for signature from the authorized party or (2) signed by the authorized party.

### Claim 24 (depends on 1)

The system of claim 1, wherein the status flags are selected from a group consisting of ready for execution, executed, original, and markup.

### Claim 25 (depends on 1)

The system of claim 1, wherein the server is further configured to:
receive a data file;
receive an input that establishes a correspondence between the data file and one of the first and second documents;
receive a first input designating the data file as a signature page;
receive a second input selecting an authorized party associated with the data file;
in response to receiving the data file and the first input, update a status flag associated with one of the first and second documents to indicate that the authorized party has executed the document.

### Claim 26 (depends on 1)

The system of claim 1, wherein the server is configured by logic to limit uploading and storage of the file in response to a predetermined security protocol associated with the authorized party.

### Claim 27 (depends on 1)

The system of claim 1, wherein the server is configured by logic to limit an ability to update a status flag associated with the authorized party based on a predetermined security protocol associated with the authorized party.

### Claim 28 (depends on 1)

The system of claim 1, wherein the server is further configured by logic to execute a query that determines that all of the first and second documents are signed, based on which a further determination is made that a transaction associated with one or more of the first and second documents is closed.

### Claim 29 (depends on 1)

The system of claim 1, wherein the server is further configured by logic to:
embed in an uploaded file a visual or scannable code; and
update a data record associated with a corresponding one of the first and second documents, the data record being updated with an alpha-numerical value representative of the visual or scannable code.

### Claim 30 (depends on 1)

The system of claim 1, wherein the server is further configured by logic to:
store in a data record associated with each of the first and second documents a meta-tag that maps to a signature page in one of the first and second documents; and
upon receiving a command as input, use the meta-tag to generate a another file that includes all signature pages of at least one of the first and second documents.

### Claim 31 (depends on 1)

The system of claim 1, wherein the server is further configured by logic to:
determine a data listing with any documents that not associated with a status flag that indicates a signed status; and
generate another file that includes all signature pages of at least one of the first and second documents.

### Claim 32

A method for managing storage of a document, the method comprising:
managing, via a local computer, storage of a plurality of versions of a first document, the plurality of versions including a first version and a second version;
storing, via a server that is communicatively coupled with the local computer:
a file representing the plurality of versions,
a data item corresponding to an authorized party,
a data structure that maps the first document to (a) the authorized party and to (b) a stored status item that represents two logical states associated with the first document,
determining, via the server, one or more status flags associated with the first document;
transmitting a list of documents that includes the first document and a second document;
causing, via the server, displaying of (i) the list of documents and (ii) an indication that the first document is (1) ready for signature from the authorized party or (2) signed by the authorized party; and
specifying a bookmark to indicate a location reference within the first document, the bookmark being included in a data record that is associated with the first document, the data record including data representing an exception.

### Claim 33 (depends on 32)

The method of claim 32, further comprising communicating with a remote computer to display (i) the list of documents and (ii) the indication that the first document is (1) ready for signature from the authorized party or (2) signed by the authorized party.

### Claim 34 (depends on 32)

The method of claim 32, wherein the status flags are selected from a group consisting of ready for execution, executed, original, and markup.

### Claim 35 (depends on 32)

The method of claim 32, further comprising:
receiving, via the server, a data file;
receiving, via the server, an input that establishes a correspondence between the data file and one of the first and second documents;
receiving, via the server, a first input designating the data file as a signature page;
receiving, via the server, a second input selecting an authorized party associated with the data file; and
in response to receiving the data file and the first input, updating, via the server, a status flag associated with one of the first and second documents to indicate that the authorized party has executed the document.

### Claim 36 (depends on 32)

The method of claim 32, further comprising limiting, via the server, uploading and storage of the file in response to a predetermined security protocol associated with the authorized party.

### Claim 37 (depends on 32)

The method of claim 32, further comprising limiting, via the server, an ability to update a status flag associated with the authorized party based on a predetermined security protocol associated with the authorized party.

### Claim 38 (depends on 32)

The method of claim 32, further comprising executing, via the server, a query that determines that all of the first and second documents are signed, based on which a further determination is made that a transaction associated with one or more of the first and second documents is closed.

### Claim 39 (depends on 32)

The method of claim 32, further comprising:
embedding, via the server, in an uploaded file a visual or scannable code; and
updating, via the server, a data record associated with a corresponding one of the first and second documents, the data record being updated with an alpha-numerical value representative of the visual or scannable code.

### Claim 40 (depends on 32)

The method of claim 32, further comprising:
storing, via the server, in a data record associated with each of the first and second documents a meta-tag that maps to a signature page in one of the first and second documents; and
upon receiving a command as input, using, via the server, the meta-tag to generate a another file that includes all signature pages of at least one of the first and second documents.

### Claim 41 (depends on 32)

The method of claim 32, further comprising:
determining, via the server, a data listing with any documents that not associated with a status flag that indicates a signed status; and
generating, via the server, another file that includes all signature pages of at least one of the first and second documents.
