Skip to main content
DoneThat

AI Adoption GuideProcurementSelect

Contract term pre-population

Based on selected supplier and category, AI pre-populates standard terms, SLAs, and payment schedules into the contract shell, using tools like Ironclad.

Procurement processRequestApproveSourceEvaluateSelectOrderReceiveReview

By Don, DoneThat’s AI coach · updated

Populate from this award, not last year's signed file

The job is to fill a contract shell from the awarded event and the category playbook. It is not to rewrite the deal or copy last year's MSA.

Commercial values come from the award pack: price, volume or sites, payment schedule, term, and any SLA the issued RFP asked for and the awarded bid accepted. Standard T&Cs come from the category template. Locked legal and ESG stay locked. Where the event was silent, the field stays blank.

A model that "completes" the document by borrowing last year's SLA, last year's Net terms, or a category default the RFP never stated is drafting a different contract than the one you awarded. Speed here means assembly, not invention.

Ironclad, Icertis, SAP Ariba, and Coupa are examples of the same class: contract lifecycle and source-to-contract suites that assemble a draft from a template plus metadata. The mapping is the point. If the metadata is last year's file, the draft is last year's file with a new party name.

Three sources go into the shell

Run the fill from three inputs only. If one is missing, stop and get it rather than substituting a neighbor.

Awarded commercials. Take price, payment terms, term, start logic, volume or sites, and service levels from the awarded bid against the issued pack. If proposal scoring against RFP criteria produced a recommendation, still take commercials from the award record, not the scoring memo. A score is not a payment term.

Category template. Use the MSA or call-off shell for this UNSPSC or internal node: section order, definitions, standard exhibits. This is the playbook legal already approved for the category and value band, not a blank Word outline and not supplier paper.

Locked legal and ESG. Indemnity, limitation of liability, insurance minimums, audit, governing law, and any labor or ESG clauses that were mandatory in the issued RFP stay locked. Those shalls should match the pack that RFP/RFQ auto-drafting helped produce, as issued. ESG supplier screening may have informed who you invited. It does not author new clauses at award. A living-wage exhibit stays only if it was in the RFP.

Map fields by name. Price to price. Payment to payment. SLA to the SLA exhibit the RFP used. Do not let a generic "service level" slot swallow an IT availability clause.

Supplier mark-up on their paper is not a fill. It is a deviation queue for legal.

Worked example: facilities cleaning after a three-plant award

A manufacturer awarded a 36-month facilities cleaning MSA for three plants after a competitive RFP. The walkthrough is illustrative, not a measured result.

The issued pack asked for a fixed monthly price per site, monthly invoices on Net 30, a credit equal to a missed scheduled clean, and next-business-day response to a complaint logged in the plant system. The awarded bid accepted those commercials. It did not propose indexation, an "availability" percentage, or liquidated damages beyond the missed-clean credit.

The category playbook is a facilities MSA with locked indemnity, insurance minimums, audit rights, no-subcontract-without-consent, and a labor exhibit that was an RFP attachment.

What the fill should carry

  • Party names and sites from the award record.
  • 36-month term and the start rule the RFP published (first of the month after signature, not a guessed date).
  • Monthly price per site from the awarded commercial schedule.
  • Net 30 monthly invoicing, because that is what the RFP awarded.
  • Missed-clean credit and next-business-day complaint response, copied from the awarded SOW, not paraphrased.
  • Locked legal and the labor exhibit, untouched.

What must stay blank or blocked

  • Last year's SLA. The expiring incumbent file used a "service availability" percentage copied from an IT template. That figure was never in this RFP. Pasting it creates an SLA the event did not state.
  • Payment terms the RFP did not award. The incumbent was on Net 45. The fill must not keep Net 45 because master data still shows it. Net 30 won.
  • Indexation. The bid did not include an annual uplift. A category default does not belong in the shell.
  • Liquidated damages beyond the missed-clean credit. The RFP was silent. Leave the LD field blank for legal. Do not import an LD schedule from another site's MSA.
  • Termination notice. The playbook locks 30 days. The model does not overwrite it with 60 days from supplier paper unless legal accepts a deviation.

Contracting then reviews insurance certificates against the locked minimums, checks that SOW exhibits actually attached, and works the blank LD field. The draft is ready for legal's pass, not for signature.

If the event did not award it, the field stays blank

A complete-looking draft is a failure mode when the completeness is borrowed.

Treat every commercial field as one of three states:

  • Awarded. Copy the awarded text or value, with a pointer to the bid schedule or SOW paragraph.
  • Locked playbook. Insert the approved clause. The model cannot edit it.
  • Silent. Leave the placeholder empty and tag it for legal. Silence is not a cue to complete.

The substitutions that cause the most rework are last year's SLA and payment terms the RFP did not award. Category norms (Net 60 in logistics, availability percentages in software, CPI indexation in facilities) look professional in a gap. They are still not this event.

If the awarded bid is silent on a point the template expects, do not backfill from the runner-up's schedule. That bidder lost.

When a field is blank on purpose, say so on the cover sheet: "not awarded; legal to decide." A reviewer who sees an empty SLA table should not have to guess whether the model failed or the RFP never asked.

A pre-filled Word file is not executed

The output is a draft in the contract system. It is not a signed contract, a notice to proceed, or a PO.

Do not email the filled file to the supplier as "the contract." Do not start work against an unsigned file because the commercials match the award. The award authorizes you to negotiate and execute that paper. It does not replace execution.

Keep the draft in the CLM or contract workspace until the named legal reviewer clears locked-clause integrity, the blank fields, and any supplier mark-up. Signature, or your system's executed state, is the gate. Only then should contract terms auto-applied to PO stamp orders with the payment terms and SLA credits you actually signed.

Capture term, end date, and notice period from the executed record for contract renewal alerting. A guessed start date will page someone early, or not at all.

If work starts on an unsigned file, you have operations running with no executed limitation of liability and no clean PO match.

Is this worth automating for you?

Whether this pays back depends on how much time it takes your team today. Most teams estimate that from memory, and the estimate is usually wrong in one direction or the other.

DoneThat reconstructs where the time actually went, with no timers to forget, so you can measure the baseline before committing to a project and check the gain afterward.

Measure the baseline first