ESTATE-PLANNING

Irrevocable life insurance trust structure

An irrevocable life insurance trust, often called an ILIT, is commonly diagrammed around four relationships: the grantor's gifts, the trustee's administration, the policy held by the trust and the trust's distributions to beneficiaries. The life insurance carrier pays the death benefit to the trust under the policy terms, while the trustee administers the proceeds under the trust agreement. A diagram helps a family or adviser distinguish the policy owner from the insured person and from the people who may benefit. It does not establish tax treatment or replace the signed documents. Funding methods, policy ownership, beneficiary rights and notices can have significant consequences, so use the current trust and policy records when preparing the diagram.

UPDATED 2026-09-24
TYPEEntity
EXAMPLEIrrevocable life insurance trust structure
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Irrevocable life insurance trust

Key decisions

  • Funding: Show annual gifts to the trust.
  • Administration: Identify the independent trustee.
  • Policy: Show the trust's insurance policy.
  • Proceeds: Trace the death benefit and distributions.

When to reuse this

Use this as a conceptual ILIT diagram. Tax treatment, ownership and notice requirements need review with qualified legal and tax advisers.

FAQ

Frequently asked questions

What does an ILIT diagram show?01
It shows the grantor, irrevocable trust, trustee, policy, insurer and the path from gifts and proceeds to beneficiaries.
Who owns the policy in this example?02
The trust is shown as owning the policy; the diagram should be changed if the policy records state otherwise.
Why is the insurer separate from the trust?03
The carrier issues the policy and pays its death benefit, while the trustee administers the trust and its proceeds.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.