Supplier Prequalification File for Oman Projects
Vendor registration, project prequalification and material approval are different gates. Organise evidence in one controlled PQ file.
A supplier prequalification file for an Oman project explains, with evidence, whether a company can manage the proposed product or service scope. A corporate brochure alone is not enough. Registration, authority, experience, technical scope, quality, HSE, financial capacity, local delivery and document validity need to tell one consistent story.
Prequalification is not approval or a guarantee of work. Entity registration, tender access, project PQ, manufacturer approval, material submittal and site acceptance may be separate gates. Continue with the Türkiye-to-Oman construction material sourcing guide.
1. Read the request and evaluation scope
Before copying a generic archive, record the client, consultant, main contractor, package, product/service class, deadline, language, file size, signature and portal rules. Requirements differ by entity. The current official portal and tender document take precedence over a general checklist.
2. Company identity and legal records
- Commercial registration, legal name and business activities
- Address, authorised contacts and official communication
- Tax and chamber evidence as applicable
- Ownership, branch, agent or local-partner structure
- Issuer, document number, date and validity
Presence is not enough: each record must match the applying legal entity and scope. Expired or mismatched evidence belongs in an exception register and must not be silently presented as current.
3. Separate manufacturer, distributor and supplier roles
The applicant may be manufacturer, authorised distributor, trader, installer or a combination. Verify the manufacturer authorisation for the offered brand and family, territory, expiry and signature. Do not interpret one letter as automatic authority for every product or GCC country.
4. Prove similar experience
Reference entries should state project, country, client, year, contract scope, quantity/value band, completion status and verifiable contact or acceptance evidence. A photograph, logo or project name alone is not completion proof. Separate ongoing, completed and bidding-stage opportunities.
5. Build a technical product matrix
Open a row for manufacturer, brand, model, origin, use, standard, TDS, test report, certificate and warranty. Product codes in evidence must match the offer and sample. Review certificate scope by model, plant, standard edition and validity. A general company certificate is not product-performance evidence.
6. Demonstrate quality and traceability
Explain organisation, document control, supplier evaluation, incoming checks, lot/serial traceability, calibration, nonconformance and corrective action. Where ISO evidence is provided, verify issuer, accreditation, scope, address and validity. A certificate alone does not prove project execution; connect it to procedures and sample records.
7. Explain HSE and site-delivery capacity
Depending on scope, include risk assessment, method statements, PPE, competence, incident reporting, emergency planning and subcontractor control. Current SDS, storage and transport controls apply to chemicals. Do not report safety statistics without period, working hours and scope.
8. Organisation and key personnel
Identify project, technical, quality, HSE, logistics and commercial roles. Link CV duties, experience, certificates and availability to the proposed package. Do not assume that a person shown on another project is allocated to this one.
9. Financial and commercial capacity
When requested, provide audited accounts, bank letters, insurance, turnover bands and bonding capacity under controlled confidentiality. State currency and reporting period. Financial evidence does not replace a quotation or payment terms; sensitive records should move only to authorised recipients through a secure channel.
10. Local Oman operating plan
Explain importer, customs support, warehouse, inland transport, site appointment, unloading, service, spares and Arabic/English communication. International-vendor registration and local-contractor classification may not be equivalent. Check current company types and mandatory fields on Esnad and the relevant entity portal at submission.
11. Create a controlled file index
- Cover, package and submission identity
- Contents and document matrix
- Corporate and legal records
- Authority and organisation
- Experience and acceptance evidence
- Technical product/service file
- Quality, HSE and personnel
- Finance and insurance
- Local logistics and support
- Exceptions, gaps and pending confirmations
Give every record a code, revision, date, validity, owner and source. An indexed read-only data room with controlled access is often safer than uncontrolled email attachments.
12. Use AI with controls
AI can classify documents, extract dates and numbers, match company and product codes, compare revisions and flag gaps. It should not decide authenticity, legal validity, technical acceptance or authority. Present every extraction with source page and confidence for human review.
Share the PQ scope and product list through the RHB Group contact page to review the evidence matrix and delivery plan.
Frequently asked questions
Is Esnad registration a project PQ approval?
No. Portal registration does not replace separate technical and commercial evaluation by an entity or project.
Does a company ISO certificate approve the product?
No. Management-system scope and product technical conformity require different evidence.
Is a submitted PQ considered approved?
No. Submission receipt, review comments and formal approval status must be tracked separately.
