For the complete documentation index, see llms.txt. This page is also available as Markdown.

Everyone says they run moves management. Almost nobody does.

Best fit: major gifts, fundraising consultancy and practitioner audiences

Ask a development shop whether they run moves management and the answer is almost always yes. Ask what stage a specific named prospect is at, when they entered it, and what the next move is, and the answer becomes considerably less confident.

The gap between those two answers is where most major gift programmes actually live.

What the discipline requires

Moves management is a straightforward idea. A prospective major donor progresses through defined stages, each move is deliberate and recorded, and the pipeline can be inspected at any point to see who is where and what happens next.

The stages vary by organisation, but the shape is consistent: identification, qualification, cultivation, solicitation, stewardship. The value is not in the names. It is in three properties the system produces when it works.

You can see the pipeline, which means you can forecast. You can see where prospects stall, which means you can fix a stage rather than blame a person. And when an officer leaves, the pipeline survives them, because the state of each relationship is recorded rather than remembered.

None of those three properties survives partial implementation.

The three ways it degrades

The stages become labels. Every prospect is marked "cultivation" because that is the safe answer and nobody audits it. The field is populated, the report runs, and the data is meaningless. This is the most common failure and the hardest to detect, because it looks identical to a functioning system from the outside.

The moves are not recorded. The stage is updated when something big happens, but the individual contacts between stage changes are not logged. So you know someone is in cultivation and have no idea whether that means four substantive meetings or a card at Christmas.

Nobody reviews the pipeline. The data may be reasonable, but nothing happens with it. A pipeline that is never inspected does not produce forecasting or stall detection, which were two of the three reasons to keep it.

We went through the stages, what the published benchmarks actually say about progression, and who realistically needs to be in the system, in a full guide to moves management stages and benchmarks.

Why it degrades, which is not laziness

The honest explanation is that recording a move costs more than it appears to.

After a good donor meeting, an officer has perhaps twenty minutes before the next thing. Writing a proper contact report means recalling the conversation, deciding what is significant, choosing the right stage, and typing it into a system that was not designed for prose. The alternative is to remember it, which works fine until it does not.

So the recording slips, and it slips first for the relationships that are going well, because there is no immediate consequence. Six months later the pipeline shows the problem cases in detail and the healthy relationships as blanks.

Any fix that adds administrative burden fails for this reason. The officers most worth capturing from are the busiest, and asking them to type more will not work.

A smaller version that survives

If a full implementation has failed before, try a narrower one.

Limit the pipeline. Twenty-five active prospects per officer, not the whole file. A pipeline containing everyone contains nothing.

Define one thing precisely: what qualifies. The single most valuable definition in moves management is what has to be true for someone to enter the pipeline at all. Get that right and the later stages sort themselves out. Get it wrong and you have a list of names.

Review monthly, briefly, out loud. Fifteen minutes, each officer, what moved and what did not. Verbal review catches the label problem immediately, because "cultivation" cannot survive the question "what happened last?"

Record the why, not the what. A contact report saying "lunch, 14 March" is nearly worthless. One saying "wants their gift to fund the scholarship specifically, not general operating" is the thing you would pay to have when they leave.

The connection to stewardship

Moves management gets treated as an acquisition discipline for new major prospects. The larger return is usually on existing donors, because the people most likely to make a major gift are already giving you smaller ones.

That is where the pipeline meets the retention programme, and where most organisations have the biggest unworked opportunity. We set out how the two disciplines connect in a donor stewardship guide.

The test

Pick a prospect at random from your pipeline. Ask the responsible officer what stage they are at, when they entered it, and what the next move is.

If you get three confident answers, you are running moves management. If you get one, you have a field in a database.

More on the subjects above

free trial

how Gratefully works

what Grace does

AI fundraising assistant

fundraising intelligence

handover dossier

donor knowledge graph

smart donor segments

donor portfolio reports

nonprofit brand voice AI

donor workflows

LYBUNT and SYBUNT donors

donor email and SMS

annual fund software

alumni relations software

eTapestry alternatives

DonorSearch alternatives

Gratefully vs DonorSearch

Gratefully vs Bloomerang

Gratefully vs Virtuous

Gratefully vs ChatGPT

donor prediction software

donors at risk of lapsing

cost of replacing a donor

moves management

RFM analysis for donors

donor stewardship guide

donor data redaction

AI agents in major gifts

ROI of fundraising AI

nonprofit AI policy

donor handoff checklist

about Gratefully

Last updated

Was this helpful?