Guidance is where management sets expectations) and where surprises begin. A single quarter's range is easy to read in an earnings press release; the pattern across four to eight quarters tells you whether a team sandbags, tightens ranges before macro shocks, or quietly walks down growth without a formal cut.
Transcript language adds texture that tables omit. "Conservative given macro uncertainty" in Q2 may precede a range reduction in Q3 even when the numeric guide is unchanged. Tracking guidance credibly means preserving both the numbers and the words around them.
Vantafin does not expose a dedicated management guidance REST API. What we provide is full earnings transcript access in the app and through MCP: search_transcripts finds outlook language by keyword, and GET /transcripts/* REST routes return transcript content. This post shows how to build a guidance tracking workflow from transcript search and company pages.
What you see in the product
Open any covered name (try Microsoft or Amazon) and navigate to the transcripts section. Each earnings call is available with searchable text so you can jump to passages where management discusses revenue outlook, EPS ranges, margin expectations, or macro caveats. Read the prepared remarks and Q&A. Analysts often press for clarification that the press release omitted.
Build a simple tracking table manually or via agent: for each quarter, record the guided range, the actual result, and a link to the transcript passage where management stated the outlook. Revision markers are yours to annotate when language tightens or widens versus the prior quarter, even when management does not use the word "revise" explicitly.
Add the ticker to watchlists and enable alerts ahead of the next report on the calendar. Email alerts on filings and news help you catch supplemental releases and analyst days that sometimes clarify ranges after the initial call.
Search with MCP and REST
Use search_transcripts via the MCP server with queries like "full year revenue outlook" or "EPS guidance range" scoped to your ticker. The tool returns matching passages you can paste into earnings preview notes or a guidance comparison table. Over REST, GET /transcripts/* endpoints fetch transcript content for programmatic pipelines that archive calls quarter over quarter.
Researchers using Cursor can ask the agent for a table of guidance-related passages across the last four calls before drafting earnings preview notes. The same query that took twenty minutes of copy-paste becomes a thirty-second fetch you still edit heavily) because judgment stays human.
Batch exports work well for peer sets. Pull transcript search results for five semiconductor names in one session and compare how each management team behaved through the same downcycle. Join with get_earnings and get_financials for reported actuals alongside guided ranges.
Research angles
Pair guidance trends with pre-earnings news drift studies to see whether the street prices revisions before the call. If drift and transcript tone align repeatedly, your preview note should acknowledge positioning, not just fundamentals.
For governance shocks, cross-check material 8-K events the same week guidance language shifts. Leadership transitions and outlook resets often arrive together; treating them as unrelated misses the narrative investors trade on.
Available on Pro plans and above. See pricing. Our methodology is summarized on about. Guidance tracking is most powerful when it becomes a habit before every earnings season, not a workflow you discover after a surprise.
Guidance versus consensus
Management guidance is the company's own forward view; consensus is the street's average. Tracking both reveals when executives are above, inline, or below expectations, which is often more predictive than the print alone. Vantafin extracts outlook language from earnings transcripts and aligns it with reported results on company pages; programmatic access flows through REST transcripts routes and MCP tools search_transcripts and get_earnings.
Companies update revenue, EPS, and margin ranges at different cadences, so normalize each revision into a comparable midpoint time series rather than treating every update as interchangeable. A withdrawn range is its own signal, distinct from a narrowed range or a raised midpoint. Each row on the guidance panel links to the transcript passage we parsed so you can audit the extraction in seconds) that transparency matters for desks that feed guidance into models.
Align guidance updates with earnings dates so you know when the next official revision may arrive. Pair with pre-earnings news drift for positioning context. Drift with downward guidance can signal denial rather than strength.
Building screens and peer comparisons
Add a screener column for guidance direction: upward revisions in the last two quarters, downward revisions, or stale guidance older than ninety days. Compare guidance trends across competitors in the same sub-industry; divergence often precedes estimate revisions on the laggard. When one peer raises and another lowers within the same week, the sector narrative is shifting even if index-level data looks quiet.
Use email alerts when filing or news triggers fire on names where you track guidance, and include links to source transcripts in your research notes so recipients never hunt for provenance. Pull structured earnings history via get_earnings in the MCP server and store normalized rows in your warehouse for factor research. Point-in-time guidance series beat "current guidance only" exports when you study revision momentum.
Ask the MCP server: "Which watchlist names lowered revenue guidance this quarter?" for a fast pre-market brief. The query returns cited transcript excerpts rather than a prose guess, which makes it suitable for forwarding to a risk channel after a quick sanity check.
From tracking to investment process
Guidance revisions interact with ETF holdings when sector funds reprice entire baskets on a single company's update. A lowered guide from a large index constituent can pressure peers that did not change their own ranges. Macro overlay from the Treasury yield curve dashboard helps separate rate-driven estimate cuts from operational deterioration.
Document your revision definitions in a team runbook: "midpoint change" versus "range width change" produce different signal sets. Confirm entitlements on pricing before automating wide-universe transcript pulls, and cache stable historical series locally rather than re-fetching full history on every dashboard load.