Why does a customer detail change require reasoning across business processes?

A customer asks a utility provider to change their postal address. The account contains a correspondence address, a service location and an address attached to an unresolved installation request. These fields may contain identical text while representing different facts. Changing all of them would move the paperwork correctly but could send a technician to the wrong property.

The agent must interpret what changed, identify which records depend on that fact and preserve records that describe something else. Matching field names is insufficient: a service location represents where supply is delivered, while a correspondence address represents where notices should go.

This matters for training because a locally correct edit can produce a globally incorrect outcome. It matters for evaluation because checking only the account record misses damage elsewhere in the process.

A generated task pack can make these distinctions explicit through relationships and policy text. Buyers can assess whether an agent follows the meaning of a change across the business, including recognising when a superficially similar field should remain untouched.