Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 199

Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 133

Deprecated: Return type of Pimple\Container::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 98

Deprecated: Return type of Pimple\Container::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 79

Deprecated: Return type of Pimple\Container::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 143

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 60

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 66

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 72

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 76

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 56

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 578

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 585

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 606

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 613

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 620

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 395

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 387

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 381

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 399

Deprecated: Return type of WPCF7_Validation::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 78

Deprecated: Return type of WPCF7_Validation::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 72

Deprecated: Return type of WPCF7_Validation::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 59

Deprecated: Return type of WPCF7_Validation::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 82

Deprecated: Automatic conversion of false to array is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/modules.php on line 137

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/script-loader.php on line 348

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 22

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 28

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp.php on line 173

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php:9) in /home/wilbul4/maxoutofpocket.com/wp-includes/feed-rss2.php on line 8
Cash allocation Archives - Max Out of Pocket https://www.maxoutofpocket.com Where personal finance meets healthcare. Tue, 21 Apr 2020 11:16:40 +0000 en-US hourly 1 https://wordpress.org/?v=5.7.11 https://i1.wp.com/www.maxoutofpocket.com/wp-content/uploads/2020/12/cropped-Max_OOP_Profile_Photo.png?fit=32%2C32&ssl=1 Cash allocation Archives - Max Out of Pocket https://www.maxoutofpocket.com 32 32 157852510 How Much Cash Should I Keep In My Pocket? https://www.maxoutofpocket.com/how-much-cash-does-max-keep-on-hand/?utm_source=rss&utm_medium=rss&utm_campaign=how-much-cash-does-max-keep-on-hand https://www.maxoutofpocket.com/how-much-cash-does-max-keep-on-hand/#comments Tue, 21 Apr 2020 12:00:00 +0000 https://www.maxoutofpocket.com/?p=6532 Cash. When things get tough, cash is king. If the total stock market falls 30%, cash holds its value. When bonds fall 10%, cash holds its value. Call it a security blanket. But it can be an expensive blanket. The expense comes in the form of inflation. The problem is, as the cost of goods and services rise, cash stays flat. It loses its purchasing power over time. A $10,000 “stack of high society” tucked...

The post How Much Cash Should I Keep In My Pocket? appeared first on Max Out of Pocket.

]]>

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/wp-db.php on line 3030

Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/jetpack/class.jetpack.php on line 4222
Cash. When things get tough, cash is king. If the total stock market falls 30%, cash holds its value. When bonds fall 10%, cash holds its value. Call it a security blanket. But it can be an expensive blanket.

The expense comes in the form of inflation. The problem is, as the cost of goods and services rise, cash stays flat. It loses its purchasing power over time. A $10,000 “stack of high society” tucked away in my pocket way back in 1998 is still worth $10,000 in 2020. But it also can’t buy as much.

For example, a 16 oz craft beer is quickly approaching $8 at pubs in my community. Luckily, I have blue-collar tastes. So I usually avoid fancy beers or only buy them during happy hour. But even if I go cheap, a Pabst Blue Ribbon will still run me $4.50. It seems like just yesterday I was paying $1.00 for a draft PBR. If you think beer is bad, you should see how much my health insurance deductible has increased over the years. The long and the short of it is there’s a cost that comes with holding cash because things become more expensive.

Milwaukee, Wisconsin in 2016: former home of Pabst Blue Ribbon

So how much cash should we keep in our portfolio?

Deciding How Much Cash to Have in a Portfolio

So, we need to come up with a way to help us decide how much cash to keep in our portfolio. Most simple investment portfolios are made up of stocks (equities), bonds, and cash. Some people like to try and get fancy and throw REITs into the mix, but that really isn’t necessary.  

For people like me, cash can help provide some security when the world around us is collapsing. Everyone has different ideas about how much cash someone should have in their pocket. These are just a handful of them:

  • Cash should only be used to cover an emergency fund.
  • Cash should be no less than a 3-month emergency fund.
  • Cash should be no less than a 6-month emergency fund.
  • Cash should be a percentage of our total net worth.
  • Cash should be a fixed amount based on our expenses.
  • Cash allocation should be a moving target depending on what the market is doing.
  • Cash should be $0.00; 100% equities is definitely the way to go.
  • Cash should be $0.00; keep it in short term bonds to get a higher return on investment.  
  • Cash should be $0.00; use your credit card as an emergency fund. 
  • Cash allocation should be determined by what the Shiller price-to-earnings ratio is doing.
  • Cash is out, Bitcoin is in.

I have used several different methods over the years to try to determine how much cash I should have. Early on, the goal was to save one month of expenses. Then three. Once I hit that, I was able to start taking advantage of investing in the stock market. But as my net worth grew, strategies needed to change. An unexpected bear market forced me formally define that strategy.

Max’s Approach

I have enough self-awareness to know I am not going to freak out in a bear market. In other words, I know better than to sell my total stock market index fund when things get tough. But I also think having a solid cash allocation helps me deal with any anxiety that comes up during tough times.

Now, when I talk about my “cash in my pocket”, I am talking about liquid cash that is not held in a retirement account. In other words, my cash allocation refers to cash I can get access to instantly should I ever need it. I do have some little pockets of cash spread out in various accounts throughout my portfolio, but I can’t easily get to it. For example, my Health Savings Account (HSA) provider requires me to keep $1,000 in cash so I have it in case I need it for medical bills. I don’t consider that liquid cash since I need to jump through a hoop or two to get access to it.

Max is far from an academic. Keeping things simple is important. So, although I am sure some of the ideas above are great ones, I tend to stick with things I can easily understand. So how much cash does Max keep on hand? Here’s a hint. We only have to look as far as Max Out of Pocket crew’s 2019 annual spending.

The Max Out of Pocket crew’s 2019 spending

A Fully Funded Year

In 2020, Max is keeping a full year emergency fund in cash. That comes to $51,436 and it sits in a Vanguard money market fund (VMMXX) in my brokerage account. It is a pretty nice security blanket. I know that if Mrs. Max OOP and myself both got laid off tomorrow, unemployment aside, I would have over a year before I needed to consider selling investments in a down market. That’s a nice little runway for me to figure things out. I would also definitely make lifestyle changes to reduce expenses to make the money last even longer. In 2019, that would have meant cutting the Ecuador trip, not buying a new computer, and rolling back on the skiing. Those cuts, along with a few other changes, would extend the runway even longer.

Exactly $51,436

Getting to this number took some serious work. Unrelentless saving and planning in my 20s led me to have this level of security in my 30s. A nice reserve to help me sleep at night. It is also just a fraction of my overall portfolio, a fraction that will hopefully continue to shrink over the years.

But Max, This Isn’t Cash…?

Keeping $50,000 stuffed under the mattress isn’t ideal. There are things outside of my control like wind, water, fire, and thieves that could accidentally ruin my cash allocation. My pocket isn’t much better. So, I hold it in a Vanguard money market fund in my brokerage account.

Some people may argue the technicalities, but I consider this a “cash-equivalency”. I can save that argument for another day, but I would much rather hold cash-equivalents than real cash. It also gives me some light protection from inflation because I get interest payments paid out every month on the balance. The interest income is taxed, but I’ll take it.

Leaving Money On The Table?

Statistically, I would get a much better return on this $50,000 if it was invested in the stock market. But I am willing to forgo those returns in the name of security and liquidity. It’s a luxury I am willing to pay for.

That said, as levelheaded as I like to think I am, it has been very difficult for me not to invest my last $50,000 into the stock market during this pandemic. I needed to formally define how much cash I wanted to hold on to. So I held tight, requiring myself to leave a year of cash untouched in my brokerage account. Now, it’s officially documented as part of our strategy.

Are there situations where I might want to invest this $50,000 into an extreme bear market or a house? Maybe. Can I ‘borrow’ from my cash allocation to help me fund day to day living during a short term front-loading exercise? Probably. Can I fund small projects around the house from it and pay it back? Perhaps. But I need to document those situations/criteria before they happen. I plan to do just that.

Additionally, maintaining a cash allocation like this is much easier when you have W2 income coming in to pay the regular bills. I am still working fulltime and Mrs. Max OOP is working part-time teaching, a field diversified from my own. I am grateful to have a pretty solid current of cash flow hitting our accounts each month. If we didn’t have this W2 cash flow, I would probably require a bigger security blanket to help me sleep better at night.

Take-Home

Your cash allocation is personal. There are a lot of variables that go into it. I have chosen to keep a cash allocation that will last us at least a year. I have to say, it is a nice feeling. But will my strategy change? Maybe, but not anytime soon.

I generally don’t think it is a good idea to regularly change personal finance strategy. There is an opportunity cost that comes with overthinking this stuff. But that doesn’t mean we can’t make some light changes to plans over the years. At the moment I don’t plan on changing anything. But I can’t say I don’t have other things in development to help me better manage some of the negatives that come along with holding cash.

Am I leaving money on the table by not having this invested? Definitely. But it’s a price I am willing to pay for my security blanket. The nice thing is, now that we have this built up, I can invest every dollar that comes in (after expenses) without really thinking about it.

How big is your security blanket?

*I do keep a limited amount of cash in our Fidelity checking account. Finance people like me might call this an “operating account”. It is where our paychecks land and bills are paid from. It is generally less than a few thousand dollars and it is “swept” every two weeks into investments, retirement accounts, or other “buckets” as needed. I will touch more on this later.

The post How Much Cash Should I Keep In My Pocket? appeared first on Max Out of Pocket.

]]>
https://www.maxoutofpocket.com/how-much-cash-does-max-keep-on-hand/feed/ 3 6532