Elite DCS
22px
Elite DCSPrepared for
Timed Build 01 (Practice Naturals test build)

Handoff document · Client Build

Timed Build 01 (Practice Naturals test build)

Prepared August 25, 2026. Every item below was read back from your live account unless it says otherwise. Three states only: confirmed, done but not yet confirmed (with the reason), or waiting on someone else (with who and roughly when).

Last updated August 25, 2026 at 10:58 PM UTC · this page is refreshed every time the account is re-checked

Not ready to hand off: 4 items still to confirm7 items confirmed against your live account, 4 done but not yet confirmed, 2 waiting on someone else.
7
Confirmed
4
Not yet confirmed
2
Waiting on others

Confirmed in your account

Each of these was read back live, not assumed.

Checked

Intake form exists in the account

The intake form is in place: GHL Command Blueprint — Client Intake is live in the account, alongside the existing Practice Naturals Inquiry form.

Checked

Brief validates with no gaps

Your intake answers were turned into a build brief for Practice Naturals and checked with no gaps: an online-store setup aimed at capturing and nurturing leads, with text messaging registration (A2P) approved. The one note is that the calendar is not connected to Google or Outlook yet, which is a reminder rather than a problem.

Checked

Every planned pipeline and stage exists

The Practice Naturals Pipeline is in place with all seven stages in order: New Lead, Contacted, Qualified, Consult Booked, Won, Reorder / Retention, and Lost.

Checked

Every planned custom field exists

All seven planned contact fields are in place, including Lead Source, Program Interest, and Clinic / Practice Name, along with 29 intake fields that hold the answers from your intake form, for 36 fields in total.

Checked

Every planned tag exists

All 20 planned tags are in place, including interest-nutrition-program, lifecycle-new-lead, and source-website, plus 2 intake tags, for 22 tags in total.

Checked

No silently broken reference in any workflow

All nine workflows were checked for links to things that do not exist, such as a missing tag, field, or pipeline stage, and nothing was wrong.

Checked

Account health summary shows no blocking issue

A review of the account found nothing that would block going live. The account is still quiet: one contact so far, no deals in the pipeline, no conversations, and no phone number set up yet.

Done, not yet confirmed

The work was done; the read-back could not confirm it yet, and here is why.

Done, not checked

Every planned workflow exists and is published

Why it is not confirmed: All eight planned workflows have been built, including Speed to Lead, Lead Nurture, and Won - Welcome and Retention, but every one of them is still saved as a draft and is not running yet. Only the Blueprint Intake — Submitted workflow is switched on, so the other eight need to be turned on before they will do anything.

Done, not checked

Users and roles as planned

Why it is not confirmed: No team members have been added to this account yet, so there is nothing to compare against the plan. Until at least one person is added, the workflows have no one to send internal alerts to.

Done, not checked

Workflow bodies match the plan action for action

Why it is not confirmed: The original build plan was not available during this check, so the workflows could not be compared to it step by step. All eight workflows were read in full and hold 56 steps between them, with each pipeline stage move placed after a check that the deal exists, but none of them is switched on yet.

Done, not checked

Client completes one named task unaided on the handoff call

Why it is not confirmed: This is checked on the handoff call itself: you complete one everyday task in the account on your own, without help. It cannot be verified automatically, so it is recorded by hand once it happens.

Waiting on someone else

Outside our control. Who resolves it, and roughly when.

Waiting on someone else

A2P registration approved

Who resolves it: Phone → Trust Center in the GHL UI shows Approved. Roughly when: 1 to 7 business days after submission.

Waiting on someone else

Calendar OAuth (Google or Outlook) connected

Who resolves it: Settings → Integrations shows the connected account. Roughly when: same day; it is the client's own login.

What happens next

  1. Review the workflows and publish them; until then nothing sends
  2. Add at least one staff user to the account so notifications and calendars can be assigned
  3. Keep the approved build plan with the account so future checks can compare against it
  4. On the handoff call, complete one named task in the account yourself; whoever runs the call records it
  5. A2P registration approved: Phone → Trust Center in the GHL UI shows Approved (1 to 7 business days after submission)
  6. Calendar OAuth (Google or Outlook) connected: Settings → Integrations shows the connected account (same day; it is the client's own login)
Prepared by Elite DCS for Timed Build 01 (Practice Naturals test build) · August 25, 2026Prepared by Elite DCS