Analisa Supplier Screening Pass (Delivery)
A checklist with 7 steps: Confirm the client's screening question and jurisdiction list before touching Analisa.
By InnovaAI ResearchPublished
What are the steps?
Analisa Supplier Screening Pass (Delivery)
- 01
Confirm the client's screening question and jurisdiction list before touching Analisa
Get the compliance or recompete question in writing plus the counties, municipalities, or agencies in scope. Analisa's value depends on US public data coverage, so flag any jurisdiction outside that footprint before the agency quotes the work.
- 02
Open the Analisa workspace and set the watchlist to the client's places and suppliers
Free tier caps the watchlist at 100 items; Pro raises it to 1,000. For a multi-county screening, size the watchlist against the plan the agency is billing on so delivery does not stall mid-pass.
- 03
Run the supplier screening pass against the client's question
Pro includes supplier screening at 500 rows a month. Track rows consumed per client so a second engagement in the same month does not exhaust the allowance before the report ships.
- 04
Configure saved alerts for the triggers the client cares about
Free allows 3 saved alerts on a weekly email; Pro allows 50 on a daily email. Set alerts on spending, demographic, and recompete signals, then confirm delivery lands in the inbox or channel the client actually reads.
- 05
Pull the maps, rankings, and profiles into the client deliverable
CSV exports run to 10,000 rows on the free tier. Capture the exact Analisa outputs used (map views, ranking positions, profile metrics) so the agency can defend each figure if the client's compliance team audits the report.
- 06
Generate the report set and check the monthly cap
Pro includes 10 reports a month. Assign report slots to clients at kickoff, not on demand, so a retainer with several screening requests does not run dry in week two.
- 07
Hand the configured workspace to the client or account lead
Document the watchlist structure, alert cadence, and remaining monthly allowances (rows, reports, alerts) so whoever runs the next pass does not rebuild the setup or misjudge plan capacity.
More on Analisa
- StrategyWhy Analisa Is a Data Layer, Not an Anchor, for Agency Retainers
- ConceptAnalisa Data Layer Test
- Evaluation RuleAnalisa Rule: Adopt Only When a Client Mandate Names a US County or Municipality
- Decision FrameworkAnalisa: Buy vs Skip (US Public Data Retainers)
- Failure PatternThe Analisa Watchlist Sprawl Trap: Why Agencies Fail With Analisa on Multi-County Retainers
- Implementation BlueprintAnalisa County Screening Retainer Build (6-8 days)