Goal of the analysis:
The goal is to measure and manage the volume of invention disclosures (IDFs) submitted by employees, contractors, and collaborators, and to understand their quality, alignment to strategy, and conversion to filings. For executives, Invention Disclosure Count is an early indicator of innovation throughput and IP pipeline health. It helps ensure ideation is broad and sustained, not concentrated in a few teams or time periods, and that submissions are meaningful (patentable, commercially relevant) rather than volume for volume’s sake. A disciplined view supports resource planning for triage and drafting, focuses invention harvesting on priority domains, and improves the cost-to-value ratio of the IP program.
Data required:
- IDF intake and metadata:
- Submission ID, date/time, title/abstract, problem–solution statement, diagrams, keywords/CPC tags.
- Inventor(s) names, roles, site/business unit, manager, tenure.
- Linked R&D project/product/platform, strategic theme, market/application.
- Completeness score (required fields present), attachments, confidentiality/third-party input declarations.
- Triage and screening outcomes:
- Decision: approve to file (provisional/utility), defer, request more info, reject/publish.
- Reason codes: novelty/prior art, business relevance, overlap/duplicate, trade secret preference, cost constraints.
- Prior art search results (basic/advanced), similarity scores, conflicts with internal filings.
- Cycle times: submission→first review, submission→final triage decision.
- Process and pipeline metrics:
- Backlog and aging: IDFs pending review; % older than SLA (e.g., 30/45/60 days).
- Resubmissions/duplicates merged; cross-team collaborations.
- Downstream linkage: IDF→provisional/utility filing IDs; eventual grant status (lagging).
- Portfolio and strategy linkage:
- Mapping to product roadmap milestones, customer problems, and priority technology domains.
- Competitive targets/white spaces; standards engagement (if relevant).
- Financials and normalization:
- R&D spend by site/domain; R&D FTE counts and skill mix.
- Budget for IP triage, drafting, and prior art searches; outside counsel capacity.
- External indicators:
- Competitor filing trends in relevant CPC classes; citation hotspots; jurisdictional focus.
Detailed step-by-step instruction on how to conduct the analysis:
- Define scope and counting rules:
- Inclusion: all unique IDFs submitted within the period; exclude training or test entries.
- Deduplicate: consolidate multiple submissions of the same invention across teams/sites; maintain a link map.
- Define period views: monthly/quarterly cadence; rolling 12/24 months for trend; cohort views by submission quarter.
- Extract data:
- From IPMS/IDF portal (e.g., Anaqua, CPA, Foundation IP, in-house portals): IDFs, triage decisions, timestamps, attachments, reason codes.
- From PLM/PPM/ELN: project/product links, technology tags; from HRIS: inventor role/site/FTE counts; from finance: R&D spend.
- Optional: competitor intelligence from public databases (USPTO/EPO/WIPO/Google Patents).
- Cleanse and standardize:
- Normalize inventor identities, site/business unit labels, technology domains/CPC tags.
- Merge duplicate IDFs using title/abstract similarity and shared inventors; flag resubmissions.
- Ensure triage decisions and reasons follow a consistent taxonomy; backfill missing decisions if already filed.
- Compute core metrics:
- Invention Disclosure Count = number of unique IDFs submitted in the period.
- Normalized counts: per 100 R&D FTEs and per $10M R&D spend (overall and by domain/site).
- Quality proxies:
- Triage Conversion = IDFs approved to file / total IDFs.
- Completeness Rate = IDFs meeting minimum completeness criteria.
- Duplicate/Low-Novelty Rate = IDFs rejected for prior art/overlap / total IDFs.
- Process health:
- Aging = % of IDFs pending decision beyond SLA (e.g., 45 days).
- Median decision time and P90 decision time.
- Downstream (lagging) outcomes for older cohorts: Filing Rate and eventual Grant Rate linked to IDFs.
- Segment and compare:
- By business unit, site, product/platform, technology domain (CPC), inventor cohort (tenure/seniority), project type (platform vs. derivative).
- By campaigns/harvesting events vs. BAU submissions to assess initiative effectiveness.
- Trend and seasonality:
- Plot 24–36 months of IDF counts; identify spikes (e.g., year-end campaigns) and troughs (holiday periods).
- Use rolling 12-month averages to distinguish structural improvements from short-term pushes.
- Strategy alignment checks:
- Share of IDFs mapped to priority domains/roadmap milestones; heatmap vs. competitive hotspots.
- Identify gaps where priority domains show low IDF activity relative to plan.
- Capacity implications:
- Compare IDF inflow to triage capacity and drafting bandwidth; estimate backlog clearance time at current rates.
- Forecast filing and cost impact from today’s IDF cadence (assuming historical conversion rates).
- Synthesize and recommend:
- Pareto key drivers of low conversion or high aging; quantify value-at-stake (e.g., weeks to decision saved, cost avoided by reducing duplicates).
- Propose 3–5 actions with owners and timelines (e.g., targeted harvesting, triage SLAs, duplicate detection).
Format of the output of analysis:
- Executive summary: total and normalized IDFs, conversion to filing, process aging, alignment to strategy, top actions.
- Time series: monthly/quarterly IDF counts with rolling averages; annotation of campaigns.
- Funnel: IDFs → triage-approved → filings → grants (for historical cohorts), with conversion and aging overlays.
- Heatmaps: IDFs by domain/platform/site; alignment to roadmap priorities.
- Quality vs. quantity scatter by team/site (IDFs per 100 FTEs vs. triage conversion).
- Aging dashboard: pending IDFs by age bucket; SLA compliance trend.
How to interpret results:
- High IDF count with strong conversion and low aging indicates a healthy ideation and screening engine; ensure distribution isn’t overly concentrated in a few teams.
- High count with low conversion often signals low novelty/overlap or misaligned incentives (rewarding volume). Tighten triage criteria and training.
- Low count with high conversion may mean under-harvesting despite strong quality; run targeted campaigns in strategic domains.
- Rising backlog and SLA breaches suggest triage capacity shortfalls or decision bottlenecks; expect delays and inventor frustration.
- Large swings driven by year-end pushes can degrade quality; look for subsequent dips in conversion and higher duplication.
- Segment differences matter: discovery-heavy labs may produce fewer, deeper inventions; platform teams may generate steady, incremental disclosures.
Steps a company can take to improve on this measure:
- Front-end alignment and harvesting:
- Run theme-based harvesting aligned to roadmap and competitive white spaces; co-create with product and marketing.
- Time campaigns around major milestones (design freeze, prototype) to capture teachable inventions.
- Quality-by-design for IDFs:
- Standardize IDF templates with problem–solution–advantage, use cases, data, and known prior art.
- Provide exemplars and checklists; offer short clinics on patentability and claim scope.
- Triage process and SLAs:
- Establish cross-functional review board with clear criteria and 30–45 day decision SLAs; publish schedules.
- Introduce a “fast-track” lane for time-sensitive inventions (imminent disclosure or filing deadlines).
- Tooling and data:
- Enable duplicate detection via text similarity; integrate basic prior art search within the IDF portal.
- Connect IPMS with PLM/PPM to auto-link IDFs to projects and strategic themes; automate metric dashboards.
- Incentives and culture:
- Reward quality outcomes (filed/granted, strategic impact) rather than raw IDF counts; recognize collaborative inventions.
- Celebrate inventor contributions publicly; create mentorship between prolific inventors and new contributors.
- Portfolio discipline:
- Set thresholds for filing vs. publication/trade secret; maintain a “defer” queue with expiration to prevent backlog creep.
- Prune low-value topics early; focus drafting resources on high-impact, high-likelihood cases.
- Targeted responses to patterns:
- If duplicates are high: improve internal publication of filed concepts; run brown-bags to share coverage and avoid overlap.
- If certain sites underperform: deploy local champions, tailored training, and joint harvesting with central IP.
- If conversion drops in a domain: raise the bar for submissions, add specialist counsel, and refine search practices.
Benchmark comparisons:
General benchmarks:
- Normalized annual IDF volume: many mature engineering organizations see 20–60 IDFs per 100 R&D FTEs per year; high-performing, IP-centric cultures can reach 60–100+ with strong triage discipline.
- Triage Conversion: 20–40% from IDF to filing is common in disciplined programs; higher rates imply strong screening at source or a conservative disclosure culture.
- Decision SLAs: 30–45 days from submission to triage decision for 80–90% of IDFs is a practical target.
Segment- or industry-specific benchmarks:
- Software/ICT: higher IDF counts with smaller average claim scope; conversion varies widely by art unit risk appetite.
- Mechanical/electronics: moderate IDF rates; steady conversion and predictable prosecution.
- Life sciences/biotech: lower IDF counts per FTE but higher-value disclosures; conversion may be selective due to cost/clinical proof thresholds.
If robust external benchmarks are not directly comparable, build internal benchmarks by domain, site, and product line. Track rolling 12–24 month cohorts, compare to internal top quartile teams, and set targets that pair volume with quality and process health (conversion, aging, and downstream grant performance) to avoid incentivizing low-value submissions.
