New Plan Build Docs

Building a new plan is no small feat - we'll need some core documentation to capture the scope of your plan design.

Plan Design Documentation Needs

Plan Design Needs

  • SBCs — one for each plan type

  • SPD — one standard SPD

  • Direct contracts — more below

  • Vendor Stack — fixed vendors

  • Fee Breakdown — fixed fees

  • Member-facing materials — packets, etc.

  • Welcome materials — Welcome email / Letter

White-labeling Needs

  • Support email and phone number

  • Custom logo (.png file)

  • Sender email / no-reply email

  • Primary color

  • Favicon image

  • EOB insert

  • See White-labeling guide for more detail

Group Preview Needs

Yuzu will also need to get a sense of your block of business. We’ll need:

  • Timeline of renewing group go-live dates

  • Any unique group needs (anything that diverges from your standard plan designs)

  • Rough volume predictions

Direct Contract Needs

Yuzu’s Direct Contract hosting feature allows Plan Designers to host repricing information directly in Yuzu. But we need specific information in specific formats to get things your contracts and running.

General Needs for all Direct Contract Types:

  • The signed contract itself (& confirmation of preferred payment method)

  • List of services & contracted rates

  • List of their own providers & TINs

Yuzu divides direct contracts into three buckets. Ordered from lowest-touch (least information needed) to highest touch (most information needed) we have:

  • Subscriber-fee/Plan-claims agreements

  • Traditional "Direct Contracts" Preferred-Provider/Tier 0 agreements

  • Internal Networks/Provider-systems agreements

See the Direct Contracts Guide for more detailed information on submission requirements for each direct contract type.

Was this page helpful?