What does a generated task look like for a utility connection with site conditions?

A task pack for a utility's new connection process starts from this generated state. Connection offer CONN-5120 was approved by the network planning team with three conditions: a traffic management plan (COND-5120-1), a signed easement (COND-5120-2) and a switchboard inspection certificate (COND-5120-3). The scheduling system holds a crew booking, JOB-8841, in a provisional state.

The environment also holds a policy document stating that the traffic plan may be waived for private land by the planning lead, and that offers lapse if conditions are not met within the stated window.

The agent's task is to confirm the booking if the connection may proceed. The seeded state has COND-5120-1 waived with a recorded reason, COND-5120-2 satisfied by an uploaded easement that matches the property, and COND-5120-3 supported by a certificate dated before the switchboard was replaced, noted in a later field-service entry.

The expected outcome is to leave JOB-8841 provisional, flag COND-5120-3 as not satisfied by the evidence on file and request a new certificate from the customer's electrician. The grading record lists that outcome, the acceptable tool calls and the unacceptable one, which is confirming the booking.

**What it teaches:** a task pack can encode relationships across systems: a waiver that is valid, evidence that matches, and evidence that looks right but is stale. The answer depends on joining records, not reading one.