Bequest

Podcast 2 — In conversation

Speaker A: A charity I volunteer for is trying to grow its legacy giving programme and they keep talking about 'bequests' and 'legacies' as if they're the same thing. Are they?

Speaker B: In charitable fundraising, they're used as near-synonyms, though technically they're not quite the same. A bequest is the specific legal term for a gift made in a will. A legacy has a broader range — it can mean a bequest, but it can also refer to a heritage or something handed down in a non-legal sense. In fundraising language, 'leaving a legacy' tends to be the warmer, more emotionally resonant phrase used in donor communications — it sounds like giving meaning beyond death, which is what donors want to hear. 'Leaving a bequest' is slightly more transactional and precise, more likely to appear in the will itself and in estate documents. Charities typically use 'legacy giving' and 'leave a legacy' in their marketing, and 'bequest' when they're communicating with solicitors, executors, and in formal acknowledgements of actual gifts received.

Speaker A: What are the different types of bequest a charity might receive?

Speaker B: Three main categories. A pecuniary bequest is a specific sum of money — 'I leave five thousand pounds to the RNLI'. A specific bequest is a particular identified asset — shares, property, jewellery, art — left to a named beneficiary. A residuary bequest is the most significant for charities: it's a share or all of what remains in the estate after all other bequests, debts, and taxes have been settled. Residuary bequests are unpredictable in value but tend to be the largest gifts charities receive, because the donor gives whatever is left rather than ring-fencing a fixed amount. Legacy fundraisers often say that residuary bequests are the ones that fund major capital projects — buildings, endowments, research programmes — because the sums involved can be substantially larger than a donor might ever give in their lifetime.

Speaker A: Is there a risk of confusion between 'bequest' and 'inheritance'? I sometimes see them used as if they mean the same thing.

Speaker B: They're related but distinct. A bequest is something specific given by a testator to a named beneficiary through a will — it's gift-giving through a legal instrument. An inheritance is what a person receives — it's the beneficiary's perspective, and it doesn't necessarily come only from a will. You can inherit property through intestacy — when someone dies without a will — through trust distributions, or through other legal mechanisms that have nothing to do with a bequest. So all bequests result in an inheritance, but not all inheritances come from bequests. In everyday speech the two are often conflated, which is fine in casual conversation, but in legal and financial writing the distinction matters.

Podcast 3 — Prompt engineering

Speaker B: 'Bequest' in development prompts is the noun companion to 'bequeath' — use it when you're building the data side of inheritance and legacy giving. A bequest is a record, an entity, a line item in an estate or a charity's gift pipeline. Let's work through how to use it precisely in different prompt contexts.

Speaker B: First — a bequest registry schema for an estate law firm:

Speaker B: PROMPT: Design a PostgreSQL schema for an estate law firm managing client wills. The bequests table stores bequest_id, will_id, bequest_type — enum: specific, pecuniary, or residuary — asset_description, monetary_value_pence, beneficiary_id, conditions_text, and status — enum: pending, distributed, or contested. A summary view aggregates total distributed bequest value per will, grouped by bequest_type. Add an index on will_id and status. Stack: PostgreSQL.

Speaker A: The three-value bequest_type enum — specific, pecuniary, residuary — maps directly to the legal categories estate lawyers work with daily. Having status as a column per bequest rather than per will reflects the reality that in complex estates, some bequests are distributed quickly while others are contested or delayed for years.

Speaker B: Good. Now a charity legacy pipeline CRM:

Speaker B: PROMPT: Build a legacy giving CRM for a UK charity. The bequest_pledges table stores pledge_id, donor_id, bequest_type — enum: pecuniary, residuary, or specific — estimated_value_pence, solicitor_name, will_date, and pipeline_stage — enum: notified, confirmed, in_probate, or received. A legacy pipeline dashboard shows total estimated bequest value per stage, average time in each stage, and a list of bequests in probate with their expected completion dates. Stack: Node.js, PostgreSQL, and React.

Speaker A: Tracking average time in each pipeline stage — from notified through to received — is the CRM metric that helps legacy fundraising teams set realistic income forecasts and identify bottlenecks. A bequest stuck in probate for longer than the sector average might indicate a contested estate that needs proactive management.

Speaker B: Here's a bequest notification and acknowledgement system:

Speaker B: PROMPT: Build an automated bequest acknowledgement system for a charity. When a new bequest is added to the system with status 'received', the system automatically generates a personalised acknowledgement letter to the executor and, if specified, a family notification. Letters are templated by bequest_type — a specific bequest letter differs from a residuary bequest letter in tone and content. Sent letters are stored with sent_at timestamp, recipient_email, and template_used. Stack: Node.js, SendGrid, and PostgreSQL.

Speaker A: The different letter templates per bequest_type — a specific bequest acknowledgement differs in tone from a residuary one — reflects the genuine communication difference. Acknowledging that someone left a named painting to the charity is a different kind of gratitude from acknowledging a share of an estate, and the correspondence should reflect that.

Speaker B: Now a UI for a solicitor's bequest summary panel:

Speaker B: PROMPT: Design a bequest summary side panel for a solicitor's estate management UI. The panel lists all bequests in an active will with each bequest showing: type badge — specific, pecuniary, or residuary — beneficiary name, asset or value, conditions if any, and a status pill. Bequests can be reordered via drag-and-drop to reflect priority of distribution. Contested bequests are highlighted with an amber border and a dispute note field. Stack: React and Tailwind CSS.

Speaker A: The drag-and-drop priority ordering for bequests — rather than just a static list — reflects the practical need in estate administration to communicate distribution priority to executors. When estate assets are insufficient to cover all bequests, the order of priority determines what gets paid and what doesn't.

Speaker B: One final prompt — a full application:

Speaker B: PROMPT: Build a full-stack digital will and bequest management platform for individuals and their solicitors. Individuals create a will profile, add bequests of different types, and assign beneficiaries from their contacts. Solicitors have an admin view showing all client wills, bequest totals, and probate pipeline status. When a will enters probate, beneficiaries receive automated notifications of their specific bequests. The platform generates a printable will summary with all bequests listed in legal format. Stack: Next.js, Node.js, PostgreSQL, and PDF generation via Puppeteer.

Speaker A: The printable will summary in legal format — generated from the structured bequest data — is what bridges the digital platform and the legal process. A will exists as a legal document, not a web record, and generating a properly formatted printable summary means the platform produces something admissible and usable in the real probate process.

Speaker B: The lesson: 'bequest' in prompts is the entity noun for inheritance. Use it when you need schemas with bequest_type, distribution status, beneficiary records, and estimated values. It's more specific than 'gift' or 'donation' and immediately signals the legal, post-death transfer domain — which generates the right fields and UI components for estate management and legacy fundraising applications.