ETF Overlap Checklist
Last verified: 2026-07-19
An ETF overlap checklist helps investors avoid owning the same exposure three different ways without realizing it. Two funds can have different names, different tickers, and different marketing pages while still holding many of the same companies or factors.
Educational note: this is a process framework, not personalized tax, legal, trading, or investing guidance.
The simple framework
- ▸Check the source record before trusting the label.
- ▸Write the key number that would change the decision.
- ▸Separate process risk from market outcome.
- ▸Define the review date before emotion enters the decision.
- ▸Keep tax, account, broker, and professional-review notes separate when relevant.
Example math
Suppose Fund A is 30% technology and Fund B is 45% technology. If a portfolio puts 50% of its money in each fund, the blended technology exposure is 37.5%: half of 30% plus half of 45%. If the top five holdings also repeat across both funds, the real concentration may be higher than the fund count suggests.
What to write down
- ▸The account, goal, position, fund, or source record used for the review.
- ▸The rule that applies before the decision becomes emotional.
- ▸The key number that would change the plan.
- ▸The source gap that could make the review incomplete.
- ▸The next review date.
Common mistakes
- ▸Trusting the name of the product, setup, or headline without checking the underlying records.
- ▸Reviewing only the outcome instead of the process that produced it.
- ▸Ignoring size, liquidity, concentration, or time horizon.
- ▸Changing the rule during stress without writing why the evidence changed.
- ▸Skipping the follow-up note after new information arrives.
Bucko workflow
Use Bucko to turn the checklist into a repeatable research, journaling, guardrail, scenario-analysis, and review workflow. TradingView indicators can support context checks, Monko user-configured automation should stay tied to trader-defined controls, and Copy Trader review notes should keep caps, audit trails, and user decisions visible.
Practical checklist
- ▸Write the key number first.
- ▸Attach the source record.
- ▸Define the rule in plain English.
- ▸Mark the pause trigger.
- ▸Review the result after the decision window closes.