Make Your Center's Numbers Visual: AI Infographics for Your Next Report
People remember what they see, not the tables they skim. How to use AI to turn your center's numbers into accurate one-page infographics, why code-built graphics beat image generators for data, and three prompts to try.
Every learning center leader knows the end-of-term report problem. You have the numbers. Visits are up, tutor hours are logged, and students who came in for tutoring passed at higher rates than those who didn't. Then it all goes into a dense table, gets sent to the dean, and gets skimmed for thirty seconds.
Ruben Hassid's recent guide on making infographics with AI makes a point that applies directly to us: people hold on to images far better than walls of text. His line is blunt: “People forget what they read. They remember what they saw.” If your data story lives in a spreadsheet, a lot of it isn't landing.
The good news is that you don't need a designer or a graphics budget to fix that anymore. Here's what's useful in his approach for a center, and where to be careful.
Two ways AI makes images, and why it matters for data
Hassid separates two approaches. The first is image generation, where a tool like ChatGPT builds a picture from a description, pixel by pixel. It looks great and works well for visual-heavy pieces. The second is having a tool like Claude write the infographic as code (an HTML page) that then displays as a finished graphic.
For learning centers, that distinction is the whole game. Image generators can garble numbers and labels, because they're drawing them, not placing them. Code-built graphics put your exact numbers on the page. Hassid compares it to the difference between sketching a table by hand and building it in Excel. If you're telling a provost that 4,212 students visited this year, you want 4,212 on the page, not 4,121 in a slightly warped font.
So here's a simple rule: use the code route for anything with numbers you'd be embarrassed to get wrong. Use image generation for things like a flyer background or a tutor recruitment graphic.
He also suggests combining them. Generate a background image first, then have the code-based tool lay the charts and numbers on top. That's a nice option for the cover page of an annual report.
Set your look once
The most useful part of the guide is the first step. Instead of asking for an infographic cold, you upload a few reference images you like and ask the AI to pull out the design system they share: colors, fonts, spacing, and the one element that makes the look recognizable. It then builds a preview page so you can check the style before anything real gets made.
For a center, your reference images are probably already sitting around. Your institution's brand guide, a past annual report you liked, a page from your campus marketing office. Starting there means your graphics look like they came from your college, not from a generic template.
Once you have the design system, Hassid shows how to save it as a reusable skill, so future requests can be short. He admits this makes everything look similar. For a center, that's a feature. Consistent visuals across your semester reports, your website, and your recruitment materials make the center look organized and established.
Where this fits in a learning center
A few places this pays off quickly:
- Semester and annual reports. One visual page summarizing visits, unique students, top courses, and outcomes, placed at the front of the full report.
- Budget requests. A single graphic showing usage growth against staffing levels is easier to argue from than a paragraph.
- Faculty outreach. A short visual for a department chair showing how many of their students used tutoring and how those students did.
- Tutor training. Your session protocol or referral process as a one-page visual that tutors will actually look at.
A few cautions
Don't upload student-level data. Use aggregate counts and percentages you've already pulled from your tracking system. If it would be a problem in an email sent to the wrong person, it doesn't belong in a chat window.
Check every number in the final graphic against your source. The code route is more reliable, but you still own the accuracy. The AI checking its own work is helpful. It isn't a substitute for you reading it.
And keep the full data available. The infographic is the front door, not the whole report. Link or attach the detailed tables for anyone who wants to dig in.
Start small this week
Pick one set of numbers you already report, like last month's visits by subject. Then:
- Grab two or three images that show the look you want, such as your college's brand guide and a report page you like.
- Upload them to an AI tool that can build HTML pages (Claude handles this well) and ask it to describe the design system it sees and show you a preview.
- Paste in your aggregate numbers and ask for a one-page infographic using that system.
- Check every figure, then share it with one person: your supervisor, a faculty partner, or your own staff.
Give it twenty minutes. You'll know pretty quickly whether this belongs in your end-of-term report.
Try It
These prompts work in whatever AI tool your campus provides. Fill in the bracketed parts before you paste.
1. Set your center's visual style. For directors and coordinators who produce reports, flyers, or web content and want one consistent look.
You are a graphic designer who supports college offices that have no design staff. I work at the learning center at [COLLEGE NAME], and I want all of our reports, handouts, and graphics to share one consistent look.
I have attached [NUMBER] reference images: [DESCRIBE THEM, e.g., a page from our college brand guide, a past annual report page I like].
Goal: identify the design system these images share so I can reuse it for every infographic we make.
Give me:
1. A palette of 4 to 6 colors with hex codes and a role for each (background, main text, accent, muted).
2. Fonts for headings, body text, and small labels. If a font is not free to use, name the closest free alternative.
3. The spacing, border, and layout habits you see.
4. The one signature element that makes this look recognizable.
5. A short list of things this design never does.
Use plain language, under 300 words, and flag anything you are guessing at rather than seeing. Then build a one-page HTML preview that shows the colors, the fonts, and one sample stat card so I can check the style before we use it.
2. Turn term numbers into a one-page infographic. For directors and coordinators preparing a semester report, annual report, or budget request. Paste totals and percentages only. Remove student names and ID numbers before pasting.
You are a data designer helping a college learning center report its results to campus administrators.
Goal: turn the summary numbers below into a one-page infographic for [AUDIENCE, e.g., our dean, the provost's office, our advisory board] that makes this point: [MAIN POINT, e.g., tutoring use grew this year and students who used it passed at higher rates].
Context:
- Center: [CENTER NAME] at [COLLEGE NAME]
- Time period: [TERM OR ACADEMIC YEAR]
- Visual style: [PASTE YOUR DESIGN SYSTEM, OR DESCRIBE YOUR COLORS AND FONTS]
- Aggregate numbers only:
[PASTE TOTALS, e.g., total visits, unique students, tutor hours, top 5 courses by visits, pass rate for tutoring users vs. non-users]
Build it as a single HTML page sized to print on one letter-size sheet. Include a headline, 3 to 5 key stats, one simple chart, and a one-sentence takeaway. Use every number exactly as I gave it. Do not round, estimate, or add any number I did not provide. After the page, list every number you used so I can check it against my source.
3. Turn a tutoring or coaching procedure into a one-page job aid. For tutor supervisors and coaching supervisors who want staff to actually follow a protocol during sessions.
You are an instructional designer who makes one-page job aids for peer tutors and academic coaches.
Goal: turn the procedure below into a one-page visual that [TUTORS / ACADEMIC COACHES / FRONT DESK STAFF] at [CENTER NAME] can glance at while they work.
Context:
- Who uses it: [e.g., first-semester peer tutors, mostly sophomores]
- When they use it: [e.g., at the start of every session, when making a referral to counseling or advising]
- Visual style: [PASTE YOUR DESIGN SYSTEM, OR DESCRIBE YOUR COLORS AND FONTS]
- Our procedure as currently written:
[PASTE YOUR SESSION PROTOCOL, REFERRAL STEPS, OR CHECKLIST]
Keep our steps and meaning intact. You may shorten sentences, but do not add or drop steps. If anything is unclear or seems to be missing, list it as a question at the end instead of filling it in yourself.
Build it as a single HTML page that prints on one letter-size sheet. Use numbered steps or a simple flowchart, short phrases, and text large enough to read at arm's length.
Sources
- Ruben Hassid, “Infographics,” How to AI
AI use statement
Sources come from my own reading, plus articles flagged by Elvis, an AI agent I built in Muse (Meta, 2026). I save the ones worth keeping with a note on why they matter for learning centers. Claude (Anthropic, 2026) helps me review those notes, choose topics, and outline and draft the article and its prompts. I revise every draft, check claims against the sources, and decide what gets published.
I tested the prompts in ChatGPT (OpenAI, 2026), Claude (Anthropic, 2026), Copilot (Microsoft, 2026), Gemini (Google, 2026) and Grok (xAI, 2026).
References
- Anthropic. (2026). Claude (Opus 5.5 version) [Large language model]. https://claude.ai
- Google. (2026). Gemini [Large language model]. https://gemini.google.com
- Meta. (2026). Muse (Muse Spark version) [AI assistant]. https://www.meta.ai
- Microsoft. (2026). Copilot [Large language model]. https://copilot.microsoft.com
- OpenAI. (2026). ChatGPT [Large language model]. https://chatgpt.com
- xAI. (2026). Grok [Large language model]. https://grok.com
About the author
[[shortcode.authors.mark-woolwine]]