Intake in Irys One

Reviews

A review is a set of documents and the questions you asked of them. Rows are documents. Columns are questions. Each cell is the answer that question got from that document, with the citation it came from.

Reviews lives at Intake, Reviews, the only child in the rail under Intake.

Older Multi-Doc Analysis links still work. They resolve to the same review in its new home, with a one-time notice saying so. Nothing was lost.

Starting a review

Pick the documents, then ask the questions. A review autosaves from the first document you pick, under an untitled name you can change. There is no run button to remember and no session to lose: a review is a saved view, and you come back to it.

Reviews open from three places. From Intake itself, from the Reviews entry in the rail, and from a table inside a conversation, which opens here with a line saying where it came from and a way back to the conversation. A conversation keeps a small preview of the table rather than the whole grid.

Answer shapes

Five shapes, and only these. Irys picks one from the way you phrased the question. Change it if it guessed wrong.

Shape	Returns
Text	Free text taken from the document.
Yes/No	A binary answer.
Number	A plain number.
Date	A single date.
Bullet List	Several items.

You can start a question set from a saved template, and save your own with Save as a template.

What a review costs you

This is the part worth understanding, because it changes how you work.

Anything that arrived through Intake has already been read. That reading is kept. When you put those documents into a review, the answers come back without the documents being read again.

The same applies to anything you add later. Adding one question to twenty-four documents that have already been read costs one question, not twenty-four documents, and nothing else in the table is touched. The old version of that job meant reading all twenty-four again.

It works in the other direction too. Add a question to an intake process and Intake will offer to ask it of the items already sitting in the register, because they were already read. Asking one new question of forty-six vendor agreements costs one question, not forty-six documents.

Reviews do not expire. Re-opening one, extending one, or adding to one costs only what is new.

There is no fixed cap on how many documents a review can hold. Past about forty you get a plain warning, and nothing stops you. Answers land document by document as they come, so you can leave the page and come back without losing anything.

Asking one more question

Add a column and it is answered against every document already in the table. Existing columns are not re-run and existing answers do not change.

When you write a question, Amplify can sharpen it: it rewrites the ask in the language the documents themselves use, so a clause that says the same thing in different words is still found. You choose whether to use the sharpened version or keep yours.

When a document cannot be read

Failure is named in the table, never quietly marked done. A banner says how many documents could not be read, and each one sits in the table with its reason. Each is retried individually.

Reason	What it means	What to do
Could not read the file	There is no text in it. It is a photograph of paper rather than a document.	Build the text layer, then retry.
Too long to read in one go	The document runs past the page limit for a single pass.	Read it in parts.
Nothing found	The document was read and the question has no answer in it.	Nothing. The cell is greyed, which is an answer.

Correcting a cell

Cells are editable. An edited cell shows your corrected value, a note that you changed it, and what Irys originally found underneath, with the citation kept. The original extraction is retained alongside your correction rather than overwritten by it, so an edited cell can never present itself as an extracted fact.

Saving a review as an intake process

This is the main way intake processes get made. Build a review ad hoc, find that it works, and promote it. The process carries its provenance, so it says which review it came from and how many real documents and questions it was built on.

The save summary tells you what you are turning on in plain terms: the number of questions, the threshold it routes at, and that a person decides what happens next.

The process is a copy taken at the moment you promote it. Editing the process later never rewrites the review it came from, and changes apply from then on. Nothing already in the register is moved or relabelled behind your back.

Authoring a process from scratch is possible and is the fallback, not the front door.

Exporting

Export is the frozen record of the table as it stands.

Format	What you get
XLSX	The table with citations as links.
CSV	Values only.
PDF	The table as a document.