Contract Review

A contract holds the terms that a counterparty expects nobody else to read. Summarizing one with a model moves those terms into a request, and a careless prompt can move a settlement figure with them. The controls here concentrate on that boundary and on the wording that comes back.

In-house counsel and contract teams reach for this starter when redlines and summaries already run through a model. A prompt that contains the words settlement amount is refused, and the same applies to sealed filing and to privileged and confidential. Matter numbers and docket numbers are masked before the request leaves the gateway. Contract language often includes those blocked phrases, so plan wording and staff guidance in advance.

Returned text that instructs a reader to sign this settlement is blocked, and so is text that says file this lawsuit. That screen keeps a clause summary from reading as direction to a client. One response screen is reserved for privilege wording and holds no phrases yet.

The source check pulls citations out of the draft and grades them against supplied context. It flags what it cannot verify and lets the answer through unless you configure a block. The aggregate floor is 0.90, and relevance and accuracy must reach 0.78 and 0.80 in turn. Length below 120 characters fails the same check.

Privilege calls, professional duties and the final contract position remain with a qualified lawyer. No reviewer is paged when a clause summary looks wrong, because the oversight setting is empty until you fill it in. Audit marking never blocks a call and never becomes a retention record. History capture keeps metadata about each call rather than the text of the exchange.