How to Build a Patent Asset Dashboard with Comparable Patent Counts
A patent asset dashboard is useful only when every panel can be traced back to a defined query and counting rule. Using a CATL battery-scope excerpt as a worked example, this developer guide explains how to build comparable patent-data panels while preserving scope, collapse logic, time windows, and API boundaries with the Build Patent Asset Dashboard Skill.
This excerpt comes from a real CATL battery-scope run using one APNO-collapse contract. It shows comparable query panels without presenting the result as CATL’s company-wide portfolio.
CATL battery-scope patent dashboard excerpt
The 2025 count is shown without calling it a decline because publication lag and coverage effects were not analyzed.
Each production panel should preserve these fields so the displayed number remains reproducible.
Supports
A reproducible query-level portfolio overview, annual windows, and selected authority comparison.
Does not prove
Company-wide portfolio size, mutually exclusive shares, filing momentum, ownership quality, or legal conclusions.
PBD · APNO · LATEST · Advanced Patent Search
Define the applicant, technology scope, counting unit, and cut-off first.
What this patent dashboard counts
The scope is CATL plus battery-related patent text, not every patent associated with the company. Every visible number uses the same representative-record rule: PBD, APNO collapse, LATEST ordering.
Patent-type and authority panels are separate filtered queries. They are useful comparisons, but they should not be summed into a portfolio total or treated as mutually exclusive strategic shares.
What the recorded run established
The run completed a total query count, three patent-type subsets, five application-year windows, and five selected authority queries. It did not complete classification distribution, authenticated REST response mapping, complete office coverage, or the final production dashboard.
The year panel shows 2024 as the largest displayed APD window. The lower 2025 value remains descriptive because publication lag and query coverage were not analyzed.
How the Skill builds comparable dashboard panels
The Skill first defines one panel contract: applicant scope, technology scope, query, counting unit, representative-record rule, cut-off, and expected fields. It then runs each total, type, year, or authority panel under that contract and keeps overlapping subsets separate.
This lets developers compare like-for-like values and trace every displayed number back to the request that produced it.
Prepare, configure, and run
Provide the legal applicant, aliases, technology scope, cut-off date, and counting unit. The authorized connection keeps its credential outside the prompt and output; the Skill should preserve the executed query and contract beside every returned panel.
Build a patent asset dashboard for [legal applicant] and [technology scope]. Use APNO collapse, PBD as the representative-record field, LATEST ordering, and a stated cut-off date. Return a total query count, patent-type subsets, application-year windows, and selected authority queries. Preserve every query and counting rule, do not sum overlapping subsets, and mark panels that require a different endpoint as not run.How to use the dashboard excerpt
Use the result to verify scope, compare like-for-like queries, and decide which panels deserve deeper record review.
Review next: confirm entity aliases, inspect representative records, add classification coverage, and verify REST-only panels before treating the dashboard as a production portfolio view.
Patent analysis backed by connected records
A reliable dashboard needs structured patent fields, stable applicant and family relationships, and explicit counting contracts. Patsnap patent intelligence supplies that data layer for comparable panels, while the Skill preserves query, collapse, and run boundaries; users must still validate entity scope and production API coverage.
Database foundationPatsnap links global patent bibliography, families, applicants, classifications, claims, legal status, citations, scientific literature, and enterprise signals. That connected database foundation makes the evidence easier to retrieve, reconcile, and audit.
Patsnap OpenPatsnap Open provides integration paths through APIs and MCP Servers so selected patent data and research tools can be used inside AI and enterprise workflows. The records support analysis; qualified reviewers still own legal interpretation and current-register checks.
Review the current patent API catalog
Confirm authentication, entitlement, endpoint schemas, and response fields before connecting the dashboard to production data.
Frequently asked questions
Is 43,604 CATL’s total patent portfolio?
No. It is the result of the defined CATL-and-battery query under one APNO-collapse contract.
Can the patent-type counts be added together?
No. They are filtered subsets and do not account for every patent state or category in the total query.
Does the 2025 value prove filings declined?
No. Publication lag, incomplete visibility, and query coverage must be reviewed before interpreting momentum.
Was an API key exposed to the Skill?
No. The authorized Advanced Patent Search connection handled authentication without exposing the raw credential in the prompt, article, or output.
