Embedded Approval Tracking in Electronic Documents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional electronic document platforms do not efficiently track approval requests and responses, leading to increased latency and resource consumption due to redundant approval requests, inefficient section-specific approval handling, and separate status tracking, which affects overall system efficiency and latency.

Innovation Solution

Implementing an approval data structure embedded within the content of electronic documents to track and manage approval requests and responses, allowing users to interact with approval requests and responses directly within the document, reducing redundant requests and improving workflow efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional separate tracking methods are used for approval requests, then approval status can be monitored, but system latency increases and resource consumption increases due to redundant requests

Engineering Contradiction:
Improveapproval tracking accuracyVSAvoidsystem latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines the approval tracking system with the electronic document structure by embedding approval data structures directly within document sections. This merging eliminates separate tracking systems, reducing system latency and resource consumption while maintaining accurate approval status monitoring through integrated real-time updates.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If conventional separate tracking methods are used for approval requests, then approval status can be monitored, but computing resource usage increases

Engineering Contradiction:
Improveapproval tracking accuracyVSAvoidcomputing resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The approval tracking functionality is merged into the electronic document structure itself, eliminating the need for separate tracking systems. This integration reduces computing resource consumption by consolidating data storage and processing within a single unified system while maintaining reliable approval status monitoring.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates embedded copies of approval data structures within each document section, allowing local tracking without requiring continuous queries to external systems. This copying approach reduces computing resource usage by enabling self-contained approval tracking at the section level.

Inventive Principle:
Principle #26Copying

3Productivity

If section-specific approval handling is implemented, then workflow efficiency improves, but device complexity increases

Engineering Contradiction:
Improveworkflow efficiencyVSAvoiddata structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the approval tracking system into section-specific data structures embedded within individual document sections. This segmentation enables independent section-level approval handling, improving workflow efficiency while managing complexity through modular, self-contained approval units rather than a monolithic system.

Inventive Principle:
Principle #1Segmentation

4Productivity

If approval data structure is embedded within document content, then real-time status updates are achieved, but device complexity increases

Engineering Contradiction:
Improvereal-time tracking capabilityVSAvoiddocument structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The approval data structure is merged directly into the electronic document content, enabling real-time status updates as users interact with the document. This integration achieves real-time tracking capability while managing complexity through unified data management that eliminates synchronization overhead between separate systems.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250371252A1Tracking approvals for an electronic document managed by an electronic document platform
Publication Date: 2025.12.04 GOOGLE LLC
  • US20250371252A1 patent drawing
  • US20250371252A1 patent drawing
  • US20250371252A1 patent drawing

AI summary

Access to an electronic document is provided to a first client device associated with a first user via a first application, with one or more entries of an approval data structure. When the first user engages with first GUI elements associated with the entries, indicating an approval request for a second user to approve portions of the content, the approval data structure is updated accordingly. The second client device is provided with access, via a second application, to the relevant content and approval data. If the second user engages with second GUI elements associated with the entries, providing a response to the approval request, a notification indicating this response is sent to the first client device.