This SOP outlines the standard procedure for creating new reports, ensuring consistency, compliance, and
controlled usage of report settings.

Applicable to all team members involved in report creation across any domain or module.

1.Responsibilities

• Developer / Report Creator: Responsible for following this SOP.
• Team Lead: Responsible for reviewing and approving new report requests.
• QA / Review Team: Ensures reports are compliant before deployment.

2.Procedure

Step 1: Approval

• No new report should be created without prior written approval from the Team
  Lead.
• The approval should include:
  • Report purpose
  • Target module or department
  • Expected fields and filters

Step 2: Report Development Compliance

After receiving approval:
✅ Use only system-configured (dynamic) values.

• ❌ Do NOT use:
  • Custom or hardcoded values (e.g., fixed company name, phone number, etc.)
  • Custom addresses or contact details
  • Manually inserted logos or external URLs
    ✅ All logos, addresses, and related details must be pulled from the application settings or
    configuration files.

Step 3: Review & Deployment

• Submit the report to QA or assigned reviewer.
• Confirm:
  • All values are dynamic.
  • No manual customization exists
• After clearance, deploy the report following standard deployment procedures

3.Notes

• Violations of this SOP may result in rollback or rejection of the report.
• For exceptions (e.g., one-time use reports), Team Lead must explicitly approve custom values in
  writing