Meet Vera AI VendorBenchmark is now Vera AI. Same team, same numbers. See what changed →
VendorBenchmarkUser manual PDFOpen the app →

18 · Migration & data-in

Everything on the platform gets sharper with data: benchmarks read your real deals, renewals watch real dates, and Vera answers from your actual estate. This chapter is the complete guide to getting that data in, whether you are carrying one quote, a folder, a whole contract estate, or an export from the tool you are leaving. It ends where every migration should: at a green Data health score.

The honest headline first: you do not migrate into this platform by retyping. Documents are read, registers are mapped, and your corrections always outrank the machine's guesses. The work that remains for a person is choosing, checking, and deciding, not data entry.


Choose your way in

Four ways in, sized to what you are carrying. They combine freely: most organizations use the folder in week one and the connectors forever after.

The way inBest forYour effortWhat is standing afterwards
One by oneA handful of documents, or anything you want benchmarked nowMinutes per documentAnalyst Benchmark in the analyst queue; agreements with watched dates
The folderYour contract folder as it exists today, up to 300 files a runOne drag, then answer three questionsThe estate filed by vendor, renewals flagged, an executive brief
The estateHundreds to thousands of documents, plus your contract registerA guided run with a sign-offA reconciled, quality-scored portfolio that goes live in one stroke
ConnectorsKeeping everything current from your other systemsAn owner connects each source onceContracts, invoices, and license data flowing in on their own

Two properties of intake worth knowing before you pick:

Contract Management: four screens

Where: Contracts & renewals › Contract Management · /office
Who: everyone in the organization

Every contract you have uploaded, in four screens: what you hold and what needs you, the full list, the dates ahead, and a report to send. Use it to see where the estate stands, decide a renewal before its notice date, give a contract an owner and tell the board. Press any contract to open it.

On the screen

How to use it

  1. Open Contract Management. Overview shows what you hold and, under Needs you, what to do first.
  2. Press Decide on a row and choose Renew, Renegotiate or Give notice. The choice is recorded on the contract with your name and the time, and the next step is offered: Open the Deal Agent, Draft the notice, or Ask for a price rise cap. Undo withdraws it.
  3. Press Assign owner on a contract nobody owns and pick a colleague. The owner is told when its dates come up.
  4. Press any contract to open it. Read its life and key terms on Summary, open Document to see where the contract says each one, and use Team to comment or to ask a colleague: pick Ask and a name beside the box and it goes on their list with a due date.
  5. On Renewals, move If prices rise by to see what next year costs at that rise.
  6. On Report, press Boardroom deck. Press Present to show the slides full screen (arrow keys move, Exit leaves), or Download PowerPoint.
  7. Press Email on Report, or Draft an email on a contract, to open the email client with a draft already written. Read it, change it, then copy it or open it in your own mail.
  8. Press Add a contract (N) and choose PDF or Word files, up to 25 MB each. Vera reads each one and files it under its vendor.

Tips

Related: Entitlement Agent · The whole estate: the Enterprise Uploader

The Contract Management Portal

Where: Contract Management › View › Earlier window · /office?classic=1
Who: everyone in the organization

This is the window Contract Management replaced on 5 October 2026. It is still here for the screens the four do not carry: Sign, Tasks and approvals, the key terms grid, the register, Benchmarks, the board pack and Files.

One window over the whole estate, built as a Windows application: twelve screens, one set of documents, one model every figure derives from. Use it when you want to copy contracts in, have them read, work the renewals, move files through their stations, watch the signatures, see where each deal stands, and stand back over every vendor you hold, without moving between screens. Opening any document hands it to the reader you already know.

Your Archive folded into this window in August 2026, so the estate has one window rather than two. /archive and its pages now redirect into the matching screen. Contract Management folded in on 25 August 2026 for the same reason, bringing its four unique boards with it: /agreements/command now redirects here, and a ?desk= link lands on the screen that took over its work. Each agreement's own file is untouched, at the same address as before.

The Contract Management Portal: the Contracts screen, the ledger by consequence beside the details
The menubar: File open, with the accelerator letters underlined
The sample estate over an empty estate, labeled in the caption and the status bar
Two documents open as tabs, split side by side, Compare one press away
The redline on an open document: their language against yours, the tracked change drawing live
New agreement: the template, the particulars, and the draft composed from your positions
The Contract Office's first screen: what needs you, the four figures in one row, the upload, and the contracts that need a decision

On the screen

The left side, from the top:

The tabs: six across the top, keys 1 to 6: Contracts with how many documents, Calendar with the key dates in the next 30 days, Renewals with what renews in 90 days, Spend, Tasks with what wants a person, and Reports. The screen's filter box sits at the right end of the row. The other screens are in the View menu and Ctrl K: Key terms (7), Benchmarks (8), Vendors (9), Search (0), Register and Sign.

The head, on every screen:

How it works: six stops under the head of the six tabs, from File by vendor to Report. Press a stop to go to its screen. Walk me through it explains the screen you are on, Ask the guide opens the guide, and the x hides the strip.

How the office works, in the Help menu: one screen with four figures, the upload, what needs you inside thirty days, and what each screen of the office is for. Back to work or Esc returns you to the screen you were on.

The inspector: four tabs down the right, and Ctrl I hides or shows it.

The status bar: the keys (1 to 6 the tabs, / search, J and K the rows, F full screen, G the guide, T talk to Vera, ? every key), then the estate in one line, what is selected and when the window last saved.

The grid — every list is a grid you can work: a sticky header that sorts when pressed, 52 pixel rows (40 with compact rows on), one line per cell with the rest in the tooltip, money right aligned in tabular figures with USD in the column header, group rows that carry the count and the money, a checkbox column and a header checkbox for selecting several rows (Ctrl click and Shift click do the same), and a 3 pixel bar on the selected row. Every grid has a column chooser (View, Choose columns, or the right click on the empty space), remembered per screen. A narrow grid scrolls sideways under its header rather than crushing the name column; the contracts ledger instead keeps the columns that fit and names the ones it set aside in its footer, so nothing sits off the edge unannounced. Benchmark is held back at every width because it carries a press rather than a fact, and Notice is the first to go.

The details — in the inspector's Details tab, for whatever you selected, with three tabs of its own. Details argues the row: the document's facts, the term as a timeline from start to end with today, the notice date and the vendor's quarter close on it, what the document says about notice and uplift with the quoted line and its page, the three questions where a benchmark exists (your discount, what peers are offered, where you rank, with the gap in money over the term), shown since 27 September 2026 with the rank on the ladder from Poor to Top of the market and the deal and the peer midpoint marked on the peer range, and under the term a notice lever that starts on the period the document states and moves the last day to give notice and the days left to act as you move it, the products on the order, your own fields, the family the document belongs to, and every stored version; one filled button in it does the thing the document needs. Scenario is the what if instrument: the uplift for this document (following the estate's lever unless you move it), the seat count where the document prices seats, the term in years, Next year, N ways as bars with the difference from today (renew as offered, hold the vendor to the cap the document states, hold the price, price at your ask), and the ask lever over the band of what peers are offered. Activity is the thread with a composer and every read and write of the document. With nothing selected the details show the estate: Where it stands, one chart for the screen you are on (where every document stands on Contracts, how much of the standard read is answered on Key terms, annual value by where each contract stands on the Register, how much is searchable on Search, where the benchmarked contracts rank on Benchmarks, what renews month by month on Renewals with the months holding a notice date in amber, and annual value by vendor on Vendors and Reports), then Moves, up to five next steps the figures ask for with the first one lit, each one press away, then the estate in figures.

The case room: double click a contract and it opens as its own room over the whole window: the plan, the key dates, the benchmark, the research, Vera, the comments, the files and the people. See The six tabs and the case room.

Open documents — a document opened in a tab (Open in a tab on the right click or in the Document menu, Ctrl+Alt+T) sits at the top of the content layer with its vendor and kind, and the screens stay one key away. A tab shows the document three ways: Document (the viewer with the inspector beside it), Read (the terms with their clauses) and Redline (the redline screen, below). Split puts the two most recent tabs side by side and Compare opens the comparison of the two. Ctrl+Alt+Right and Left walk the tabs, Ctrl+Alt+W closes one, Ctrl+Alt+S splits. Close the portal and open it tomorrow: the tabs are still there, up to eight.

The redline — press Redline on an open document (or Open the redline on the right click, Ctrl+Alt+R): their language against your clause positions, finding by finding, the tracked change drawing live as you edit, Accept, Edit or Reject each one, and one press composes the real Word redline onto the document's version chain. Send the redline as a task hands it to a colleague; Open the record opens the agreement file. A document with no record yet says so rather than opening an empty screen.

New agreement — File, New agreement (Ctrl N) starts a document from your own clause positions: pick the template (Mutual Non-Disclosure Agreement, Data Processing Agreement, Order Form, Statement of Work, Amendment or Contract Rider), name the vendor, and the draft composes with your preferred language where the library speaks and the template's own baseline where it is silent, marked in the draft. The customer, the governing law, the term and the parent agreement fill in from the vendor folder where they can. The Word file lands in the vendor folder as a document at Drafting, on the record's version chain, and opens as a tab; when their document comes back, the redline screen is one press away.

The twelve screens:

Notice windows, on Renewals: each row is a gray stretch up to its notice date, then the notice window to the term end in amber, or in red when it opens inside thirty days, with the days to the notice date at the end of the row. Press a row to select that renewal.

The right click, everywhere: any document answers a right click with the same menu, in this order:

Ctrl K — one palette for the whole window: your recent documents when the box is empty, then screens, vendors, documents, views, commands and your recent sessions as you type, and from three letters the passages in the reads with the page they sit on. Type ? first and the rest of what you type becomes a question for the estate.

The keys:

Tools: the Tools menu opens Compare two documents, Extract a table, Group by subject, Diligence review, Vault, Contract policy, Document Agent, Entitlement Agent and Import an existing estate, then the obligations register, the kept ledger, the board pack, the approval inbox and the signing commands. A tool that is a window of its own parks the portal on the taskbar while it is open.

The sample estate: Sample data in the title bar shows a labeled sample in place of your estate: five vendors, seven documents, a renewal due and a notice deadline named, so every screen can be walked, whether or not your own contracts are filed. The switch is yours alone and stays as you leave it (see Sample data). The status bar says sample data, nothing in it can be changed, and switching it off brings your own estate back untouched. An empty estate offers the same switch as See a sample estate.

Coming back: the portal remembers what you were doing: compact rows, every screen's columns and sort, the levers, the filter you typed, the documents you had open as tabs, a lens you were describing, an envelope half composed. Open it again, on any browser, and the work is there, no question asked. File, Continue where you were lists the last five sessions, and Start new in the same menu sets the current work aside rather than throwing it away.

Vera at the wheel — say the screen, a vendor folder, a document, or a lever value to the specialist on the seat and the window does it: open Renewals, show the Salesforce folder, put the uplift at three, compact rows, clear. Every driven change says what it did and can be undone. Signing, sending, deleting, moving and holds stay your own press; the seat can open the Sign screen and stops there.

Light or dark — View, Dark mode flips the whole account between light and dark without leaving the office (the same theme as the top bar switch, remembered across devices); View, Follow the Windows theme hands the choice back to your operating system. Every screen takes the night interior from the same tokens.

How to use it

  1. Open Contract Management Portal from the menu on the left. It opens as its own window with nothing loading behind it, from Home as well.
  2. Read the sentence in the head: it says what is at stake on this screen, and the filled button beside it is the first move.
  3. On Contracts, press Add documents and pick the files, or drag files or a whole folder onto the window. Every document is read as it lands and filed under its vendor.
  4. Press a row and read the inspector: the term as a timeline, what the document says, where the deal sits. Move a lever in Scenario and watch the money move.
  5. Double click a contract to open its case room: the plan, the key dates, the benchmark and the people on it.
  6. Press 3 for Renewals to work the year ahead, and / for Search to find a clause.
  7. Right click any contract to read it in the Contract Decoder, benchmark it, talk to Vera about it or get negotiation talking points.

When something goes wrong

The material

The window is a Windows application, not a page under frosted glass.

Tips

Where Contract Management went

What you came forWhere it is now
In motionContract Management Portal › Tasks (key 5), the board and the approval inbox
The estate (one row per vendor)Contract Management Portal › Vendors (key 9), the Vendors tab
The watch (rights and duties)Contract Management Portal › Vendors (key 9), Obligations and Rights
RenewalsContract Management Portal › Renewals (key 3)
Benchmarks (one row per vendor family)Contract Management Portal › Benchmarks (key 8), By vendor
The clockContract Management Portal › Reports (key 6), Cycle time
The archiveContract Management Portal › Contracts (key 1)
The enterprise migration wizardFile or Tools in the menus, Import an existing estate
An agreement's own fileUnchanged, at /agreements/command/<id>

Related: Files: the explorer, Key terms: reading the documents, Contracts: the renewals, Search: every word of every document, Vendors: every vendor you hold

The six tabs and the case room

Where: the Contract Management Portal, the screens down the left · /office?classic=1
Who: everyone in the organization

Since 13 October 2026 the window wears the cut every other app wears. Its twelve screens are numbered rows down the left, grouped as Documents, Portfolio and Work, each with the count it carries and the key that opens it; the row of tabs above the work is gone. Under a screen's name one sentence states its figures, and the screen's filter sits under that sentence. The details column leads with What to do now, the estate's first next move with the press that does it, and carries Your estate in figures as rows under the Details tab. The six screens you use most, keys 1 to 6:

The other screens are rows on the left too, and in the View menu and Ctrl K: Key terms (7), Benchmarks (8), Vendors (9), Search (0), Register (the renewals ledger, see Contracts: the renewals) and Sign.

The health mark. Every contract carries one of three words, with one line saying why: On track, Needs attention (a notice date inside ninety days, no owner, no decision, or a term the read was unsure of) or At risk (a notice date inside thirty days, or passed on a contract that renews on its own, with no decision recorded). It is worked out from the contract's own dates, owner and decision, so it changes the moment they do.

The case room. Double click any contract, or choose Open the case file on its right click, and the contract opens as its own room over the whole window. Esc closes it and puts you back where you were. Every tab carries the same frame:

Create a case file (since 1 October 2026), on the right click and in the Document menu, is a different thing: it saves the contract's case once, with its plan written back from the dates, and opens it in Case Rooms. A contract that already has one keeps it as it is and opens it.

The eight tabs, keys 1 to 8:

Plan, in three parts, on a contract (a supporting document points you to its main contract's case room):

Key dates: the term start, the notice deadline, the day the term ends or renews, the vendor's quarter close before it, the plan's open milestones and the dates you add (a QBR, a budget cycle, a board meeting).

Benchmark, in two parts:

Research: From the research library, the documents the library holds on the vendor, each one press from the reader, with Open the library on that vendor; Analyst briefs where there are any; What it means for this contract (the cap, the notice date, the vendor's quarter); and Ask the research agent, three questions and a box for your own.

Vera: five questions about this contract and a box for your own go to Vera with the contract named, and Talk to Vera opens the voice line.

Comments: the Comment board, with Post, Reply, Resolve and Reopen and an @ that tells the person, then Meeting notes from the contract's Teams Room.

Files: the contract and every stored version, its master and the documents under it (each with Open its case room), Link to a master where it has none, and Add a new version.

People: who can open the contract, each with their role; Give access by email as Can view, Can comment or Can edit; Assign an owner or Change the owner; Hand to a colleague; and The Teams Room with its open actions, or Open a Teams Room for this contract where there is none (Teams Rooms are part of the Enterprise plan).

The what if. The three sliders on Plan are the instrument: move the target below today's price, the cap on increases or the term, and the goal sentence and the three figures beside it move with them, on the contract's own price and uplift. The same inputs always give the same result, and the targets are saved with the room.

Follow ups (since 2 October 2026). Under Plan and Benchmark, once the contract has been read:

Four tools on the right click. Right click any contract, on any screen, and four tools sit under the case file, each opening on that contract:

A contract's case room: the goal and the targets, the plan Vera wrote from the vendor and the dates, and the aside with the next key date

Calendar: every key date

Where: the Contract Management Portal, Calendar on the left, key 2 · /office?room=calendar
Who: everyone in the organization

Every key date the portal knows, on a month: the notice deadlines still open (brick), the days contracts renew or end (navy), and each vendor's quarter and fiscal year closes (gold), taken from the vendor fiscal calendar as planning guidance rather than settlement dates.

  1. Use ‹ and › to page the months, and Today to come back.
  2. Press a kind in the key (Notice deadline, Renews or ends, Vendor quarter close) to hide or show it.
  3. Press a day: its dates list on the right, each with its kind and what the contract costs a year.
  4. Press a date, on the right or under Coming up, to open the contract's case room. Double click a day to open its first date. Right click a date for the document menu.
  5. Press Subscribe to the calendar in the head to put the notice dates and term ends in your own calendar as a feed.

Coming up lists the next twelve dates from today with how many days away each one is. The band above the month says how many key dates fall in the next thirty days and how many of them are notice deadlines.

Spend: the estate by annual spend

Where: the Contract Management Portal, Spend on the left, key 4 · /office?room=spend
Who: everyone in the organization

The estate by annual spend: a block per contract, sized by what it costs a year, grouped by vendor, darker navy for the larger vendors. The band above it says what you spend a year across how many vendors, and what share the top three take.

Settings: the window set up as you work

Where: the Contract Management Portal, File, Settings, or Ctrl , · /office
Who: everyone for the five personal pages; an owner for the eighteen organization pages

Settings is a screen of the window rather than a trip to another screen. Twenty three pages in two groups, the page list on the left and the page on the right. Nothing needs saving: a control applies as you change it, the status bar says so, and the change is takeable back for eight seconds like any other write.

You

Your organization

Views, exports and the family tree

Files: the explorer

Where: Contracts & renewals › Contract Management Portal › Contracts, the first tab, key 1 · /office?room=files
Who: everyone in the organization

The estate as a file manager. This is where documents come in and where they live. In the window the screen is the Contracts tab, and Your Archive (/archive) opens here.

From the top of the screen:

The Files inspector, Versions in the Details tab: every stored file of the document, newest first
Hand to a colleague: who, what to check, and by when
A comment anchored to the line, with the quote and the page
The Products tab: every line the deep read found on the order
The Positions tab: the document graded against your clause library

On the screen

How to use it

  1. Upload documents, paste them with Ctrl+V, or connect a source under Sources on the left. An empty estate also offers See a sample estate: a labeled sample to walk the screens with, the same switch as Sample data in the title bar. A document you drop on the sample switches it off and files into your own estate.
  2. Drag a row onto a vendor folder on the left to move it, or choose Move to a folder on its right click or in the Edit menu for the folder chooser. Views and smart folders take no upload. F2 renames one document and keeps its extension; Rename to house style renames a whole selection to Vendor, kind, date.
  3. Tick rows to act on many at once: index them, move them, set an owner, put them on legal hold, or delete them. A right click inside the selection acts on all of it.
  4. Put on legal hold stops a document or a whole folder being deleted and keeps the retention sweep away from it, until a person releases it.

Tips

Related: The Contract Management Portal, The whole estate: the Enterprise Uploader

Key terms: reading the documents

Your own fields. An owner defines the agreement types your organization files and the fields each one carries under Settings, Contract types: a cost center, a PO number, the signing entity and a contract number on an order form, a certification date on a ULA, each with a kind, a line of help and whether it is required. The New agreement wizard asks for the required ones and will not file the document without them. Every field is a column here, typed in the cell, and selecting rows and pressing Edit your fields sets a value on all of them behind one toast with one Undo. Types are yours to opt into: an organization that defines none sees the screen exactly as it was.

Where: Contracts & renewals › Contract Management Portal › Key terms, key 7 or the View menu · /office?room=index
Who: everyone in the organization · metered by plan
You get: the terms of every document in one grid, each figure anchored to the line it came from · about 40 seconds a document

Two ways to read, side by side.

The Key terms screen: the standard read, a custom lens, and the grid

On the screen

How to use it

  1. Choose the scope at the top: everything not yet read, documents needing a look, one folder, or the whole estate.
  2. Choose Standard read, or write a sentence under Custom read with Vera and press Show me the questions.
  3. Check the questions, name the lens, and press Save the lens if you want it again.
  4. Press Read N documents. The run is on the server: close the window, come back tomorrow, the grid is filled.
  5. Press any cell to see its evidence. Confirm keeps what the read found and records that a person checked it; Correct it replaces the value, saved with your name beside the read's own. Both work on every one of the nineteen terms, and changing one needs an editor's seat.

Tips

Related: Files: the explorer, Document Agent

Contracts: the renewals

Where: Contracts & renewals › Contract Management Portal › Register, in the View menu and Ctrl K · /office?room=contracts
Who: everyone in the organization

What renews, when notice is due, who owns it, and what everyone has said about it. In the window this screen is named Register. The Contracts tab is the folder view described under Files: the explorer.

The Contracts screen: the stake and the ledger, the views under Contracts on the left
Families: the master, its orders and its amendments as one tree per vendor, suggestions dotted
The Obligations tab: the document's own register, or the invitation to read it
Benchmark this document: the consent line before a request is spent
Put on legal hold: the reason box, and what a hold refuses
People: ranked by what they did, the invite composer with a seat
The counterparty room: the counterparty's link, shown once

On the screen

How to use it

  1. Press a renewal date on the row to change it. The notice deadline moves with it, and the renewal calendar is kept in step where an agreement exists for that vendor.
  2. Press the owner to assign one. The renewal owner follows.
  3. Use the inspector to record a decision (Renew as is, Renegotiate, Give notice), which then reads on the row with your name and the day; press the decision on the row, or Change beside it in the details, to pick another or clear it; set your own reminders, which reach you by email on the morning they fall due; read and add to the thread; and see who can see the contract.
  4. Or right click the row: the same moves, open, benchmark, obligations, assign, decide, remind, watch, move, rename, copy a link, legal hold, delete, without leaving the ledger. The link opens that exact contract for anyone in your organization.
  5. Benchmark this document (Ctrl+Alt+B, on the right click, in the Document menu, and in the inspector's Details tab) runs the benchmark on the document's own figures after a one-line consent, uses one benchmark request, and saves the three answers on the contract: your discount, what peers at this size are offered as a range with its midpoint, and the rank (Poor, Below market, At market, Good, Top of the market) with the gap in points and in money over the term. The rank then reads in the ledger's Benchmark column and in the inspector's Details tab, with The report beside it and Benchmark it again when the figures change. Up to ten selected documents run in one press.
  6. The Obligations tab (Ctrl+Alt+O) is the document's own register: the rights you hold and the duties you owe, each with the clause it was read from, the day its window closes and the days left, its status and its owner. Mark a row Exercised or Dismiss it with a note; both are undoable from the toast. A document the read has not been over yet leads with Read the obligations, which uses the AI read once and files what it finds.
  7. Put on legal hold (Ctrl+Alt+L, on the right click and in the Document menu) asks why before it holds, and the reason, who set it and the day then read on the record, in Properties and in the trail. Nothing on hold can be deleted, replaced by a new version, or taken by the retention sweep until Release the hold, which shows the reason it was set before you release it.
  8. People ranks everyone who can see the document by what they have done to it, shows pending invitations with the day they expire, and holds the invite composer: an email and a seat (Can view, Can comment, Can edit), then Send the invite. A colleague already in your organization sees the document at once; a new address gets an invitation by email, valid 7 days, their seat counted against your plan, and access to this document and its thread when they arrive.
  9. The counterparty room opens this document's record to the counterparty with no account: the document, the open issues and the thread, nothing else, for 30 days. The link is shown once, so copy it then; opening a new room revokes the old one, and Revoke ends it early.

Tips

Related: Renewals, Agreements

Search: every word of every document

Where: Contracts & renewals › Contract Management Portal › Search, key 0 or / · /office?room=search
Who: everyone in the organization · Ask the estate requires an AI plan

Two questions, two engines: where does it say that, and what does my estate say about this.

On the screen

How to use it

  1. Type what you are looking for and press Enter.
  2. Narrow it with an operator or by selecting a vendor.
  3. Press a hit to read it in context, then Show on the document to open it in the reader on that line.
  4. Press Save this search and it joins Smart folders on the left of the Contracts tab, answering itself again every time.

Tips

Related: Document Agent, Key terms: reading the documents

Benchmarks: where every agreement stands

Where: Contracts & renewals › Contract Management Portal › Benchmarks, key 8 or the View menu · /office?room=market
Who: everyone in the organization · the run requires an AI plan

Every agreement you hold, placed against what comparable buyers pay for the same product at the same size. Since 25 August 2026 the screen ranks two ways, and the switch at the right above the list chooses: By agreement, which places each document, or By vendor, which places the whole relationship. The vendor lens came from Contract Management's Benchmarks screen when that console folded in.

On the screen

By agreement

How to use it

  1. Press 8, or choose Benchmarks in the View menu.
  2. Press Benchmark the estate. The dialog says what the run costs and how long it takes; nothing starts until you confirm.
  3. Leave if you like. The run keeps going and a notification brings you back.
  4. Press a band in the filters to see only those, and a row for the reasoning behind its rank.
  5. From a row, Benchmark it opens the full placement, Plan the renewal puts it on the renewal ledger, and Open the document hands it to the reader.

Tips

By vendor

How to use the vendor lens

  1. Switch to By vendor and read the four figures. The opportunity figure is the size of the prize; the below-market figure is where it lives.
  2. Select the top row, which is already ordered by consequence, and read the file: the rank, the gap, and the basis.
  3. Pull the lever to the peer midpoint. That number is the annual value of the mid ask; take it into the renewal or open the family's report for the full case.
  4. Work the not-placed families last: each row names the one missing input or the one tool that places it.

If the vendor lens looks wrong

Related: Contracts: the renewals, Benchmark Library, Vendors: every vendor you hold

Workflow: the files in motion

The approval inbox. The Approvals view is a list of decisions rather than a kanban board. Every row names what is being approved, whose hand it waits on, how many days it has sat, the rule that held it and the benchmark on the document, and Approve moves the matter to its next station with your name and the day on the record. In Settings, Approval rules you can hand your approvals to a colleague between two dates, so nothing waits on you while you are away; a stand in decides under their own name, and both of you and an owner can see who was covering for whom. Select an approval and the details draw its chain: each person it passes through in order, a tick under the ones who approved with their name and when, the one it waits on glowing, and a red cross where it was sent back. An approval nobody clears is put to an owner overnight. That overnight pass moves who is asked and never decides.

Where: Contract Management Portal › Tasks in the tab row, key 5 · /office?room=workflow
Who: everyone; moving a file needs edit access, approving needs an owner or approver seat

In the window this screen is the Tasks tab. The estate's files in motion, six stations on one board: Requested, Drafting, In negotiation, In approval, Executing, In force. Each matter is an agreement record with the money on it, its owner, and a clock showing how long it has sat at its station; the clock warms as it approaches the station's target and goes brick past it.

The right click on a matter: move, assign, comment, start a workflow, open the record or copy a link
Defining a workflow: named steps with an owner, a due window and a note to close
A workflow running on a matter: the steps, who each is on, and the closing notes

On the screen

How to use it

  1. Press 5 in the Contract Management Portal.
  2. Drag a matter one station to the right when its work is done; the board refuses a skipped gate by name.
  3. When the sentence at the top says something waits on you, press Approve and the file moves itself when the last gate clears.
  4. Open Reports and its Cycle time board when the question is not what is stuck but why everything takes as long as it does.

Related: Track agreements and never miss a notice window, The agreement file

Sign: the envelope screen

Where: Contract Management Portal › Sign, in the View menu and Ctrl K · /office?room=sign
Who: everyone; remind, re-route and void need edit access

Send a document for signature and watch what happens to it. Every envelope in the estate sits on this one screen, whichever service carried it: VendorBenchmark Sign, DocuSign, or Adobe Acrobat Sign. What needs a hand sorts first.

In plain words: upload a PDF, say who has to sign it, put the boxes on the pages, and send. The screen tells you who opened it, when, and who has signed.

The signing screen: what is still to come, the chain on the row, and the whole trail beside it

On the screen

New envelope, in three steps

  1. The document. Drag a PDF to where it says Upload the PDF here, browse for one, or press Take one off the estate and pick a document already filed. Whatever you pick is pinned: the signers sign exactly what you sent, never a later version.
  2. The recipients. A name and an address each, and what they are here for: Needs to sign joins the chain and gets a personal link, Receives a copy gets no link and no turn and is emailed the executed copy at the end. A job title and a company here fill the matching areas on the document by themselves. Choose One after another (each signer is emailed when the one before has signed) or Everyone at once, and how long the links live. A signer's row also sets their Identity checks, Code by email and Access code, which start on your organization's defaults from E-sign Settings; Code by email for everyone and Email link only for everyone set every signer at once. See E-sign, identity checks.
Placing the areas: twelve kinds in the list, the area on the page, its settings beside it
  1. The areas. Twelve kinds, dragged onto the pages and colored per signer. Signature and Initials are drawn from the signature they adopt. Date signed, Full name and Email fill themselves. Job title, Company, Text box, Number, Checkbox, Dropdown and Choice buttons are asked of the signer; each one takes a label, a required flag, and a value you can fill in yourself and lock so your answer stands: a text you type, a choice you pick for them on a dropdown or choice buttons, or a checkbox that starts selected. A locked area wears the lock on the page, and the signer sees your answer rather than a box to fill.

What happens after you press send

How to use it

  1. Choose Sign in the View menu of the Contract Management Portal, or type sign in Ctrl K.
  2. Press New envelope, on the line under the head or in the Document menu, and work the three steps. An envelope can also start from an agreement file at the Executing station; the signing studio there places the same areas. An envelope you leave half composed is kept: the next time you open the portal, on any browser, it is offered back, and Start fresh puts it away.
  3. When the chain stalls, open the envelope in the inspector: if the signer never opened it, press Remind; if they have opened it four times, the hold-up is a decision, not the inbox, and a phone call beats a fourth email.
  4. When the signer has changed jobs, press Re-route.
  5. To find something already executed, press Executed and read down the months.

Related: The agreement file, The API, MCP, and agent-to-agent

E-sign

Where: Your apps › E-sign · /esign
Who: everyone; sending, reminding, re-routing and voiding need edit access

In an agreement's own file, what you choose reads in gray and ink, never the accent green: the template you draft from, the signing provider, the routing mode, the field type you arm to place, the clause you select in the reading room, and the move you are on in the landing.

E-sign is the app for signatures, one of Your apps on Home since 23 September 2026. It reads the same envelopes as the Sign screen above, in a window of its own with five screens: Envelopes, Prepare, Tracking, Archive and Read and watch. Jump to… finds it under e-sign, signature or DocuSign.

Since 9 October 2026 the numbered Screens list at the top of the left menu moves between Envelopes, Prepare, Tracking, Archive and Read and watch, and each screen opens with one plain sentence of its figures. The first card in the details column on the right says what to do next and has the button that does it.

In plain words: see what waits for your signature, send a new envelope, follow one envelope to the signed copy, and find anything already signed.

E-sign on its Envelopes screen: the menu of envelope groups and the archive on the left, the Envelopes head, and the first envelope to send
E-sign with envelopes in every group: one waiting for your signature, one waiting for others, one signed and one declined, with the selected envelope's recipients and actions in the details on the right

On the screen

How to use it

  1. Press E-sign under Your apps on Home.
  2. Start on Action required: select an envelope and press Sign now, or S. Your signing page opens in a new tab.
  3. To follow one you sent, double-click it, or press Enter, to open it on Tracking. If the signer opened it and has not signed, press Remind, or R: they get a new link, and the one they already have keeps working. If they have left the company, press Re-route a signer.
  4. Press New envelope, or N, to send a document; the five screens are also on keys 1 to 5, and the arrow keys move the selection.
  5. To find a signed agreement, press Archive and pick its folder, or search.
  6. To file one, drag it onto a folder, or right-click it and choose the folder.
  7. When a link is locked, you are emailed. Open the envelope on Tracking, select the signer and press Unlock: they get a new link, and a new access code shows for you to give them.

Identity checks

Where: E-sign › Prepare, a signer's row, and E-sign › Settings · /esign
Who: anyone sending sets them per signer; owners set the defaults

On top of the emailed link, a signer can be asked to prove it is them before the document opens. Checks are set per signer, and nothing of the document shows until every one passes: not its pages, not the signing order, not your message.

Routing

Where: E-sign › Prepare, Routing at the top of the composer · /esign
Who: anyone who can send an envelope

Routing shows who signs in what order as steps, top to bottom, with the people who receive a copy at the foot. Everyone in a step receives the envelope at once; the next step starts when every signer in it has signed.

Viewing time per page and a reminder schedule are on their way in later stages; nothing on these screens stands in for them. Saved signatures are here: see Your signatures and signing several at once.

Related: Sign: the envelope screen, The agreement file

Assign to someone else

Where: the signing page, beside Decline to sign, and E-sign › Settings · /esign
Who: the recipient whose turn it is; owners allow or stop it

A recipient who is not the right person to sign can hand the envelope to a colleague, with the colleague's name, email, job title if they like, and a reason.

Related: Routing, Identity checks

Your signatures and signing several at once

Where: E-sign › Settings, Your signatures, and E-sign › Envelopes, Sign all · /esign
Who: anyone who signs their own envelopes

Related: Identity checks, Routing

Verify a signed copy

Where: E-sign › a signed envelope's details, Verify a copy, or the link printed on every certificate · /sign/verify
Who: anyone holding the PDF; no account is needed

Proves that a PDF is, byte for byte, the signed copy on record, and so that nobody has changed a word, a figure or a signature since the last person signed.

In plain words: drop the signed PDF on the page and it says whether this is exactly the copy that was signed.

On the screen

How to use it

  1. In E-sign, select a signed envelope and press Verify a copy in the details, or open the address printed on the certificate.
  2. Drop the PDF you were sent, or press the drop zone to choose it.
  3. Optionally type the Envelope ID from the top of any page.
  4. Press Check the file and read the answer.

Tips

Related: E-sign, Identity checks

Vera in the Loop

Where: Your apps › Vera in the Loop · /docusign
Who: everyone; turning Vera on and setting the loop rules (templates, corporate policy, approvers and what Vera reads) is owners only, and an approver decides only on their own turn

Vera in the Loop puts Vera between an offer and its signature. Every envelope your team sends through DocuSign reaches Vera before anyone signs: she reads the documents, benchmarks the deal, checks it against your templates and your corporate policy, and writes a two page signing brief. The people you name approve it, and the signer signs in DocuSign with Vera's call in hand. Every contract signed in DocuSign or Coupa is filed in Contracts automatically, whether it went through the loop or not. Nothing changes in DocuSign: the envelope goes out to its signers as normal. It was called Vera for DocuSign until 7 October 2026, and has been one of Your apps on Home, beside E-sign, since 29 September 2026. Jump to… finds it under DocuSign, Coupa, signing brief or approvers.

In plain words: connect DocuSign once and set the rules; every offer your team sends for signature then gets a two page brief, passes the people who approve it, and is filed the moment it is signed.

On the screen

The window: six steps, Loop, Read, Brief, Approve, Sign and Filed, numbered across the top and on keys 1 to 6. It wears the frame every app shares: the menus, Talk to Vera and the window buttons in the title bar, one navy column on the left, and the details on the right.

Loop (1): how an offer reaches Vera. First a drawing of the loop, from the offer arriving to a signed, filed contract (Play the loop runs it again). Then every offer in the loop: the vendor and the subject, how it came in and who sent it, its value over the term, Vera's call and its rank, five dots for how far along it is, and the day it arrived. Press an offer to open it. Under them, three panels:

Below the panels, the three rules in force, Templates, Corporate policy and Approvers, each with Edit.

Read (2): what Vera checked on the offer in view, one line each with what it found: the envelope arrived, the file checks, every page read, the price against comparable buyers, the terms against the market, your corporate policy, the template that applies and the brief. What Vera found sets the result out as chips: the value over the term, the discount, the rank, the terms that read worse than the market, the money on the table and Vera's call. While Vera reads, a clock counts the time and the screen moves on by itself when she is done.

Brief (3): the signing brief on two A4 pages, written for an executive with five minutes. Page 1 says what the agreement is, Vera's call and why, the key facts, what is being bought line by line, the money by year, what is good, what to watch, and the three things to settle before signing, with who does each and by when. Page 2 is the benchmark: where the deal ranks, the discount against what comparable buyers sign, the terms against the market, the asks in the order to ask and what each is worth, the corporate policy and template checks, the dates that matter and the bottom line. Show both pages or one, at full size or fitted to the window; Download PDF prints it to a PDF. Send back with the asks has Vera draft the email to the vendor in Mail. Until Vera has written page 1, page 2 shows the finished benchmark. The What if in the details column moves the discount and shows the money over the term and the rank that discount would earn, on this deal's own figures.

Approve (4): the people who approve before signature, as the loop rules set them: In order, Everyone or Any one. The chain shows Vera's review, each approver with their decision, their note and when they decided, whose turn it is, and the signer. On your turn, Approve or Reject, with a note for the signer if you want one; your name and the time go on the envelope and in the audit log. The corporate policy and the template checks sit below, each rule or point marked met, breach, departs, missed, partly or unclear, with the clause that decides it. Email the approvers has Vera draft the request in Mail.

Sign (5): for the signer: the envelope as it stands in DocuSign and the note Vera drafts for them, Vera's call with the rank, the things to settle before signing, and how many terms are good and how many to watch. Open in DocuSign to sign opens the envelope in DocuSign, where it is signed. Email the signer from Mail sends Vera's note, with the approvals and the things to settle; nothing sends itself.

Filed (6): once DocuSign returns the signed copy, where it went: a record in Contracts with the signed copy (Open in Contracts), the renewal and notice dates on the renewals calendar, the signed text indexed for search and Vera, and the price and rank kept in the Benchmark Agent's ledger. Beside it, the audit trail of who sent, read, approved and signed, and when, and under it the key terms from the brief. At the foot, every contract signed in DocuSign or Coupa that reached Contracts, filed whether it went through the loop or not.

Loop rules: a panel from the right with five sections, opened from the left column, the Loop step or the moves. Everyone can read them; owners change them, and a change applies from the next envelope.

The email. When the brief is written, Vera emails it: her call, the benchmark, the things to settle before signing and a link to the brief. It goes to the sender when their DocuSign address belongs to an active member of your workspace, to the approvers, and to the addresses an owner lists. A signer outside your organization never receives Vera's brief. With Review every contract on, or with approvers named, it goes whatever the deal's value.

Research more: in the moves on any offer and on the Brief step. It opens what the research library holds on the vendor, each note opening in the reader, with Talk to Vera about it to go further.

The sample envelope: Load the sample envelope shows the loop end to end on an Oracle Fusion order form, with its brief, before DocuSign is connected, marked as a sample wherever it shows; Remove the sample takes it out. Sample data in the title bar is the same switch: on adds the envelope and off removes it, for everyone in the workspace.

Delete this envelope, in an offer's moves, removes it from the loop; nothing changes in DocuSign, and the benchmark report stays in the Benchmark Agent's ledger.

Related: E-sign, Benchmark Agent

Renewals: the decision runway

Where: Contract Management Portal › Renewals in the tab row, key 3 · /office?room=renewals
Who: everyone in the organization

Vera's read of this screen. At the top of Renewals, Vera sets out three moves from what is on the screen, each with one press: Decide this week (the contract whose notice date is soonest or has passed, with its value; opens its case file), Start the big one early (the largest renewal in the year ahead and its notice date; opens its case file) and Stop the silent renewals (how many contracts renew on their own and what they cost a year; asks Vera which to decide first). Under them, three questions go straight to Vera with the screen she can already read, a box takes your own, and Talk to Vera opens the voice line with the three moves as its opening.

Every renewal placed by the day it must be decided: the last day written notice still stops a renewal, or the day a term simply ends. The runway draws each one at that date, sized by the money on it and colored by urgency and by whether a decision with a name on it exists; brick means undecided and closing, green means decided.

Across the top, the twelve months read as one timeline: each month a column on a thin line, the current month named on a quiet gray fill, and a bar under a month when money renews in it (red for a passed notice, amber for one inside ninety days, green when it is on track), with the sum at its foot. Draft the notice letter sits beside the next notice date, and the uplift lever sits at the right above Vera's read.

Your calendar: the private feed address, the webcal link, and the rotation
The notice letter, drafted from the document's own dates; nothing sends from here
The autopilot: what it does, what it would work, and the switch for the whole organization

On the screen

How to use it

  1. Press 3 in the Contract Management Portal.
  2. Work the runway left to right: the first brick dot is the next undecided deadline.
  3. Press a dot, decide, set your reminders, and subscribe to your calendar once so the dates live in Outlook too and stay current. The one-off .ics export is still there for a calendar that cannot subscribe; every event carries the day it was written and an end, so Outlook and Google accept the file as it is.
  4. When the decision is to leave, press Draft the notice letter, post it from your own mail, and record the exit.

Related: Contracts: the renewals, Renewals

Vendors: every vendor you hold

The register. Vendors opens on every duty the estate owes rather than one document's: set the owner on the row, give it a date, make it repeat, snooze one that is not due yet, and close it with the letter or the receipt that proves it. The evidence then sits on the row and on the trail.

The trail. The audit trail covers the whole estate, filtered by person, by kind and by month, reading on past the first sixty events, and exports in one press with names and titles rather than ids. A row the estate cannot attribute says so rather than guessing a name. People says what each colleague sees, folder by folder, and the grant is enforced by the database rather than by this window: it narrows that colleague everywhere in the platform. A colleague with no folder granted sees the whole estate, as everyone does until a folder is given.

Where: Contract Management Portal › Vendors, key 9 or the View menu · /office?room=estate
Who: everyone in the organization

The standing view over the whole relationship set, and the one screen that answers "what do we actually hold, and what is it about to cost us". Seven tabs, one screen: Obligations, Rights, Holds, Kept, Audit trail, People and Vendors. The Vendors tab rolls the ledger up per company, and Obligations and Rights list every duty your documents ask of you and every right they grant you. Both came across when Contract Management folded into this window on 25 August 2026; the arithmetic is the same, so no figure changed in the move.

In plain words: one row per company you buy from, and one list of every deadline hiding in the document.

Under the head, one line says what needs doing first on the tab you are on (the duty that is overdue, the hold to place, the notice to draft), with its action as a button beside it. The figures below run as one quiet row of labels and values.

On the screen

The Vendors tab

Obligations and Rights

How to use it

  1. Press 9 in the Contract Management Portal.
  2. Open the Vendors tab, read the headline, then work the top of the list: it is already ordered by what each relationship costs a year.
  3. Pull the lever to what you believe a renegotiation lands, and take the resulting figure into the renewal.
  4. Switch to Obligations and Rights and work what closes inside thirty days first. A right that lapses is money you paid for and did not take.

If something looks wrong

Related: Rights register, Contracts: the renewals, Vendors

Reports: the estate in figures

Where: Contract Management Portal › Reports in the tab row, key 6 · /office?room=reports
Who: everyone in the organization

The estate argued in figures, drawn to be forwarded. Six boards (Spend by vendor, The year ahead, Cycle time, Standing and coverage, Kept and The brief) over the same rows every other screen reads, so this screen and the Register can never disagree, and a sharing menu beside them, because Reports is live for everyone in the organization: collaboration here is a link, never an attachment that goes stale.

In plain words: the charts your CFO asks for, always current, with the link that sends them.

The board pack: the estate as a document, in PowerPoint, Word and PDF
Kept: what each decision claimed against what the invoices verified

On the screen

How to use it

  1. Press 6 in the Contract Management Portal. The chips under the head name the six boards and mark the one you are reading.
  2. Read the headline, then press the largest bar: the vendor's folder opens with the documents behind the number.
  3. Set the lever to the uplift you believe, and take the run rate it prints into your budget.
  4. Press Copy the link and paste it to a colleague, or Email it for a draft with the figures and the link already written. What they open is computed from the ledger at that moment, not a stale export.

Tips

Related: Contracts: the renewals, Vendors: every vendor you hold, Spend Agent

What next: the moves on every screen

Where: the inspector's Moves tab, on every Contract Management Portal screen · /office
Who: everyone in the organization

No screen dead ends. The Moves tab is where a finished read turns into a decision.

On the screen

What to do first: up to five moves the estate's own figures ask for, the first one lit, in this order:

Three standing moves under them: Add documents, New folder and Walk me through it.

With a row selected, the Details tab carries the one filled button the document needs: Draft the notice letter, Assign an owner, Benchmark this document or Open the document.

In a case room, the aside carries Run on this contract: read the contract, benchmark it, ask Vera, or open the negotiation strategy.

On an empty estate, the Contracts tab leads with Add documents, Import an existing estate and See a sample estate.

How to use it

  1. Press Ctrl I if the inspector is hidden, then press Moves.
  2. Press a move. It opens what it names: the notice letter, the owner picker, the benchmark's consent line, or the document.
  3. Finish it there. Nothing is sent or spent by the press itself.

Tips

Related: The Contract Management Portal, Renewals: the decision runway

Entitlement Agent: your license position, from your contracts

Where: Contracts & documents › Entitlement Agent · /entitlement-office
Who: everyone in the organization. Viewers can look but not change anything. Organization settings are for owners.

Entitlement Agent answers three questions about every software product you hold: how many licenses the contracts grant, how many are in use, and what the difference costs. It reads license lines out of your contracts (or imports the register you already keep), lets you record deployed counts, links the supporting documents an auditor asks for, and builds the response pack when an audit letter arrives. It shares its data with the Contract Management Portal, so a contract uploaded in either window appears in both.

Since 9 October 2026 the left column lists the agent's seven steps as numbered rows (since 13 October 2026; the Shortfall, at list step is gone, Price benchmark and Price history sit under License lines, and the Position is one press from the register) (a tick once a step has nothing waiting) and the figure beside each; there is no step strip above the work. Each screen's head is its name and one line stating the figures, and the details column opens with a what to do now card whose button does it.

The window. Since 3 October 2026 the Entitlement Agent is built as its prototype. The title bar is white, closed by a gold rule, and carries four menus (File, Run, View and Help, with Alt and the underlined letter as the shortcut), Talk to Vera, who has the screen you are on, the theme switch and the window buttons. A navy column runs down the left: VendorBenchmark, Jump to (Ctrl K), Home, Vera AI and your pinned apps, then Your contracts, one row a screen with its figure (contracts, documents scanned, vendor folders, links between them, license lines, the shortfall at list, renewals, the report) and a dot that is gold when the screen is done and red when it wants you; the screens that sit beside a step are indented under it. Under that sit a folder a vendor with its count, Sources (every way in, each marked connected or connect, with how many are connected; press one to open Add on that way) and the related apps, and on the Register and on Read the screen's own filters. Eight numbered steps run down the left column in the order the work does: 1 Upload, 2 Scanned, 3 Organize, 4 Map, 5 Register, 6 Position, 7 Renewals and 8 Report; the step you are on is lit, and a step with nothing waiting carries a tick. A step that carries other screens shows them as chips at the top of the page: Scanned carries Reading, the Review queue and the Playbook check, Organize carries Folders, Ask every contract and Clause comparison, Renewals carries Align and consolidate, Position carries Price benchmark and Price history, Report carries Warnings, the Brief and Activity. Every screen opens with a compact head over a gold rule: its name in capitals and its status, the filter box and the screen's own actions ending in one navy button to the next step (on the Register, See the position), one row of figures (press a figure to filter the table) and the stake in one line. Under the head the screen sits on panels on a gray page: where it stands by status (press a part to filter), then the table under a header strip that carries the table's own controls. The details column on the right stands beside Upload and Scanned and opens on any other screen when you select a row; Ctrl+\ shows or hides it. The status bar along the foot carries the keys, what the estate holds, what you have selected and whether the window is working.

Every screen has a guide with three parts: what the screen shows, how to use it (numbered steps) and its keys. It never opens on its own; open it from Help, Screen guide.

Working the tables. Arrow keys move the selection; Enter opens the row; Space ticks a row; Shift click ticks a range; Ctrl+A ticks every row. A command pressed with several rows selected applies to all of them and the confirmation says how many. Ctrl+Z undoes the last change, any number of times. Right click a row for its commands; a grayed command shows why it is unavailable when you hover it. Hover a column header to see what the column means. Escape closes the open dialog, menu, guide or tab, then clears the selection; it never closes the window.

A vendor and a line as records (since 13 October 2026). Press Enter or double press a vendor on Organize and it opens as a tab beside the contracts: its money, its next date and its fiscal year end in the head, the next twelve months, the companies it signed through, its contracts, its license lines and its published rules, with Its lines, Its folder and Its renewals at the top. Press Enter or double press a line on the Register and it opens as a tab: in use against licensed drawn as the bar, the money, the chain of evidence, the contract and the sentence the line rests on, how the vendor counts, and Enter a count, Link documents, Mark as verified and Benchmark the price; The contract and The vendor at the top open those records.

On any contract (since 3 October 2026). A double press on a contract, anywhere in the window, opens the document in the reader; a sample contract, which has no document behind it, opens its tab instead. Right click a contract for Show on the map (the Map, its vendor open and the contract selected), Open its folder (Folders, its vendor folder open and the contract marked), Copy where it files (vendor, year and file name, ready to paste), Talk to Vera about it, Send to a human and Draft an email (a note to a colleague and, where the read found a notice date, one to the owner). Delete hides the contract at once and shows Undo for eight seconds; it is deleted only when that time runs out, and closing the window first deletes nothing. A term someone changed by hand shows Edited, with Use what the read found to put the read's own answer back; the document type can be changed there too.

On any contract, one press (since 13 October 2026). A single press on a contract's name, anywhere in the window (a node on the map, a row of the register, of Scanned, of Renewals, a vendor's contracts), opens the document over the window: its pages, the page count, zoom, Open in a tab, and What the read found beside the pages, each answer a press that goes to its page. A sample contract has no uploaded file behind it, so the platform's sample paper for its vendor stands in and the reader's gold tag says sample paper; your own documents open as uploaded. The reader's one primary is AI advisory (also A): it reads the pages, then lays out the verdict, four figures (changes found, money on the table a year, off your standard, worse than last time), the key terms, What is risky, What is good, Against your company template and What to do first, each row a press, with Start the review, Check against my template and Compare with last time at the foot, the same panel the Contract Agent opens on a document. On the sample estate the advisory is written on the sample's own figures; on your own documents it is written from the read. The window arrives in motion since the same day: the title, the tag, the facts counting to their values, the panels one after another, the bars growing, the rows in order, the map drawing its branches; a light follows the pointer, every press ripples, and a decision throws a short gold burst. With reduced motion on in your system the window stands still, exactly as before.

Entitlement Agent, the Register: licensed and deployed quantities, the gap, its status and the linked documents
Entitlement Agent, the Position: one row per product, with the assumptions on the right

On the screen

Entitlement Agent, the Brief: the register's own figures above the written brief on what you are entitled to
Entitlement Agent, a contract open as a tab: the licensing terms next to the commercial terms, each with the page it came from
Entitlement Agent, the Renewals: grouped by notice date, with the uplift slider in the screen header

Open the file. A contract's details, its tab bar and its right click menu each carry Open the file: the contract's file, with every benchmark, comment, action and document about it from every app (see The contract file).

How to use it

  1. Open Entitlement Agent from the menu on the left. It opens in the Register (or the screen chosen in Settings, Display). Press 1 to 7 to move through the seven steps.
  2. Upload a contract in Add (key 1). Its terms and license lines are extracted; confirm the lines with Add to register. If you keep a register in a spreadsheet, use File, Import register.
  3. In the Register (key 5), select a line and press Enter deployed count in the details column. Enter the quantity in use, the source and the date. The Gap and Status columns update. Press Link documents to record the purchase order, invoice or license certificate, then Mark as verified once you have checked the line against the contract.
  4. Press B on a line to benchmark its price.
  5. Open the Position (See the position on the Register), select a product with a shortfall and read how the count was calculated. Use the Position tab on the right to change the assumptions.
  6. Open Organize (key 3), select a vendor and read its licensing rules next to its spend. Override a rule your contract contradicts.
  7. Open Read (key 2), press Enter on a contract, check the extracted terms, correct any, and press Mark as reviewed.
  8. Press R for the Brief and press Write the entitlement brief once the register is in reasonable shape. Read it, take it as Word, and write it again whenever the register changes.
  9. Press A for Activity to see who did what, and Export if someone asks for the record.

Tips

Related: The Contract Management Portal, Renewal calendar

Intake rules and the sync schedule: how they work

Where: Entitlement Agent › Settings (Ctrl+comma) › Intake rules and Sync schedule · /entitlement-office
Who: everyone in the organization can read both pages; only an owner can change them. The sample data is read only.

Two pages decide what comes into the Entitlement Agent and how it is sorted once it is in. Intake rules sorts every license line into your own product categories and sets which lines the register shows by default. Sync schedule sets how often each connected system (Coupa, SAP Ariba, SharePoint, Okta and the rest) is asked for what is new. Both apply as you change them; there is nothing to save. Every change is written to the activity log with your name, and each page lists who changed what and when at its foot.

Product categories: how a line is placed

A category is a name and a list of words. When the register draws a line, it reads three things on it: the vendor, the product name and the part number. It then walks your categories from the top down and puts the line in the first category that has one of its words in that text. A line no word matches is Uncategorized.

The page opens on seven categories, with words for the vendors and products most estates carry:

CategoryStarts with words such as
AIcopilot, openai, chatgpt, anthropic, claude, gemini, vertex ai, bedrock
Collaborationmicrosoft 365, office 365, teams, zoom, slack, webex, google workspace, miro, box, dropbox, confluence, docusign
Securitycrowdstrike, zscaler, okta, palo alto, defender, sentinel, splunk, netskope, sentinelone, proofpoint, cyberark, fortinet
Data and analyticssnowflake, databricks, tableau, power bi, mongodb, informatica, qlik, looker, elastic
Cloud and infrastructureaws, azure, google cloud, gcp, vmware, broadcom, red hat, citrix, nutanix, oracle database
Business applicationssalesforce, sap, workday, servicenow, oracle, adobe, hubspot, coupa, netsuite
Developer toolsgithub, gitlab, atlassian, jira, jetbrains, datadog, new relic, postman

Each category's row says how many lines and how much a year it holds in your register today, so you see the effect of a word as you type it. The Uncategorized row names up to four of the lines no word matches yet, which is the quickest way to find the word you are missing. Add category adds one at the foot (up to 30), the cross removes one, and Restore defaults puts the seven back. A category name must be unique, and Uncategorized is kept for the lines nothing matches.

Where categories show. In the Register: the Categories group in the filters on the left (each with its line count; press one to see only its lines), By category in the grouping switch on the table's strip (each group carries its value a year), and the Category column in the column chooser. The register's CSV export carries a Category column. Settings, Register can make Category the grouping the register opens on.

Filters: what the register shows by default

Filters keep small or irrelevant lines out of the way without deleting anything. Five can be combined:

FilterLeaves out
Minimum annual costLines whose annual cost is below the amount, in USD. 0 keeps every line. A line with no annual cost is not left out by this filter.
Leave out lines whose term has endedLines on a term that has ended and not renewed.
Leave out lines with no priceLines where the contract states neither a unit price nor an annual cost.
Excluded vendorsEvery line of the vendors you pick.
Categories shownEvery line of a category you switch off, Uncategorized included.

The head of the Filters panel says how many lines the filters leave out now and why (for example "5 lines of 13 left out (5 below the minimum annual cost)").

What "left out" means. A line left out stays in the register, keeps its documents, counts and verification, and still counts in every total: the head of the Register, the Position, the Report, the brief and the reconciliation against your contracts all use every line, because a figure that changed with a view setting could not be trusted. Only the table hides it. Above the table a line says how many lines are left out, why, and what they are worth a year. Show them brings them into the table for this visit, Hide them takes them out again and Intake rules opens the page. The register's CSV export follows the table: it carries the lines shown.

When files arrive

Vendor folder from the file name. On (the default): when you upload files on Add, each is staged under a vendor folder guessed from its file name and the folders it sat in, for you to correct before pressing Upload. Off: every file is staged in Unfiled and you sort it yourself. Either way the contract's read names the vendor once it is uploaded.

The sync schedule: how a source is kept current

A connected source does not push its data to the platform (except Ironclad and DocuSign, below). The platform goes and asks. It does that on one run that starts every hour at half past (00:30, 01:30 and so on, UTC). On each run, every connected source is checked against your schedule, and only the sources that are due are asked for what is new. A source you have never set is due once a day, in the 06:00 UTC hour, which is exactly how every source behaved before the schedule existed.

ChoiceWhen the run takes the source
Every hourEvery run, as long as 45 minutes have passed since its last sync.
Every 6 hoursThe first run at least 5 hours 45 minutes after its last sync.
Once a dayThe run in the hour you chose, once a day. If that hour was missed (the run was down, or you moved the hour), the next run catches up once 26 hours have passed.
Once a weekThe run on the day and hour you chose. If that was missed, the next run catches up once 8 days have passed.
Only by handNever on its own. It updates only when someone syncs it on the integrations page.

What each source brings in on a sync

SourceBrings inHow much on one sync
Coupa invoicesApproved invoices, as spend by vendor and monthThe invoices dated after the last sync (a year back on the first sync), up to 200, each once
Coupa purchase ordersPurchase orders, requisitions and suppliersThe records the system returns, merged so each appears once
SAP Ariba, SAP S/4HANA, Oracle Fusion, NetSuitePurchase orders, requisitions and suppliersThe records the system returns, merged so each appears once
SharePoint, Google Drive, Box, OneDrive, Dropbox, SFTPNew contract files from the watched folder and its subfoldersUp to 10 new files; the rest wait for the next sync
Coupa contractsThe PDF and Word files attached to contracts in CoupaUp to 10 new files
SAP Ariba contractsThe PDF and Word documents in your Ariba contract workspaces (up to 200 workspaces)Up to 10 new files
OktaThe people who signed in to each app over the last 30 days (or, if the token cannot read the System Log, the people assigned to it)A fresh snapshot each sync
Microsoft Entra IDThe people assigned to each app in your tenantA fresh snapshot each sync
Ironclad, DocuSignSigned contracts and completed envelopesEach one, as it happens

Choosing a schedule. A folder source takes up to 10 new files a sync, so a team that files many contracts a day gets them sooner on Every hour (up to 240 a day) than on Once a day (10). To carry a whole existing archive across, use Import everything on the connection instead of waiting for syncs. Spend from Coupa invoices is reported by month, so Once a day is plenty. Usage from Okta and Entra moves slowly and suits Once a day or Once a week. Purchase orders during an active sourcing event suit Every 6 hours.

When a sync fails

A sync that fails (a revoked key, a changed password, a source that is down) is recorded under Recent activity on the Integrations page with the source's own message, and the connection is marked as stopped. On Sync schedule its row says Stopped on an error with that message. A stopped connection is not asked again on its own, so a broken credential does not fail every hour. To start it again, open the integrations page, fix the cause, and save the connection's details again (or, where the connection has one, press its Sync now or Import now); the next successful sync marks it connected and the schedule picks it up from there. Disconnecting a source stops its syncs at once and keeps what it already brought in.

What is kept and who can see it

How to use it

  1. Open the Entitlement Agent and press Ctrl and comma, then Intake rules.
  2. Look at Uncategorized first: add the words that place those lines in a category, or Add category for a family of your own.
  3. Set the order with Up and Down so the specific categories (AI, Security) sit above the broad ones (Business applications).
  4. Under Filters, set a Minimum annual cost if small lines crowd the register, and switch off the categories or vendors you do not manage here.
  5. Open the Register and press By category to see the estate by category, each group with its value a year.
  6. Open Sync schedule. Set each connected source to how often it should update, and pick the hour for daily and weekly syncs.
  7. Check a row's next time to confirm when the source will update, and open Open integrations to connect a source or fix one that has stopped.

Tips

Related: Entitlement Agent, Connectors: keeping it current, Coupa, SAP Ariba and your other procurement systems

One by one: proposals and agreements

The right way in when the point is the document itself, not the volume.

Upload a proposal: the fields fill in as each file is read

For anything you want benchmarked, use Upload a proposal: upload up to 20 files, watch the vendor, value, term, and seat fields fill in per file (shaded by how confident the read is), correct anything gold or red, and confirm the batch once. PDF and DOCX, 200 MB each, verified by contents rather than name.

For signed contracts with dates to watch, add Agreements: vendor, expiry date, notice period (30, 60, or 90 days), annual value, and up to five files per vendor for safe keeping. You can also type an agreement in beside the ledger and let the AI fill the details, or drag the signed document onto Drag contracts here or click to upload in the agreement's details. Up to 40 vendor agreements are tracked this way; past that scale you want the folder upload or the Enterprise Uploader.

Time: minutes. A proposal batch reads as it lands; an agreement is a one-minute entry.

Folder upload: Contracts

The way in most organizations should start with. Drag your contract folder, subfolders and clutter included, onto Contracts; Vera reads every document, files it into one folder per vendor, and judges each agreement current, due for renewal, expired, superseded, or perpetual. The judgments respect how vendors actually work: an old perpetual license is a current asset, and only your newest enterprise agreement counts as live.

Contracts: the estate filed by vendor

What to expect during the run. Up to 300 files per run, 200 MB each, PDF and DOCX; every unreadable file type is named in the results rather than silently discarded. A live ticker narrates the filing, and you can leave at any point: a floating button follows you with the percentage, and a notification brings you back when the archive is ready, even if you closed the tab mid-scan.

The three questions at the end. Next moves asks, with the money named on each: which genuinely due renewals go on the calendar (never ten-year-old document, and vendors you already track are advanced, not duplicated), whether to review your top 20 vendors by spend, and which contracts deserve an analyst benchmark. Nothing happens without your confirmation.

The Estate Intake Brief. Every scan also produces an executive document in the house brief style: the vendor table, the renewals inside the window, the lifecycle findings, and a bottom line. It prints clean, which makes it the fastest way to show a CFO what the estate actually holds, usually on day one.

The morning report. When the scan finishes, the person who uploaded the folder also gets the report by email: how many documents were read, the vendors they filed under, what the document costs a year, what falls due inside 18 months, and the short list that needs a human eye, with the full brief one click away. Like every alert, the switch to turn it off is in Settings under Notifications; it goes only to the person who started the upload.

The Estate Intake Brief, the scan as an executive document

What lands where. Archive uploads land as contracts, so everything you upload also feeds Document Agent, the spend portfolio, and the vendor pages automatically. Documents the scan could not read queue under Needs a look; fill in a vendor, end date, or value and the contract refiles immediately.

Time: one drag, then the scan works while you do something else. Plan for the three follow-up questions to take ten minutes of actual decisions.

The whole estate: the Enterprise Uploader

When the estate is hundreds to thousands of agreements, plus a register spreadsheet someone maintains, use Enterprise Uploader. Chapter 00 walks the full run step by step with screenshots; this section is the decision view.

Step 1 of the Entitlement Agent since 9 October 2026 (part of the Agent since 3 October, inside its window since 4 October). The Uploader is the Entitlement Agent's Upload step at the Agent's own address, /entitlement-office, so the line is clear: on step 1 an owner uploads a folder or files and presses Scan; step 2, Scanned, shows each contract as the scan lands; Report carries the checks and the one press that files it all. A run in flight opens the Agent on the step the run needs. /migration forwards to the Agent, and /migration?new=1 opens the door of a new run. A member, or an organization without the Uploader, sees the Agent's own upload on step 1, where each contract is scanned as it lands.

The Enterprise Uploader window with no run open: the header with the upload presses, the tree of sources, and the details panel

Since 27 September 2026 every state of the Uploader opens with the house masthead: the state named with Uploader beside it, its status tag and one factual line, the gold line naming the step (Upload, Read, Review or Live), one row of counts, and the actions at the right with one filled button over a rail of the four steps.

With no run open, the screen explains what a run does in four steps, lists the sources you can connect, and closes with After the run: where a run's documents land once it is live (File Explorer, Agreements, the Contract Management Portal) and what to do with them (benchmark a contract, work the renewals). Each move opens its own window. Down its lists, a status (what blocks going live, what to watch, a note) is a colored dot beside plain words rather than a filled capsule on every row. The same holds in its tables: the blocking count on a wave, and worth a look beside a vendor whose read came back unsure. What you choose on the screen reads in gray or dark ink, never the accent green: the date order you pick in the scan options, the fields you add, and the row you select in the run table; anything still being read spins in the In review blue.

Why the Enterprise Uploader is different. Three properties the folder upload does not have:

  1. Staging. Nothing a migration loads is visible anywhere on the platform until sign-off. No alert fires, no digest counts it, no agent reads it. Your estate becomes real in one transaction when an owner presses Go live, and the acceptance is written to the audit log with the scorecard attached. Big estates promote in waves (top vendors first, the tail later), a go-live stays reversible for seven days, dual-control sign-off is one press away for organizations that require it, and the run's acceptance certificate prints as an executive document with a filing reference, a signature block, and a Word export. Since August 2026 the whole Studio is one page that follows the run: load document (the register rides in the same upload and maps itself), let the ambient read work, then work the open items on one board, with Vera's own judgements applied and reversible on her ledger.
  2. The register comes along. Your master spreadsheet (CSV or XLSX) is mapped column by column with a dry run that shows exactly what it would create, update, and reject before anything is written. Columns the platform does not recognize are kept on each contract as custom fields, exactly as you wrote them; nothing in your register is thrown away.
  3. Reconciliation with evidence. Same-company vendor names merge themselves, for every vendor, and each merge sits on the Changes tab with the evidence and a one-press Undo; byte-identical duplicates clear themselves the same way, while agreements that supersede one another still arrive as proposals for you to decide. Binding is where renewal dates become true: a master agreement and its amendments become one contract whose terms in force are computed across the whole stack, newest document winning on each term separately, and documents of one company that print the same contract number bind into one agreement by themselves, the number named on the ledger entry. A document with no home states what the document does say, the customer it is made out to and the contract number it carries, and takes a real three-way decision: bind it to the agreement named (or any agreement you pick from the list), keep it as its own contract, or file it as reference so it stops counting against completeness. Source documents, on the Agreements tab, then shows each contract's document stack and names the exact document every live figure was read from.

What the Enterprise Uploader keeps for you. The scan brief you set before your first upload, the optional fields, the date order and the questions you write for Vera, is kept in this browser and rides with whatever opens the run: an upload on the first screen, an upload on the Load step, the demo estate, or a connector import. Once the run exists the run itself owns the brief. On a run in flight, the answers you type at sign off are kept against that run and come back in their own fields if you leave the page or close the window: waiver reasons, the materiality floor and its reason, vendor names and values you read off the document, the vendors selected for a wave. Each clears as it is saved, and the whole draft clears when the estate goes live. Your documents themselves are never kept in the browser, so a queue picked in an earlier session still asks you to re-pick the folder.

Who runs it. An owner, because a run writes thousands of records. The Enterprise Uploader itself is open to every organization; the owner can start the run and hand the working of it to someone else.

Shall I draft the email? (since 2 October 2026): under the acceptance certificate once the run is live. It is written from what was loaded, what is complete and what is still open. Press a reader and the email opens beside what you were looking at; see Send it on.

How long a scan takes

Two clocks run, and only the first one needs you at the keyboard.

The transfer moves your documents from the browser to the platform, six at a time, and finishes in minutes: a hundred documents of ordinary size take about two minutes on a decent connection, a thousand about twenty. Keep the tab open while it runs, because the bytes are on your machine and nowhere else until they land. If you close it early, re-pick the same folder and the run carries on from where it stopped.

The reading is Vera working through each agreement, and it does not need the tab, your laptop, or you. Reckon on roughly a hundred documents an hour: nearer sixty when the estate is long master agreements, over two hundred when it is short order forms. In round numbers:

EstateReading time, unattended
50 documentsunder an hour
100 documentsabout an hour
500 documentsmost of a working day
2,000 documentstwo to three days

Reading starts as soon as the first documents land, so terms appear on screen while the rest are still transferring, and the run continues on its own overnight and through a closed laptop. There is nothing to restart. Upload the estate on Monday afternoon and work the exceptions queue on Tuesday morning.

From a scanned estate to a live renewal calendar

Scanning fills the contract ledger. It does not, by itself, fill the renewal calendar: those are two records, because a contract is a document and a renewal is a commitment to act by a date. The runway at sign-off is where one becomes the other.

  1. The runway shows every dated agreement in the run across the next fourteen months, sized by annual value, with an amber flag on each speak-by date. The speak-by date is the end date minus the notice period read from that agreement's own document, so a contract with a 180 day window flags six months out and one with 30 days flags one month out. Where a document states no notice period, 90 days is assumed and the record says so.
  2. Put them all on the calendar in one press, or arm them one at a time from the runway or from a document's preview. Either way the renewal is created staged: invisible to the rest of the platform, and no alert, digest, or agent can see it.
  3. Go live promotes them with the estate. The renewals land on the live calendar the same moment the contracts do, never a day before.
  4. Alerts stay off until someone opts in, per vendor. Arming a renewal never sends anyone an email.

If an agreement is already on the calendar, importing newer document for the same vendor moves the date forward when the documents say the term was extended, and fills a blank notice period or annual value from what the document states. A figure you set by hand is never overwritten by a scan.

What is not put on the calendar: anything without a vendor or without an end date (there is nothing to count down to), and superseded document, because its successor carries the live date. Fix a missing vendor or end date in the review table and arm it afterwards.

Sending a contract into a tool

From a document's preview, Send to hands the document to a tool with the document already loaded, instead of opening empty and asking for the file you were just looking at.

Only PDF and DOCX documents can be sent, and only up to 200 MB.

What a scan cannot read, and what to do instead

Every limit below is a real ceiling in the product, stated so you can plan around it rather than discover it.

LimitValueWhat happens past it
File size200 MB per documentNamed in the stayed-behind line, not transferred
File typePDF and DOCXNamed in the stayed-behind line, not transferred
Empty files0 bytesNamed in the stayed-behind line, not transferred
Documents in one run5,000The excess is not queued; split into a second run
Length of a single agreementabout 150,000 characters, roughly 40 to 50 pages of contract textThe tail is not read. The record is marked and flagged for a look
Pages of a scanned document60Later pages are not transcribed

The length ceiling is the one worth planning for, because it is silent in a way the others are not: a 200 page master services agreement transfers cleanly, reads cleanly, and produces a record built from its first 40 to 50 pages. Commercial terms usually sit at the front, so the answer is often right. The exhibits, the pricing schedules, and the rate cards usually sit at the back, and those are exactly the pages a benchmark needs.

The platform no longer hides this. A document read only in part is recorded as partly read, cannot score as a confident read, and carries the worth a look label in the review table so it surfaces instead of blending in with the finished rows.

What to do with a very long agreement. Any of these, in order of preference:

  1. Split it and upload the commercial part on its own. Extract the order form, the pricing schedule, or Exhibit A as its own PDF and upload that alongside the full agreement. Vera reads the short document properly, and the two bind into one contract because they carry the same contract number.
  2. Add the contract by hand. Go to Contracts, press New contract, and type the vendor, the term dates, the annual value, the notice period, and the uplift cap off the document yourself. Attach the full PDF to the record for the file trail. Six fields take about two minutes, they are certain rather than read, and every figure you type outranks anything a scan produces.
  3. Ask for a hand. Escalate the document to Redress from the exceptions queue and a person reads it.

The same advice applies to any agreement the scan flags as worth a look, whatever the reason: you typing the number is always better than the platform guessing it, and the record marks your values as yours.

Time: the run is three steps and opens itself on the first upload; there is no questionnaire, and reading starts as documents land, so the first extracted terms are on screen while the rest still transfer. Reading a large estate takes several passes over hours and continues while the tab is closed. Budget real person-time for two moments: the register mapping decisions, and the reconciliation and exceptions queues, which are sorted by annual value so the top of the list is what matters. Each exception line takes an assignee from your team, or escalates to Redress with one click, and the queue's foot shows how many are cleared and the clearing pace per day, which is the burn down your champion reports upward. A run that started wrong can be deleted with Delete this run, in the Run menu and the details panel: one confirming press removes the whole staged estate, and nothing live is touched because nothing went live.

Coming from a spreadsheet

Most estates arrive with a register: the spreadsheet that lists vendors, values, and dates. Three preparations make it map cleanly, all drawn from how the mapping step actually reads your file:

  1. Know what your value column means. A column headed something like Contract Value is read as the total over the term and divided by the term length to get the annual figure. If your column is already annual, map it to Annual value instead. Getting this one mapping right is the difference between a correct portfolio and one inflated by every multi-year deal.
  2. Expect the date question. If nothing in a date column proves whether 01/04/2024 means 1 April or 4 January, the mapping deliberately stops and asks, because guessing moves every date in your register by up to eleven months. Answering once enables the dry run.
  3. Keep your odd columns. Internal owner, cost center, procurement reference: leave them in. Unrecognized columns are preserved on each contract as custom fields rather than discarded.

Run the dry run before applying: it states how many contracts would be created, how many updated, and how many rows cannot be used with the reason for each, and rejected rows download as a CSV you can fix and upload again. A register alone, with the documents to follow later, is a legitimate way in: rows create and update contracts, and document attached later adds the evidence behind the terms.

Coming from another tool

Leaving a contract management or SAM tool for this platform is an export plus one of the ways in above, not a special project. What to expect:

Connectors: keeping it current

Migration is an event; currency is a pipeline. Once the estate is in, an owner connects the systems that keep it true under Integrations:

The integration hub: intake, workflow, spend, discovery

The full catalog, with what each connector feeds, is Chapter 12; the per-connection setup walkthroughs are Chapter 19; the working recipe is Connect your data and close the gaps.

Data health: the finish line

"Migrated" is not a feeling; it is a score. Data health scans on every load and states the share of data checks you have covered, with each open gap naming the feature it would unlock and a plan ranked by value. It also carries the audit exposure estimate, built from whatever entitlement data is connected so far, which is your early read on how defensible the license position is.

Data health: the completeness score and the ranked plan

Treat the finish line as three checks, in order: every agreement that matters carries an expiry date and a notice period (without both, there is no window to watch), annual values are on the agreements so the Spend Agent lenses mean something, and the top-ranked gap on Data health has either been closed or deliberately parked with an owner. From there, the day 30 health check covers the rest of the workspace.

Migration FAQs

Will re-uploading the same folder create duplicates? No. Duplicates are detected by content, not file name: identical documents are counted and skipped whichever way in you use, and in Migration Studio the skipped row names the file it matched, with Import anyway beside it if you truly want the copy. Two different documents that share a name are both kept, because they are both real.

Will loading the estate spam my team with alerts? No. Renewal alerts are opt-in and start silent on every channel, so intake never generates email on its own. Migration Studio additionally holds everything in staging, where no alert, digest, or agent can see it until sign-off.

My register dates are ambiguous, like 01/04/2024. The mapping stops and asks rather than guessing, and stays locked until you choose, because the wrong answer moves every date by up to eleven months. Answer once; the dry run then shows you your own rows as the platform understood them.

My contracts write dates day first, like 01/04/2026 for 1 April. Set the date order in the scan brief before your first upload and every reading pass follows it, on the documents as well as the register. Contracts that spell the month out, and dates already in ISO form, read the same either way. If an estate was read before 13 August 2026 with day first chosen, re-read the affected documents from the review table: the setting was not reaching the reader, so numeric dates in those runs were read month first.

My contracts are priced in European notation, like EUR 1.500.000. Both notations are read as the number on the document. So are contracts in Canadian dollars, Swedish, Norwegian and Danish krone, and yen, each recognized as its own currency and then argued in US dollars at the day's rate, with the original currency and the rate recorded in the notes.

Some documents I picked never appeared in the run. Check the line under Upload your contracts here: it names everything that stayed behind and why, counting files over the size limit, empty files, unsupported types, and anything past the document ceiling. An empty file (zero bytes, usually a failed export or a placeholder) cannot be read and is named there rather than transferred.

How long will my estate take to read? Roughly a hundred documents an hour, so a few hundred agreements is an afternoon and a few thousand is a couple of days. It runs unattended, so the honest answer is to upload the estate and come back to the exceptions queue. See How long a scan takes for the numbers.

My agreement is 200 pages. Will it be read properly? The first 40 to 50 pages of contract text, yes. Past that the tail is not read, and because pricing schedules and exhibits live at the back, that is the part a benchmark needs. The record is marked as partly read and flagged worth a look rather than presented as complete. Split the commercial schedule out as its own PDF and upload it alongside, or add the contract by hand and type the six figures off the document. See What a scan cannot read.

Should I ever type a contract in by hand instead of scanning it? Yes, in three cases: an agreement past the length ceiling, a scan of poor quality that comes back thin, and any deal important enough that you want the figures certain rather than read. Typing vendor, dates, value, notice period and uplift cap takes about two minutes, and a value you enter always outranks a value a scan produced. Attach the PDF to the record either way, so the document is still on file.

My spreadsheet has columns the platform will not recognize. They are kept on each contract as custom fields, exactly as written. Nothing in a register is thrown away.

My value column is the total contract value, not annual. That is the expected case: a Contract Value column is read as the total over the term and divided by the term. If yours is already annual, map it to Annual value instead.

Should I exclude old and expired document? Include it. History is judged as history (superseded and expired document visibly sits in the past), it never pollutes your renewal calendar, and it powers the reads that need a past: year-over-year comparison, the Time machine, and binding, which needs the full stack to compute the terms in force.

Some documents are scans with no text layer. Scans transfer like anything else, and one the read cannot make out queues its own transcription, its pages read image by image in the background and the terms extracted from the transcription, after which the record fills in and becomes searchable. Only a scan too illegible to transcribe is filed as unreadable, named in the explorer and the exceptions queue with the reason and a Retry, and a value you fill in by hand always outranks the automatic read.

We run several agreements with one vendor at once. So do most enterprises, and reconciliation knows it: overlapping agreements with one vendor are never proposed as superseded. Superseding is only proposed where the evidence supports it, and you decide each proposal.

Our contracts are in several currencies. Enter values in the currency the row carries; rows keep their own currency, and the workspace display currency covers rows that did not record one. Benchmarks stay in USD so market comparisons hold, and nothing is silently converted.

We only have the spreadsheet today; the documents are scattered. Start anyway: map the register, let rows create the contract ledger, and switch on the watching that dates enable. Attach document as you find it, through Agreements or the Archive; binding recomputes terms as evidence arrives, and your corrections always outrank the automatic reading.


Related: Contracts · Enterprise Uploader · Connect your data and close the gaps · The owner's handbook

Next: Chapter 01 · Contracts & renewals

Was this page helpful?

Thank you. Your note goes straight to the team that writes this manual.

Updated 2026-10-13 · A Vendor Benchmark product · Download the manual as PDF · Questions? Message our team in the app.