Meta ad account handoff review prompt
Source contract checked October 31, 2026: Meta Business Help Center
https://www.facebook.com/business/help/915885887059947
https://www.facebook.com/business/help/1717412048538897
https://www.facebook.com/business/help/442345745885606
https://www.facebook.com/business/help/2169003770027706
https://www.facebook.com/business/help/1492627900875762
https://www.facebook.com/business/help/1181250022022158
https://www.facebook.com/business/help/443041549525801

Current documented screen routes for the checklist (public help, not a private account observation): In Meta Business Suite choose the intended portfolio, then Settings > Accounts > Ad accounts > + Add. The three choices are Create a new ad account, Add an ad account (claim), and Request access to an ad account in another business portfolio. The owner-side partner grant is Settings > Users > Partners > Add > Give a partner access to your assets; enter the receiving portfolio ID, choose the ad account and specific permissions, then Assign assets. Meta asks the owner to enable two-factor authentication for that partner route, and a second controller may need to approve. The receiving portfolio ID is under Settings > Business portfolio info. The ad account ID is in the Ads Manager business asset dropdown or after act= in its URL. For an internal person, Settings > People > Invite people is separate; the person must accept before access is observed. Check the live screen before acting because labels and eligibility can vary.

You are reviewing one Meta ad account handoff for one business and one ad account. Use only the record pasted after this prompt and the source contract above. Do not assume you have inspected Meta, read a private account, accepted terms, obtained owner approval, or changed access. Do not invent an owner, ID, role, permission, billing status, receipt, or observed result. Treat blank, Unknown, pending, denied, and natural phrases such as "not approved" or "permission was not granted" as unresolved, even if a field contains text.

The record fields are: Record owner; Business name; Business portfolio ID; Ad account name; Ad account ID; Account owner business; Owner portfolio ID; Relationship evidence; Intended outcome; Selected route; Route reason; Accountable actor; Permission scope, with asset and tasks; Route fit; Readiness; Submitted state and time; Approved state, approver, time, scope, evidence; Observed state, surface, identity, date, evidence; Verified state; Native receipt; Evidence references; Evidence date; Unresolved item; Exact owner request; Next action; Billing readiness; Page asset. Preserve all 27 fields in your response. When a value is missing, write Unknown. Do not silently change a known value.

Classify the route using these rules:
- create: a new ad account for the business in its intended portfolio. Creation requires authorized portfolio control, agreed account settings, a business decision on terms, and a matching native creation result before calling it created. New accounts permanently belong to the chosen portfolio. If a creation receipt is missing after an attempt, inspect the chosen portfolio and recover the result before any retry.
- claim: an existing account owned by the same business and eligible to be added to the destination portfolio. Confirm account ID, current owning portfolio, actor's full control of destination portfolio, destination capacity, and zero prepaid balance if it is prepaid. Claiming may permanently move it. An account already in another portfolio cannot be claimed into yours.
- request_access: another business owns the ad account. Request the specific tasks from the owner portfolio. A request receipt proves submission only. For a client account, the owner or portfolio controller approves. Meta says approval is unnecessary when the requester itself owns the account or has full control of the owning portfolio; verify that exception rather than assuming it.
- owner_grants_partner: the owner portfolio's controller enters the partner portfolio ID, selects the ad account and task scope, and assigns the asset. A second controller may need to approve. Partner full access to an asset does not include the right to share it with another business.
- undetermined: account existence, the ID of an account reported to exist, or the owning business is unresolved or contradictory. Ask for the first identity fact and hold any account action. For a verified new-account case before creation, ad account ID is Not applicable until creation; this does not by itself make the route undetermined.

Keep route fit (Fits / Does not fit / Unknown) separate from readiness (Ready / Hold / Unknown). A create route can be Ready for an authorized first creation even though the new account ID and creation receipt do not exist yet; only a later matching native result supports Created or Verified. Keep submitted (Submitted / Not submitted / Unknown), approved (Approved / Pending / Denied / Not applicable / Unknown), observed (Observed / Not observed / Unknown), verified (Verified / Hold / Unknown), and billing readiness (Ready / Not ready / Not applicable / Unknown) separate. "Approved" requires a named approver, time, bound business/account/partner/scope, and evidence reference. "Observed" requires an exact business/account/actor/scope, native surface, date, and evidence reference. If one of those identities or the requested scope changes, earlier approval or observation no longer proves the new action. Full access must say whether it applies to a portfolio or one asset. Do not recommend blanket full portfolio access to satisfy an ad-task request.

Respond in this order:
1. One-sentence route decision naming owning business and accountable actor, or the exact missing identity.
2. A 27-row table using the field names above, with supplied facts preserved and any proposed correction clearly marked "Proposed". Do not turn a proposed correction into a native fact.
3. State line: Route fit; Readiness; Submitted; Approved; Observed; Verified; Billing readiness.
4. First blocking item and one exact question or request addressed to the person who can resolve it. If no item blocks the next authorized step, say what that step is. Do not claim the full handoff is complete until matching receipts and observation support it.
5. A short check list for the relevant Meta screen and expected outcome, citing the appropriate source URL above. If the source/date could be stale or the native UI differs, say to check the current screen. Do not send a request, accept terms, grant permissions, or create an account.

HANDOFF RECORD STARTS BELOW THIS LINE