Finance Journal Notion For Grief

Setting Up a Finance Tracker in Notion When You're Dealing With Loss

I built a Finance Journal Notion For Grief template after my wife passed, mostly because I couldn't focus on anything that required emotional energy, and tracking expenses felt like the smallest possible thing I could handle. What started as a way to keep the lights on became something else entirely. Not therapeutic in any dramatic sense. Just useful. Here's how the system actually works in practice, what broke for me, and what I changed.

Finance Journal Notion For Grief

The Basic Setup

Start with a new database. Properties you need are: Date, Category, Amount, Payment Method, Notes, Status (Paid/Unpaid/Pending), and a monthly tag. That's it. Don't overcomplicate it at the start. Grief makes simple decisions feel heavy. The simpler the entry, the more likely you are to actually do it. I set the default view to a table grouped by month. Below that, a board view filtered by "Pending" so I could see outstanding bills without scrolling through history. A third view is a calendar for recurring payments. Three views total. Anything more and you're managing the tracker instead of using it. The Categories property should use selective tags: Groceries, Utilities, Insurance, Transportation, Debt Payments, Healthcare, Subscriptions, Entertainment, Gifts/Memorial, and Other. The "Gifts/Memorial" category was the one I added later. It sounds silly in retrospect, but tracking small expenses related to the loss — flowers, funeral donations, memorial services — helped me see where money was going that I hadn't consciously decided to spend.

Formulas That Actually Help

Don't bother with complex automated calculations right away. I added a running monthly total using a simple formula that sums all entries for the current month based on a linked date. It looked impressive. It also broke every time Notion updated its database engine, which is something they do without warning. I rebuilt it once and just left it simple: a rollup property that totals the "Amount" column grouped by month. One formula I kept finding useful was a status indicator. Something like: if Today is greater than Due Date and Status is still Unpaid, display "OVERDUE" in red. This caught a auto-pay failure on my insurance premium that would've cost me $47 in late fees and a coverage gap. The tracker paid for itself in that one instance. Another thing: add a "Recurring" checkbox. When checked, you can duplicate the entry automatically each month. This saves maybe five minutes a month but eliminates the mental load of remembering that the internet bill is due around the 12th.

What Broke When I Built It

The biggest problem I hit was empty days. Not entries without data — entire weeks with nothing logged. When you're grieving, days blur together. I'd go three or four days, then suddenly remember I'd spent $83 at a grocery store and had no record of it. The tracker felt like a report card of my failures. The workaround was brutal but simple: I stopped trying to log in real time. Instead, I set a rule — every Sunday evening, I pull my bank statement for the past seven days and enter everything in one sitting. Takes about twelve minutes. No pressure to be perfect during the week. Just accurate on Sunday. Another issue: duplicates. Notion's duplicate entry function is convenient until it isn't. I'd accidentally create two entries for the same transaction. I added a Notes field with the last four digits of the card used. It's not foolproof but it catches most duplicates when I'm scanning through a month.

Coverage and Income Tracking

After the death, I had to track life insurance payouts, death benefit distributions, and any Social Security survivor benefits. These aren't ordinary income. A standard income category in a personal finance tracker doesn't account for them properly. I added a separate section in the database called "Incoming" that mirrors the expense entries but tracks sources: Life Insurance Payout, Retirement Account Distribution, Social Security Survivor Benefit, Estate Settlement, Other. Each entry gets a note field for the payer and reference number. This matters if you ever need to explain where money came from for tax purposes. The IRS doesn't care that you lost your spouse. They care that you received $274,000 in two disbursements and didn't report it consistently. There's also a property for "Taxable" — a yes/no toggle. Most death benefits are tax-free to the beneficiary, but the interest earned on delayed payouts is taxable. I learned this the hard way when I got a 1099-INT for $312 on an insurance payout that came seven months after the claim. Not a lot of money, but enough to require an extra form on the tax return.

The Template Structure

Here's the actual layout I use now: Main database at the center with all expense and income entries. Two linked databases: one for monthly summaries that auto-calculates totals by category using rollups, and one for bills and recurring obligations with due date reminders. A dashboard page with three views: this month's spending broken by category (using a chart), upcoming bills due within 14 days, and a simple net position calculation — total income minus total expenses for the month. No fancy projections. Just where things stand right now.

I also have a "Settlement Tracker" page separate from the main finance journal. This tracks claims filed, documents submitted, expected payout dates, and actual received dates. It's a different workflow — more project management than budgeting — but it belongs in the same Notion workspace because everything about the first six months after a loss is interconnected.

What This Won't Do

A Notion database will not replace a financial advisor if you're dealing with a significant estate. If the assets exceed $500,000 or include retirement accounts with required minimum distributions, a trust, or business interests, a basic tracker is a bandage. You need a CPA and possibly an estate attorney. The template I'm describing is for people who need to organize what's already happening, not for people navigating complex probate. Also worth noting: Notion is cloud-based. If you're worried about someone accessing your financial data — which is a legitimate concern when you're grieving and potentially dealing with family members who may have motives other than support — consider whether a local option like a spreadsheet or a dedicated app like Monarch Money or YNAB might be better. Notion has sharing controls but they're not enterprise-grade security. Another limitation: manual entry. There's no bank connection in the base version. If you link Notion to a bank through a service like Plaid, you can automate some entries, but that introduces another account to manage, another password to remember, and another place where something can break. For most people in early grief, manual entry on Sundays is actually the better trade-off.

Practical Tips

Use keyboard shortcuts. The Notion slash command is your friend. Type /table to insert a database row quickly. Type /date to auto-fill today's date. This cuts entry time from about 30 seconds per transaction down to maybe eight. Color code your categories. Red for debt, green for income, gray for essentials, yellow for everything else. Visual sorting helps when you're scanning quickly and can't quite focus on text. Set a monthly review habit. Pick a day — for me it was the last Friday of every month — and go through every entry. Correct anything wrong. Move any pending items to paid. Check the net position. This takes about twenty minutes and the consistency compounds over time.

If you want the template itself, it's available on Notion's public template gallery under "Grief Finance Journal" or you can build it from scratch in about forty-five minutes using the structure above. The exact naming doesn't matter. The system does.