Symfony Profiler

1209600

"Sulu\Content\UserInterface\Controller\Website\ContentController::indexAction"

false

"sulu_route.route_id_33"

[
  "object" => Sulu\Article\Domain\Model\ArticleDimensionContent {#927
    #id: ? int
    #article: Sulu\Article\Domain\Model\Article {#740 …}
    #title: "RAK retail fit-out: programme recovered after late PM appointment"
    -customizeWebspaceSettings: false
    #additionalWebspaces: Doctrine\Common\Collections\ArrayCollection {#926 …}
    #created: DateTimeImmutable @1776357027 {#989
      date: 2026-04-16 16:30:27.0 UTC (+00:00)
    }
    #changed: DateTimeImmutable @1777203325 {#988
      date: 2026-04-26 11:35:25.0 UTC (+00:00)
    }
    #creator: Proxies\__CG__\Sulu\Bundle\SecurityBundle\Entity\User {#875 …}
    #changer: Proxies\__CG__\Sulu\Bundle\SecurityBundle\Entity\User {#875 …}
    -author: Proxies\__CG__\Sulu\Bundle\ContactBundle\Entity\Contact {#747 …}
    -authored: DateTimeImmutable @1776297600 {#991
      date: 2026-04-16 00:00:00.0 UTC (+00:00)
    }
    -lastModified: null
    #locale: "en"
    #ghostLocale: "en"
    #availableLocales: [
      "en"
    ]
    #stage: "live"
    -isMerged: true
    -version: 0
    -excerptData: [
      "more" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
      "image" => [
        "id" => null
        "displayOption" => null
      ]
      "title" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
      "description" => "<p>A RAK retail fit-out with inherited programme slippage at appointment — recovered to revised baseline within the client's original handover window.</p>"
    ]
    -excerptCategories: Doctrine\Common\Collections\ArrayCollection {#1163 …}
    -excerptTags: Doctrine\Common\Collections\ArrayCollection {#1010 …}
    -excerptAudienceTargetGroups: Doctrine\Common\Collections\ArrayCollection {#2021 …}
    -excerptSegment: null
    -route: null
    -seoData: [
      "title" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
      "keywords" => "fit-out project management UAE, construction project management RAK, retail fit-out Ras Al Khaimah"
      "description" => "A Ras Al Khaimah retail fit-out inherited significant programme slippage at TrustForce appointment. Delivered on revised baseline within the client's original handover window."
      "canonicalUrl" => "https://trustforce.ae/projects/retail-fitout-rak"
    ]
    -seoNoIndex: false
    -seoNoFollow: false
    -seoHideInSitemap: false
    #shadowLocale: null
    #shadowLocales: null
    -templateKey: "webpage"
    -templateData: [
      "url" => [
        0 => "/"
        1 => "p"
        2 => "r"
        3 => "o"
        4 => "j"
        5 => "e"
        6 => "c"
        7 => "t"
        8 => "s"
        9 => "/"
        10 => "r"
        11 => "e"
        12 => "t"
        13 => "a"
        14 => "i"
        15 => "l"
        16 => "-"
        17 => "f"
        18 => "i"
        19 => "t"
        20 => "o"
        21 => "u"
        22 => "t"
        23 => "-"
        24 => "r"
        25 => "a"
        26 => "k"
        "page" => [
          "path" => "/projects"
          "uuid" => "019d6d7f-22e5-79c6-be2b-d3241517adcd"
        ]
        "suffix" => "/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
      ]
      "title" => "RAK retail fit-out: programme recovered after late PM appointment"
      "blocks" => [
        [
          "id" => "import-block-0"
          "_id" => "6743b18f"
          "type" => "snapshot"
          "content" => """
            | Sector | Built environment — retail fit-out |\n
            | Location | Ras Al Khaimah |\n
            | Scale | Mid-size retail fit-out; multiple contractor packages across MEP, joinery, and finishes |\n
            | Outcome | Programme recovered to revised baseline; practical completion achieved within the client's original handover window |
            """
        ]
        [
          "id" => "import-block-1"
          "_id" => "21ee6d83"
          "type" => "paragraph-group"
          "intro" => ""
          "heading" => "The Situation at Appointment"
          "paragraphs" => [
            [
              "id" => "import-block-1-p-0"
              "text" => "<p>A RAK-based retail operator appointed TrustForce several weeks into a fit-out programme that had already accumulated significant slippage against its original baseline. The main contractor had been on site since the preceding quarter, but no independent PM had been in place. Reporting passed directly from the contractor to the client's operations team — a team with no construction background and limited visibility of what the delay meant for the handover date.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-1-p-1"
              "text" => "<p>The handover window was fixed. A trading lease with a landlord-imposed opening date carried financial exposure if missed. Two contractor packages — MEP and joinery — were running on sequences that had not been recoordinated since the programme first slipped, meaning further delay was probable without active intervention.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
          ]
          "preheading" => ""
          "subheading" => ""
        ]
        [
          "id" => "import-block-2"
          "_id" => "2fc209de"
          "type" => "paragraph-group"
          "intro" => ""
          "heading" => "What TrustForce Did"
          "paragraphs" => [
            [
              "id" => "import-block-2-p-0"
              "text" => "<p>The first two weeks were diagnostic. TrustForce rebuilt the programme from current site status rather than the contractor's reported position, which had not been updated to reflect actual MEP first-fix progress. That rebuild identified a recoverable window — not the full extent of slippage, but enough to meet the client's handover date if the joinery package was resequenced and authority submissions were accelerated immediately.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-2-p-1"
              "text" => "<p>TrustForce took direct ownership of the authority submissions workstream, which had not been initiated at the point of appointment. RAK civil defence and RAK Municipality building completion inspections both carry submission lead times that the original programme had underallocated. Submissions were prepared and lodged within the first weeks of engagement, ahead of the revised critical path. The contractor received a revised works sequence covering MEP second-fix and joinery installation, with weekly progress gates replacing the monthly reporting the client had previously received.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-2-p-2"
              "text" => "<p>Holding that sequence took consistent effort. The contractor pushed back on the joinery lead times throughout the recovery phase. TrustForce maintained the revised programme as the reference document for all site instructions, change requests, and payment applications. That approach removed the contractor's ability to reframe delay as a scope variation — a pattern common on fit-out programmes where the PM is absent or arrives late.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-2-p-3"
              "text" => "<p>RAK civil defence inspection scheduling carries informal lead times that are not published and shift with submission volume. Prior experience of RAK submission cycles allowed a realistic inspection date to be built into the recovery programme at the outset rather than assumed from standard guidance. The client's original programme had significantly underallocated time for civil defence sign-off — accounting for first-submission review and the standard resubmission cycle, the actual lead time ran considerably longer than the original plan had assumed. Had that gap not been identified and front-loaded into the recovery sequence, the programme would have failed regardless of site progress.</p>"
              "type" => "paragraph"
              "subheading" => "From the field"
            ]
          ]
          "preheading" => ""
          "subheading" => ""
        ]
        [
          "id" => "import-block-3"
          "_id" => "fc1641bf"
          "type" => "paragraph-group"
          "intro" => ""
          "heading" => "The Outcome"
          "paragraphs" => [
            [
              "id" => "import-block-3-p-0"
              "text" => "<p>Practical completion was certified on the revised baseline date, within the client's original landlord-imposed handover window.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-3-p-1"
              "text" => "<p>The contractor's final account was agreed without dispute. No variation claims related to the resequencing were accepted — the revised programme, issued in writing at the close of the diagnostic phase, established the baseline against which all subsequent claims were assessed.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-3-p-2"
              "text" => "<ul><li>Authority submissions to RAK civil defence and RAK Municipality lodged within weeks of TrustForce appointment, against a workstream that had not been initiated at handover</li><li>MEP second-fix and joinery resequenced promptly following the programme rebuild; weekly progress gates replaced monthly contractor reporting</li><li>Civil defence inspection obtained on the first submission cycle — no resubmission required</li><li>The majority of the inherited slippage was recovered within the engagement period</li><li>Contractor final account agreed without variation dispute; payment aligned to revised programme milestones throughout</li></ul>"
              "type" => "paragraph"
              "subheading" => ""
            ]
          ]
          "preheading" => ""
          "subheading" => ""
        ]
        [
          "id" => "import-block-4"
          "_id" => "b8b9a3c8"
          "type" => "paragraph-group"
          "intro" => ""
          "heading" => "What This Means for Similar Projects"
          "paragraphs" => [
            [
              "id" => "import-block-4-p-0"
              "text" => "<p>Late PM appointment on a fit-out does not automatically mean a missed handover — but it narrows the recovery window sharply. The recoverable time on this engagement was identified in the diagnostic phase, and only because the programme was rebuilt independently of the contractor's reported position. Clients appointing a PM after site start should expect a diagnostic phase before any recovery commitment is made. Any PM who commits to a recovery timeline before completing that diagnosis has not done the work.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
            [
              "id" => "import-block-4-p-1"
              "text" => "<p><em>For background on why early PM appointment reduces programme risk on UAE fit-out and construction projects, see <a href="/insights/when-to-appoint-pm-uae">When should a developer appoint a PM? The case for day one engagement</a>. For an overview of TrustForce's approach to construction PM, visit our <a href="/services/built-environment">Built Environment services page</a>.</em></p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
          ]
          "preheading" => ""
          "subheading" => ""
        ]
        [
          "id" => "import-block-5"
          "_id" => "6713d60a"
          "type" => "paragraph-group"
          "intro" => ""
          "heading" => "Talk to TrustForce"
          "paragraphs" => [
            [
              "id" => "import-block-5-p-0"
              "text" => "<p>If you are managing a fit-out in Ras Al Khaimah or the Northern Emirates and your programme has slipped — or you want independent oversight in place before it does — talk to TrustForce.</p>"
              "type" => "paragraph"
              "subheading" => ""
            ]
          ]
          "preheading" => ""
          "subheading" => ""
        ]
        [
          "id" => "import-block-6"
          "_id" => "4b08ed65"
          "faqs" => [
            [
              "id" => "import-block-6-faq-0"
              "type" => "faq"
              "answer" => "There is no fixed point, but the recoverable window shrinks as the programme advances. The most common scenario TrustForce encounters is appointment at 20–40% programme completion, where enough work remains to resequence but authority submission lead times have already been underplanned. Appointment after practical completion inspections have been missed is significantly harder to recover. The earlier the appointment, the more options remain open."
              "question" => "At what point is it too late to appoint an independent PM on a fit-out?"
            ]
            [
              "id" => "import-block-6-faq-1"
              "type" => "faq"
              "answer" => "Contractors typically resist resequencing because it removes flexibility in their resource allocation. In this engagement, TrustForce held the revised programme as the contractual baseline for all instructions and payment applications from the point of issue. That approach — making the revised programme the document of record rather than a recommendation — limits the scope for the contractor to treat the resequencing as advisory. Resistance was present in the first two weeks and diminished once payment applications were assessed against the revised milestones."
              "question" => "How did the contractor respond to the revised programme?"
            ]
            [
              "id" => "import-block-6-faq-2"
              "type" => "faq"
              "answer" => "Yes, with conditions. TrustForce will assess the programme position before confirming a recovery commitment. Where the remaining float has been fully consumed and the handover date is no longer achievable, TrustForce will state that position to the client at the diagnostic stage rather than commit to an outcome that the site conditions do not support. Clients should expect an honest assessment of what is recoverable before a scope of engagement is agreed."
              "question" => "Does TrustForce take on engagements where the programme is already significantly delayed?"
            ]
          ]
          "type" => "faq-group"
          "intro" => ""
          "heading" => "FAQ"
          "preheading" => ""
          "subheading" => ""
        ]
      ]
      "heading" => "RAK retail fit-out: programme recovered after late PM appointment"
      "ai_prompt" => null
      "subheading" => "Significant inherited slippage at appointment. Delivered on revised baseline within the client's original handover window."
      "headerImage" => [
        "id" => 8
        "displayOption" => null
      ]
    ]
    #mainWebspace: "website"
    #workflowPlace: null
    #workflowPublished: DateTimeImmutable @1776357027 {#990
      date: 2026-04-16 16:30:27.0 UTC (+00:00)
    }
  }
  "view" => "shared/pages/webpage"
  "_cacheLifetime" => 1209600
  "_seo" => [
    "canonicalUrl" => "https://dev.trustforce.ae/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
  ]
  "_sulu_route" => Sulu\Route\Domain\Model\Route {#722
    -id: 33
    -webspace: null
    -locale: "en"
    -slug: "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
    -parentRoute: Proxies\__CG__\Sulu\Route\Domain\Model\Route {#689 …}
    -resourceKey: "articles"
    -resourceId: "019d9645-74f9-7238-8ad4-737d01759b3b"
    -resourceIdCallable: null
  }
]

[
  "canonicalUrl" => "https://dev.trustforce.ae/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
]

Sulu\Component\Webspace\Analyzer\Attributes\RequestAttributes {#484
  -attributes: [
    "requestUri" => "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
    "portalInformation" => Sulu\Component\Webspace\PortalInformation {#468
      -type: 1
      -webspace: Sulu\Component\Webspace\Webspace {#414
        -name: "TrustForce"
        -key: "website"
        -localizations: [
          Sulu\Component\Localization\Localization {#415
            -language: "en"
            -country: ""
            -shadow: ""
            -children: []
            -parent: null
            -default: true
          }
          Sulu\Component\Localization\Localization {#416
            -language: "ar"
            -country: ""
            -shadow: ""
            -children: []
            -parent: null
            -default: false
          }
        ]
        -defaultLocalization: Sulu\Component\Localization\Localization {#415}
        -segments: []
        -defaultSegment: null
        -theme: null
        -portals: [
          Sulu\Component\Webspace\Portal {#422
            -name: "TrustForce"
            -key: "website"
            -localizations: [
              Sulu\Component\Localization\Localization {#423 …}
              Sulu\Component\Localization\Localization {#424
                -language: "ar"
                -country: ""
                -shadow: null
                -children: []
                -parent: null
                -default: ""
              }
            ]
            -defaultLocalization: Sulu\Component\Localization\Localization {#423 …}
            -environments: [
              "prod" => Sulu\Component\Webspace\Environment {#425
                -type: "prod"
                -urls: [
                  Sulu\Component\Webspace\Url {#426 …}
                  Sulu\Component\Webspace\Url {#427
                    -language: "ar"
                    -country: ""
                    -segment: ""
                    -redirect: ""
                    -main: false
                    -url: "{host}/ar"
                    -environment: "prod"
                  }
                ]
                -customUrls: []
                -mainUrl: Sulu\Component\Webspace\Url {#426 …}
              }
              "stage" => Sulu\Component\Webspace\Environment {#428
                -type: "stage"
                -urls: [
                  Sulu\Component\Webspace\Url {#429 …}
                  Sulu\Component\Webspace\Url {#430
                    -language: "ar"
                    -country: ""
                    -segment: ""
                    -redirect: ""
                    -main: false
                    -url: "{host}/ar"
                    -environment: "stage"
                  }
                ]
                -customUrls: []
                -mainUrl: Sulu\Component\Webspace\Url {#429 …}
              }
              "test" => Sulu\Component\Webspace\Environment {#431
                -type: "test"
                -urls: [
                  Sulu\Component\Webspace\Url {#432 …}
                  Sulu\Component\Webspace\Url {#433
                    -language: "ar"
                    -country: ""
                    -segment: ""
                    -redirect: ""
                    -main: false
                    -url: "{host}/ar"
                    -environment: "test"
                  }
                ]
                -customUrls: []
                -mainUrl: Sulu\Component\Webspace\Url {#432 …}
              }
              "dev" => Sulu\Component\Webspace\Environment {#434
                -type: "dev"
                -urls: [
                  Sulu\Component\Webspace\Url {#435 …}
                  Sulu\Component\Webspace\Url {#436
                    -language: "ar"
                    -country: ""
                    -segment: ""
                    -redirect: ""
                    -main: false
                    -url: "{host}/ar"
                    -environment: "dev"
                  }
                ]
                -customUrls: []
                -mainUrl: Sulu\Component\Webspace\Url {#435 …}
              }
            ]
            -webspace: Sulu\Component\Webspace\Webspace {#414}
          }
        ]
        -security: null
        -navigation: Sulu\Component\Webspace\Navigation {#417 …}
        -templates: [
          "page" => "default"
          "home" => "article"
          "search" => "search"
          "error" => "error"
        ]
        -defaultTemplates: [
          "page" => "default"
          "home" => "homepage"
        ]
        -excludedTemplates: []
        -resourceLocatorStrategy: "tree_leaf_edit"
      }
      -portal: Sulu\Component\Webspace\Portal {#422}
      -localization: Sulu\Component\Localization\Localization {#415}
      -url: "dev.trustforce.ae"
      -redirect: ""
      -main: true
      -urlExpression: "dev.trustforce.ae"
      -priority: 5
    }
    "matchType" => 1
    "portalUrl" => "dev.trustforce.ae"
    "webspace" => Sulu\Component\Webspace\Webspace {#414}
    "portal" => Sulu\Component\Webspace\Portal {#422}
    "localization" => Sulu\Component\Localization\Localization {#415}
    "locale" => "en"
    "urlExpression" => "dev.trustforce.ae"
    "resourceLocator" => "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
    "dateTime" => DateTime @1777279004 {#470
      date: 2026-04-27 08:36:44.797420 UTC (+00:00)
    }
    "host" => "dev.trustforce.ae"
    "port" => 443
    "path" => "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
    "scheme" => "https"
  ]
}

Sulu\Route\Domain\Model\Route {#722
  -id: 33
  -webspace: null
  -locale: "en"
  -slug: "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
  -parentRoute: Proxies\__CG__\Sulu\Route\Domain\Model\Route {#689 …}
  -resourceKey: "articles"
  -resourceId: "019d9645-74f9-7238-8ad4-737d01759b3b"
  -resourceIdCallable: null
}

Sulu\Article\Domain\Model\ArticleDimensionContent {#927
  #id: ? int
  #article: Sulu\Article\Domain\Model\Article {#740 …}
  #title: "RAK retail fit-out: programme recovered after late PM appointment"
  -customizeWebspaceSettings: false
  #additionalWebspaces: Doctrine\Common\Collections\ArrayCollection {#926 …}
  #created: DateTimeImmutable @1776357027 {#989
    date: 2026-04-16 16:30:27.0 UTC (+00:00)
  }
  #changed: DateTimeImmutable @1777203325 {#988
    date: 2026-04-26 11:35:25.0 UTC (+00:00)
  }
  #creator: Proxies\__CG__\Sulu\Bundle\SecurityBundle\Entity\User {#875 …}
  #changer: Proxies\__CG__\Sulu\Bundle\SecurityBundle\Entity\User {#875 …}
  -author: Proxies\__CG__\Sulu\Bundle\ContactBundle\Entity\Contact {#747 …}
  -authored: DateTimeImmutable @1776297600 {#991
    date: 2026-04-16 00:00:00.0 UTC (+00:00)
  }
  -lastModified: null
  #locale: "en"
  #ghostLocale: "en"
  #availableLocales: [
    "en"
  ]
  #stage: "live"
  -isMerged: true
  -version: 0
  -excerptData: [
    "more" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
    "image" => [
      "id" => null
      "displayOption" => null
    ]
    "title" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
    "description" => "<p>A RAK retail fit-out with inherited programme slippage at appointment — recovered to revised baseline within the client's original handover window.</p>"
  ]
  -excerptCategories: Doctrine\Common\Collections\ArrayCollection {#1163 …}
  -excerptTags: Doctrine\Common\Collections\ArrayCollection {#1010 …}
  -excerptAudienceTargetGroups: Doctrine\Common\Collections\ArrayCollection {#2021 …}
  -excerptSegment: null
  -route: null
  -seoData: [
    "title" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
    "keywords" => "fit-out project management UAE, construction project management RAK, retail fit-out Ras Al Khaimah"
    "description" => "A Ras Al Khaimah retail fit-out inherited significant programme slippage at TrustForce appointment. Delivered on revised baseline within the client's original handover window."
    "canonicalUrl" => "https://trustforce.ae/projects/retail-fitout-rak"
  ]
  -seoNoIndex: false
  -seoNoFollow: false
  -seoHideInSitemap: false
  #shadowLocale: null
  #shadowLocales: null
  -templateKey: "webpage"
  -templateData: [
    "url" => [
      0 => "/"
      1 => "p"
      2 => "r"
      3 => "o"
      4 => "j"
      5 => "e"
      6 => "c"
      7 => "t"
      8 => "s"
      9 => "/"
      10 => "r"
      11 => "e"
      12 => "t"
      13 => "a"
      14 => "i"
      15 => "l"
      16 => "-"
      17 => "f"
      18 => "i"
      19 => "t"
      20 => "o"
      21 => "u"
      22 => "t"
      23 => "-"
      24 => "r"
      25 => "a"
      26 => "k"
      "page" => [
        "path" => "/projects"
        "uuid" => "019d6d7f-22e5-79c6-be2b-d3241517adcd"
      ]
      "suffix" => "/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
    ]
    "title" => "RAK retail fit-out: programme recovered after late PM appointment"
    "blocks" => [
      [
        "id" => "import-block-0"
        "_id" => "6743b18f"
        "type" => "snapshot"
        "content" => """
          | Sector | Built environment — retail fit-out |\n
          | Location | Ras Al Khaimah |\n
          | Scale | Mid-size retail fit-out; multiple contractor packages across MEP, joinery, and finishes |\n
          | Outcome | Programme recovered to revised baseline; practical completion achieved within the client's original handover window |
          """
      ]
      [
        "id" => "import-block-1"
        "_id" => "21ee6d83"
        "type" => "paragraph-group"
        "intro" => ""
        "heading" => "The Situation at Appointment"
        "paragraphs" => [
          [
            "id" => "import-block-1-p-0"
            "text" => "<p>A RAK-based retail operator appointed TrustForce several weeks into a fit-out programme that had already accumulated significant slippage against its original baseline. The main contractor had been on site since the preceding quarter, but no independent PM had been in place. Reporting passed directly from the contractor to the client's operations team — a team with no construction background and limited visibility of what the delay meant for the handover date.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-1-p-1"
            "text" => "<p>The handover window was fixed. A trading lease with a landlord-imposed opening date carried financial exposure if missed. Two contractor packages — MEP and joinery — were running on sequences that had not been recoordinated since the programme first slipped, meaning further delay was probable without active intervention.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
        ]
        "preheading" => ""
        "subheading" => ""
      ]
      [
        "id" => "import-block-2"
        "_id" => "2fc209de"
        "type" => "paragraph-group"
        "intro" => ""
        "heading" => "What TrustForce Did"
        "paragraphs" => [
          [
            "id" => "import-block-2-p-0"
            "text" => "<p>The first two weeks were diagnostic. TrustForce rebuilt the programme from current site status rather than the contractor's reported position, which had not been updated to reflect actual MEP first-fix progress. That rebuild identified a recoverable window — not the full extent of slippage, but enough to meet the client's handover date if the joinery package was resequenced and authority submissions were accelerated immediately.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-2-p-1"
            "text" => "<p>TrustForce took direct ownership of the authority submissions workstream, which had not been initiated at the point of appointment. RAK civil defence and RAK Municipality building completion inspections both carry submission lead times that the original programme had underallocated. Submissions were prepared and lodged within the first weeks of engagement, ahead of the revised critical path. The contractor received a revised works sequence covering MEP second-fix and joinery installation, with weekly progress gates replacing the monthly reporting the client had previously received.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-2-p-2"
            "text" => "<p>Holding that sequence took consistent effort. The contractor pushed back on the joinery lead times throughout the recovery phase. TrustForce maintained the revised programme as the reference document for all site instructions, change requests, and payment applications. That approach removed the contractor's ability to reframe delay as a scope variation — a pattern common on fit-out programmes where the PM is absent or arrives late.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-2-p-3"
            "text" => "<p>RAK civil defence inspection scheduling carries informal lead times that are not published and shift with submission volume. Prior experience of RAK submission cycles allowed a realistic inspection date to be built into the recovery programme at the outset rather than assumed from standard guidance. The client's original programme had significantly underallocated time for civil defence sign-off — accounting for first-submission review and the standard resubmission cycle, the actual lead time ran considerably longer than the original plan had assumed. Had that gap not been identified and front-loaded into the recovery sequence, the programme would have failed regardless of site progress.</p>"
            "type" => "paragraph"
            "subheading" => "From the field"
          ]
        ]
        "preheading" => ""
        "subheading" => ""
      ]
      [
        "id" => "import-block-3"
        "_id" => "fc1641bf"
        "type" => "paragraph-group"
        "intro" => ""
        "heading" => "The Outcome"
        "paragraphs" => [
          [
            "id" => "import-block-3-p-0"
            "text" => "<p>Practical completion was certified on the revised baseline date, within the client's original landlord-imposed handover window.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-3-p-1"
            "text" => "<p>The contractor's final account was agreed without dispute. No variation claims related to the resequencing were accepted — the revised programme, issued in writing at the close of the diagnostic phase, established the baseline against which all subsequent claims were assessed.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-3-p-2"
            "text" => "<ul><li>Authority submissions to RAK civil defence and RAK Municipality lodged within weeks of TrustForce appointment, against a workstream that had not been initiated at handover</li><li>MEP second-fix and joinery resequenced promptly following the programme rebuild; weekly progress gates replaced monthly contractor reporting</li><li>Civil defence inspection obtained on the first submission cycle — no resubmission required</li><li>The majority of the inherited slippage was recovered within the engagement period</li><li>Contractor final account agreed without variation dispute; payment aligned to revised programme milestones throughout</li></ul>"
            "type" => "paragraph"
            "subheading" => ""
          ]
        ]
        "preheading" => ""
        "subheading" => ""
      ]
      [
        "id" => "import-block-4"
        "_id" => "b8b9a3c8"
        "type" => "paragraph-group"
        "intro" => ""
        "heading" => "What This Means for Similar Projects"
        "paragraphs" => [
          [
            "id" => "import-block-4-p-0"
            "text" => "<p>Late PM appointment on a fit-out does not automatically mean a missed handover — but it narrows the recovery window sharply. The recoverable time on this engagement was identified in the diagnostic phase, and only because the programme was rebuilt independently of the contractor's reported position. Clients appointing a PM after site start should expect a diagnostic phase before any recovery commitment is made. Any PM who commits to a recovery timeline before completing that diagnosis has not done the work.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
          [
            "id" => "import-block-4-p-1"
            "text" => "<p><em>For background on why early PM appointment reduces programme risk on UAE fit-out and construction projects, see <a href="/insights/when-to-appoint-pm-uae">When should a developer appoint a PM? The case for day one engagement</a>. For an overview of TrustForce's approach to construction PM, visit our <a href="/services/built-environment">Built Environment services page</a>.</em></p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
        ]
        "preheading" => ""
        "subheading" => ""
      ]
      [
        "id" => "import-block-5"
        "_id" => "6713d60a"
        "type" => "paragraph-group"
        "intro" => ""
        "heading" => "Talk to TrustForce"
        "paragraphs" => [
          [
            "id" => "import-block-5-p-0"
            "text" => "<p>If you are managing a fit-out in Ras Al Khaimah or the Northern Emirates and your programme has slipped — or you want independent oversight in place before it does — talk to TrustForce.</p>"
            "type" => "paragraph"
            "subheading" => ""
          ]
        ]
        "preheading" => ""
        "subheading" => ""
      ]
      [
        "id" => "import-block-6"
        "_id" => "4b08ed65"
        "faqs" => [
          [
            "id" => "import-block-6-faq-0"
            "type" => "faq"
            "answer" => "There is no fixed point, but the recoverable window shrinks as the programme advances. The most common scenario TrustForce encounters is appointment at 20–40% programme completion, where enough work remains to resequence but authority submission lead times have already been underplanned. Appointment after practical completion inspections have been missed is significantly harder to recover. The earlier the appointment, the more options remain open."
            "question" => "At what point is it too late to appoint an independent PM on a fit-out?"
          ]
          [
            "id" => "import-block-6-faq-1"
            "type" => "faq"
            "answer" => "Contractors typically resist resequencing because it removes flexibility in their resource allocation. In this engagement, TrustForce held the revised programme as the contractual baseline for all instructions and payment applications from the point of issue. That approach — making the revised programme the document of record rather than a recommendation — limits the scope for the contractor to treat the resequencing as advisory. Resistance was present in the first two weeks and diminished once payment applications were assessed against the revised milestones."
            "question" => "How did the contractor respond to the revised programme?"
          ]
          [
            "id" => "import-block-6-faq-2"
            "type" => "faq"
            "answer" => "Yes, with conditions. TrustForce will assess the programme position before confirming a recovery commitment. Where the remaining float has been fully consumed and the handover date is no longer achievable, TrustForce will state that position to the client at the diagnostic stage rather than commit to an outcome that the site conditions do not support. Clients should expect an honest assessment of what is recoverable before a scope of engagement is agreed."
            "question" => "Does TrustForce take on engagements where the programme is already significantly delayed?"
          ]
        ]
        "type" => "faq-group"
        "intro" => ""
        "heading" => "FAQ"
        "preheading" => ""
        "subheading" => ""
      ]
    ]
    "heading" => "RAK retail fit-out: programme recovered after late PM appointment"
    "ai_prompt" => null
    "subheading" => "Significant inherited slippage at appointment. Delivered on revised baseline within the client's original handover window."
    "headerImage" => [
      "id" => 8
      "displayOption" => null
    ]
  ]
  #mainWebspace: "website"
  #workflowPlace: null
  #workflowPublished: DateTimeImmutable @1776357027 {#990
    date: 2026-04-16 16:30:27.0 UTC (+00:00)
  }
}

Symfony\Component\Routing\Route {#1746
  -path: "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
  -host: "dev.trustforce.ae"
  -schemes: []
  -methods: []
  -defaults: [
    "object" => Sulu\Article\Domain\Model\ArticleDimensionContent {#927
      #id: ? int
      #article: Sulu\Article\Domain\Model\Article {#740 …}
      #title: "RAK retail fit-out: programme recovered after late PM appointment"
      -customizeWebspaceSettings: false
      #additionalWebspaces: Doctrine\Common\Collections\ArrayCollection {#926 …}
      #created: DateTimeImmutable @1776357027 {#989
        date: 2026-04-16 16:30:27.0 UTC (+00:00)
      }
      #changed: DateTimeImmutable @1777203325 {#988
        date: 2026-04-26 11:35:25.0 UTC (+00:00)
      }
      #creator: Proxies\__CG__\Sulu\Bundle\SecurityBundle\Entity\User {#875 …}
      #changer: Proxies\__CG__\Sulu\Bundle\SecurityBundle\Entity\User {#875 …}
      -author: Proxies\__CG__\Sulu\Bundle\ContactBundle\Entity\Contact {#747 …}
      -authored: DateTimeImmutable @1776297600 {#991
        date: 2026-04-16 00:00:00.0 UTC (+00:00)
      }
      -lastModified: null
      #locale: "en"
      #ghostLocale: "en"
      #availableLocales: [
        "en"
      ]
      #stage: "live"
      -isMerged: true
      -version: 0
      -excerptData: [
        "more" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
        "image" => [
          "id" => null
          "displayOption" => null
        ]
        "title" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
        "description" => "<p>A RAK retail fit-out with inherited programme slippage at appointment — recovered to revised baseline within the client's original handover window.</p>"
      ]
      -excerptCategories: Doctrine\Common\Collections\ArrayCollection {#1163 …}
      -excerptTags: Doctrine\Common\Collections\ArrayCollection {#1010 …}
      -excerptAudienceTargetGroups: Doctrine\Common\Collections\ArrayCollection {#2021 …}
      -excerptSegment: null
      -route: null
      -seoData: [
        "title" => "RAK retail fit-out: programme recovery after late PM appointment | TrustForce Projects"
        "keywords" => "fit-out project management UAE, construction project management RAK, retail fit-out Ras Al Khaimah"
        "description" => "A Ras Al Khaimah retail fit-out inherited significant programme slippage at TrustForce appointment. Delivered on revised baseline within the client's original handover window."
        "canonicalUrl" => "https://trustforce.ae/projects/retail-fitout-rak"
      ]
      -seoNoIndex: false
      -seoNoFollow: false
      -seoHideInSitemap: false
      #shadowLocale: null
      #shadowLocales: null
      -templateKey: "webpage"
      -templateData: [
        "url" => [
          0 => "/"
          1 => "p"
          2 => "r"
          3 => "o"
          4 => "j"
          5 => "e"
          6 => "c"
          7 => "t"
          8 => "s"
          9 => "/"
          10 => "r"
          11 => "e"
          12 => "t"
          13 => "a"
          14 => "i"
          15 => "l"
          16 => "-"
          17 => "f"
          18 => "i"
          19 => "t"
          20 => "o"
          21 => "u"
          22 => "t"
          23 => "-"
          24 => "r"
          25 => "a"
          26 => "k"
          "page" => [
            "path" => "/projects"
            "uuid" => "019d6d7f-22e5-79c6-be2b-d3241517adcd"
          ]
          "suffix" => "/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
        ]
        "title" => "RAK retail fit-out: programme recovered after late PM appointment"
        "blocks" => [
          [
            "id" => "import-block-0"
            "_id" => "6743b18f"
            "type" => "snapshot"
            "content" => """
              | Sector | Built environment — retail fit-out |\n
              | Location | Ras Al Khaimah |\n
              | Scale | Mid-size retail fit-out; multiple contractor packages across MEP, joinery, and finishes |\n
              | Outcome | Programme recovered to revised baseline; practical completion achieved within the client's original handover window |
              """
          ]
          [
            "id" => "import-block-1"
            "_id" => "21ee6d83"
            "type" => "paragraph-group"
            "intro" => ""
            "heading" => "The Situation at Appointment"
            "paragraphs" => [
              [
                "id" => "import-block-1-p-0"
                "text" => "<p>A RAK-based retail operator appointed TrustForce several weeks into a fit-out programme that had already accumulated significant slippage against its original baseline. The main contractor had been on site since the preceding quarter, but no independent PM had been in place. Reporting passed directly from the contractor to the client's operations team — a team with no construction background and limited visibility of what the delay meant for the handover date.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-1-p-1"
                "text" => "<p>The handover window was fixed. A trading lease with a landlord-imposed opening date carried financial exposure if missed. Two contractor packages — MEP and joinery — were running on sequences that had not been recoordinated since the programme first slipped, meaning further delay was probable without active intervention.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
            ]
            "preheading" => ""
            "subheading" => ""
          ]
          [
            "id" => "import-block-2"
            "_id" => "2fc209de"
            "type" => "paragraph-group"
            "intro" => ""
            "heading" => "What TrustForce Did"
            "paragraphs" => [
              [
                "id" => "import-block-2-p-0"
                "text" => "<p>The first two weeks were diagnostic. TrustForce rebuilt the programme from current site status rather than the contractor's reported position, which had not been updated to reflect actual MEP first-fix progress. That rebuild identified a recoverable window — not the full extent of slippage, but enough to meet the client's handover date if the joinery package was resequenced and authority submissions were accelerated immediately.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-2-p-1"
                "text" => "<p>TrustForce took direct ownership of the authority submissions workstream, which had not been initiated at the point of appointment. RAK civil defence and RAK Municipality building completion inspections both carry submission lead times that the original programme had underallocated. Submissions were prepared and lodged within the first weeks of engagement, ahead of the revised critical path. The contractor received a revised works sequence covering MEP second-fix and joinery installation, with weekly progress gates replacing the monthly reporting the client had previously received.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-2-p-2"
                "text" => "<p>Holding that sequence took consistent effort. The contractor pushed back on the joinery lead times throughout the recovery phase. TrustForce maintained the revised programme as the reference document for all site instructions, change requests, and payment applications. That approach removed the contractor's ability to reframe delay as a scope variation — a pattern common on fit-out programmes where the PM is absent or arrives late.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-2-p-3"
                "text" => "<p>RAK civil defence inspection scheduling carries informal lead times that are not published and shift with submission volume. Prior experience of RAK submission cycles allowed a realistic inspection date to be built into the recovery programme at the outset rather than assumed from standard guidance. The client's original programme had significantly underallocated time for civil defence sign-off — accounting for first-submission review and the standard resubmission cycle, the actual lead time ran considerably longer than the original plan had assumed. Had that gap not been identified and front-loaded into the recovery sequence, the programme would have failed regardless of site progress.</p>"
                "type" => "paragraph"
                "subheading" => "From the field"
              ]
            ]
            "preheading" => ""
            "subheading" => ""
          ]
          [
            "id" => "import-block-3"
            "_id" => "fc1641bf"
            "type" => "paragraph-group"
            "intro" => ""
            "heading" => "The Outcome"
            "paragraphs" => [
              [
                "id" => "import-block-3-p-0"
                "text" => "<p>Practical completion was certified on the revised baseline date, within the client's original landlord-imposed handover window.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-3-p-1"
                "text" => "<p>The contractor's final account was agreed without dispute. No variation claims related to the resequencing were accepted — the revised programme, issued in writing at the close of the diagnostic phase, established the baseline against which all subsequent claims were assessed.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-3-p-2"
                "text" => "<ul><li>Authority submissions to RAK civil defence and RAK Municipality lodged within weeks of TrustForce appointment, against a workstream that had not been initiated at handover</li><li>MEP second-fix and joinery resequenced promptly following the programme rebuild; weekly progress gates replaced monthly contractor reporting</li><li>Civil defence inspection obtained on the first submission cycle — no resubmission required</li><li>The majority of the inherited slippage was recovered within the engagement period</li><li>Contractor final account agreed without variation dispute; payment aligned to revised programme milestones throughout</li></ul>"
                "type" => "paragraph"
                "subheading" => ""
              ]
            ]
            "preheading" => ""
            "subheading" => ""
          ]
          [
            "id" => "import-block-4"
            "_id" => "b8b9a3c8"
            "type" => "paragraph-group"
            "intro" => ""
            "heading" => "What This Means for Similar Projects"
            "paragraphs" => [
              [
                "id" => "import-block-4-p-0"
                "text" => "<p>Late PM appointment on a fit-out does not automatically mean a missed handover — but it narrows the recovery window sharply. The recoverable time on this engagement was identified in the diagnostic phase, and only because the programme was rebuilt independently of the contractor's reported position. Clients appointing a PM after site start should expect a diagnostic phase before any recovery commitment is made. Any PM who commits to a recovery timeline before completing that diagnosis has not done the work.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
              [
                "id" => "import-block-4-p-1"
                "text" => "<p><em>For background on why early PM appointment reduces programme risk on UAE fit-out and construction projects, see <a href="/insights/when-to-appoint-pm-uae">When should a developer appoint a PM? The case for day one engagement</a>. For an overview of TrustForce's approach to construction PM, visit our <a href="/services/built-environment">Built Environment services page</a>.</em></p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
            ]
            "preheading" => ""
            "subheading" => ""
          ]
          [
            "id" => "import-block-5"
            "_id" => "6713d60a"
            "type" => "paragraph-group"
            "intro" => ""
            "heading" => "Talk to TrustForce"
            "paragraphs" => [
              [
                "id" => "import-block-5-p-0"
                "text" => "<p>If you are managing a fit-out in Ras Al Khaimah or the Northern Emirates and your programme has slipped — or you want independent oversight in place before it does — talk to TrustForce.</p>"
                "type" => "paragraph"
                "subheading" => ""
              ]
            ]
            "preheading" => ""
            "subheading" => ""
          ]
          [
            "id" => "import-block-6"
            "_id" => "4b08ed65"
            "faqs" => [
              [
                "id" => "import-block-6-faq-0"
                "type" => "faq"
                "answer" => "There is no fixed point, but the recoverable window shrinks as the programme advances. The most common scenario TrustForce encounters is appointment at 20–40% programme completion, where enough work remains to resequence but authority submission lead times have already been underplanned. Appointment after practical completion inspections have been missed is significantly harder to recover. The earlier the appointment, the more options remain open."
                "question" => "At what point is it too late to appoint an independent PM on a fit-out?"
              ]
              [
                "id" => "import-block-6-faq-1"
                "type" => "faq"
                "answer" => "Contractors typically resist resequencing because it removes flexibility in their resource allocation. In this engagement, TrustForce held the revised programme as the contractual baseline for all instructions and payment applications from the point of issue. That approach — making the revised programme the document of record rather than a recommendation — limits the scope for the contractor to treat the resequencing as advisory. Resistance was present in the first two weeks and diminished once payment applications were assessed against the revised milestones."
                "question" => "How did the contractor respond to the revised programme?"
              ]
              [
                "id" => "import-block-6-faq-2"
                "type" => "faq"
                "answer" => "Yes, with conditions. TrustForce will assess the programme position before confirming a recovery commitment. Where the remaining float has been fully consumed and the handover date is no longer achievable, TrustForce will state that position to the client at the diagnostic stage rather than commit to an outcome that the site conditions do not support. Clients should expect an honest assessment of what is recoverable before a scope of engagement is agreed."
                "question" => "Does TrustForce take on engagements where the programme is already significantly delayed?"
              ]
            ]
            "type" => "faq-group"
            "intro" => ""
            "heading" => "FAQ"
            "preheading" => ""
            "subheading" => ""
          ]
        ]
        "heading" => "RAK retail fit-out: programme recovered after late PM appointment"
        "ai_prompt" => null
        "subheading" => "Significant inherited slippage at appointment. Delivered on revised baseline within the client's original handover window."
        "headerImage" => [
          "id" => 8
          "displayOption" => null
        ]
      ]
      #mainWebspace: "website"
      #workflowPlace: null
      #workflowPublished: DateTimeImmutable @1776357027 {#990
        date: 2026-04-16 16:30:27.0 UTC (+00:00)
      }
    }
    "view" => "shared/pages/webpage"
    "_controller" => "Sulu\Content\UserInterface\Controller\Website\ContentController::indexAction"
    "_cacheLifetime" => 1209600
    "_seo" => [
      "canonicalUrl" => "https://dev.trustforce.ae/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
    ]
    "_sulu_route" => Sulu\Route\Domain\Model\Route {#722
      -id: 33
      -webspace: null
      -locale: "en"
      -slug: "/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"
      -parentRoute: Proxies\__CG__\Sulu\Route\Domain\Model\Route {#689 …}
      -resourceKey: "articles"
      -resourceId: "019d9645-74f9-7238-8ad4-737d01759b3b"
      -resourceIdCallable: null
    }
  ]
  -requirements: []
  -options: [
    "compiler_class" => "Symfony\Component\Routing\RouteCompiler"
    "utf8" => true
  ]
  -condition: ""
  -compiled: Symfony\Component\Routing\CompiledRoute {#481 …}
}

"/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"

"shared/pages/webpage"

"website"

"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"

"gzip, deflate, br, zstd"

"en-GB,en;q=0.9"

"0"

"dev.trustforce.ae"

"u=0, i"

"https://dev.trustforce.ae/projects"

"document"

"navigate"

"same-origin"

"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.4 Safari/605.1.15"

"1"

"max-age=240, public, s-maxage=240"

"text/html; charset=UTF-8"

"Mon, 27 Apr 2026 08:36:45 GMT"

"edce01"

"Sulu/3.0.0"

"1209600"

"0"

"dev"

"00625a63eb4397f41f7a7b86af8adcf8"

"var/share"

"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"

"noreply@trustforce.ae"

"info@trustforce.ae"

"mysql://alphasec_tfpm_dev:uc7n6nk648BcXF2a7PW337XQ@localhost:3306/alphasec_sulu_tfpm_dev?serverVersion=8.0.32&charset=utf8mb4"

"http://localhost"

"flock"

"smtp://info%40trustforce.ae:Tv7%3B3%40%2FP2YJ%7D.42R%5Ej3%29%2F9w3@mail.trustforce.ae:465"

"doctrine://default?auto_setup=0"

"loupe://%kernel.project_dir%/var/indexes"

"tfpm@dev.alidade.de"

"0"

"/home/alphasec/dev.trustforce.ae"

""

"/home/alphasec/dev.trustforce.ae"

"off"

"off"

""

""

"17"

"3935217-98-17"

"on"

"on"

"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"

"gzip, deflate, br, zstd"

"en-GB,en;q=0.9"

"dev.trustforce.ae"

"u=0, i"

"https://dev.trustforce.ae/projects"

"document"

"navigate"

"same-origin"

"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.4 Safari/605.1.15"

"/usr/local/bin:/usr/bin:/bin"

"/index.php"

"/"

""

"off"

"off"

""

""

"17"

"3935217-98-17"

"on"

"on"

"dev.trustforce.ae"

"200"

"ae8gHIiwv9RA2X4Qx6UFvgACUQY"

"/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"

"217.165.37.226"

"42530"

"GET"

"https"

1777279004

1777279004.7437

"/projects/rak-retail-fit-out-programme-recovered-after-late-pm-appointment"

"/home/alphasec/dev.trustforce.ae/index.php"

"/index.php"

"192.250.239.80"

"webmaster@dev.trustforce.ae"

"dev.trustforce.ae"

"443"

"HTTP/2.0"

""

"Apache"

"dev.trustforce.ae"

"/home/alphasec/dev.trustforce.ae.sulu/.env"

"APP_ENV,APP_SECRET,APP_SHARE_DIR,DEFAULT_URI,LOCK_DSN,MAILER_DSN,DATABASE_URL,SULU_ADMIN_EMAIL,MESSENGER_TRANSPORT_DSN,SEAL_DSN,APP_DEBUG,CLAUDE_API_KEY,CONTACT_NOTIFICATION_TO,CONTACT_NOTIFICATION_FROM"

"/tmp"

"/tmp"

"/tmp"

"ae8gHIiwv9RA2X4Qx6UFvgACUQY"