You have a spreadsheet that works. It has your courses, your indicators, and enough evidence to have gotten you through the last CEAB visit. It's messy, it's fragile, and you've memorised which tabs break if you touch them wrong — but it works. So why would you move to a different system?
The answer is not that your spreadsheet is broken. The answer is that it is a flat map of a three-dimensional problem. And as long as you are working in two dimensions, you are compensating for that limitation with your own time, memory, and attention.
Moving from a spreadsheet to a connected evidence map is not a technology migration. It is a shift in how you think about the accreditation data structure. This post walks through what that shift looks like, step by step, and what you can expect during the transition.
The Spreadsheet as a Starting Point
There is nothing wrong with starting with a spreadsheet. In fact, every program that now uses an evidence map system started with one. Spreadsheets are flexible, familiar, and require zero procurement. When a new coordinator sits down and thinks "I need to map these courses to these indicators," a spreadsheet is the natural first tool.
The limitation is not in the tool's intent. It is in the tool's architecture. A spreadsheet presents data in rows and columns. But accreditation data has multiple axes simultaneously:
- Course to indicator: Which courses deliver evidence for which CEAB Graduate Attribute indicators?
- Indicator to evidence: What exemplars, assessments, and documents support each indicator?
- Evidence to quality: Is the evidence current, diverse, and sufficient to meet CEAB expectations?
- Time to change: How has the mapping evolved across accreditation cycles?
A spreadsheet can represent one axis well. To show the others, you need separate tabs, cross-references, and manual reconciliation. The data is there. But it is not connected. You hold the connections in your head.
What "Connected" Means in Practice
An evidence map is not a prettier spreadsheet. It is a different data model. Instead of rows and columns, you have objects and relationships. A course is an object. An indicator is an object. An exemplar is an object. And the connections between them are stored as links, not as text in a cell.
This matters because it changes what the system can do for you. Here is the difference in practice:
In a spreadsheet: You want to know which courses support GA 4.2. You filter the GA mapping tab for "4.2", read the course codes, then switch to the evidence tab to check if those courses have current exemplars. Three manual steps, two tabs, one point of failure if a formula breaks.
In an evidence map: You click on GA 4.2. The system shows you the connected courses, the evidence attached to each course, and a health indicator for the overall coverage. One click. Live data. No filtering, no tab-switching, no reconciliation.
The difference is not cosmetic. It is structural. And it compounds across the hundreds of queries you run during an accreditation cycle.
The Migration: What You Actually Move
When coordinators ask "how long does it take to move from my spreadsheet to a new system?" the honest answer is: the data migration takes an afternoon. The mental migration takes a week or two.
Here is what the data migration involves:
Step 1: Extract your course list
Your spreadsheet has a column or tab listing every course in the program. Course code, course title, department, year/term offered. This becomes your course registry in the new system. It is a one-time import. In MapOutcomes, you can paste from a spreadsheet or upload a CSV — the system parses the columns and creates course objects.
Step 2: Define your indicators
CEAB publishes 12 Graduate Attributes, each with one or more indicators. These are not program-specific — they are the same across all CEAB-accredited programs. A connected system includes the CEAB framework pre-loaded, so this step is usually just confirming the indicator names and numbering match your internal conventions.
Step 3: Map courses to indicators
This is the core of your spreadsheet — the matrix that says "MIE201 supports GA 2.1 and GA 4.3." In a spreadsheet, this is a grid of check marks, letters, or numbers. In an evidence map, it is a set of links between course objects and indicator objects.
You can build these links from your spreadsheet data. If your mapping tab has courses as rows and indicators as columns, you read each row and create the corresponding links. It takes roughly one hour per program for a coordinator who knows the data.
Step 4: Attach existing evidence
Your exemplar files — assignment descriptions, rubrics, student work samples, assessment reports — likely live on a shared drive or in folders on your desktop. In the new system, you link files to the indicators they support. You do not need to re-upload everything on day one. You can start with the evidence you use most frequently and migrate the rest over time.
This is an important advantage of the evidence map approach: you do not need to move everything at once. The system works with partial data. You can have three indicators fully mapped and the rest still in spreadsheet form, and the map still gives you a live view of what is connected and what is not.
Step 5: Validate
Once the core structure is in place, you run the system's gap detection. It will show you which indicators have no courses mapped, which mapped courses have no evidence, and which evidence is older than your program's retention policy. You compare this against your spreadsheet's "best understanding" of the same picture.
At this stage, most coordinators find one or two gaps they didn't know existed. This is the system doing what a spreadsheet cannot: revealing the shape of the data without human interpretation.
The Mental Migration
The data moves in an afternoon. The mindset takes longer to shift. Here are the three mental changes that happen during the transition:
From "building a report" to "reading a dashboard"
In the spreadsheet world, you spend time building views. Filtering tabs, setting up conditional formatting, writing formulas that count evidence per indicator. Every time someone asks "how are we doing on GA 7?", you either have a pre-built view that answers it, or you build one.
In an evidence map, the view is always built. You click an indicator and see the picture. You want a different slice — evidence by department, coverage by year level, recency of assessments — and the system gives you those views without construction. The mental shift is from being a builder of reports to being a reader of data.
From "hoping it's right" to "knowing it's live"
Every coordinator who has worked with spreadsheets knows the feeling of opening the file and wondering: "Is this the latest version? Did someone change a formula? Did the course code update propagate?" You proceed with a degree of uncertainty that you have learned to accept as normal.
An evidence map eliminates that uncertainty. The data is single-source. When a course changes, the change propagates. When evidence is added, it appears immediately. You stop hoping the data is right and start knowing it is current.
From "owning the process" to "enabling the team"
This is the biggest shift, and the one that has the most downstream impact. In the spreadsheet model, the coordinator owns the entire data structure. Faculty contribute by sending files or filling in cells. The coordinator integrates, validates, and maintains.
In an evidence map, faculty can contribute directly within the system. They upload evidence to the indicators they are responsible for. They see the context of their contribution within the larger map. The coordinator's role shifts from data integrator to data curator — reviewing what comes in, flagging gaps, and maintaining the overall picture.
This is not just a personal time-saver. It changes the accreditation culture. When faculty can see their contribution and understand how it fits, participation increases. When the coordinator is not the sole gatekeeper of the data, the process becomes more transparent and more resilient.
What Happens to the Spreadsheet
You do not need to delete it. Most coordinators keep their spreadsheet for one more cycle as a reference. Use it to validate the migration. Then archive it.
The spreadsheet does not become obsolete because it was wrong. It becomes obsolete because it was incomplete. It captured one dimension of a multi-dimensional problem. The evidence map captures the whole picture.
Think of it like this: you wouldn't stop using a compass and keep navigating by paper calculations, even after the calculations got you to the right place last time. You adopt the tool that gives you a live, reliable view of where you are and where you need to go.
Timeline: What a Real Migration Looks Like
Here is a realistic timeline based on programs that have completed this migration:
- Day 1 (afternoon): Course import and indicator setup. The system's CEAB framework loads automatically. You import your course list and verify the names and codes.
- Day 2 (morning): Course-to-indicator mapping. You transfer your spreadsheet's mapping grid into the system's link structure. One to two hours per program.
- Day 2 (afternoon): Evidence attachment for priority indicators. You upload exemplars for the three to five indicators that are most critical for your upcoming self-study. The rest can wait.
- Week 2: Validation and gap review. You run the system's gap detection, compare against your spreadsheet, and resolve any discrepancies.
- Week 3: Faculty onboarding. You invite department heads to the system and show them how to view and contribute to their areas. Most adoption happens in the first week of access.
- Month 2: Full evidence migration. You move the remaining exemplars and assessment documents. The spreadsheet is now a historical reference.
Two months from blank system to full migration, with the system providing value from Day 1. The spreadsheet is archived by the end of Month 2, not because it was discarded, but because it is no longer needed.
Is It Worth It?
If your spreadsheet is working and your last visit was clean, the case for change is not urgent. It is strategic.
The strategic case has three parts. First, every accreditation cycle gets harder if you stay on spreadsheets. Curriculum changes, faculty turnover, and evolving CEAB expectations all add complexity that spreadsheets handle poorly. The second cycle on a connected system is easier than the first. The tenth cycle on a spreadsheet is harder than the first.
Second, the coordinator who migrates to an evidence map becomes more valuable, not less. They spend less time maintaining data and more time interpreting it, engaging faculty, and contributing to curriculum decisions. The tool elevates the role.
Third, the program becomes more resilient. When the coordinator transitions — and every coordinator transitions eventually — the incoming person inherits a live, connected system rather than a set of files that need reconstruction. The institutional knowledge stays.
The spreadsheet got you through the last visit. An evidence map will get you through the next five — and the five after that — with less work, fewer surprises, and a clearer picture at every step.
That is the migration. Not from a bad tool to a good one. From a flat map to a living one.
This post was written for Accreditation Coordinators preparing to modernize their accreditation workflows. For a breakdown of the hidden costs that accumulate in spreadsheet-based processes, see The Hidden Cost of Spreadsheet Accreditation. For a practical guide to building evidence maps that hold up during visits, see How to Map Course-to-Indicator Evidence in 5 Steps.