Move through overview, financials, news, technicals, valuation, and memo workflows inside the signed-in symbol cockpit.
Use this guide when the broader markets workspace has already narrowed to a single symbol and you need to keep the symbol read coherent across tabbed analysis, peer context, events, and memo capture.
Treat the symbol workspace as a connected cockpit rather than isolated tabs. Overview, news, technicals, valuation, and peer context are meant to reinforce each other.
Start with the overview workspace to establish the current read, then branch into the tab that best explains the live question.
Use the symbol memo and artifact conversions to preserve the conclusion before you hand the idea into research, datasets, or backtests.
These are the deeper symbol surfaces behind the top-level markets workflow.
Use the primary symbol cockpit for quote, chart, event, news, peer, and research-cockpit context.
Review filing coverage, revisions, data-table detail, and filing evidence for the symbol.
Inspect the linked symbol feed, selected story detail, and topic clustering without leaving the symbol path.
Check indicator snapshots, return windows, and range context before you over-read a price move.
Review valuation signal, assumptions, multiples, and profitability context together.
Use the research cockpit, peer panels, ownership context, event history, and memo flow to turn the symbol read into a durable artifact.
Use this sequence to keep the symbol read evidence-based instead of tab-hopping without a clear thread.
Use the main cockpit to anchor the current symbol thesis with quote, chart, event, and peer context before drilling deeper.
Open financials, news, technicals, or valuation based on the question you are answering instead of trying to read everything at once.
Bring peer analysis, event history, analyst intelligence, ownership, and the research cockpit back into view before finalizing the read.
Prepare or save the symbol memo once the evidence is coherent so the next downstream workflow inherits the same context.
Use these playbooks when the symbol cockpit needs to turn scattered tab reads into one durable conclusion.
Start in overview to confirm the gap, open news for the primary headline cluster, use financials to verify filing-backed revisions, then return to cockpit and events so the move is anchored to the current catalyst instead of price action alone.
You finish with a symbol read that connects the move, the filing evidence, and the event context before you hand the name into research or memo capture.
Use technicals to inspect range and momentum, then open valuation and peer context to see whether the move is supported by profitability, multiples, or a broader sector repricing.
You decide whether the move is an actual regime shift, a valuation mismatch worth tracking, or a short-term technical event that should not drive the thesis alone.
After the read is coherent, use cockpit support panels, peer review, and memo actions to preserve the evidence chain rather than leaving the conclusion trapped in tab state.
The next downstream workflow inherits a memo-backed symbol thesis with the same context you used to make the call.
Do not jump straight to valuation or technicals without first checking the overview state and current event context.
Use the peer and ownership context to verify whether the symbol read is idiosyncratic or part of a broader cluster move.
Treat filing evidence, linked headlines, and technical snapshots as complementary evidence rather than competing narratives.
Capture the read as a memo before handing it into research, datasets, or backtests so the symbol context stays durable.
Jump into the signed-in markets workspace and navigate from discovery into a live symbol cockpit.
Return to the higher-level markets workflow if you still need the broader discovery and catalyst loop.
Move into the deeper research inputs when the symbol read needs fundamentals, macro, news, or dataset follow-through.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issueJump to the section you need without losing your place.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issue