Notes

You have gathered the patents, described your product, and read the mappings Patalyze produced. Now someone has to write the verdict. A note is where the investigation becomes a conclusion others can act on: a free-form rich-text document that lives in the research database, right next to the data it concerns.

A note at a glance#

Tables and dashboards hold the evidence; a note is where you say what it means. Here is the kind of write-up you might hand to counsel once the analysis lands.

It reads like a document, not a database: a title, a few sentences of judgement, a quoted warning and a checklist of what happens next. The publication numbers are live links; click one and you land on that patent. The conclusion and the evidence sit on one page.

Writing in a note#

A note is free-form. Start typing as you would in any document, press Enter for a new paragraph, and reach for Markdown shortcuts (# for a heading, - for a bullet, > for a quote) if you think in Markdown.

Select any text for a floating toolbar with bold, italic, headings, color and highlight, and type a colon to drop in an emoji. This is for shaping the text you have written; to add something new, reach for a block.

Blocks#

Text is only the start. Type / anywhere to open the block menu and insert without leaving the keyboard; filter by typing, then press Enter. The blocks fall into five groups.

Text#

The essentials of a written document: paragraphs, three heading levels, bullet, numbered and to-do lists, blockquotes and code blocks.

Layout#

Structure for longer notes: a table, a table of contents that builds itself from your headings, and a separator to break sections apart.

Images#

A resizable image with a caption, uploaded or pasted straight in.

Charts#

Drop a chart straight into the page from the slash menu and it behaves exactly like a tile on a dashboard: bar, line, area, pie, donut and tree charts, plus a single-number stat, each counting live records and redrawing as the database changes. A verdict can carry the evidence it reasons about, like which companies own the field.

Jobs#

A status block listing the running and pending analysis for the research database, the same block the executive summary shows while it fills in.

Links#

A note does not just sit beside the database; it points back into it, to the records and pages it concerns, and out to the wider web. Patalyze turns the right text into links as you write, so a write-up stays tied to the mappings and records behind it even as the analysis grows.

Patents#

Type a publication number, like US11888132B2, and it becomes a link to that patent. Patalyze recognises standard publication numbers, a country code followed by the number such as EP3866227A1, and resolves them to the record live as you type. Hover a link to preview the patent; click to open it.

Products#

Type a product's name and it links to that product the same way. Patalyze matches the names already in your research database, so a product becomes linkable the moment it is added. A name shared by more than one product is left untouched, so a link never points at the wrong one.

Pages#

Where a patent or product link opens a single record, typing the name of another page in this research links to that page, whether it is a table, a note or a dashboard, with the page's icon in front. Patalyze matches the page names in the database, so a page becomes linkable as soon as it is created.

External links#

For anything outside the database, links work as they do anywhere else. Select some text and paste a URL to link it, or type a bare address and Patalyze turns it into a hyperlink; the toolbar that appears on a selection lets you add, edit or remove one. External links open in a new tab.

Summary from workflow#

You do not always start from a blank page. Each workflow generates one note for you, an executive summary, and fills it in once the analysis finishes; while it runs, the note tracks the steps in progress. It calls out the highest-risk patents and the specific claim elements that read on your product, drawing on the mappings in the database. What it contains depends on which workflow produced it.

Freedom to operate#

A freedom-to-operate summary reads as a verdict on whether you can ship. It opens with a one-line call, Clear, Mitigation required or High risk, and a table of the headline numbers, then works down through:

• A risk deep dive: the highest-risk patents, each with its owner, its risk band, and the claim elements that read on your product with the evidence behind them.
• Geographic and legal exposure: the countries and legal statuses where those patents are live.
• Feature risk attribution: which of your product's features trigger the most high-risk hits, so the redesign targets that would clear the most overlap are named first.
• Recommendations: practical next steps tied to the data, from redesign priorities and licensing to invalidity review and third-party observations.

Infringement detection#

An infringement-detection summary runs the other way, as a verdict on which products practice your claims. It opens with a one-line takeaway and a core-insights table, then covers:

• A dataset overview: the top patent owners and the target manufacturers in scope, when more than one is present.
• A claim-score analysis: how the matches spread across the score bands and how concentrated the strongest ones are.
• Top targets: the strongest product matches, each with the patent it reads on, the match strength, and the claim elements it appears to practice with evidence.
• Geographic enforceability: the countries and statuses of the high-scoring patents.
• Recommendations: next steps, from closer claim-chart review and evidence collection to licensing or litigation on the strongest matches.

Either way the summary leads with the verdict, embeds charts for the distributions that matter, and links every patent and product back to its record. It is an automated first pass rather than a legal opinion, and from there it is an ordinary note: edit it, restructure it, add your own judgement, then hand it to your legal or product team.