What does a conditional policy issue look like in a generated insurance environment?

A small-business insurer's underwriter approves quote QTE-5521 for a commercial property policy, subject to one condition: a current fire safety certificate must be on file before cover starts. The policy administration team receives the task to issue the policy.

In the environment, the agent reads QTE-5521, finds the party BIZ-2260 and checks documents. The certificate DOC-9014 is present but expired, and the start date in the quote is three days away.

The agent has three paths. It can issue POL-7782 as active, which breaks the condition. It can close the task without issuing anything, which leaves the customer uncovered and unexplained. Or it can create POL-7782 in pending status, link the quote, send a request for an updated certificate to the broker contact, and set a follow-up task for the underwriter dated before the start date.

The third path produces the expected end state: one pending policy, one document request, one follow-up task assigned to the underwriter role, and no premium invoice yet.

The first path pays off later in the episode, when a claim arrives against an active policy whose condition was never met and the claims team has to contest cover.

**What it teaches:**

- A pending state lets the agent make progress without overclaiming. - Conditions in an approval must be read and enforced. - Delayed events let the grader see the cost of a shortcut.