Etimad tenders in 2026 follow updated submission standards. This guide covers the technical proposal structure, mandatory sections, document formats, and pre-submission checklist so you avoid rejections.
Document Format Requirements. Technical proposals must be submitted as PDF files unless the RFP specifies otherwise. Use A4 page size, 12-point font (minimum), 1.5 line spacing, and margins of at least 2.5 cm on all sides. Avoid fancy formatting, multiple columns, or embedded graphics that make scanning difficult. Evaluators will print and annotate your proposal—simple, clean formatting works best. File size should not exceed 10 MB. If your file is larger, compress or split into sections.
Mandatory Section 1: Executive Summary. This section—typically 2–3 pages—must summarize your approach, key differentiators, team composition, and schedule overview. It should not repeat the methodology in detail. Instead, it should answer: Why are you the right choice? What do you understand about the scope? How will you manage risk? Keep it concise and use clear headings for navigation.
Mandatory Section 2: Technical Methodology. This is your longest section (typically 15–25 pages for mid-size tenders). Organize it by work stream or phase. For each phase, include: objective, proposed approach, quality controls, resource allocation, deliverables, and timeline. Use diagrams (Gantt charts, swimlane charts, process flows) to clarify complex methodologies. Support every claim with evidence: comparable project examples, tool names, process controls. This section determines your technical score.
Mandatory Section 3: Organizational Structure and Key Personnel. Name your Project Manager and provide their CV (2–3 pages). Include relevant experience (5+ years in similar scope or geography), past projects on Etimad or Saudi public sector, and key accomplishments. Also name other key roles (technical lead, quality manager, safety manager if required). Brief CVs (0.5–1 page each) are acceptable for secondary roles. Ensure all named personnel are real, contactable, and approved to represent your organization.
Mandatory Section 4: Schedule and Milestones. Provide a detailed Gantt chart showing all major activities, deliverables, and milestones. The timeline must be realistic (no overlapping critical paths unless justified), include review cycles and approval buffers, and align with your methodology. Identify critical path and key decision points. If you are proposing accelerated delivery, explain the resource implications and risk controls.
Mandatory Section 5: Quality Assurance and Control. Describe your QA plan: how you will test, verify, and validate deliverables. Include inspection points, approval gates, and escalation procedures. If you are using industry standards (ISO 9001, CMMI, etc.), reference them. Mention any quality tools or automated testing approaches. This section reassures evaluators that you have controls in place.
Mandatory Section 6: Risk Management and Compliance. List the top 5–7 risks (schedule slippage, resource attrition, scope creep, budget overrun, regulatory change, etc.). For each risk, state: risk description, probability assessment, impact assessment, mitigation strategy, and contingency plan. This section proves you have thought critically about execution challenges. Avoid listing trivial risks; focus on material risks that evaluators actually care about.
Mandatory Section 7: Past Performance and References. Include 2–4 relevant case studies of similar work delivered in Saudi Arabia or region. For each case study, note: client name, project scope, your role, duration, budget, measurable outcomes (e.g., "delivered 18 days early, 8% under budget"). Provide contact names and phone numbers for references (with client permission). Evaluators may call your references. Ensure they are prepared to speak to your delivery quality.
Optional but Recommended Section: Innovation and Value-Add. If your methodology includes novel approaches, cost-saving techniques, or value-added services not required by the RFP, document them. Innovation is a scoring lever in many Etimad tenders. Examples: automation approaches, sustainability measures, enhanced reporting, faster timeline. Do not oversell; be specific about added benefit.
Common Mistakes to Avoid. (1) Vague language: "We will ensure quality delivery" is not acceptable. State exactly how. (2) Unsubstantiated claims: Every assertion should have supporting evidence. (3) Inconsistency between sections: If your methodology says you will use methodology A, and your team section says you are hiring expertise in methodology B, that is a red flag. (4) Missing Saudi context: Do not write as if you are delivering in a generic market. Reference Etimad rules, Saudi labor practices, local supply chains. (5) Over-length: Respect page limits. Evaluators will not read beyond what is specified. Prioritize clarity over comprehensiveness.
Pre-Submission Checklist. Before uploading your proposal, verify: (1) All mandatory sections are present and complete. (2) Executive summary is 2–3 pages. (3) Methodology section addresses every deliverable. (4) All named personnel have CVs. (5) Gantt chart is logically consistent. (6) Risk register includes 5+ material risks. (7) At least 2 Saudi case studies are included. (8) File is in PDF format and under 10 MB. (9) No confidential or proprietary information is disclosed (unless specified in RFP). (10) Spell-check is complete and formatting is professional.
Etimad Platform Upload Rules. When uploading to Etimad, note: (1) Do not upload multiple versions. Only the final version will be evaluated. (2) Use the exact file naming convention specified in the RFP. (3) Allow extra time for platform submission—Etimad servers can slow near deadlines. Upload at least 2 hours before the deadline. (4) Verify your file uploaded completely by downloading and spot-checking. (5) You will receive a confirmation email with a submission reference. Keep it. (6) Do not attempt to reupload after the deadline, even if you spot an error. Resubmission after deadline is grounds for disqualification.
Final Thought: Your technical proposal is your contract with the client. It sets expectations for scope, methodology, schedule, and quality. Write clearly, support every claim with evidence, and ensure consistency throughout. Ambiguity in your proposal will be resolved against you—evaluators will assume the narrowest interpretation. The goal is a proposal that passes technical evaluation and earns your bid a place in the financial comparison round.