The risk-tier mapping is the canonical pre-RFQ filter. PharmaDB joins inspections, compliance events, sanctions, and litigation per supplier and computes the worst-signal tier. The view is v_risk_flags. Refresh cadence is weekly.
Bucket every supplier into a risk tier from the joined view of inspections, enforcement, sanctions, and litigation. The pre-RFQ exclusion model.
Risk tier collapses the joined compliance picture into four buckets: block (active enforcement that precludes commercial commitment), watch (recent enforcement that warrants close monitoring), qualifiable-with-conditions (clean today but with a yellow signal), qualifiable-clean (clean across inspection, enforcement, sanctions, and litigation). The tier is the canonical pre-RFQ filter; PharmaDB computes it from the joined view of inspections, compliance events, sanctions, and litigation.
| # | Tier | Definition | Triggers | Example count | Recommendation |
|---|---|---|---|---|---|
| 1 | Block | highest severity | 4 of 60 example | WL + IA active | OAI |
| 2 | Watch | elevated signal | 9 of 60 example | VAI + 1 enforcement event | VAI |
| 3 | Qualifiable with conditions | yellow signal | 17 of 60 example | VAI no enforcement | VAI |
| 4 | Qualifiable clean | green | 30 of 60 example | NAI no enforcement | NAI |
Upload or define your supplier base. PharmaDB resolves each supplier to its plant entities and corporate parent.
Inspection trajectory, active enforcement events, OFAC and equivalent sanctions, and litigation status are joined per supplier. The tier is the worst signal across the inputs.
Citation-anchored tier mapping with the per-tier triggers and the recommended response per supplier. Useful as the pre-RFQ filter and the C-suite exception register.
Block, watch, qualifiable-with-conditions, qualifiable-clean. The vocabulary the procurement, QA, and BD teams can all use to talk about the same supplier.
The tier is the worst signal across the inputs. A clean inspection record cannot upgrade a supplier that carries an active sanction. The rule is conservative by design.
When a supplier moves between tiers, the notification fires. Useful for the QA team's exception review and the BD team's pipeline maintenance.
Tier distribution across the supplier base, the watchlist, and the open market. Useful for the C-suite portfolio review and the supplier-diversification programme.
A real chat thread in PharmaDB. Type a question, the AI agent runs the tools, the answer lands as a saveable note.
pharmagraph_query Approximate tier distribution across a 60-supplier resolved list · the canonical pre-RFQ exclusion shape · live warehouse.
The risk-tier mapping is the canonical pre-RFQ filter. PharmaDB joins inspections, compliance events, sanctions, and litigation per supplier and computes the worst-signal tier. The view is v_risk_flags. Refresh cadence is weekly.
Active warning letter, active import alert, active consent decree, active OFAC sanction, or repeat-OAI status at the supplier plant. Any one of these triggers block-tier classification. The rule is conservative by design: block tier is the hard-exclusion bucket.
Most-recent inspection VAI plus at least one compliance event in the trailing 24 months, or repeat-VAI sequence with no NAI cycle in the last three years. The watch tier is the elevated-signal bucket: not a hard exclusion but worth close monitoring.
The tier is computed from the joined view; the underlying signals are the appeal surface. If a supplier disputes the inspection record or claims an event has been resolved, the catalog row is the citation anchor for the conversation. Tier changes flow automatically when the underlying signals change.
On the cadence of the underlying inputs. Inspections and compliance events refresh weekly; sanctions refresh weekly. A supplier can move tier mid-week if any input signal changes. Tier-change alerts are first-class notifications.
Yes. The tier is computed per plant and rolled up to supplier at the worst-plant rule. A supplier with one block-tier plant and five clean-tier plants is overall watch-tier, with the block-tier plant separately flagged so the buyer can route around it.
The tier is a procurement and quality screening output, not a credit metric. It captures regulatory and quality risk, not financial distress. Finance teams should pair tier with credit-bureau and trade-decline signals for a complete supplier-risk view.
Bring the molecule, the lane, or the supplier you're sourcing this week. The AI agent runs it on PharmaDB in 30 minutes. You keep the brief.