What needs checking · 12A Partner programme operations

D19. Decide the scheme, re-paper every active partner, and issue figures in a schedule to the agreement, never in the playbook.
Agreement versions. Which version each partner signed, including any DocuSign of the older one (Karl, John Cooper); file the signed agreement held outside the Knowledge Base.
Reset decision. Founders to confirm the pack lead's 19 October position (existing partners continue; certificate follows) over the stricter reset.
Registration contact and inbox. The playbook says "your Maktura contact, named in your agreement". Confirm one exists and who monitors it, then name the role in the playbook.
Referral links and the reply aim. Whether tracked links exist or attribution is by registration and code only (Dom); whether the team can meet the one-working-day aim during soft launch.
Live checkout and the pricing page. The playbook says only that the team will set a contact up and take payment at sign-up, and that the team confirms the current price. The £69 test payment was unconfirmed as at 8 October. Once John confirms checkout end to end (D29) and Alex confirms the pricing page is fixed, restore a pricing page pointer in the next playbook version.
ASA influencer guidance (2023). Karl to review against the playbook's labelling rules.
Certificate and kit. The certificate parameters depend on D26; the interim route needs an owner; the asset kit must be built.
Pending decisions that change the playbook. D11 (if Holly's name changes, the playbook's product, script, certificate, copy, never-say and questions sections change); D10 (not used in partner copy); D13 and D1 (partner wording GREEN-only until both clear); D23 (the "It isn't ChatGPT" answer keeps partners out of the question).
Testimonials. Partners are given none until customers consent in writing.