A sentence with a wrong number can be edited where it sits. A number inside an image cannot. It was exported, downloaded, screenshotted and dropped into other people's slides, and each copy carries the error without the caption that might have qualified it. This workflow is for the person who owns a partner firm's channels: the communications lead at an agency, a consultancy or an advisory practice, on the day someone points out that the referral graphic is wrong.
Why an image is harder to correct than a sentence
Three things make graphics different. The text is baked into pixels, so where a channel lets you edit only the caption, the wrong picture stays up. Copies travel without context, so a screenshot of a carousel panel loses the disclosure that sat in the post text. And the shapes make claims of their own: a bar as tall as the largest example says "this is what people get", an arrow from the company's payment to your firm says "this comes out of their money", and no caption undoes that.
That is why a correction has to sit on the image itself. Section 255.0 of the FTC's Endorsement Guides describes a visual disclosure that, "by its size, contrast, location, the length of time it appears, and other characteristics, should stand out from any accompanying text or other visual elements so that it is easily noticed, read, and understood." The same section adds: "In any communication using an interactive electronic medium, such as social media or the internet, the disclosure should be unavoidable." Whether those Guides reach your graphic is your counsel's call. Read as design advice, they say a correction in small gray type under the post will not do the job.
Which economics a graphic usually gets wrong
Before you fix anything, name each error precisely, because each one has a different source sentence.
| What the graphic shows | Why it is wrong | Rests on |
|---|---|---|
| A pie or bar labeled the greater of $50,000 plus 5% and 15% "of the deal" | The base is Actual Supplier Payout, which excludes SourceX's fees and the Acquisition Partner's full transaction price | Terms section 4 |
| The largest example as the hero figure | A top figure reads as a typical result, and "SourceX does not provide income projections." | Offer block; rewards page |
| An arrow from the company's payment to your firm | SourceX funds the reward on its own; nothing is taken from what the company agreed to receive | Terms section 4 |
| A timeline with payment 60 days after the introduction | The deadline runs from the later of the Acquisition Partner's final written acceptance and completed handoff, and open conditions defer it | Terms section 5 |
| A calculator screenshot showing an amount | "Estimates shown in the portal or calculator are projections, not promises." | Terms section 5 |
| The USD 50,000 floor shown on every deal | The floor applies once per referred company, to its first qualifying transaction; a repeat, renewal or amendment first agreed within the 12-month Repeat Window pays 15% of its payout with no floor | Terms section 4 |
| "Paid rewards are final" | If the company's payout is reduced or reversed, the reward is recalculated on the reduced total | Terms section 6 |
| An amount or range for the company | The company's payout is fixed only in its signed Dataset Deal Confirmation; earlier figures are indicative | SourceX process page |
Then note who saw it. A CEO reads a company amount as an offer. A colleague reads a hero figure as an expectation and repeats it. And because your firm may be paid if a company it introduces completes a qualifying transaction, every reader is entitled to know that interest, on the image as well as in the post.
The asset replacement and notice workflow
Run it the day the error is found.
- Freeze the evidence. Save the original file, every URL where it was published, the date and whatever you know about who saw it.
- Build the replacement first. A corrected file ready to drop in means each takedown is also a replacement, with no gap in which the old image is the only one around.
- Map the copies with the table below, one row per place.
- Replace or stamp each copy according to its row.
- Notify the people listed in the row.
- Retire the old file. Delete it from shared drives, brand kits, design-tool templates, scheduled posts and the website's media library. Give the corrected file a new name with a version and date, so the two are never confused.
- Log what you changed, where, when and who you told.
| Where the image lives | Can you change the file? | Action | Who to tell | Done when |
|---|---|---|---|---|
| Your web page or blog | Yes | Replace the file and add a dated note under it | Anyone you know acted on it | The page and the preview its link shows both carry the new image |
| Your social post | Often only the text | Post the corrected image with a correction note; edit the original text to point to it, or remove the original and say what was removed | People who reshared it | The original points to the correction |
| Deck, PDF or one-pager | Yes, the master copy | Replace, with a version and date on the slide or page | Everyone who received the old version | No shared folder still holds the old one |
| Email attachment already sent | No | A new email with "Correction:" in the subject and the corrected file attached | Every recipient | Each recipient has the correction |
| Colleagues' or other partners' reposts | Not by you | Send them the corrected file and the correction text | The reposters | Each confirms, or you log the refusal |
| Copies you cannot reach | No | Ask where you can; your own channels carry the correction | Nobody further | Logged |
| Printed handouts or banners | Remaining stock only | Withdraw what is left | The event organizer | Stock destroyed |
| Templates, brand kits and scheduled posts | Yes | Delete the old file and anything queued with it | Everyone who uses the kit | The old file can no longer be found |
Method note. The error catalog applies SourceX's program terms (version 2026-11-04), its rewards and process pages and the unsigned sample Channel Partner Agreement; the placement advice draws on section 255.0 of the FTC's Endorsement Guides. All were read on 2026-11-04. The copy map is our design and has not been tested against how far partner graphics actually travel; no such data has been published.
Rebuild the graphic so it cannot fail the same way
- Words or symbols, never a dollar example. If the graphic shows the arithmetic at all: SourceX pays the company P on its first qualifying transaction (at least USD 100,000), the reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and a further qualifying transaction first agreed within 12 months pays 15% of its own payout. If P is later reduced, the reward is recalculated on the reduced total.
- The company line. "SourceX pays any reward separately; the company's own payment is unchanged." That rests on section 4.
- Conditions on the face of the image. One line saying that no lead, meeting or signature on its own pays anything.
- Your interest on the image. A short line that your firm may be paid if a company it introduces licenses data to SourceX, in the same size and contrast as the rest of the text.
- The correction stamp. "Corrected 28 Oct 2026: an earlier version showed the reward as a share of the deal." Name the error in words; never reprint the wrong figure.
- A source line and version. "Program terms, version 2026-11-04", so the next reviewer knows what to recheck.
- SourceX's name and logo. Section 4.5 of the sample agreement grants no trademark license and requires written authorization before you publicly identify SourceX as a partner. If the old graphic used either without that authorization, the new one leaves them off until you have it.
Before the replacement goes out, run its figures through the number-definition-source review, and its wording through the direct licensing glossary.
Telling the people who acted on it
CEOs who replied or applied. Send each a private note: what the graphic got wrong, the accurate terms, your interest, and a plain choice to continue or stop. If the company has already applied, tell your SourceX contact what the company was shown, so its review starts from accurate expectations.
Colleagues who passed it on. Give them the corrected file and the correction text, and ask them to replace rather than delete, so their followers see the fix.
SourceX. The published terms do not require you to report a wrong graphic. If the graphic named SourceX, tell your contact what was wrong and what replaced it.
What a correction must never do is offer something new to make up for the error. Section 7.1 of the sample agreement says a partner may not commit SourceX to payouts, and section 4.6 bars telling a company that an estimate, positive interest, a signature or an upload assures a purchase or a reward. For a text message that has already spread, the wider routine is in correcting an overenthusiastic message.
A carousel card, corrected (Illustrative)
Illustrative: an invented 12-person marketing agency and an invented post.
The agency published a three-panel carousel. Panel one carried the largest worked example from the rewards page, labeled "per introduction". Panel two was a pie chart showing the greater of $50,000 plus 5% and 15% "of every deal". Panel three was a timeline reading "paid 60 days after you refer". The post went to the agency's page, two staff accounts, its monthly newsletter and the sales deck.
| Panel | Error | Corrected panel |
|---|---|---|
| 1 | A top example as a per-introduction figure | "No fixed amount per introduction: the reward follows the company's first qualifying deal, and nothing is paid unless one completes" |
| 2 | Wrong base | "the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, paid separately from it" |
| 3 | Wrong trigger | "Payment deadline set in the program terms, section 5, counted from acceptance and handoff, not from your introduction" |
The agency built the three new panels first, then replaced the newsletter's web copy and the deck, posted the corrected carousel with a stamp on panel one, edited the original post's text to point to it, and sent both staff members the new files. One CEO had replied to the original asking what his company would earn; he got a private note explaining that his company's payment would be fixed only in its own signed agreement, and that the agency might be paid separately. The old files were removed from the agency's design templates the same afternoon.
Where the workflow runs out
- Copies you will never find. Screenshots and reposts by strangers stay wrong. Your own channels carrying a clear correction is the limit of what you control.
- Corrections that spread the error. Reprinting the wrong figure inside a correction gives it a new life. Describe the error; show only the fix.
- Platform limits. Some channels allow neither editing nor deletion of an image. Then the correction post has to stand on its own.
- Terms that change later. A graphic that is right today can go stale with the next terms version; the payout claim checklist explains which money lines to recheck, and the calculator usability study shows why the largest example makes a poor default image.
- Your professional rules. Whether you may accept a reward at all is for your counsel or ethics adviser.
How the reward statuses progress is set out on the rewards page, and further partner questions sit in the guides hub.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
Once every copy is replaced or stamped and the old file is gone, register as a partner if you have not signed yet, send readers to who qualifies instead of putting fit on an image, and build your next graphic straight from the program terms.