Contract graph you can query before every renewal.

Point Nexus at the contracts folder. It builds a queryable graph of parties, clauses, obligations and renewal dates, so you can ask which contracts renew in the next 30 days and get each one cited to its clause.

Run Nexus
AuthorMariete
AgentNexus
Runtime~ 15 minutes to build the graph
IndustryLegal Ops
  1. 1

    Describe the task

    Nexus can take a folder of PDF contracts and turn it into a living graph of parties, clauses, obligations and renewal dates, no manual calendar entry, no clause read twice. It reads each agreement, pulls out who owes what by when, and links related contracts to the same counterparty, so you can ask which deadlines fall in the next 30, 60 or 90 days and get them back with the obligation and the source clause, cited.

    The more clearly you define the triggers, the sharper the answers. Tell Nexus where the contracts live, which dates matter, and how you want obligations grouped, and it holds that structure consistently across every agreement in the folder, ready to query.

    Index the contracts folder at drive://legal/contracts and build a living obligation graph. For each agreement: - Extract the parties, key clauses, and obligations on both sides - Capture every date-based trigger: renewal, notice period, price review, termination window - Link contracts that share a counterparty so I see total exposure per vendor When I ask, list every trigger in a date range with the contract name, the deadline, and the action required, and cite the clause and source file for each. End with a summary: contracts indexed, upcoming triggers in the next 90 days, and any auto-renewals I should decide on now.

  2. 2

    Give Nexus context

    In a Nexus workspace, point the run at the contracts folder and tell it which date-based triggers matter. Nexus reads the agreements together, so two contracts with the same vendor resolve to one counterparty node and you see total exposure instead of scattered PDFs.

    Tell Nexus your notice-period convention up front, some contracts count 30 days from the renewal date, others from the notice deadline. Stating the rule once keeps every answer counting the deadline the same way, so a query for the next 30 days never misses a window.

    Required context
    A contracts folder or DMS export containing the signed agreements to index
    The date-based triggers that matter to you, renewal, notice period, price review, termination window
    Optional context
    A standard notice-period rule, so every answer counts deadlines consistently across differently worded contracts
    A glossary of counterparty aliases, so one vendor under three names resolves to a single node
    A list of priority counterparties, so high-value renewals surface first when you query the graph
    legal/contracts foldernotice-period-rules.mdcounterparty-aliases.md
  3. 3

    What Nexus creates

    Nexus reads every agreement, extracts the obligations and dates, and links contracts by counterparty into one graph. You get a queryable obligation register: ask for the triggers in any date range and Nexus lists them with the deadline, the action required and the source clause, cited, and flags any auto-renewal that needs a decision now.

    From Nexus: Indexed 214 contracts from drive://legal/contracts into a live obligation graph.

    214Contracts indexed
    38Triggers in the next 90 days
    7Auto-renewals to decide now
    Triggers in the next 30 days11 triggers
    ContractCounterpartyTriggerDate
    Cloud hosting MSAAurelia CloudAuto-renewalAug 14
    Data processing DPAMeridian DataPrice reviewAug 22
    Office leaseHarborline RealtyNotice windowAug 28
    Exposure by counterparty2 flagged
    CounterpartyActive contractsNote
    Aurelia Cloud3Two auto-renew in the same window, worth consolidating
    Meridian Data2Price review clause with no cap, flag for legal

    "7 contracts auto-renew inside the next 30 days and would need notice served this week to exit. Want me to pull the exact termination clause and deadline for each so you can serve notice, or show total exposure per counterparty first?"

  4. 4

    Follow-up prompts

    Pull the exit terms for each renewal

    For any renewal you might exit, Nexus can return the contract’s own termination clause, the party to notify and the deadline to serve notice, cited to the source, so you have everything the letter needs. Pair it with Painter or Builder when you want the notice itself drafted.

    For the 7 auto-renewals I want to exit, list the exact termination clause, the counterparty, and the deadline to serve notice for each, cited to the source contract.

    Fold newly signed contracts into the graph

    When new agreements are signed, drop them in the contracts folder and re-point Nexus at it, the new contracts join the graph on your next run, their triggers extracted and ready to query alongside the rest.

    Re-index drive://legal/contracts and fold any newly signed contracts into the graph. Show me their date-based triggers in the next 90 days, each cited to its source agreement.

    Ask for a renewal rollup on demand

    When legal ops wants the full picture, ask Nexus for a rollup of everything coming up in the next 90 days in one place, grouped however you need it, instead of chasing one contract at a time.

    Give me a rollup of all triggers in the next 90 days grouped by counterparty, with the action required and the source clause cited for each.

  5. 5

    Tips and troubleshooting

    State your notice-period rule once

    Contracts word deadlines differently, "60 days before renewal" versus "by the notice date." Give Nexus one convention and it normalises every answer to it, so a query never surprises you with a window that closed earlier than expected.

    Link by counterparty to see real exposure

    A single vendor with four contracts is easy to under-manage as four separate PDFs. Nexus rolls them into one counterparty node, so you negotiate and renew with the full picture instead of one agreement at a time.

    Scanned contracts need OCR first

    Image-only PDFs with no text layer will be flagged rather than indexed. Ask Nexus to run OCR on those, or feed it the text-based originals, so no obligation slips through because a file could not be read.

  6. Ready to try it yourself?

    Point Nexus at your contracts folder, name the dates that matter, and ask which renewals, notice windows and price reviews fall in the next 30, 60 or 90 days, each answered with the deadline and source clause, cited.

    Run Nexus