GovTribe

Visual Analysis and Document Review

Use the Interactive Apps skill in GovTribe AI to create charts, KPI cards, maps, selectable views, and annotatable document previews.

Use Visual Analysis and Document Review when a visual, clickable, or document review output would be clearer than prose. In GovTribe AI, select the Interactive Apps skill for this work.

This workflow can help GovTribe AI turn GovTribe search results, transaction data, award records, saved-search context, or generated artifacts into in-conversation visuals such as KPI cards, trend charts, comparison charts, leaderboards, geo maps, and annotatable document previews.

It is especially useful when the question starts with "visualize," "compare," "rank," "map," "show the trend," or "make this easier to present." The best prompts name the target market, the metric, the date window, the grouping, and the visual output you want. If the question depends on GovTribe data, ask GovTribe AI to use GovTribe search tools or aggregations before it creates the visual.

Use these visual formats when they fit the work:

NeedAsk for
A fast executive snapshotKPI cards with total value, count, average, largest item, or other headline metrics.
Movement over timeA trend chart by year, quarter, month, fiscal year, or rolling period.
Top vendors, vehicles, buyers, locations, NAICS, PSC, or set-asidesA leaderboard chart sorted by the metric that matters.
Side-by-side market slicesA comparison chart for agencies, locations, buyers, categories, or selected records.
Geographic concentrationA geo map with markers sized by spend, award count, locations, offices, or facilities.
Follow-up selectionA selectable map or option list that lets you click items and send the selection back into the conversation.
Document markup and requested editsAn annotatable document preview where you can add highlights, notes, free-text comments, or rectangles and submit them back to GovTribe AI.
Visual analysis can turn GovTribe aggregations into KPI cards inside the conversation.
Visual analysis can also create comparison charts and ranked leaderboards from selected market slices.

Spending visualization

Use this pattern when you want GovTribe AI to turn a market, buyer, vendor, vehicle, category, or saved search into a visual briefing.

Example prompt:

Use Interactive Apps with GovTribe search tools.

Visualize the last 5 years of spending for [agency, buyer, vehicle, vendor, NAICS, PSC, geography, or saved search]. Use GovTribe aggregations and federal transaction data where spending is the question.

Create KPI cards for total obligated dollars, transaction count, average transaction, and largest transaction. Then create a trend chart by year and leaderboards for the top vendors, vehicles, and NAICS or PSC lanes. Include source notes and explain any caveats, such as obligations versus award ceiling.

Location and map analysis

Use this pattern when geography matters and you want the chart to become a follow-up workflow, not just a picture.

Example prompt:

Use Interactive Apps and GovTribe search tools.

Map the top places of performance for [agency, buyer, vendor, vehicle, or saved search] over [timeframe]. Size markers by obligated dollars, turn on clustering if there are many locations, and let me select locations for a follow-up drilldown.

After the map, create a comparison chart and vendor leaderboard for the locations I select. Keep the source, date range, and location assumptions visible.

Selected-market comparison

Use this pattern when you want to compare two or more selected slices from a chart, map, saved search, or prior AI response.

Example prompt:

Use Interactive Apps.

Compare [market slice A] and [market slice B] using GovTribe data. Create a comparison chart for total obligated dollars and transaction count, then create a leaderboard of the top vendors in each slice.

Summarize the market character of each slice, explain what the chart shows, and call out the next capture question our team should answer.

Document annotation and revision

Use this pattern when GovTribe AI creates a document that needs human review, such as a deep-dive PDF, proposal outline, compliance artifact, capture memo, or briefing draft.

The Interactive Apps skill can open a PDF or other viewable document inside the conversation with annotation tools. You can highlight text, add a note, draw a rectangle around an area, or place free-text comments directly on the preview. When you submit the annotations, GovTribe AI receives the marked locations and your comments as review instructions.

Annotations do not edit the file by themselves. They tell GovTribe AI what to change next. For example, if you add a note to a title that says "make this red," GovTribe AI can use the annotation location to find the title, revise the document, render-check the result, and reopen the updated document for another markup pass.

Effective annotation comments are specific enough to act on:

  • Say the exact change you want, such as "replace this sentence with..." or "make this heading red."
  • Mark the smallest area that identifies the target text, table, chart, or section.
  • Use separate annotations for separate edits.
  • Say whether the edit applies only to the marked place or to every similar occurrence.
  • Flag uncertainty directly, such as "check this against Section L" or "confirm this value before final."
Hovering over a document annotation shows the instruction that GovTribe AI can use for the next revision.
After annotations are submitted, GovTribe AI can revise the document and reopen the updated preview for more markup.

Example prompt:

Use Interactive Apps with Proposal Workflows if this is a proposal or capture artifact.

Create an annotatable PDF preview of [document, file, or artifact]. Enable highlight, note, free-text, and rectangle annotations, and label the submit action "Submit requested edits."

After I submit annotations, treat each comment as a requested document edit. Use the annotation location to identify the exact text, table, chart, or section. Apply clear edits such as "make this red," "replace this sentence with...," "shorten this paragraph," or "flag this as unsupported." If an annotation is ambiguous, ask me before changing the file. Render-check the revised document and reopen it for another annotation pass.