LearnGrokNothing here is legal advice. A draft is a starting point for a qualified person, not a substitute for one.
Start with the signed agreement, not a sales summary or an unsigned draft. Build one register that delivery and procurement can use to see the action, the deadline, the owner, the dependency and the contract source. These prompts are for in-house lawyers and contract managers handing a completed agreement to the teams that must run it.
Nothing here is legal advice. The outputs are draft work products. A qualified person must decide questions of construction, priority, enforceability and compliance.
Key point
Work from the complete signed set
Include the main agreement, amendments, order forms and schedules. A duty in a schedule is still a duty the delivery team may need to perform.
1. Assemble the contract set
Put the executed agreement, every referenced schedule and any amendment into one review set. Label each document before pasting or attaching it. Use names such as Master services agreement, Schedule 2: service levels and Amendment 1.
Do not treat a signature page as proof that you have the complete operational record. Check for references to:
- statements of work or order forms
- service descriptions and acceptance criteria
- pricing schedules that require reports or approvals
- security, data, insurance or policy schedules
- change controls and amendments
- an order-of-precedence clause
Use Build the first obligations register first. It creates the working list and preserves the source locator for each line. The model should extract a party obligation as written, then leave the internal owner unassigned unless your role map supports an allocation.
Watch out
Do not replace the contract party with an internal team
The supplier or customer is the contractual actor. Delivery, procurement and finance are proposed internal owners, not substitutes for that field.
2. Separate the register from the diary
A register answers, “What must happen?” A diary answers, “When must somebody act, and how?” Keep both. A renewal notice may be one register item but also needs a diary entry with the calculation, method, recipient and source clause.
Run Extract dates and notice requirements after the first extraction. Give it the same contract set and the register. This catches deadlines that are easy to miss because they sit in a boilerplate notice clause, a service schedule or a termination provision.
Use the diary for fixed dates and for conditional events. Conditional events include a request for consent, a breach notice, a change request or a missed milestone. They cannot be placed on a calendar until the trigger occurs, but they still need an escalation route.
If document upload or input handling affects your workflow, check the current, version-dependent options in the xAI documentation.
3. Allocate work without inventing accountability
Use Assign operational owners only after you have supplied an internal role map. That may be a short list of teams and responsibilities. For example, identify who controls service reporting, supplier communications, invoice approval, security evidence and acceptance sign-off.
The worksheet is deliberately a proposal. Send rows marked Unassigned or Low confidence to the handover meeting. Do not make a plausible guess merely to make the table look complete. A named person who has not accepted the action creates more risk than a visible gap.
Check
Test each row against the source
Pick several rows across the main agreement and schedules. You should be able to find the stated action, timing and trigger from the source locator without searching the whole document.
4. Check what the first pass missed
Run Check register coverage and conflicts before you circulate the register. This is where you find duties hidden in definitions, duplicated obligations and changes made by an amendment. It also prevents a summary in the main agreement from being treated as the only relevant wording.
Pay particular attention to entries with these warning signs:
| If you see this | Do this |
|---|---|
Not stated for a due date |
Check definitions, schedules and the trigger clause. Keep it as Not stated if no timing is given. |
| An action appears twice | Keep both source references and ask whether they are duplicates or separate requirements. |
| An amendment changes a schedule | Flag it for qualified review. Do not choose which wording controls. |
| An email address appears outside the notice clause | Do not assume it is a permitted notice address. |
The output is wrong if it turns a condition into a fixed obligation, drops a business-day qualification, assigns an owner unsupported by your role map, or omits the clause reference. It is also wrong if it presents conflicting wording as settled. Check a sample from every schedule, not just the main agreement.
Stop
Do not circulate an untraceable action list
If a row has no usable clause or schedule reference, it is a task suggestion, not a contract handover record.
5. Give operational teams a short briefing
Use Prepare the delivery handover brief when the register and diary have been checked. It produces a shorter document for the meeting, while the register remains the detailed record. Share both documents. The briefing helps teams start work; the register lets them trace each action back to the contract.
Ask each proposed owner to confirm three things: they understand the action, they can meet the timing, and they know what evidence to retain. Record the answer in your internal tracking system rather than changing the contract-derived fields without a source.
When it does not work
If the extraction is incomplete, split the review by document, then reconcile the results using the coverage-check prompt. If tables lose clause references, repeat the extraction with fewer documents and require page numbers where visible. If the contract wording is ambiguous, do not keep refining the prompt to force an answer. Mark the row for qualified review, preserve the wording and take the issue to the responsible lawyer.
