VISDOM is CobbleStone's powerful artificial intelligence (AI) backed by machine learning.
VISDOM AI
NEW FEATURES
Ability to Have VISDOM Write a Brief of Your Working Day on the Home Page
Reference #: 260916.200.0001
A VISDOM Brief card on the Home page writes a short read of your working day. Press Brief me on my day and VISDOM gathers the approval and signature steps waiting on your action, anything already overdue, the documents you hold checked out, what you have sent that is still out with somebody, your drafts and unsent processes, open tasks, key dates in the next two weeks, unread alerts, surveys waiting on your answer and documents handed to you to file. For a System Administrator it also weighs the organization's renewal pressure. The brief says plainly which of those items is blocking somebody else, and marks the first thing to do with a Start here tag.
Every statement in the brief carries a numbered reference you can click, which opens the record, process, calendar entry, alert or insights board behind it, with a named reference list underneath that pages three at a time, so a number always resolves to something. The brief is timestamped and takes the time of day into account. An answer is held for an hour, so returning to Home shows it again without running the model a second time.
How will this affect users?
The card appears for people who have VISDOM licensed and switched on, and is hidden entirely where VISDOM is switched off for the organization or by that person in their own profile menu. It runs only when the button is pressed, so no one is charged for a brief they did not ask for.
Ability to Search the Clause Library by Meaning
Reference #: 260916.200.0004
A Semantic Clause Search screen under Clauses lets you describe the protection or wording you need, for example "cap on liability" or "auto renew unless cancelled", and returns the clauses in your library that come closest in meaning, ranked by how close they are, rather than matching keywords. Results are filtered by your own record permissions, so you see only the clauses you are entitled to see. The matching runs on your own server, so clause wording is not sent anywhere to be searched and none of your VISDOM word allowance is consumed. The daily VISDOM job downloads the language model it needs if it is missing and encodes any clause in the library that has not been encoded yet, so no manual preparation is required; a single unreadable clause is skipped rather than stopping the run. Where the feature has not been set up on a site, the screen says so and points at keyword search in the Clause Library, which continues to work as before.
How will this affect users?
Anyone who drafts or reviews contract language can find precedent wording by describing what it needs to do, instead of guessing the exact words used when the clause was filed.
Ability to Have VISDOM Suggest Where Signature Fields Belong on a Document
Reference #: 260916.200.0005
A Suggest fields action on the signature layout screens reads the document and proposes where people should sign, of what kind, and for which signer. It first reads the signing locations a document already declares: CobbleStone's own signer, date and text authoring tokens, the text tags and anchor strings written by common signing services, typed markers such as [Signature] and <<Sign Here>>, and the form fields on a fillable PDF. Anything declared that way is placed from measured coordinates rather than guessed, and costs no AI usage at all.
Where the document declares nothing, VISDOM recognizes the full range of signature block captions, including initials, printed name, title, witness, notary and attestation lines, reads the party named above each column so a two party block is attributed to the right person, stays within the signature block instead of ranging over the body of the contract, and places standard sized fields exactly on typed lines, underlined blank runs and lines drawn on the page. Suggested fields arrive as ordinary fields you can move, reassign or remove, and the whole pass is a single undo step.
How will this affect users?
Anyone preparing a document or template for signature can have the signing locations found for them instead of placing every field by hand. VISDOM must be licensed and enabled.
VISDOM Compares What a Document Says Against What the Record Holds
Reference #: 260916.200.0007
Values VISDOM reads out of a document are now classified against the record and shown under tabs with counts: values that disagree with the record, values that fill a field that is blank, values that agree, and values that do not appear on the form at all. Same value detection is deliberately generous, so a date written two ways, an amount with or without its currency symbol, and a list field's stored value against its display text are all recognized as agreeing rather than raised as a conflict. Comparison cards print the record value and the document value in the same format, so two dates are genuinely comparable, and field labels are shown as readable words.
Field extraction now runs as soon as the document opens rather than waiting behind a button, applying a value writes it to the record and can be undone, and each found value carries a show me link that opens the field in the form below, expanding its section and highlighting it. Values that VISDOM filled carry a small mark on the field, so a reader can tell them from values a person typed.
How will this affect users?
Anyone creating or editing a record from a document can see at a glance where the paper and the record disagree, which nothing in the previous version reported.
Ability to Ask VISDOM About the Record You Are Viewing
Reference #: 260916.200.0009
Contracts, requests, solicitations, purchase orders and Vendor/Company records now carry an Ask VISDOM about this section in their insights panel, named for the kind of record you are on, with four questions ready to ask: Summarize, Risks, What next and Value. Answers are reasoned from that record's own field values and the figures shown beside them. Other record types do not carry the section, and the assistant panel is still available on those screens for a general question.
The assistant panel is also handed the record's details as the screen shows them, including the labels behind list and lookup values, formatted dates and amounts, and the names of the fields that were left empty. A chip in the panel names what it can see, for example "Contract #12", so it is always clear what an answer is based on, and a single click turns the context off for a general question and offers it back afterwards. A question such as "what is missing on this one?" can now simply be asked. A question that clearly reaches beyond the record, such as what other contracts you hold with the same vendor, is rewritten against the open record first, so the search knows who "this vendor" is. List screens deliberately publish no context.
How will this affect users?
Anyone reviewing a contract, request, solicitation, purchase order or Vendor/Company record can question it from the record itself. VISDOM must be licensed and enabled.
Ability to Start a New Record by Asking the Assistant
Reference #: 260916.200.0010
Typing an instruction such as "start a new contract called Acme MSA" into the assistant, on any screen, is now recognized as a request to create a record. The assistant shows you a review card first and never writes anything on its own. It asks which record type to use where the fields depend on one, then opens the real add form already filled in, so the usual required field checks, duplicate checks and save behavior all apply and the record is saved by you. Only record types you have permission to create are offered. It recognizes records only, so setup actions that would change an area or a shared list stay on their own screens, and a phrasing it does not match exactly is interpreted rather than refused with instructions.
How will this affect users?
Anyone can start a record from wherever they happen to be working, without navigating to the right module first, and still reviews and saves it themselves.
Ability to Add Reference Data Without Leaving the Launchpad
Reference #: 260916.200.0011
The Launchpad's reference data step lets you type the values a setup step is waiting on and have them created without opening each list screen in turn: contract types, departments, locations, contract statuses, categories and occurrences, one at a time or several separated by commas. Each value is checked against your own create permission and against what the list already holds, so a value that is already there is reported back rather than added twice, and the board refreshes so the step's readiness reflects what was just added.
How will this affect users?
End users are not affected as only System Administrators have access to the Launchpad.
VISDOM Review of Your System Configuration
Reference #: 260916.200.0012
The Launchpad carries four review passes VISDOM runs on request: Duplicate values across shared lists, which finds the same value recorded in more than one form; Configuration gaps for a system of this size, which names capabilities a system of this shape normally has configured and this one does not; Naming and structure consistency; and Records inconsistent with their classification, which finds records whose title contradicts the type or status they are filed under, such as a title that says NDA against a type that says Services.
Each pass states on screen exactly what it sends before it runs, and what it sends is option names, field and type names and counts, never the content of your records, with the one exception it declares. Review findings sit in the same list as the counted ones, so they can be dismissed or snoozed with a reason and appear in the printable review, and where a finding is a near duplicate it offers the same merge dialog with the real record counts behind each spelling. Running a pass again replaces its previous findings.
How will this affect users?
End users are not affected as only System Administrators have access to these reviews. VISDOM must be licensed and enabled for the passes that use a model.
Ability to Listen to a Spoken Brief of a Document
Reference #: 260916.200.0017
The document previewer carries an Audio brief button that produces a short spoken brief of the document you are looking at, with the text shown alongside so it can be read as well as heard, and controls to start, pause and stop the reading. The brief is produced from the document's own text and spoken by your browser, so nothing is uploaded to produce the audio. It is offered for documents only and is shown switched off with a reason for image files or where VISDOM is off, and a scanned page with no text layer says so rather than failing silently.
How will this affect users?
Anyone who wants a quick sense of a document before opening it, including users who prefer listening to reading, can get one from the previewer.
Web Search Assistant in the VISDOM Assistant Panel
Reference #: 260916.200.0019
Web Search is available from the assistant picker and answers questions about the outside world through the same secure service and the same credentials as the rest of VISDOM, with suggested starter questions of its own. When the month's included searches have been used, the reply says so in one sentence instead of failing without explanation. Record context is deliberately not attached on this assistant, because the search service does not use it. Assistants that genuinely are not configured for the selected model are shown switched off with the reason, rather than presented as working assistants with nothing behind them.
How will this affect users?
Anyone using the assistant for questions that are not about their own records has an assistant for them in the same panel.
Ability to Have VISDOM Write the Negotiation Brief for Your Team
Reference #: 260916.200.0040
Negotiation brief, under VISDOM Tools on the Create with VISDOM and Edit with VISDOM workspaces, asks VISDOM to write the internal brief for the team handling the agreement. It opens with a short position on whether the document is signable as it stands, then the points to put to the other party worst first, then a separate Check on our side section for anything where your own record and the document disagree, and closes with what is already settled so nobody reopens a decided point. Every point has to come from a finding, a playbook position or guidance your organization has recorded, and VISDOM is required to say when the material does not support a point rather than filling the gap.
The draft can be corrected in place, and the corrected wording is what is filed, sent and copied; a further take can be asked for where the framing is wrong. From the brief you can file it onto the record as a document and send it by email. On Create with VISDOM, where the record does not yet exist, filing waits until Save creates it, and the send control says why it is waiting rather than sitting switched off without a reason.
How will this affect users?
Anyone reviewing a counterparty's document who then has to tell colleagues what to ask for gets a first draft of that message, written from the findings already on screen. VISDOM must be licensed and enabled.
The VISDOM Workspace Opens on a List of What to Do Next
Reference #: 260916.200.0041
Both VISDOM workspaces open on a Next steps panel: a short ordered list of what this review still needs, worst first, assembled from everything found so far. It names the values that disagree with the record and says when one of them is a required field, the clauses carrying non standard language, the playbook clauses missing from the document and the ones that deviate from your standard wording, how many field values were read and how they compared with what the record already held, the names in the document that your system does not hold, the obligations waiting to be kept or discarded, and any edits to the document not yet saved.
Each line carries a button that opens the panel which resolves it. The list is rebuilt as the work is done, so it shortens as the review progresses, and when nothing is left it says so rather than sitting empty. Where no playbook comparison has been run yet, running one is offered as a step of its own.
How will this affect users?
Everyone reviewing a document with VISDOM, and people opening the workspace for the first time in particular, has somewhere to start rather than a row of panels to work through in no stated order.
Clause Coverage Across the Whole Portfolio
Reference #: 260916.200.0042
The Overview board of Contract Insights carries a clause coverage grid built from the clauses VISDOM has found across your contracts: clause categories down the side, contract types across the top, and in each cell the share of the read contracts of that type that carry that clause. Cells are shaded as most have it, some have it, or a gap. A cell where too few contracts of that type have been read is shown in a state of its own rather than as a gap, so absence of evidence is never presented as evidence of absence, and every cell explains itself when the pointer rests on it, naming how many of the read contracts carry the clause.
The panel states how many contracts VISDOM has found clauses in and what share of the portfolio that is, along with how many clause categories have been seen in total, with the most widely present of them shown in the grid.
How will this affect users?
End users are not affected as only System Administrators have access to Contract Insights.
VISDOM AI
ENHANCEMENTS
Ability to Ask VISDOM a Question from Any Screen
Reference #: 260916.200.0002
A VISDOM button now sits in the corner of every screen and opens an assistant panel without leaving the page you are on. The panel opens on Auto, which reads each question and decides for itself whether it is a question about your own records or a general one, so a question such as "which contracts expire in the next 90 days" is answered from your data without having to change assistant first. Choosing a named assistant from the picker turns Auto off and keeps every turn with that assistant; Auto and the general assistant share one conversation, so moving between them keeps everything already said on screen.
From the panel you can choose which VISDOM tier answers, widen it, copy any answer, and clear the conversation. Choosing the Clause expert and describing the protection you need returns a drafted clause as a card in the conversation with an Add to Clause Library button, and once it is added the card carries a link to the saved clause; because that assistant now drafts rather than explains, a general question about clauses is better put to the General assistant. Conversation history is kept between visits. Where VISDOM Services are not connected the panel says so rather than failing quietly.
How will this affect users?
Everyone licensed for VISDOM can ask a question from wherever they are working instead of navigating to a dedicated page. Users who have VISDOM switched off do not see the button.
The Reports Assistant Now Answers From Your Own Data
Reference #: 260916.200.0003
When you ask the assistant for a figure, a count or a list, it now works out which parts of your data the question involves, writes and runs a single read only query, corrects itself once if the first attempt fails, and answers from the rows that came back. In the previous version the answer came from the language model alone and could be confident and wrong. A Show how I looked that up link reveals the query that produced the figures, and the assistant narrates its stages while it works.
Every query is checked in code before it runs and is refused unless it is a single, comment free read; row counts and running time are capped; and results are limited to the rows the person asking is permitted to see, whether that is everything, their department or their own records. The check that a query does not touch a restricted table is applied to the query that actually runs, not to the list of tables the assistant said it would use, and refused queries are recorded alongside successful ones. When the assistant cannot help, because it is switched off for the organization, the account is excluded, or it is not configured for the selected model, it says so in one sentence instead of quietly answering from general knowledge.
How will this affect users?
Anyone asking the assistant for figures drawn from contract data gets an answer produced from that data and can see how it was produced. Answers still respect each user's existing record permissions.
Playbook Coverage Now Reports the Clauses a Document Is Missing
Reference #: 260916.200.0006
Playbook results now report every clause in the selected playbooks with a status of Covered, Deviates or Missing, scored across the whole document. The previous version could only report where a paragraph matched a standard clause, which cannot answer the more important question of what has quietly been left out. From the results you can insert a missing standard clause into the document as a tracked change that can be undone, redline every deviation in one pass, and ask VISDOM what a particular deviation costs you. Findings raised in the review also carry a Suggest language action, which asks VISDOM for a rewording of that clause and opens it as a marked up comparison against the document's current wording, with a color key, so what would change is what you read rather than two blocks of text to compare for yourself. Where a finding has no wording behind it to compare against, the suggestion is shown plain. It is a one off suggestion and is not stored.
How will this affect users?
Anyone reviewing a counterparty document against a clause playbook can see the omissions as well as the matches. VISDOM must be licensed and enabled.
Ability to Run a Playbook Redline on a Document Attached to a Record
Reference #: 260916.200.0008
Playbook redline, reached from the document toolbox on a record's Files tab, compares a document attached to the record against a clause playbook one clause at a time and produces a marked up version showing where the counterparty's paper matches your position, where it falls short, and the wording you would prefer. Clauses that are missing, or that match only weakly, are raised as findings for a person to decide on rather than being rewritten automatically, and the result is filed as a new version of the file through the same versioning as any other edit. The playbooks themselves are named sets of standard clauses maintained on the Clause Playbooks screen under Clauses, where each one can be edited and reused. This replaces the earlier automatic redline tool.
How will this affect users?
Legal and procurement reviewers who negotiate against a house standard get the comparison with a human decision point before anything is written into the document.
VISDOM Configuration in One Place, Including Model Routing per Service
Reference #: 260916.200.0013
A VISDOM AI card in Administration opens a VISDOM Configuration screen with four views: availability, which governs whether VISDOM is available at all and which version the AI screens open with; the organization's default extraction set, which is the set ticked the first time somebody runs VISDOM on a document and which had no editor in the previous version; extraction settings such as the confidence levels at which obligation suggestions are hidden or flagged and the limits on how many fields and how much text are read from one document; and models and providers. Each extraction setting states what it does when left empty: a suggested obligation type is hidden below the confidence percentage set as the cutoff and shown marked as low confidence between that and the flag percentage, with sixty percent applied where no cutoff has been set; raising the limit on how many fields one pass may fill lengthens runs on wide record types; and the document text handed to the assistant is cut at the length set, with sixty four thousand characters applied where that setting is empty or zero.
The models and providers view carries the AI Profile Manager, where each AI service is pointed at its own provider, model and fallback rather than sharing one global setting. The services that can be routed separately are field extraction, obligation analysis, obligation tasks, record type detection, the chat assistant, language risk, value selection, sentiment and the setup assistant, each with tier defaults supplied and its own switch. Settings are staged and saved as one audited batch, in the same way as Application Settings, and the screen links to connection health, usage and background jobs rather than repeating them. Only the settings this application acts on are offered here; the remainder stay under Application Settings.
How will this affect users?
End users are not affected as only System Administrators have access to these settings. People can still turn VISDOM off just for themselves from the VISDOM AI switch in their own profile menu.
VISDOM Status Screen for Connection Health and Enabled Capabilities
Reference #: 260916.200.0014
A VISDOM Status screen in Administration gives one health view of the AI service: whether the application is authorized, whether its access is still valid and when it expires, which service it is pointed at, and which capabilities are switched on, including chat, live extraction, field reading, the model in use and the subscription tier. In the previous version this information was spread across the authorization and usage screens, and some of it was not visible at all.
The same screen carries first time connect. The system uses the activation key your installation already holds to identify your organization and provision or find the account, so an administrator no longer has to create an account with the service by hand and then come back to authorize it, and reachability is checked with a standard web request rather than a network ping, which is frequently blocked in hosted environments. Connecting is refused on a demonstration system or one that is already configured. The page otherwise reads configuration only, so opening it does not call the AI service or consume any of your word allowance.
How will this affect users?
End users are not affected as only System Administrators have access to this screen.
VISDOM Now Fills Record Fields That the Trained Extraction Leaves Blank
Reference #: 260916.200.0015
After the trained extraction has run, the fields it left empty are now put to VISDOM along with each field's label, description and kind and, for a field backed by a list, the actual values that list accepts. Measured on our own test agreements, the trained extraction was leaving most of a contract form blank, and the fields it missed were not obscure ones but obvious gaps such as title, vendor, status and description; those are the gaps this fills.
Every answer must quote the document's own words, and any answer whose quotation cannot be found in the document is discarded, so nothing is invented. An answer that does not map to a real list entry is dropped, everything is held to the configured confidence level, and the whole pass can be switched off. Values found this way arrive on the same review screen as the rest of the extraction and are reviewed and accepted in the same way.
How will this affect users?
Anyone creating or updating a record from a document has fewer fields left to key by hand, and still reviews every value before the record is saved.
Ability to Export Assistant Results and Open the Records They Name
Reference #: 260916.200.0018
A list of records returned by the assistant now carries a download control that saves the same rows as a spreadsheet file, and each result carries a Go to record link that opens the record inside Contract Insight. A result whose record cannot be resolved simply has no link, rather than one that goes nowhere. Replies now render headings and tables as well as lists and bold text, so asking about a list gets a table back, and one tap follow up questions appear beneath an answer, each of them a question the returned rows can answer.
How will this affect users?
Anyone asking the assistant for lists of records can export them or open them directly, instead of retyping what the answer named.
Documents Now Shown on Their Real Pages in the VISDOM Workspace
Reference #: 260916.200.0020
A PDF opened in the VISDOM workspace now shows the document's actual pages rather than only the text read out of it, scrolls the whole document, and draws each finding on the line it belongs to, one box per line rather than one block over a whole clause. Clicking a finding jumps to its page and tags it. The plain text view remains and is still used for scanned documents with no text layer, and the original page images stay available through a toggle. Where a finding's wording cannot be located in the document, for example because a clause has been summarized or edited, the application says so rather than highlighting the wrong text. Two faults in the document pane were resolved at the same time: switching between views left the previous view on screen above the one you asked for, and a long document could not be scrolled past its first screen.
How will this affect users?
Everyone using Create with VISDOM or Edit with VISDOM reads findings in place on the page they sit on.
Updates to Create with VISDOM and Edit with VISDOM
Reference #: 260916.200.0021
Creating a record from a document is now a single workspace rather than the one dense screen of the previous version. Upload a contract or other agreement, VISDOM reads it, and the review step is the record's own add form pre-filled with the extracted values, each carrying a confidence indicator, so per-type fields, list fields, conditional fields and required checks behave exactly as they do on a normal add. Beside the form, a rail holds the clauses, obligations, risk and sentiment findings, possible system additions such as counterparties and governing law, GSA clauses and other key data read from the document, each reviewable and editable before you commit. The GSA pass names the federal clauses a document incorporates, each with its clause number, title and category and a link to the published text, and the ones you keep are saved with the record's found clauses. The document and the record sit side by side, so every value can be checked against the wording it came from, with a column for asking VISDOM about the document while you work. The document is attached to the new record on save, along with the clauses and obligations you kept. If your session is interrupted, the document you queued is still waiting when the workspace reopens.
Create with VISDOM and Edit with VISDOM are now the same workspace behind two entry points, so each gained what the other lacked. Reviewing an existing record gains obligations, the text and original document views, and the ability to create a company the document names but the system does not hold. Creating a record gains playbook coverage, redline, replace and insert into the document, the changes panel and filing the negotiation brief. Two behaviors stay different on purpose: creating a record applies every usable extracted value automatically, while editing never overwrites an existing value without you asking, and each screen says so.
Create with VISDOM has its own navigation entry and also opens when a document is dropped onto the application. Edit with VISDOM always needs a document, so it has no navigation entry of its own: it opens from a file's own action on a record's Files tab, or from Update with VISDOM in the record's Actions menu, which is where the same action sat in the previous version and which lands on that record's documents so the file can be chosen. A Word document opens for editing and a PDF opens for analysis only; any other file type, and a file another person has checked out, are listed but shown unavailable with the reason, so it is clear why a particular file cannot be opened and who is holding it. Saving files a new version of the document on the record, through the same versioning as every other edit, so the version you opened is kept alongside the one you saved. When wording VISDOM has already judged is changed, every findings panel says the findings on the edited clauses may now be out of date, and Re-analyze runs the analyses you choose again over the document as it now stands; where the document cannot be edited on the screen you are on, the control explains that VISDOM's reading is already current rather than sitting inactive with no reason given.
How will this affect users?
Everyone who creates records from incoming documents gets a clearer process, less re-keying, and the same set of capabilities whether the record already exists or not.
Fewer and More Accurate Clause and Alert Findings From VISDOM
Reference #: 260916.200.0022
When a paragraph was recognized by several trained categories, the previous behavior returned it once per category, so in our own testing roughly half of a result list was a word for word duplicate. A passage now produces one result carrying every category it was given, shown as the leading category plus a count, with the full list on the card, and all of them are saved. Where a paragraph names its own subject in its opening words, for example a paragraph beginning "Severability", that is now the category shown on the card and saved with the clause, instead of a leading category chosen effectively at random; only the opening of the passage is considered, so a cross reference further down does not retitle it.
A clause that favors one party used to raise two alerts, one saying it was unfavorable to the first party and one saying it was favorable to the second, which in our own testing made favorability findings outnumber genuine risk findings two to one. Where a clause has a party it goes against, that is now the single alert and the parties it favors are named in its detail, while a standalone favorable finding is still raised where there is no unfavorable side to pair it with. In addition, where the analysis cannot determine what kind of contract a document is, it now uses the contract type already chosen on the record instead of asking whether the language is standard for an unknown kind of contract, a question that had no answer and raised non standard language findings against perfectly ordinary clauses. Measured across a sample of real agreements in our own testing, these changes roughly halved both the clauses returned and the alerts raised, with no information lost.
How will this affect users?
Anyone reviewing clauses or alerts VISDOM found in a document sees a shorter list in which every entry is a distinct finding.
Extracted Values Now Select the Matching List Entry, and Formatted Amounts and Written Dates Are Understood
Reference #: 260916.200.0023
When VISDOM reads a document and fills a field backed by a list, such as the vendor, the extracted text is now matched against the real list entries so the correct entry is selected, rather than free text being left in the box. Matching allows for differences in spacing, capitalization and small spelling variations, and where nothing matches confidently the raw text is left for a person to review. Amounts written with currency symbols or thousands separators, and dates written out in words, are now recognized and converted into values the form accepts; previously anything that was not a plain number or a plain date was quietly dropped, and a value that still cannot be interpreted is now listed as needing manual entry instead of disappearing.
The review bar also counts only the values that actually landed on the form, shown as the number applied and the number needing review. Anything VISDOM found that is not configured on the chosen record type is listed separately as not on this form, instead of being counted and then silently dropped, which used to look like a mapping fault.
How will this affect users?
Anyone creating records with VISDOM re-keys far less, and the count on screen matches what is really on the form.
Updates to Extract Clauses with VISDOM
Reference #: 260916.200.0026
From a header action on the Clause Library, or from a file in My Pending Files, you can upload one or more agreements and have every paragraph scored against the clauses in every playbook. The screen now reads a document's paragraphs on the server, using the author's own paragraph boundaries for word processing files and a clause heading splitter for everything else, instead of sending the document away to be read. It therefore works on a system where VISDOM is not configured and spends no AI allowance to gather the text; only the two draft buttons, which write a first pass at the negotiating comment and the business justification, call the AI service. A scanned page with no text layer yields nothing, and the screen names the file rather than reporting that no clauses were found.
Paragraphs that do not match anything already in the library are now offered in a separate New to your library group, so a document can be used to build the library rather than only to re-capture wording for clauses you already hold; in the previous version these were calculated and then never shown. Each paragraph produces one candidate carrying every playbook it matched, instead of a separate card per playbook, and only the best match's playbook is pre-selected, so ticking a card does not quietly commit the clause to a dozen playbooks. A candidate is now a card summarizing what will be saved, what it is called, how close the match is and where it came from, with the editing in a pane beside it split into a review view and a comparison against your library that shows the matching clause, the redline between them and the option to replace the existing wording. A single searchable picker replaces the previous pair of drop down lists, so a library of more than a thousand clauses is still workable.
How will this affect users?
Anyone who curates a clause library can grow it from documents already in hand, including customers who have not enabled VISDOM.
Updates to the VISDOM Usage Screen
Reference #: 260916.200.0027
VISDOM Usage now has a month picker, so any previous month can be reported on; in the previous version the monthly figures were fixed to the current calendar month with no way back. The allowance gauge follows the month being viewed and names it, and where the month you picked has no recorded activity the page says so and tells you the date usage actually ends on, instead of showing zero totals beside populated average tiles and a full user grid, which previously made the screen look broken. The default view still opens on the current month.
The page reports word consumption with monthly and daily totals, averages, the subscription tier cap with the percentage consumed, and a per user breakdown that names the model each person's answers came from. One control switches between the monthly and the daily view, and where more than one VISDOM tier is available a second control switches between those. The figures are calculated directly from the usage log, so opening the page does not call the AI service or consume any allowance. Authoring of usage alerts is not available on this screen in this release.
How will this affect users?
End users are not affected as only System Administrators have access to this screen.
Field and Obligation Type Definitions Are Now Sent to VISDOM Automatically
Reference #: 260916.200.0028
Your field definitions, record type definitions and active obligation types are now sent to the VISDOM service as part of the daily VISDOM job, straight after it confirms a working connection, so extraction matches what your system actually holds. A Sync field metadata button on the VISDOM Status screen does the same on demand, and all active obligation types can be sent from there as well, which is useful on a new environment. Previously only types somebody had edited since the upgrade had ever reached the service, which is why obligations could come back under types the system did not recognize, and why field level extraction could return nothing while clause analysis worked.
Creating, editing or deleting an obligation type still sends the change to VISDOM straight away, but the change is now saved in Contract Insight whether or not that send succeeds. In the previous version a delete was abandoned when the service rejected the call, so an obligation type could not be removed at all while VISDOM was unreachable. Two corrections on the same screens: the record area list now reads Vendors/Customers, and a type's detail screen shows the date it was last updated in the updated field instead of repeating the date it was entered.
How will this affect users?
End users are not affected as only System Administrators have access to this setting, although everyone relying on field level extraction benefits from the definitions being kept in step.
VISDOM Background Preloader Now Runs as a Scheduled Job
Reference #: 260916.200.0029
The VISDOM Background Preloader listed under Administration, Scheduled Jobs is now a working job that finds pending document analysis work, processes it, and sends the completion email and in application notification when it finishes. Service health is checked before new work is accepted. It is supplied switched off, so a System Administrator must enable it before it runs on a schedule.
How will this affect users?
End users are not affected as only System Administrators have access to this setting, although where it is enabled, document analysis is prepared before a user opens the record.
Updates to the Document Pane and Panel Layout in the VISDOM Workspace
Reference #: 260916.200.0030
The workspace now opens document first, with the review panel narrower so the document takes the larger share of the screen, and the size control widens the panel on its first press, stepping it through three preset widths, 40, 60 and 75 percent, with the document taking the rest. The divider between the document and the findings can be dragged and the width you choose is remembered for next time; double clicking the divider forgets it again. The editing toolbar can be folded away from the side rail, which gives the document more height for reading, and that setting is remembered as well.
A document opens fitted to the width of its pane and re-fits when the pane grows, so hiding the panel, dragging the divider or maximizing the window no longer leaves the page stuck at a small zoom, and a document that occasionally opened cut off at the right edge now settles correctly. The word processor's own review pane starts closed, so the document itself is what you see, and tracked changes are accepted or rejected from a changes panel beside the findings that produced them, individually or all at once. Dropping a document onto either workspace now loads it into the page rather than being taken by the header's intake area.
How will this affect users?
Anyone reviewing a document with VISDOM, particularly on a smaller screen, gets more of the screen given to the document and keeps the layout they chose.
Risk and Sentiment Findings Now Presented as One Graded Alerts List
Reference #: 260916.200.0031
High risk findings and party sentiment are now presented as a single alerts list graded Critical, Warning and Info, with a count summary in the review bar, the same underlying reasons the analysis gives, and a filter across all three grades. Party sentiment is shown per party with no perspective to set first, which in the previous version left every clause reading as neutral until it was changed. Findings can still be dismissed for the session. The workspace also opens as soon as the document has been read and the field values extracted, with clauses, obligations and their dependent analyses arriving behind their own indicators, rather than holding the whole review back until every pass has finished, and the waiting estimate is based on how long this system's own recent documents actually took.
How will this affect users?
Anyone reviewing risk and sentiment findings gets one ordered list and can start reading the document sooner, especially on long documents.
Refinements to the VISDOM Assistant Panel
Reference #: 260916.200.0032
The assistant being used and the tier every answer is billed at now sit on a permanent slim strip under the panel header, as two compact pickers, replacing a summary chip that took two clicks to read and three to change. Starter questions are written per assistant and per area, rather than every list in the application offering the same generic prompt, and they wrap so all of them are readable where they previously ran off the edge of the panel. After a data answer, the follow up suggestions are drawn from the rows that actually came back and take over until the subject changes; they are no longer printed under every reply and are available from the suggestions control when you want them.
The panel follows the application theme correctly in both light and dark mode, uses the application's own slim scrollbar, and honors the operating system setting for reduced motion, so the panel and its activity indicators stop sliding and traveling. It also adds a widen toggle that is remembered between visits, copy on hover for any answer, Escape to close, the cursor landing in the box when the panel opens, an input that grows as you type, and hover timestamps. Dates that carry no time of day are shown as a date alone instead of being followed by "12:00:00 AM".
How will this affect users?
Everyone using the assistant gets a panel that is easier to read and quicker to work in, particularly people working in dark mode or with reduced motion turned on.
Smaller Improvements to Creating a Record with VISDOM
Reference #: 260916.200.0033
When a document is dropped into Contract Insight you can create a record with VISDOM, create a record by hand, or attach the file to an existing record. Files parked in My Pending Files previously offered only the last two, so parking a document quietly cost you the AI route. My Pending Files now carries Create with VISDOM as well, using the copy already stored so nothing is uploaded twice, and the action is shown with an explanation rather than hidden where VISDOM is switched off.
The save control on the workspace is now a split button with three destinations. The default action creates the record, attaches the document, saves the clauses and obligations and opens the new record; the second does the same and then resets the workspace for the next document, which suits working through a stack of documents in one sitting; and Save & edit jointly creates the record, attaches the document and opens that document straight into a joint document process, so a document read and marked up with VISDOM can be handed to the other side without a detour through the record's Files tab. The third is offered on Create with VISDOM only, and where the joint document process has not been set up on the system it is shown switched off with that reason rather than hidden. Email the brief now creates the record and opens the message against it in one step, where it used to sit switched off telling you to save the record, leave the screen and come back. A message naming a required field that is still needed now takes you to that field, opening its tab and section rather than only switching panel.
How will this affect users?
Anyone processing documents with VISDOM has fewer round trips: the AI route is available wherever the document is parked, several records can be created in a row, and the summary can be sent without leaving the screen.
The Record Types and Document Formats VISDOM Works With
Reference #: 260916.200.0043
Create with VISDOM offers the six kinds of record VISDOM is trained to read: contracts, requests, purchase orders, Vendor/Company records, employees and solicitations. Only the kinds you hold permission to create are listed, so most people see a shorter list than the full set. The same six are where Update with VISDOM appears in a record's Actions menu and where a file's Edit with VISDOM action opens from, because they are the record types that keep documents. On every other kind of record, a document is worked on with the ordinary document tools on its Files tab.
Both workspaces accept Word documents, rich text files and PDFs, up to 30 megabytes each. Plain text files are not accepted, because the document reader will not take them. A file of a kind that is not accepted, or one over the size limit, is refused as it is chosen, with a message naming the reason, rather than failing later on the loading screen. A scanned page carrying no text layer gives VISDOM nothing to read, and the workspace says so and keeps the page images on screen instead of presenting an empty review.
How will this affect users?
Anyone feeding documents to VISDOM knows before starting which records it covers and which files it will take.
Obligation Types and the Field Updates Each One Applies
Reference #: 260916.200.0044
Obligation Types, in the Administration hub under Lookup Tables, is where the kinds of obligation people track are defined, with the list and the type itself on one screen. Each type carries the field updates it applies to the record when an obligation of that type is applied: setting a field to a fixed value, or setting a date by counting an interval forward from another date and landing it on a chosen day of the month. Existing updates are listed with a delete action on each row, and a new one is built by choosing the field first, so only the settings that field can accept are offered.
A type belongs to one record area and can be limited to a single record type. Changing the area clears the field updates, because they no longer apply, and changing the type keeps only the ones that still do. Only active types are offered to a reviewer or sent to VISDOM, so a type nobody has activated produces no suggestions.
How will this affect users?
End users are not affected as only System Administrators have access to this setting, although the obligations users are offered, and the field updates that applying one makes, both follow from what is defined here.
Where VISDOM Is Not Connected, the AI Screens Show Clearly Marked Sample Results
Reference #: 260916.200.0046
On a system where VISDOM Services have not been connected yet, Create with VISDOM and Edit with VISDOM still open and still work as screens, filled with generated sample values so the process can be seen and tried before the service is connected. A Sample data marker sits in the workspace header and states that no AI ran, the banner across the review asks for the values to be checked before a record is created, and the document question panel says its replies are placeholders. Nothing is sent anywhere and none of your word allowance is used. Connecting the service on the VISDOM Status screen in Administration replaces the samples with real readings from the next document onward.
How will this affect users?
Anyone at an organization that has not connected VISDOM can see how the screens work, and can tell at a glance that the values on them did not come from their document.
Change in Behavior: Who May Ask VISDOM Questions About Your Own Data
Reference #: 260916.200.0047
Answering a question from your own contract data is governed by an application setting with three positions, nobody, administrators only, or everyone, and by a named permission that switches the same capability off for the individuals who hold it. Both existed in the previous version and made little practical difference there, because the assistant answered from the language model rather than from your data. Now that it writes and runs a real query against your database, they decide who gets an answer at all, so the position should be confirmed as the one your organization wants before people begin asking.
Where somebody is excluded, the assistant says so in one sentence instead of answering from general knowledge. The administrators only position is judged by the person's license level being Administrator, which is the rule the previous version used and is kept deliberately, and it therefore covers fewer people than the system administrator setting on an account would.
How will this affect users?
Users who are excluded are told plainly rather than being given an answer drawn from general knowledge. The two controls themselves are reached only by System Administrators.
Change in Behavior: The VISDOM AI Switch in Your Account Menu Now Turns the AI Off
Reference #: 260916.200.0048
The VISDOM AI switch in your own account menu now turns VISDOM off for you entirely: the assistant button, the entry points for creating and editing records with VISDOM, and document extraction all disappear while it is off, and return when it is switched back on. In the previous version the same switch chose which version of VISDOM answered you, so turning it off left the AI running on the other setting. Choosing which VISDOM tier answers has moved to the assistant panel and the AI workspaces, where it is picked per conversation rather than once per account.
The switch is not shown at all where an administrator has turned VISDOM off for the whole organization, because there is nothing left for it to decide.
How will this affect users?
Anyone who had set this switch in the previous version should check it after the upgrade, because it now decides whether VISDOM appears at all rather than which version answers.