NYC Donor-Advised Fund Pitches: Pre-Contact Checklist

When I sit down with executive directors across the five boroughs, the conversation about donor-advised funds almost always arrives at the same uncomfortable threshold: the moment when a board member or a major donor leans across the table and asks, “Can we just have our DAF cover the gala table?”

It is a small sentence, but it carries enormous weight. The answer determines whether your organization stays within the rules governing donor-advised funds or creates a problem for the donor, the sponsoring organization, and potentially the nonprofit itself. DAFs have become one of the most dynamic parts of New York’s philanthropic ecosystem, yet the practical mechanics of pitching, receiving, and acknowledging DAF-sourced capital remain poorly understood by many community-based organizations that depend on this funding.

The work begins before anyone makes a recommendation. A nonprofit needs to be easy for a sponsor to identify, clear about what a DAF grant can and cannot support, disciplined about donor intent, and precise in its acknowledgments. The organizations that handle these details well do not make the relationship feel bureaucratic. They make it feel trustworthy.

A DAF grant that purchases a gala table is not philanthropy — it is a prohibited benefit transaction waiting to become an expensive problem.

Digital Infrastructure for DAF Discoverability

The first work you do is digital, and it is work that far too many nonprofits underestimate. A donor-advised fund sponsor — whether it is a national entity like Fidelity Charitable or a regional community foundation in the New York metropolitan area — cannot recommend a grant to an organization it cannot reliably identify.

Your donation page should display, with quiet confidence and absolute clarity:

• Your organization’s full legal name.
• Your current mailing address.
• Your Employer Identification Number.
• Clear instructions for donors who want to recommend a grant through a DAF.
• A contact route for questions about wire transfers, checks, or sponsor-specific procedures.

The legal name matters because the name used in a donor’s recommendation may not match the public-facing name used by your organization. A nonprofit may operate under a shortened name, a program name, or a familiar acronym, while the sponsor’s records and IRS filings use the formal corporate name. If those names do not line up, the grant may be delayed while the sponsor confirms that the recommended recipient is the intended organization.

The EIN is equally important. I have watched fundraising teams debate the visual placement of the EIN for entire board meetings, treating it as a compliance afterthought, when in practice it is one of the most useful identifiers in the DAF verification process. It should not be buried in an image, hidden behind a form, or presented in a way that makes copying it difficult. Put it where a donor, sponsor, or finance officer can find it without detective work.

Make the giving path obvious

The modern DAF ecosystem runs on a mixture of sponsor portals, embedded giving tools, and direct instructions. Tools such as DAF Direct and DAFpay can be integrated into donation pages so that a donor can log into a sponsoring organization’s portal and initiate a grant recommendation without having to reconstruct the entire transaction from memory.

If you are not using one of these tools, the alternative should still be simple. Provide a short set of instructions explaining that the donor will need your legal name, EIN, mailing address, and any program or fund designation required by your organization. If the sponsor allows donors to search by name, tell them exactly which version of your name to use.

Every additional click creates friction. A donor who must leave your site, remember your EIN, open a new browser tab, search for your organization, and re-enter everything by hand may still complete the gift. But the experience is needlessly fragile, particularly when the donor is managing several recommendations at once.

Your donation page should also distinguish clearly between:

• A direct personal donation.
• A DAF grant recommendation.
• A grant from a private or family foundation.
• A corporate contribution.
• An event payment or membership transaction.

Those are not interchangeable revenue streams. They may arrive in the same bank account, but they do not carry the same restrictions, acknowledgment requirements, or implications for donor benefits.

A donor who clicks “give” should not have to infer which path is appropriate. If the page combines personal gifts, event registration, membership renewals, and DAF instructions in one undifferentiated form, the organization is inviting precisely the kind of ambiguity that becomes difficult to correct after money has moved.

Explain the mechanics without overexplaining them

A plain-language DAF explainer can prevent confusion later. Many donors, particularly those who established their funds years ago, are surprised to learn that a DAF grant is irrevocable once assets have been contributed to the sponsoring organization. The donor may recommend a recipient, but the sponsor retains legal control and discretion over the assets.

Your site does not need a legal treatise. It does need to make several points understandable:

• A donor recommends a grant; the sponsor approves and distributes it.
• The donor cannot treat the DAF as a personal checking account.
• A DAF grant cannot be returned to the donor.
• A DAF grant cannot be used to obtain a benefit that is more than incidental or tangible for the donor, advisor, or another person connected to them.
• Timing depends on the sponsor’s review and processing procedures.
• A nonprofit may acknowledge the donor’s recommendation, but the tax acknowledgment belongs with the sponsoring organization.

That fourth point deserves careful wording. It is not accurate to tell donors that every membership, sponsorship, or acknowledgment is automatically prohibited. The relevant question is what the payment provides and whether the donor receives more than an incidental benefit or another tangible benefit in connection with the grant.

A membership that is purely honorary or provides no meaningful goods, services, admission, discounts, or other personal value may require a different analysis from a membership that includes benefits. A sponsorship that consists solely of charitable recognition may not present the same issue as a package that includes tickets, hospitality, meals, merchandise, or preferred access. The organization should not make those distinctions casually, but it should make them accurately.

This information is not merely educational content. It is part of your internal risk control. When donors understand the mechanics before they make a recommendation, your development team is less likely to receive a request that cannot legally or operationally be fulfilled.

Navigating IRS Compliance and Prohibited Benefits

The most consequential terrain is the prohibition on benefits that flow back to a donor, advisor, or related person. This is where well-meaning nonprofits most often get into trouble, because the donor’s intention may be generous while the proposed transaction still creates a prohibited benefit.

In practical terms, DAF funds cannot be used to pay for a benefit provided to the donor or another person when that benefit is more than incidental or tangible. That can include a gala ticket or table, an auction item, a raffle entry, or the benefits bundled into a sponsorship package. It can also include a membership when the membership provides more than an incidental or tangible benefit.

The distinction matters. A blanket statement that DAF money can never be connected with any membership or sponsorship is too broad. The analysis turns on the benefit attached to the payment, not simply on the label printed on the invoice.

For event transactions, the safest operational rule remains simple: keep DAF grants entirely separate from payments for admission, hospitality, merchandise, or participation. A donor should not ask a DAF to cover part of a gala table and pay the balance personally. Nor should a nonprofit divide one sponsorship package into a DAF-funded “charitable” portion and a personally funded “benefit” portion if the package itself includes tickets, hospitality, or other tangible privileges.

The clean separation is straightforward:

• The donor may use personal funds to purchase the gala ticket or table.
• The donor may separately make an unrestricted personal contribution.
• The donor may separately recommend a DAF grant to support the organization’s charitable work.
• The DAF grant must not be credited toward the price of an event benefit or made conditional on the donor’s attendance.
• Any membership or sponsorship paid with personal funds should be reviewed according to the benefits it provides; a DAF grant should not be used to purchase benefits that are more than incidental or tangible.

That separation needs to be reflected in your forms, invoices, email language, and staff training. If a donor writes, “I will cover the balance personally and send the rest from my DAF,” the answer should not be improvised. The development officer should explain that DAF funds cannot be used for any part of the event purchase and offer the donor the two separate pathways.

What counts as a benefit in practice

The obvious examples are gala tickets and tables, but event-related benefits can be broader than the admission itself. A DAF grant should not be used to pay for:

• A ticket or table at a fundraising dinner.
• A sponsorship package that includes tickets, hospitality access, meals, merchandise, preferred seating, or other tangible privileges.
• A charity auction purchase.
• A raffle or lottery entry.
• A membership that includes meaningful personal benefits, such as admission, discounts, goods, services, or other benefits beyond an incidental level.
• A paid reception, performance, or program with restricted admission.
• Branded merchandise or other goods of more than incidental value.
• A meal or hospitality package when the payment is connected to admission or participation.

The question is not whether the nonprofit calls the payment a “donation.” The question is whether the payment provides something of value to the donor or another person connected to the donor. A payment labeled “supporter contribution” can still be tied to a benefit if it is required to obtain access, recognition, hospitality, merchandise, or participation.

The same care applies to memberships. Some nonprofits use “membership” as a broad community label for anyone who supports the mission. If the membership confers no meaningful personal benefit, the label alone does not answer the compliance question. Other memberships include free admission, invitations, discounts, publications, classes, merchandise, or priority access. Those benefits must be examined, and a DAF grant should not be used to purchase a membership when the associated benefits are more than incidental or otherwise tangible.

The organization also needs to be careful with sponsorship language. A corporate or personal sponsor may receive recognition, but a DAF grant cannot be used to purchase a sponsorship package if that package includes tickets or other tangible benefits. If a sponsor’s package combines charitable recognition with event access, the DAF cannot fund it as a unit.

If the sponsorship provides only recognition and no more-than-incidental or tangible benefit, the analysis may be different, but the organization should document what the sponsor receives and avoid promising that every sponsorship is DAF-eligible. A sponsor’s name on a website or program is not the same thing as a table, private reception, branded merchandise, or other event privilege. The package needs to be reviewed as it actually operates, not as its most charitable-sounding description.

Staff should know what not to promise

Development staff are often the first people to hear a donor’s proposed workaround. They should be able to identify the red flags immediately:

• “Can the DAF pay the deductible portion?”
• “Can the DAF cover the sponsorship and I will pay for the tickets?”
• “Can you issue the ticket in someone else’s name?”
• “Can the grant be credited to my family’s table?”
• “Can the DAF pay now and I reimburse the organization later?”
• “Can you treat the ticket as a separate thank-you?”
• “Does the DAF count as payment for my membership if the benefits are small?”

Each formulation requires the same basic discipline: identify the benefit, determine whether it is more than incidental or tangible, and do not let a donor’s preferred label decide the outcome. When the transaction involves a ticket, table, hospitality, merchandise, or a membership with substantive benefits, the organization should keep the DAF grant out of that transaction.

The consequences can include a penalty excise tax of 125 percent of the value of the benefit against the donor or advisor. That is not a minor administrative correction, and it is not a fee the nonprofit can quietly absorb on the donor’s behalf. The organization should not reimburse the donor, characterize the benefit as a charitable grant after the fact, or create a paper trail that suggests the transaction was deliberately structured to avoid the rule.

The donor’s personal payment does not “clean” a DAF-funded gala purchase. DAF money must stay entirely outside the ticket, table, and event-benefit transaction.

Managing Donor Intent Without Binding Pledges

A second area of friction is the relationship between a DAF grant and a pledge. Because a DAF grant is a recommendation made by the donor to the sponsoring organization — and the sponsoring organization retains discretion to approve or decline that recommendation — the resulting transfer should not be treated as a legally binding pledge from the donor to your nonprofit.

This distinction can be difficult in a fundraising culture built around commitments. A donor may say, “I will give the organization $25,000 each year for the next three years through my DAF.” The nonprofit may reasonably want to include that anticipated support in a budget conversation. But the donor does not own the DAF assets in the same way they own personal cash, and the sponsor is not automatically bound by the donor’s conversation with your organization.

The donor can recommend a grant. The sponsor decides whether to make it.

That does not mean your organization has to treat every DAF conversation as meaningless. It means the organization needs to document the conversation accurately. A non-binding letter of intent can acknowledge the donor’s expressed wish to recommend a particular grant amount, identify the anticipated timing, and clarify that the grant becomes available only after approval and disbursement by the sponsoring organization.

The language should be deliberate. It can say that the donor intends to recommend grants. It should not say that the donor is legally obligated to deliver DAF assets that remain under the sponsor’s control. It can support internal planning. It should not be presented as an unconditional promise to fund a program, hire staff, repay a loan, or satisfy a contractual obligation.

Keep the budget conversation honest

When a DAF donor expresses multi-year intent, development and finance staff should agree on how that intent will be reflected in internal planning. The organization may assign a confidence level to the anticipated support, discuss the risk with the board, or build a contingency plan if the funds do not arrive. What it should not do is report an unapproved recommendation as if it were cash in hand.

That discipline matters particularly when a nonprofit is:

• Expanding a program.
• Hiring staff.
• Signing a long-term lease.
• Taking on debt.
• Making a restricted commitment to a community partner.
• Promising services over multiple years.

If the organization has publicly committed to an expansion based on donor commitments that turn out to be recommendations the sponsor declines to fund, the difference between a binding pledge and a letter of intent becomes the difference between a difficult conversation and a legal crisis.

The same care applies to restricted purposes. A donor may recommend that a DAF grant support a particular program, neighborhood, or type of service. The organization should confirm that the proposed designation is compatible with its charitable purposes and its own grant acceptance policies. A recommendation that is too narrow, operationally impossible, or inconsistent with the sponsor’s requirements can delay the grant or create problems after receipt.

A donor may also ask the nonprofit to reserve a grant for a specific individual, family, or private obligation. That is a warning sign. A charitable program can have a defined service population, but a DAF grant should not become a disguised personal transfer or a way to satisfy an obligation that belongs to the donor.

Do not promise a grant’s timing

A donor may tell you that a recommendation is being submitted this week. That is useful information, but it is not the same as a payment date. Sponsors may have review procedures, holiday schedules, verification questions, or additional requirements. Your acknowledgment and program planning should reflect that uncertainty.

A practical internal vocabulary helps:

• “The donor intends to recommend” means the donor has expressed an intention.
• “The recommendation has been submitted” means the donor says it has been sent to the sponsor.
• “The grant has been approved” means the sponsor has confirmed approval.
• “The grant has been received” means the funds have arrived and been recorded by the nonprofit.

Those phrases should not be collapsed into one another. Clear language protects the relationship with the donor and prevents the finance team from making decisions based on money that has not yet arrived.

Protocol for Acknowledging DAF-Sourced Grants

Acknowledgment is where well-run nonprofits distinguish themselves, and it is also where organizations can accidentally create confusion about tax deductibility.

When a DAF grant arrives, the official tax receipt — the document that substantiates the donor’s charitable deduction — should be sent to the DAF sponsoring organization, not to the individual donor or advisor. The donor generally received the tax treatment when assets were contributed to the DAF, not when the sponsor later distributed a grant to your nonprofit.

Your organization should therefore avoid sending the individual a second receipt that says the grant is tax-deductible. It should also avoid language suggesting that the donor is entitled to a new charitable deduction for the distribution. The sponsor’s transmittal letter or grant notice may provide its own wording requirements, and those should be followed.

What you send to the individual donor or advisor is a separate stewardship letter. It can acknowledge the recommendation, express genuine gratitude, describe the impact the gift will have, and invite continued engagement with the organization. It should not describe the grant as a new tax-deductible contribution by the individual.

A useful acknowledgment process has several parts:

1. Record the sponsor as the legal remitting entity in the finance system.

2. Record the donor or advisor as the recommending party when that information is provided and when doing so fits your privacy and database practices.

3. Note any program designation communicated by the sponsor.

4. Send the official receipt or acknowledgment to the sponsor.

5. Send a separate gratitude message to the donor without promising a new deduction.

6. Check that neither letter implies the DAF grant purchased a ticket, membership, sponsorship benefit, or other personal advantage.

The final point is easy to miss when a donor has an established relationship with the organization. A thank-you letter that says, “We are delighted to welcome you as a member through your DAF gift,” may unintentionally suggest that the DAF paid for membership benefits. If the donor made a personal membership payment separately, say so in the appropriate record. If the DAF grant supported the organization’s charitable work, describe that charitable purpose instead.

Attribution and anonymity

DAF grants often arrive with different levels of donor information. Some sponsors identify the donor; others identify only the fund or sponsoring organization. Some donors request anonymity. Your database, gift acknowledgment process, and public recognition policy should be prepared for each possibility.

Do not assume that a sponsor’s disclosure of a donor’s name is permission to publish it. Public recognition, annual reports, event programs, and donor walls should follow the organization’s consent practices. A donor’s desire to remain private can be especially important in a DAF context because the donor may have chosen the sponsoring vehicle partly for discretion.

At the same time, anonymity should not prevent the organization from reconciling the grant properly. Finance and development may need different information for different purposes. The organization should establish who can see the donor information, how it is stored, and what appears in public-facing materials.

When a grant arrives with a problem

Sometimes the issue becomes visible only after the check or electronic transfer has arrived. The grant may carry an unclear designation, reference an event, or appear to be connected to a benefit the donor has already received. Do not solve that problem by silently changing the description in your records.

Pause the acknowledgment, separate the funds from any event transaction, and contact the sponsoring organization or the organization’s legal or tax adviser as appropriate. Ask for clarification in writing. If the grant cannot be accepted under the stated terms, the nonprofit should follow its gift acceptance policy rather than improvising a workaround.

A clean record is more valuable than a fast thank-you. The goal is not to make a questionable grant look ordinary. The goal is to determine whether it can be accepted and used consistently with the sponsor’s terms, the nonprofit’s policies, and the rules governing DAF distributions.

Regional Nuances of NYC-Based DAF Sponsors

“New York donor-advised funds” is not a single operating system. A nonprofit working in New York City may receive recommendations from national sponsors, financial institution–associated programs, community foundations, family foundations operating through charitable entities, and regional funds with their own procedures.

The legal principles may be broadly familiar, but the administrative experience can vary. One sponsor may make recipient search easy and provide a detailed grant notice. Another may require additional verification. A regional sponsor may ask more questions about the organization’s local work or the proposed charitable purpose. A donor may also use a fund whose name sounds like a family foundation even though the grant is being processed through a DAF sponsor.

Your pre-contact preparation should therefore include a sponsor-neutral file containing:

• The organization’s exact legal name and EIN.
• Its current address and payment instructions.
• A short description of its charitable purpose.
• The programs that can accept designated support.
• Any restrictions in the gift acceptance policy.
• The staff contact responsible for grant questions.
• Standard language explaining how DAF grants are acknowledged.
• A separate explanation of how event payments, memberships, and sponsorships are handled.

This is especially useful for smaller nonprofits that do not have a dedicated grants manager. The file gives a development associate, executive director, or finance contractor a reliable answer when a donor asks how to recommend a grant.

Community foundations and local context

A community foundation or locally rooted sponsor may know the city’s nonprofit landscape well, but that does not eliminate the need for precision. In fact, local familiarity can create a different kind of risk: people assume that because everyone knows the organization, the transaction can be handled informally.

A donor may have served on your board, attended the same neighborhood event, or supported your work for years. A program officer at a regional sponsor may understand the organization’s mission without a lengthy explanation. None of that changes the need to distinguish a charitable grant from a payment for a personal benefit.

Local context does matter in other ways. A sponsor may want to understand whether a grant supports a citywide program, a borough-based initiative, a particular population, or a specific community partnership. Your pitch should make that purpose legible without turning a DAF recommendation into a contract with the donor.

If the proposed support is restricted, describe what the organization can actually deliver. “Support for youth programming in Queens” may be workable if the organization has a defined program and accounting process. “Support for my neighbor’s family” is not a charitable program description. The more precise the donor’s requested designation, the more important it becomes to confirm that the organization can administer it.

National sponsors and search visibility

For national sponsors, discoverability is often the first practical hurdle. Your public name, legal name, EIN, address, and website should be consistent across the places a sponsor or donor is likely to look. A recent merger, a move, a fiscal sponsorship arrangement, or a change in legal status can create mismatches that are invisible to the public but obvious during sponsor verification.

When your organization changes its name or address, update the donation page and notify relevant funders and sponsors through the appropriate channels. Do not assume that a donor’s saved recipient record will update automatically. A grant sent to an outdated entity or an old address may require manual correction.

The pitch itself should also be designed for the way DAF donors often work. A donor may not be submitting a traditional proposal. They may be comparing several organizations, looking for a clear charitable purpose, and trying to complete a recommendation through an online portal. A concise program description, current financial information, and a visible contact person can do more than a long general appeal.

That does not mean reducing the organization’s work to a few generic lines. It means making the central proposition easy to carry from your website into a sponsor’s recommendation form: what the organization does, whom it serves, what the grant would support, and how the nonprofit will report on the work.

Keep NYC-specific language useful

A donor may search for “NYC community trust DAF guidelines” or ask about a particular sponsor by name. Staff should resist the temptation to promise that one sponsor’s process applies to every fund. Guidelines change, portal instructions differ, and the sponsor — not the nonprofit — controls the grant approval process.

Your public language can say that donors should use the organization’s legal name and EIN, follow the instructions of their sponsoring organization, and contact the nonprofit if the sponsor requests additional information. That is more useful than publishing a long list of sponsor-specific assumptions that may become outdated.

The same restraint applies to turnaround times. A nonprofit can explain when it processes incoming grants internally, but it should not promise that every sponsor will approve or deliver a recommendation on the same schedule. If a donor needs funds to arrive before a program date or fiscal deadline, the organization should discuss the risk openly and suggest that the donor confirm timing with the sponsor.

Build the Pitch Before the Donor Asks

A strong DAF pitch is not a special version of a gala appeal. It is a clear description of charitable work that a donor can recommend to a sponsor without attaching a personal benefit or an informal promise the organization cannot enforce.

Before contacting a donor, be ready to answer five practical questions:

1. What charitable purpose would the grant support?

2. Can the organization accept the grant with the proposed designation?

3. What information will the donor need to identify the organization?

4. How will the nonprofit acknowledge the grant?

5. Is anything being offered to the donor in connection with the recommendation?

The fifth question should be asked even when the proposed benefit seems small. A donor may expect an invitation, a membership renewal, preferred seating, a private briefing, or recognition at an event. Some forms of acknowledgment are ordinary stewardship. Other benefits may be more than incidental or tangible. The organization should know the difference before the pitch is made.

A useful internal matrix can keep the conversation grounded:

This is not a substitute for professional advice, and it should not become a script that staff read mechanically. Its value is that it forces the organization to name the transaction accurately. A DAF grant supporting a program is one thing. A DAF-funded event package with a charitable label is another.

The best donor conversations are often the least complicated. Explain what the grant will accomplish, provide the correct recipient information, state that the sponsor retains approval authority, and make clear that any ticket, membership benefit, sponsorship privilege, or other tangible benefit must be handled separately when applicable.

The Standard to Set Before Contact

A nonprofit does not need a sophisticated fundraising department to handle DAF recommendations well. It does need agreement between development, finance, leadership, and the board about what the organization will accept and how it will describe the process.

That agreement should cover:

• Who answers DAF questions.
• Who verifies incoming grants.
• How designated gifts are recorded.
• How donor attribution and anonymity are handled.
• Which memberships and sponsorship packages include benefits.
• What language staff should use when a donor proposes a split payment.
• When a question must be escalated to counsel or a tax adviser.
• How the organization will communicate a delay, rejection, or correction.

The point is not to turn every donor interaction into a compliance exercise. It is to prevent staff from having to invent policy while a donor is waiting for an answer. Consistency is a form of stewardship. It tells the donor that the organization knows how its funding works and will not put the donor in an avoidable position.

For New York City nonprofits, that preparation is increasingly part of basic fundraising infrastructure. DAF donors may come through a national sponsor, a regional community foundation, a family fund, or an existing relationship with a board member. The source may change, but the organization’s responsibilities do not.

Make the nonprofit easy to find. Describe the charitable purpose plainly. Keep personal benefits outside the grant. Treat donor intent as intent until the sponsor has approved and distributed the funds. Send the tax acknowledgment to the sponsor and the gratitude message to the donor. When memberships and sponsorships are involved, examine the actual benefits rather than relying on broad labels.

That is the pre-contact checklist that matters. Not a polished pitch deck, not a clever workaround, and not an assurance that a DAF can pay for “just one small part” of an event. The credible pitch begins with a transaction the donor, sponsor, and nonprofit can all understand — and ends with charitable support that remains charitable from recommendation to receipt.