Our approach
Our focus, our boundaries, our delivery model
This page explains the discipline behind the work rather than the full step-by-step flow. Source trail, operating limits, uncertainty handling and privacy are explicit from the start.
What the work is centered on
A focused decision-support layer for international opportunities that fit your scope. In short:
Read official procurement sources, filter them against defined criteria, and deliver one decision label plus a concise decision note for every tender record that reaches evaluation.
The weekly decision note lives in the customer area, while access and a short summary arrive by email. IhaleAtlas is a controlled, written decision-support model that turns official tender streams into a readable recommendation surface.
Where is the operational flow explained?
If you want to see the profile setup, weekly delivery and written follow-up on one line, the process and delivery page is the operational view of this framework. Here we keep the boundary logic and working discipline explicit.
Operational notes
We do not publish customer-count or revenue metrics here; only the numbers that explain the operating frame.
8
official sources
screened weekly
5
decision labels
ELIGIBLE, LIKELY, UNCLEAR, CRITICAL GAP, NOT ELIGIBLE
1
main surface
customer area
Weekly
cadence
fixed format, fixed day
Written
support model
follow-up stays in the same thread
Explicit
boundary line
included and excluded work is stated upfront
Operational framing; updated if the model changes.
Expectations that are intentionally outside this delivery model
The items below are not part of the standard weekly delivery and are not planned as near-term product additions:
- Raw tender-listing interface or general search-engine behavior
- Enterprise tender ERP or unlimited BI dashboarding
- Push alerts, instant notifications or a mobile app
- Live support line or SLA-backed response promises
- Legal advisory, bid drafting or partner brokerage
- Client-logo wall, case-study wall or public success-rate board
This is an intentional boundary. Outside the standard rhythm we open only a narrower screening focus or a deep evaluation for one specific tender.
How the decision is produced
Each tender record passes through three layers:
1. Rules. Deterministic filters are applied first: country, sector, project scale, contract type and explicit out-of-scope lists.
The output stays traceable; the system preserves which rule filtered a notice and why.
2. AI-assisted analysis. Records that pass the rules are reviewed through a language-model layer: the specification is summarized, risk signals are surfaced and missing data is called out.
AI does not make the final decision; it prepares the material needed for a defensible one.
3. Human review. Every published label is read before release.
A machine-generated draft is never delivered on its own; there is a human review pass before each weekly publication.
The purpose of these three layers is a traceable decision chain. What was read, how it was narrowed and why it was labeled should remain understandable after the fact.
How we mark uncertainty
The most dangerous mistake in tender screening is behaving as if missing information were known. IhaleAtlas keeps that explicit through two separate labels:
Label
UNCLEAR
There is not enough information to decide. The uncertainty is written as-is; it is not guessed away.
Label
CRITICAL GAP
A material field cannot be read from the source. In that state, taking action in the opposite direction is not recommended.
When something is UNCLEAR, the missing points and the path for follow-up are stated explicitly.
Framework table
Privacy, data and communication
Form submissions and written correspondence are used only for reply and scope clarification. There is no marketing reuse or third-party sharing. If you stop, the record is deleted or archived on request.
Email is the primary communication channel. Data is stored in an encrypted database, and deletion or archiving is available when requested.