Revenue & Customer Operations School · Learning track
Move campaigns from idea to measured execution with clean handoffs and controls.
Start Lesson 1No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.
Not saved. Worksheets, answers and practice notes currently last only in this tab.
Practice markers are self-reported, never credentials.
A different tab changed this track. Nothing was overwritten. Export your current draft first if needed, then load the saved version before editing and saving again.
01 Learning plan
Public foundation 2026.10.08-learning-paths-1 · published 2026-10-08. Independent subject-matter review is pending; paid delivery and credential issuance remain closed. This track is organized around inspectable work, not attendance alone.
Workload
No validated completion time is published. Read the six modules, then complete the six case assignments and self-review across as many sessions as needed. This release has not yet been timed with learners; no facilitated capstone is included.
Prerequisites
Outputs
Working vocabulary
02 Public foundation curriculum
Each module states what to understand, what to practice, what evidence to retain, and the criteria for moving forward. The case lab turns those standards into six realistic assignments.
Module 1
Objective: Convert a marketing request into a controlled brief with one primary objective, evidence-backed claims, owners, constraints, and a decision rule.
Open Lesson 1: examples, worksheet & feedback →A campaign brief prevents activity from masquerading as strategy. Begin with the business context, target audience, problem, desired behavior, offer, and one primary objective. 'Increase awareness' is incomplete unless the team defines an observable signal, a time period, and the decision the result will inform. Record the current baseline when one exists, but do not manufacture precision from weak data. State exclusions, budget, timing, channels, geographic limits, accessibility needs, and dependencies. If legal, regulatory, medical, financial, environmental, performance, or comparative claims appear, identify the qualified reviewer and substantiation required before creative work advances.
The brief should distinguish facts, hypotheses, and decisions. A customer insight supported by interviews is different from a marketer's assumption; an approved price is different from a proposed promotion. Define the single owner who can approve scope and the specialists who approve claims, privacy, brand, and technical implementation. Add a stop rule for material defects or unexpected harm and a change-control rule for edits after approval. A strong brief is short enough to use but complete enough that copy, design, web, sales, and analytics teams can make compatible decisions without relying on private conversations.
Practice
Turn a vague request to 'promote the new service everywhere' into a two-page brief with objective, audience, evidence, claim-review needs, constraints, owners, and stop rule.
Evidence to keep
Submit the brief and a decision log showing which requested elements were clarified, rejected, deferred, or escalated.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 2
Objective: Build an audience rule that is relevant, privacy-conscious, reproducible, and reviewed for applicable channel and jurisdiction requirements.
Open Lesson 2: examples, worksheet & feedback →An audience should be defined by a legitimate campaign purpose and the minimum data needed to execute it. Document where each field came from, what it means, how current it is, and whether the approved use covers the channel. A purchased list, an old customer file, a webinar registration, and an active subscriber do not create the same rights or expectations. Apply suppression lists before upload or send, including opt-outs, legal restrictions, internal exclusions, and active disputes where appropriate. Never bypass a suppression because a campaign is urgent or because a vendor claims that compliance is handled automatically.
Segmentation improves relevance only when the variables are reliable and ethically appropriate. Avoid sensitive or proxy attributes unless a qualified privacy, legal, and ethics review has approved the use. Small segments can expose individuals even when names are removed. Record inclusion and exclusion logic in plain language, test the resulting counts, and retain an authorized snapshot of the rule rather than uncontrolled audience exports. Laws and platform rules vary by channel and location; operators should use an approved consent framework and escalate uncertainty instead of interpreting law from a checklist. The course teaches operational controls, not legal advice.
Practice
Design audience logic for a fictional webinar follow-up across customers, registrants, prospects, unsubscribed contacts, employees, and contacts with unknown status.
Evidence to keep
Submit the inclusion rule, suppression order, field-source inventory, segment counts, and questions requiring privacy or legal review.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 3
Objective: Coordinate content from request through archive using clear ownership, version control, substantiation, accessibility, and approval evidence.
Open Lesson 3: examples, worksheet & feedback →A content calendar is useful when it records decisions, not merely dates. For each asset, capture the campaign objective, audience, channel, format, owner, dependencies, source materials, claim class, accessibility requirement, review status, publish window, and archive location. Separate a working draft from the approved source of truth. Use stable file names or system identifiers and prevent last-minute edits from bypassing claim, brand, privacy, or accessibility review. Reuse is not automatically approved: a testimonial, price, statistic, endorsement, or disclosure may become inaccurate when the channel, date, audience, or surrounding context changes.
Asset workflow should make the review burden proportional to risk. A routine formatting change may need peer review; a regulated claim or public executive statement may require specialists. Build sufficient time for alt text, captions, translations, link checks, localization, and mobile rendering. Disclosures must be clear and conspicuous in the actual placement, not hidden in a master brief. When an outside creator, influencer, or agency contributes, document ownership, permitted use, material connections, and approval responsibilities. Archive the approved asset and supporting evidence together so the team can later explain what was published and why. Map accessibility work to the applicable WCAG 2.2 success criteria and record the review result; alt text, captions, or mobile rendering alone do not establish accessibility or conformance.
Practice
Create a four-week calendar for a fictional launch containing email, landing page, social post, short video, and partner asset, including approvals and accessibility steps.
Evidence to keep
Submit the calendar, responsibility map, version convention, claim-support index, and one completed approval record.
Ready to move on when
Module provenance
Mapped sections or criteria: WCAG 2.2: 1.1.1 · WCAG 2.2: 1.2.2 · WCAG 2.2: 1.4.10
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 4
Objective: Define decision-oriented measurement and complete a documented preflight that verifies the whole customer and data path before launch.
Open Lesson 4: examples, worksheet & feedback →A tracking plan starts with the campaign decision, then defines events and dimensions needed to support it. For each measure, specify the user action, trigger, property names, allowed values, source system, owner, consent dependency, test method, reporting delay, and known limitation. Use a governed naming convention for campaign parameters and avoid placing personal or sensitive information in URLs, event names, or free-text analytics fields. Reconcile key conversion events against a system of record where possible. Attribution shows how a platform assigns credit under a rule; it does not by itself prove that a campaign caused the result.
Preflight tests the experience end to end. Use approved test records to verify audience and suppression, sender identity, claims, disclosures, subject line, asset versions, links, redirects, page rendering, keyboard access, forms, validation, confirmation messages, lead routing, notifications, analytics events, error handling, and unsubscribe behavior. Capture evidence with date, environment, and reviewer. Define who can pause the campaign and how rollback works. A launch should not proceed because most checks passed if a critical control fails. Privacy, accessibility, payment, or security defects require the responsible specialist, not an informal workaround. For accessibility checks, record the applicable WCAG 2.2 criterion, method, environment, result, evidence, and unresolved limitation. A partial checklist must not be represented as a WCAG conformance determination.
Practice
Build and execute a preflight for a fictional email-to-landing-page campaign with form submission and CRM routing, seeding three known suppression and test records.
Evidence to keep
Submit the tracking specification, test evidence, defect log, release decision, and rollback owner.
Ready to move on when
Module provenance
Mapped sections or criteria: WCAG 2.2: 1.4.10 · WCAG 2.2: 2.1.1 · WCAG 2.2: 2.1.2 · WCAG 2.2: 2.4.3 · WCAG 2.2: 2.4.7 · WCAG 2.2: 3.3.1 · WCAG 2.2: 3.3.2 · WCAG 2.2: 4.1.2 · WCAG 2.2: 4.1.3
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 5
Objective: Create a transparent handoff that routes qualified responses to an accountable owner with context, service levels, and exception handling.
Open Lesson 5: examples, worksheet & feedback →A marketing response becomes operational value only when the right team can act on it. Define what counts as an inquiry, marketing-qualified response, sales-ready response, service request, duplicate, spam, and disqualified record. Each category needs minimum required data, a route, an owner, an acceptance target, and a return reason. Avoid scoring models that hide sensitive proxies or create false certainty from low-quality engagement data. A lead score is a prioritization signal under stated rules, not proof that a person is ready to buy or that a representative should ignore context.
The handoff should preserve the campaign, offer, consent context, customer action, relevant account history, and requested next step without copying unnecessary personal data. Test ownership rules for territories, existing accounts, partners, time zones, and absences. Returned records should enter a correction queue with a standardized reason rather than disappear. Monitor speed and quality together: fast routing with missing context can damage trust, while perfect records delivered days late can waste demand. Marketing and sales should review a sample jointly, resolve definition disagreements, and document changes to lifecycle or scoring rules.
Practice
Design routing rules for ten fictional responses, including an existing customer, duplicate, partner account, out-of-region prospect, support request, and high-engagement but poor-fit record.
Evidence to keep
Submit the definitions, routing table, acceptance service level, returned-record reasons, and results of a seeded handoff test.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 6
Objective: Produce a decision-ready campaign report that separates observations from explanations and preserves the evidence needed for reuse or audit.
Open Lesson 6: examples, worksheet & feedback →A campaign report should answer what happened, compared with what, over which period, and what decision follows. Begin with data-quality notes, objective, baseline, target, audience definition, spend, and primary result. Show the funnel with consistent denominators and segment only where the sample is adequate and ethically appropriate. Distinguish delivered, viewed, engaged, qualified, converted, retained, and revenue outcomes. Report absolute counts with rates so small denominators are visible. Platform-reported attribution and modeled conversions should be labeled, and material discrepancies with finance, commerce, CRM, or service records should be investigated rather than silently reconciled.
Learning requires competing explanations and a planned next test. A high conversion rate could reflect better creative, a narrower audience, seasonality, tracking loss, or an unusually strong offer. State what the evidence supports, what remains uncertain, and which change will be tested next. Archive the approved brief, audience and suppression logic, assets, disclosures, approvals, tracking specification, QA evidence, incident notes, report, and decision log under a retention rule. Remove unnecessary exports and revoke temporary vendor access. The archive should support responsible reuse, not preserve personal data indefinitely.
Practice
Analyze a fictional campaign dataset with a tracking discrepancy and write a one-page executive report plus a technical appendix and next-test recommendation.
Evidence to keep
Submit calculations, limitations, alternative explanations, decision recommendation, and a complete archive index with retention owner.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Free operational lesson
Before launch, verify the audience, permission basis, links, landing page, forms, routing, tracking, mobile rendering, owner, stop rule, and rollback plan.
Define one objective, audience, evidence, constraints, owners, and the decision the campaign should inform.
Document consent, suppression, claims, versions, approvals, privacy, accessibility, and specialist review before activation.
Coordinate assets, pages, forms, routing, and tracking against a shared source of truth.
Run an end-to-end preflight using known test records and block launch on defined critical failures.
Report facts and limitations, choose the next decision, and archive enough evidence to reproduce the result responsibly.
Worked example
A webinar campaign shows a 40 percent conversion rate in the advertising platform, but the CRM records only 18 percent of landing-page visitors as valid registrants.
The campaign beat expectations with a 40 percent conversion rate. We should double the budget next month.
The platform attributes 200 registrations to 500 visits, while the CRM confirms 90 valid registrations. Testing found that the advertising event fired when the form loaded rather than after successful submission. We cannot use the 40 percent figure for a budget decision. Correct the event, reconcile the 90 records, and run a controlled retest before changing spend.
Why it matters: The improved analysis distinguishes systems of record, explains the measurement defect, and defers an irreversible budget decision until the evidence is reliable.
03 Control the work
Common failure modes
Choosing email, search, or social before defining the objective and audience produces activity that cannot be evaluated coherently.
Having an email address or platform audience does not automatically establish that a particular use, channel, or jurisdiction is approved.
Late copy, link, price, or disclosure changes can invalidate earlier reviews; only a versioned, approved asset should launch.
A platform's credit-assignment rule is useful for analysis but does not prove that the campaign alone caused the observed outcome.
Operating measures
Valid, definition-matched responses divided by the eligible reached audience, with both numerator and denominator documented.
Use it to decide: Inspect audience relevance, offer, message, and routing when the rate changes; do not infer quality from clicks alone.
The percentage of activated records that should have been excluded under approved suppression rules.
Use it to decide: Pause affected activation and investigate source, timing, and vendor controls when any material defect appears.
The percentage of routed responses accepted by the receiving team without return for invalid status, missing context, or incorrect ownership.
Use it to decide: Correct definitions, required fields, or routing logic where avoidable returns cluster.
The absolute and percentage difference between a campaign event count and the relevant system-of-record count for the same definition and period.
Use it to decide: Investigate instrumentation, timing, deduplication, and definitions before using a material gap for investment decisions.
04 · Applied case lab · 2026.08.31-practice-3
The packet contains contradiction and incomplete evidence on purpose. Each assignment now identifies the exact fictional inputs available to the learner. Complete a bounded starter, mark missing records instead of inventing them, and compare your reasoning with the debrief—not with a pretend single perfect answer.
This fictional, sanitized training case contains fabricated campaign and audience data. It includes no real personal or confidential records and does not provide legal, privacy, advertising, or revenue guarantees.
CB01 · citable versioned case brief
JuniperWorks is a fictional provider of workflow software for regional construction firms. The marketing team proposes a webinar campaign called Reduce Project Delays, with a $24,000 media and production budget. The draft objective is generate awareness, while finance expects 80 qualified registrations and sales can accept no more than 20 discovery handoffs during the campaign month. The proposed audience file has 9,400 business contacts. Of those, 1,100 are existing customers, 620 have opted out, 730 came from a trade-show scan without documented follow-up permission, 240 are duplicates, and 85 contain free-text personal observations. The landing page promises users can cut delays by 35 percent. That number comes from three selected customers; the full eight-customer review ranges from a 9 percent increase to a 31 percent decrease, with different definitions and periods. Design has approved version 7, but the live page is version 6 with an old price. The analytics plan uses five campaign parameters inconsistently and has no test for duplicate conversion events. The form routes every submission to sales, including students, vendors, existing customers, and incomplete records. Sales wants a one-hour response target, but coverage exists only during Mountain Time business hours. Legal and privacy review are still pending, the speaker release is unsigned, and one image license cannot be located. Leadership asks to launch Friday because ad inventory was reserved. Learners must convert the brief into a decision-ready objective, build an appropriate audience, control content and asset versions, preflight tracking and claims, design a two-way handoff, and report results with limitations. Reserved media and executive enthusiasm do not replace release evidence.
Judgment required: Decide whether a carefully qualified claim is supportable or whether the number should be removed pending better evidence.
Do not assume: Do not average incompatible measures or present selected cases as typical results.
Judgment required: Compare rescheduling cost with legal, privacy, claims, license, and customer-experience risks at an authorized gate.
Do not assume: Do not treat sunk cost, executive urgency, or a calendar date as approval.
Bounded case starter
Resolve the competing expectations into one primary objective and supporting constraints.
Deliverable: A campaign-brief proposal with objective, audience, budget, capacity, metric, and decision use, plus an approval-request field left pending.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F10, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 2 authored artifacts with 9 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: A campaign can have one primary decision goal and several constraints. The brief should resolve what valid means and keep volume within the team's ability to respond.
Bounded case starter
Apply purpose, consent, suppression, minimization, duplication, and segment rules before activation.
Deliverable: An aggregate audience decision table and suppression-test plan with test records and results explicitly pending.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F03, F04, F05, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 2 authored artifacts with 7 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Audience size should fall when controls are applied. A smaller permissioned, relevant file is stronger than a larger one with opt-outs, duplicates, or unnecessary notes.
Bounded case starter
Repair the delay claim and reconcile approved, live, speaker, and image versions.
Deliverable: A claim-ledger starter, asset gap manifest, and version-control release checklist; no version-seven asset package or approval is represented as supplied.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F06, F07, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 3 authored artifacts with 6 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Mixed evidence may support a carefully bounded statement, but not the selected 35-percent claim. Asset control must also prove that the approved version is the one published.
Bounded case starter
Specify event, parameter, form, routing, accessibility, mobile, privacy, and failure tests.
Deliverable: A tracking plan and preflight evidence-capture checklist with execution, signature, and results fields explicitly pending.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F07, F08, F11, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 2 authored artifacts with 10 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: A green page is not enough. Preflight should exercise negative paths and capture proof that tracking, routing, accessibility, privacy, and claims controls work together.
Bounded case starter
Route registrations by audience and qualification while making service targets achievable.
Deliverable: A routing map, handoff record, acceptance workflow, and coverage plan.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F02, F09, F10, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 4 authored artifacts with 15 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: The handoff should respect audience context and service capacity. A transparent business-hour target is better than a one-hour promise that the operating model cannot meet.
Bounded case starter
Create a reporting and archive design that distinguishes measurement rules from causal claims.
Deliverable: A metric dictionary, campaign report template, and archival index.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F04, F05, F06, F07, F08, F09, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 3 authored artifacts with 11 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Attribution rules assign credit under stated assumptions; they do not prove cause. A useful report connects decision metrics to limitations and preserves a reusable archive.
Self-review standard
There is no universal launch recommendation or campaign benchmark. Strong work makes the objective, audience rights, claim evidence, capacity, controls, and reporting limitations visible. The downloadable rubric is formative guidance only—not a grade, verified completion, credential assessment, or professional approval.
Route to: Qualified privacy or advertising counsel and the organization's authorized claims and rights owners
Learner boundary: The marketing operator coordinates proof and approval but does not make legal conclusions.
Route to: Authorized analytics, platform, privacy, and accessibility owners
Learner boundary: The learner documents tests and blocks release but does not override owner acceptance.
05 Editable working tool
Use one row for each launch-critical control. Link to the approved evidence, record an objective pass or fail, and name both the correction owner and the person authorized to approve release. Add as many rows as needed, export a CSV, or print only this tool. Entries are not transmitted. They last only in this tab unless you opt into device-only saving in the learning-work panel. No account or cross-device sync is provided.
| Campaign control | Owner | Evidence or URL | Pass/fail | Correction and approval |
|---|---|---|---|---|
Completed example
Data boundary: Work only in an approved system. Do not place passwords, payment-card data, government identifiers, health information, export-controlled material, client secrets, or unpublished invention details in this public worksheet.
Each two-question check works independently. Review any answered question immediately; you do not need to finish all twelve. Feedback is formative, not a verified grade or credential.
07 Sources and handoffs
Module provenance distinguishes external authorities, legal-status evidence, and Wealth Synergy internal operating standards. Requirements change; verify current source text and obtain qualified advice when a decision carries legal, financial, technical, employment, safety, or regulatory consequences.
ftc-advertising-marketing · Official guidance
FTC primary guidance on truthful, non-deceptive, evidence-based advertising and specialized marketing obligations.
Open reviewed external source ↗ftc-can-spam · Official guidance
FTC explanation of U.S. commercial-email requirements, opt-outs, sender information, and responsibility for vendors.
Open reviewed external source ↗ftc-endorsement-guides · Official guidance
FTC guidance on truthful endorsements, material connections, disclosures, reviews, and advertiser responsibilities.
Open reviewed external source ↗ftc-consumer-reviews-rule · Official guidance
Current FTC business guidance on the Consumer Reviews and Testimonials Rule, including fake reviews, sentiment-conditioned incentives, insider reviews, suppression, and review-site independence. Verify current scope and obtain qualified advice for material compliance decisions.
Open reviewed external source ↗nist-privacy-framework · Official guidance
A voluntary primary framework for identifying and managing privacy risk in products, services, and data processing.
Open reviewed external source ↗w3c-wcag-22 · Standards-body recommendation
Normative W3C Recommendation. Select and test the success criteria applicable to the content and target conformance level; a checklist or partial test is not a conformance claim.
Open reviewed external source ↗ws-marketing-operating-control · Academy internal operating standard
Academy-selected campaign, approval, suppression, asset, preflight, routing, reporting, and archive controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.
Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum ownerExplore marketing implementation support after the campaign brief, evidence, audience rules, and approval responsibilities are defined.
Explore the handoff →Connect campaign operations to the broader launch plan for a validated product; marketing cannot substitute for product, regulatory, or commercial readiness.
Explore the handoff →Future facilitated pathway · not open
The public case lab is available now. A future facilitated cohort may add assignments, feedback, and human capstone review only after a named qualified facilitator and reviewer, schedule, rubric, privacy controls, support, price, refund terms, and delivery terms are published in writing. No enrollment or payment is accepted here.
Course material supports professional development. It does not replace legal, tax, accounting, cybersecurity, engineering, regulatory, employment, translation, or other qualified professional advice where that expertise is required.
The public knowledge check and portal review markers are learning aids only. They do not award a credential. Pilot curriculum and credential assessment are in quality review; Foundry Academy is not currently representing these pages as accredited instruction or an automatic path to a certificate.
Participation does not guarantee employment, client work, funding, licensure, certification by a public authority, or any business outcome.
Use the public foundation
All public materials and case files are available without enrollment. A fit conversation is non-binding and does not reserve a place in a future pilot.
Ask about this track