This area is available on CORE plans. Some actions, such as adding sources or generating claim constructions, cost tokens to run.

Use Patent Details when you need to read a project patent closely and move between the patent text, its claims, and any claim-construction work tied to that patent. This area is built for target-patent review inside a project, so it keeps the patent viewer and the claim-analysis workflow close together instead of forcing you to jump between unrelated pages.

Patent Details lives inside a project, under the navigation for a specific target patent. In the target area, &AI shows a set of patent-focused pages, including:

Start on Patent when you want to read the document itself. Move to Claims when you are ready to build or review claim constructions. The surrounding pages give you the patent family, prosecution history, PTAB context, and charts that support the same target.

If you do not see a target patent in the project yet, add the patent to the project first. Patent Details is not a standalone workspace. It depends on having a patent record inside the project.

The Patent page is the core document view for the target. &AI supports a patent-reading workflow that is more than a simple file preview. Depending on the document and processing state, the page can show synchronized patent text and PDF content, searchable chunks, figure references, metadata, and claim-related information that other workflows reuse.

From the target patent entry, the current navigation exposes these document views:

Use Details to orient yourself around the patent and its metadata. Use Body when you want to read the chunked patent text, search within the document, and work with passages that later workflows can cite. Use References Cited when you need to inspect backward references connected to the patent.

The patent viewer is especially useful when you need to:

Patent Details includes both claim review and claim-construction work, but they serve different purposes.

Use the claim-review experience when you need to inspect the actual claims, verify claim structure, or edit limitations. This is where you confirm what the patent says and how the claims are organized.

Use the Claims page when you need to decide what important terms mean, gather evidence for those meanings, and approve working constructions. That workflow is about construing claim terms, not rewriting the claim text itself.

In practice, many teams move back and forth between the two:

Because the workflows are tied to the same target patent, approved construction terms can be reflected back into the patent-reading experience instead of living in isolation.

Patent Details is usually not the end of the workflow. It is the center point for several related patent-analysis tasks inside the same target:

That matters because claim review and claim construction rarely happen alone. You often read the patent, inspect claim text, review the family or prosecution context, and then continue into charting or drafting.

From here, review and edit claims if the structure needs cleanup, use claim construction for term definitions and evidence, or continue into prosecution, family, PTAB, or charts.