How to Build an Earnings Watchlist for the Next Two Weeks

A two-week earnings watchlist keeps event work manageable. It is long enough to prepare, short enough to stay current, and focused enough to avoid turning every report into a crisis. The goal is not to track every public company. The goal is to know which reports matter to your research questions.

A useful watchlist includes the company, confirmed or expected date, source, priority, pre-report question, post-report status, and follow-up document. Without those fields, the watchlist becomes a date table. With them, it becomes an operating queue.

Start with a reason for inclusion

Do not add a ticker only because it reports soon. Add it because the report can answer a question. The question might involve guidance, margins, demand, cash flow, liquidity, sector read-through, customer concentration, or a watchlist thesis. If there is no question, the ticker can stay off the priority list.

This filter keeps the workflow from becoming too broad. A smaller list with clear questions is more useful than a large list that nobody can review properly.

• Write one pre-report question for every watchlist name.
• Classify the reason as holding, watchlist, sector read-through, or research candidate.
• Remove names with no actionable question.
• Keep low-priority reports in a separate scan list.

Confirm dates and sources

Expected dates are useful, but confirmed dates are better. Use company investor relations pages, press releases, and reliable earnings-calendar sources, then record where the date came from. If the date is estimated, label it clearly and check it again before the event window.

The source field matters because earnings dates can move. A stale date can cause missed preparation or false urgency. The closer the event gets, the more important confirmation becomes.

• Record expected, confirmed, reported, or unknown status.
• Save the source link or source name for the date.
• Refresh uncertain dates inside the two-week window.
• Track report time when available, such as before open or after close.

Create priority tiers

Not every report deserves the same attention. A core holding or high-conviction research candidate may need preparation before the release. A sector read-through may need only a quick note after the call. A low-priority name may need only a date reminder.

Priority tiers make the workload honest. They also prevent a common failure where every event is marked important and the list becomes impossible to use.

• Tier 1: prepare before release and review release, call, and filing.
• Tier 2: review release and guidance, then decide whether to go deeper.
• Tier 3: scan for major surprises or sector read-through only.
• Archive names once the event no longer supports the question.

Use post-report states

After the company reports, the watchlist should not stay in the same state. Move each name to reported, needs call review, needs 10-Q, thesis changed, no action, or remove. The state tells you what work remains.

This is where many earnings workflows fail. They prepare for the event but do not close the loop. A post-report state makes follow-up visible and keeps old catalysts from cluttering the list.

• Move reported names into a post-event state.
• Add separate follow-up for transcript or 10-Q review.
• Record whether guidance, quality, or risk changed.
• Remove names when the original question has been answered.

An earnings watchlist is useful only when every date has a question attached.

Build the next-two-weeks list around source-confirmed dates, priority tiers, and post-report states. That keeps earnings season from becoming an endless stream of alerts.