The following responsibilities apply to all engagements. Where advisory and implementation tracks differ materially, this is noted.
Named Contact The customer provides a named project contact with sufficient authority to make decisions relevant to the engagement scope. This contact is available for scheduled sessions and responds to open questions within one business day.
Input Materials & Documentation (particularly relevant for Advisory & Assessment) For assessment-type engagements, the quality and completeness of analysis depends on the input provided. The customer is responsible for making relevant documentation, system access, and subject-matter expertise available within the agreed timeframe. Incomplete or delayed input may limit the depth of findings.
Technical Access & Prerequisites (particularly relevant for Implementation) Required access to systems, environments, test data, or third-party platforms is provided by the customer before the engagement begins. Delays caused by missing access are the customer's responsibility and may affect timelines and effort.
Infrastructure Readiness DNS configuration, firewall rules, certificate provisioning, and any other infrastructure prerequisites within the customer's environment are the customer's responsibility. Retarus provides guidance; implementation rests with the customer.
Timely Feedback & Sign-off Deliverables requiring customer review – reports, architecture documents, test results – are reviewed within five business days of delivery unless agreed otherwise. Delayed sign-off may result in revised timelines.
Third-Party Coordination Where the engagement involves third-party systems, providers, or integrations, the customer is responsible for coordinating access, availability, and cooperation with those parties.
📌 Engagements are scoped based on information provided during the initial alignment. Material changes to scope, environment, or requirements identified after scoping may result in a revised effort estimate and a separate order.