A PRACTICAL HIGHQ GUIDE
HighQ iSheets.
A clearer structure for legal work.
Understand what iSheets do, plan your records and permissions, and choose how to bring spreadsheet data into HighQ. A practical starting point for law firms building a matter tracker, intake process or client workspace.
Discuss your iSheet projectIn this guide: iSheets explained · Setup checklist · Excel import · Workflows and applications
What are
HighQ iSheets?
iSheets are the structured data module in Thomson Reuters HighQ. They organise information into records and typed columns, with views and permissions for the people working with that information. Think of a shared register with a defined structure, rather than a workbook passed between colleagues.
For a law firm, the starting point might be a register of matters, client requests or key dates. Each row represents one item; its fields describe the information the team needs to capture and maintain. HighQ also supports Excel import and export, alongside API access for integrations.
Thomson Reuters maintains the official introduction to iSheets. The checklist below focuses on decisions to make before configuring a workspace.
An example: a client request register
Start with a request reference, a short description, an owner, a status and a target date. Agree what “in review” and “complete” mean before adding more fields. A useful first view could show open requests by owner; another could highlight approaching target dates.
This is an illustrative design, not a client case study. Decide separately which records and fields a client should be able to access, then test that access with the intended user role.
Plan the iSheet
before the fields.
Before creating or changing an iSheet, work through these five decisions with the people who will maintain it:
- Define one record. Decide whether a row represents a matter, a request or a separate action. Avoid mixing those concepts in the same register without a clear relationship.
- Choose the fields. Separate identifiers, status choices, dates and narrative notes. Agree required information, consistent choice labels and who owns each value.
- Design useful views. Write down the questions each role needs to answer. An owner reviewing their open requests may need different columns from a team member preparing a monthly report.
- Review permissions. HighQ supports access controls for iSheet views, columns and records. Check the actual permissions; do not treat a filtered view as proof that information is restricted.
- Test realistic exceptions. Include missing dates, a change of owner, a reopened request and an intended external user. Use sanitised test records before introducing live information.
Our HighQ consultancy and implementation work starts with these process and configuration decisions.
Import Excel data
into HighQ iSheets.
First decide whether you are creating a new iSheet, adding records to an existing one or updating existing records. Those are different import tasks. HighQ includes native Excel import; the Thomson Reuters import guide explains the platform routes and field-specific requirements.
When the spreadsheet layout needs mapping
Our Excel importer for HighQ iSheets provides a mapping and review workflow for creating new records in an existing iSheet. Select the worksheet and header row, connect spreadsheet columns to supported fields, review errors and download an outcome report.
It supports Excel and CSV files, but it does not update existing records or detect business duplicates. For those requirements, assess the native route or scope a separate workflow. The application page lists its supported fields and limits.
A small import test before the full file
Agree the destination fields, compare date formats and choice labels, and test a small sanitised sample. Check what was actually created and retain the outcome report. If an import only partly succeeds, reconcile confirmed records before retrying rows.
From iSheet records
to a working process.
A useful register gives the team a consistent view of the information. The next design question is what should happen when that information changes: who reviews a request, what needs approval and which exceptions require a person to decide.
For HighQ workflow automation, agree the trigger, responsible role and expected outcome before configuring rules. Test repeated changes and incomplete information as well as the expected sequence.
Did you know your iSheets could do this?
Explore custom dashboards, external reporting and more ways to use your HighQ iSheets, with examples of interfaces, document generation and connected workflows.
Where your process needs a focused interface or integration, we can scope custom HighQ applications. Our G-28 form generator, for example, uses a reviewed iSheet record to prepare an editable PDF draft. Configuration and testing are needed for each environment.
BEFORE WE BEGIN
Questions about HighQ iSheets.
Are iSheets the same as Excel spreadsheets?
No. iSheets organise shared records inside HighQ, with defined column types, views and permissions. Excel can be a source or destination for data, but the workbook and the live iSheet need their own agreed structure and ownership.
Do we need a custom application to use iSheets?
No. Start by assessing native iSheet configuration and import options. Consider a custom application when you have a specific interface, mapping or integration requirement that needs additional development.
Can you help improve an existing iSheet?
Yes. We can review the purpose of the register, field definitions, views, permissions and data import process. Bring a description of the problem and a sanitised example so we can agree a focused scope.
Where can I find HighQ iSheets product documentation?
Use the Thomson Reuters documentation linked in this guide for platform instructions. Oryon Legal is an independent consultancy providing configuration and development services; we are not Thomson Reuters.
04 — CONTACT
Have a legal
technology challenge?
Tell us what your firm has in mind.
Let’s find the right way forward.