Spline Client Scene Handoff and Export QA (Delivery)

Spline Client Scene Handoff and Export QA (Delivery)

1. 01

   Duplicate the approved scene into a client-owned Spline file

   Copy the master scene out of the agency workspace into a file owned by the client account so the retainer does not depend on one designer's seat. Keep the agency copy as the working master and treat the client file as the delivered artifact.

2. 02

   Lock the scene structure and name every layer before export

   Rename groups and layers to client-facing names, then freeze geometry so late edits do not break the embed. Spline's version history is the rollback point if a rename breaks a variable binding.

3. 03

   Audit Variables, APIs and Webhooks on the Pro tier

   Pro at $30 per seat monthly ($25 annual) includes unlimited Variables, APIs and Webhooks. Confirm every dynamic field points at a live endpoint and that no webhook still targets a staging URL before the client sees it.

4. 04

   Verify the export target matches the client contract

   Web embed with no watermark is available from the Hobby tier at $15 per seat monthly ($12 annual). Apple and Android exports and video export require Pro. If the brief includes an App Store build, confirm the client is paying for the Pro seat before you promise the Xcode project.

5. 05

   Run the mobile and desktop load check on the live embed

   Test the embedded scene on a throttled mobile connection and on desktop, then record frame behavior. Spline scenes that pass on a studio machine routinely stall on mid-range phones, and this check is what protects the delivery timeline.

6. 06

   Strip agency branding from anything client-facing

   Spline does not publish a white-label program, so client-facing exports and embeds carry Spline branding. Tell the client this in writing at handoff rather than letting them discover it on launch day.

7. 07

   Hand off credentials and a one-page operating note

   Transfer the client file, list which tier each seat sits on, and note the monthly cost the client is absorbing. Include the refresh cadence your retainer covers so scope creep on scene edits has a written boundary.