Illustrated workflow
Keep the connection offer in view.
Bring the offer, its written expiry and the next decision together before an acceptance is due.
Illustrated engineering workflows, with current product capabilities and the decisions for your people shown on each page.
The example
A connection offer arrives with conditions and a written expiry. This example follows a person checking those terms and preparing a decision.

The illustrated steps
Keep the offer
File the original offer and its attachments against the confirmed job.
Read the written terms
The project lead checks the offer itself for its expiry, conditions and any required response.
Confirm the date
A person records the date from that offer, with the source. This example assumes no standard validity period.
Prepare the review
Bring the offer and outstanding questions to the person responsible for the decision.
Decide what happens next
The managing director or authorised person decides whether to accept or ask for a change.
Record the response
The authorised person handles the response and any payment outside this illustration, then keeps the record.
What is built, and where it stops
These existing date checks and registers do not establish a complete connection-offer watch service. Automatic offer extraction, acceptance and a guarantee against expiry are not available claims.
Current product scope recorded 28 October 2026. Built, switched off means it is not switched on for customers yet. Coming means it is planned and not yet available.
- James: Daily contract, framework and compliance date checks
- Built, switched off
Checks contract, framework and compliance dates and lists those coming due for the managing director.
- James: Contract, NDA, framework and dispute registers
- Built, switched off
Keeps registers of contracts, NDAs, framework call-offs, disputes and professional indemnity exposure.
Records only, not legal advice.
These scope statements use the same source as the Feature List in the procurement pack. Read the OpsWork specification →