Contract Renewal Agent
Tracks supplier contract renewals and notice dates.
- Industry
- Oil & Gas
- Department
- Procurement
- Team
- Sourcing and Contracts
- Kind
- Assistant
- Approver
- Procurement Lead
- Code
- PRC-04
It tracks renewal and notice dates on contractor and supply contracts, such as drilling rigs, supply vessels, catering, chemicals and frame agreements, and the rates and call-off volumes behind them. It builds the renewal calendar and flags contracts to retender before their notice dates pass.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ERP's finance, maintenance and supply modules: the contracts register with end and notice dates, annual spend, rate history and extension options..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Procurement Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ERP's finance, maintenance and supply modules: it sets the renewal reminders and opens retender requests for the contracts named. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The contracts register guide: notice periods, auto-renewal and extension option terms, rate review clauses, retender rules and the owner of each contract.
Reads from
the ERP's finance, maintenance and supply modules: the contracts register with end and notice dates, annual spend, rate history and extension options.
Acts in
the ERP's finance, maintenance and supply modules: it sets the renewal reminders and opens retender requests for the contracts named.
Hands back
A list with one entry per contract, each with reference, supplier, end_date, notice_date, action (renew, extend, retender or exit), reason, campaign_conflict (or null) and owner.
Asks a person when
A contract's notice date is less than 120 days away and no owner has acted, or a rig or vessel contract would lapse during a planned campaign.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Start review before the notice date (days) | 120 | Owners are alerted this many days before the notice date. |
| Warn before auto-renewal (days) | 60 | Contracts that renew automatically get an extra warning. |
| Rate rise that triggers retender (%) | 10 | A proposed rate rise above this sends the contract to retender. |
| Annual value that must be retendered (USD) | 1000000 | Contracts above this are retendered at the end of their term. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Alert each owner 120 days before the notice date, and 60 days before any auto-renewal.
- A rate rise above 10 percent, or a contract above 1000000 a year at term end, goes to retender.
- Check a rig or vessel contract's end against the planned campaigns that need it; a gap or overlap is named.
- Use an extension option only within its written terms; never assume one exists.
See the Contract Renewal Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.