Cross-Project Intelligence (Early Access)

LOIS now has cross-project intelligence, enabling users to get answers about multiple project’s documents at once. 

With cross-project intelligence, a user selects multiple Filevine projects and makes a single request. LOIS makes the query for each project and returns the answers in a table, with a row for each project.

Cross-Project Intelligence

Until now, LOIS answered questions from one project's documents at a time. Users who needed the same answer across many cases often had to repeat the question for each project, or hit errors trying it in one long conversation.

With cross-project intelligence, a user can select up to 100 Filevine projects and ask one question. LOIS returns a table, with a row for each project. Each cell is a finding for that project, with linked sources. Optional extra columns can hold summaries or extracted fields.

Select Projects

In LOIS, click the project selector. 

Select the projects you’d like to include in the request. Select from the list of most recent projects, or search by project name, type, or project tag. Select all to select the currently-displayed list, up to 100.

Prompt LOIS

Cross-project intelligence is currently optimized for questions answered from a single project, then repeated. For example:

• Which cases have a policy over $1M?
• Which contracts contain specific language? 
• Which cases show evidence of a specific injury?
• Which of these contracts include a data processing agreement (DPA), and what is the breach notification period in each?

View Table

LOIS returns a results table that can be opened alongside the chat. The table has a row for each project. Projects that reviewed no findings are collapsed at the bottom of the table.

Click Full screen to view the results table in the full window. You can also Export the table as an .html, .md, or .csv file. A Sources panel, grouped by project, is available under the table view.

Click the project name to open the project in a new tab. Click the expand icon at the end of a row to open the summary and full analysis with numbered citations. Click Sources to view just the sources for that project. Switch directly between project details with the arrows or the dropdown menu. 

You can add for new columns or other changes in chat, and LOIS will generate a new table with that information. 

Continue the Conversation

You can continue the conversation with LOIS. The cross-project table becomes part of the conversation context, so users can ask follow-up questions about the results.

Reference Projects

Cross-project intelligence also opens up a new way to use projects. 

A project doesn't have to be a matter. It can hold a motion bank, a master file, expert opinions, or model filings. Projects used this way—as reference projects—can be used as source material and context for other projects. 

The functionality for this type of project already exists in Filevine, and many firms already engage with projects in this way. However, with cross-project intelligence, these reference projects allow users to answer a question about one case using reference material from other projects.

Ask about this case, and let LOIS draw on your master file, playbook, or past work for its answer. 

Using Reference Projects

To use projects as reference projects for LOIS, select the matter project and up to five reference projects. Star the primary project to indicate to LOIS that other projects should be used as reference. 

LOIS reads each project for the part of the question that fits it and returns one combined answer that cites each project and states which ones it used. LOIS writes only to the primary project, and if a project can't be read, the answer says so.

For example, a legal team keeps its data processing agreement (DPA) playbook, with its required terms, in one project and each vendor contract in another.

• Setup: Select both projects. Star the vendor contract as the primary project. The DPA playbook becomes the reference.
• Ask: "Based on the DPA playbook, which of this contract's data protection terms meet our requirements, and which do not?"
• Expected: A narrative answer that separates the terms that meet the playbook from those that don't, with citations labeled by project (requirements from the playbook, clauses from the contract).

Two Ways to Work Across Projects