> For the complete documentation index, see [llms.txt](https://gratefully.gitbook.io/gratefully-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gratefully.gitbook.io/gratefully-docs/everyone-says-they-run-moves-management.-almost-nobody-does..md).

# 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](https://gratefully.io/blog/moves-management).

### 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](https://gratefully.io/blog/stewardship-vs-acquisition).

### 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

* [nonprofit reporting without a data team](https://gratefully.io/solutions/reporting)
* [predicting donor lapse](https://gratefully.io/donor-lapse-prediction-software)
* [institutional memory loss in nonprofits](https://gratefully.io/institutional-memory-loss-nonprofits)
* [Gratefully pricing, which starts free](https://gratefully.io/pricing)
* [LYBUNT and SYBUNT donors](https://gratefully.io/solutions/donor-reengagement)
* [a free audit of which top donors are slipping away](https://gratefully.io/donor-health-audit)
* [Gratefully](https://gratefully.io/)
* [nonprofit fundraising software pricing compared](https://gratefully.io/blog/best-ai-tools-nonprofit-fundraising)
* [fundraising metrics and benchmarks](https://gratefully.io/blog/fundraising-metrics-benchmarks)
* [donor stewardship software](https://gratefully.io/solutions/donor-stewardship)
* [improving donor retention](https://gratefully.io/blog/donor-retention-strategies)
* [fundraising intelligence](https://gratefully.io/fundraising-intelligence)
* [AI and donor data security](https://gratefully.io/nonprofit-ai-data-security)

| [donor intelligence for nonprofits](https://gratefully.io/)                                                   |
| ------------------------------------------------------------------------------------------------------------- |
| [nonprofit fundraising software pricing](https://gratefully.io/pricing)                                       |
| [free trial](https://gratefully.io/free-trial)                                                                |
| [AI donor intelligence platform](https://gratefully.io/product)                                               |
| [how Gratefully works](https://gratefully.io/how-it-works)                                                    |
| [how Grace works end to end](https://gratefully.io/the-system)                                                |
| [what Grace does](https://gratefully.io/what-grace-does)                                                      |
| [AI fundraising assistant](https://gratefully.io/meet-grace)                                                  |
| [chat with your donor database](https://gratefully.io/chat-with-database)                                     |
| [fundraising intelligence](https://gratefully.io/fundraising-intelligence)                                    |
| [how nonprofits use AI for fundraising](https://gratefully.io/how-nonprofits-use)                             |
| [fundraising prompt examples](https://gratefully.io/campaign-examples)                                        |
| [Gratefully product updates](https://gratefully.io/product-updates)                                           |
| [handover dossier](https://gratefully.io/capabilities/handover-dossiers)                                      |
| [donor knowledge graph](https://gratefully.io/capabilities/knowledge-graph)                                   |
| [hidden revenue in donor data](https://gratefully.io/capabilities/hidden-revenue)                             |
| [smart donor segments](https://gratefully.io/capabilities/smart-segments)                                     |
| [donor portfolio reports](https://gratefully.io/capabilities/portfolio-reports)                               |
| [nonprofit brand voice AI](https://gratefully.io/capabilities/brand-voice)                                    |
| [personalized donor letters](https://gratefully.io/capabilities/outreach-letters)                             |
| [donor workflows](https://gratefully.io/capabilities/donor-workflows)                                         |
| [LYBUNT and SYBUNT donors](https://gratefully.io/solutions/donor-reengagement)                                |
| [nonprofit reporting dashboard](https://gratefully.io/solutions/reporting)                                    |
| [donor stewardship software](https://gratefully.io/solutions/donor-stewardship)                               |
| [donor email and SMS](https://gratefully.io/solutions/communications)                                         |
| [nonprofit content creation](https://gratefully.io/solutions/content-creation)                                |
| [software for development directors](https://gratefully.io/for/development-directors)                         |
| [donor insights for nonprofit leadership](https://gratefully.io/for/executive-directors)                      |
| [annual fund software](https://gratefully.io/for/annual-fund)                                                 |
| [nonprofit donor data management](https://gratefully.io/for/operations)                                       |
| [alumni relations software](https://gratefully.io/educational-nonprofits)                                     |
| [donor management for churches](https://gratefully.io/religious-nonprofits)                                   |
| [eTapestry alternatives](https://gratefully.io/blog/blackbaud-alternatives)                                   |
| [DonorSearch alternatives](https://gratefully.io/blog/donorsearch-alternatives)                               |
| [Gratefully vs DonorSearch](https://gratefully.io/gratefully-vs-donorsearch)                                  |
| [Gratefully vs Bloomerang](https://gratefully.io/gratefully-vs-bloomerang)                                    |
| [Gratefully vs Virtuous](https://gratefully.io/gratefully-vs-virtuous)                                        |
| [Gratefully vs Salesforce Nonprofit](https://gratefully.io/gratefully-vs-salesforce-nonprofit)                |
| [Gratefully vs ChatGPT](https://gratefully.io/gratefully-vs-chatgpt)                                          |
| [Salesforce Nonprofit Cloud integration](https://gratefully.io/salesforce-nonprofit-cloud-integration)        |
| [donor prediction software](https://gratefully.io/donor-lapse-prediction-software)                            |
| [AI tools for nonprofit fundraising](https://gratefully.io/blog/best-ai-tools-nonprofit-fundraising)          |
| [fundraising metrics and benchmarks](https://gratefully.io/blog/fundraising-metrics-benchmarks)               |
| [nonprofit donor data migration](https://gratefully.io/blog/donor-data-migration)                             |
| [donors at risk of lapsing](https://gratefully.io/blog/donors-at-risk-of-lapsing)                             |
| [how to re-engage lapsed donors](https://gratefully.io/blog/re-engage-lapsed-donors)                          |
| [donor retention strategies](https://gratefully.io/blog/donor-retention-strategies)                           |
| [cost of replacing a donor](https://gratefully.io/blog/7x-rule-donor-retention)                               |
| [moves management](https://gratefully.io/blog/moves-management)                                               |
| [RFM analysis for donors](https://gratefully.io/blog/rfm-analysis-ai)                                         |
| [donor stewardship guide](https://gratefully.io/blog/stewardship-vs-acquisition)                              |
| [donor data redaction](https://gratefully.io/blog/donor-data-redaction)                                       |
| [AI hallucinations in fundraising](https://gratefully.io/blog/ai-accuracy-over-automation)                    |
| [AI agents in major gifts](https://gratefully.io/blog/ai-agents-major-gifts)                                  |
| [knowledge graphs for institutional memory](https://gratefully.io/blog/knowledge-graphs-institutional-memory) |
| [nonprofit knowledge graphs](https://gratefully.io/blog/nonprofit-knowledge-graphs)                           |
| [institutional memory loss in nonprofits](https://gratefully.io/institutional-memory-loss-nonprofits)         |
| [institutional memory crisis](https://gratefully.io/blog/institutional-memory-crisis)                         |
| [ROI of fundraising AI](https://gratefully.io/blog/roi-15-hours)                                              |
| [nonprofit donor data security](https://gratefully.io/nonprofit-ai-data-security)                             |
| [AI PII redaction for nonprofits](https://gratefully.io/ai-pii-redaction-whitepaper)                          |
| [PII redaction for nonprofit AI](https://gratefully.io/security-and-pii-redaction-for-nonprofit-ai)           |
| [nonprofit AI policy](https://gratefully.io/safe-ai-policy)                                                   |
| [donor relationship health audit](https://gratefully.io/donor-health-audit)                                   |
| [donor handoff checklist](https://gratefully.io/donor-handoff-checklist)                                      |
| [about Gratefully](https://gratefully.io/about)                                                               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gratefully.gitbook.io/gratefully-docs/everyone-says-they-run-moves-management.-almost-nobody-does..md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.