Reliable technology work depends on clear authority, accurate information, controlled access, tested backups, timely decisions, and cooperation between the service provider, the client, users, and third-party vendors.
Services are primarily delivered remotely through scheduled meetings, approved remote-access tools, cloud administration portals, secure document exchange, project management systems, and support channels. On-site work is not included unless expressly stated in a written scope. Delivery dates are estimates until dependencies, access, approvals, and required third-party resources are confirmed.
We rely on client-provided inventories, diagrams, account lists, license records, policies, objectives, and descriptions of current problems. The client must disclose known outages, unsupported hardware, prior incidents, disputed ownership, regulatory requirements, vendor restrictions, and critical operating periods. Hidden dependencies or inaccurate information can materially change cost, risk, and schedule.
Discovery is a point-in-time review of the systems reasonably made available. It is not a guarantee that every defect, threat, unauthorized device, historical compromise, licensing problem, or undocumented dependency will be found.
The client must identify an executive sponsor, technical contact, billing contact, and emergency contact as appropriate. We may rely on instructions from designated contacts unless informed in writing that authority has changed. High-impact actions may require a named approver and a defined maintenance window.
The client is responsible for internal communication, labor relations, employee notices, privacy notices, change approvals, and business decisions. We do not determine who should have organizational authority or access; we implement approved decisions within the agreed scope.
The client must lawfully control or have permission to access every system included in the project. Access should use named accounts, multi-factor authentication, least privilege, expiration, and logging where supported. Shared credentials should be avoided. Credentials and recovery codes must not be placed in the public website form.
Temporary access may be removed when no longer required. The client must promptly revoke access for departed personnel, notify us of compromised credentials, and maintain an independent method to recover ownership of critical domains, cloud tenants, and business accounts.
Before material production changes, the client must confirm that current, restorable backups exist unless creation and testing of backups is expressly part of our scope. A successful backup job is not the same as a verified recovery. Restoration testing, retention, off-site separation, encryption, recovery time, and recovery point objectives should be documented.
Some emergency fixes or vendor-controlled changes cannot be fully tested. We will communicate known limitations when practical. The client decides whether the business urgency justifies residual risk and must maintain continuity plans for critical operations.
The client is responsible for purchasing and maintaining required licenses, subscriptions, warranties, connectivity, supported hardware, and vendor agreements unless procurement is expressly included. Recommendations are based on information available at the time and do not guarantee that a vendor will preserve pricing, features, compatibility, location, or availability.
Vendor outages, product defects, license enforcement, account verification, deprecation, support delays, and platform policy changes may affect delivery. We may coordinate with a vendor but cannot bind it or guarantee its response.
We implement only the controls accepted in writing. The client remains responsible for organization-wide governance, personnel screening, user training, insurance, physical security, incident escalation, legal reporting, compliance interpretation, and decisions about residual risk. A recommendation not approved, funded, or implemented remains the client’s responsibility.
The client must notify us promptly about suspected compromise, unusual account activity, lost devices, ransomware, unauthorized access, or material configuration changes. Delayed notice may reduce available options and increase recovery time and cost.
For website development, the client must provide final text, trademarks, images, policies, product claims, accessibility requirements, domain access, and approvals on schedule. The client warrants that it may lawfully use supplied content and is responsible for factual accuracy, consumer disclosures, industry-specific claims, and ongoing content maintenance after handoff.
Browser, device, application, theme, and platform updates can change presentation over time. Ongoing monitoring, content entry, search performance, accessibility remediation, and application compatibility are included only when expressly stated.
The client must provide qualified users for testing and review deliverables within the stated period. Feedback should be consolidated, specific, and tied to the accepted scope. Conflicting instructions from multiple contacts may pause work until an authorized decision is provided.
An in-scope material nonconformity should be reported with steps to reproduce, expected behavior, actual behavior, screenshots or logs where appropriate, and affected users. New preferences, added features, expanded environments, or changes after approval are change requests rather than defects.
Support coverage, channels, included users, priority definitions, response targets, maintenance activities, and excluded work are defined in the service order. A response target is the time to acknowledge or begin triage, not a guaranteed resolution time. Resolution depends on complexity, cooperation, parts, vendor response, access, and the nature of the incident.
Emergency channels should be reserved for genuine business-critical events. Abuse, threats, repeated unauthorized requests, or attempts to bypass verification may result in restricted communication or suspension.
We will create the documentation identified in scope. Documentation represents the environment at the time prepared and must be updated after later changes. The client must store ownership records, recovery information, licenses, architecture notes, and procedures securely and ensure that more than one appropriate person can access business-critical continuity information.
A missed dependency can move milestones and resource availability. If a project is paused, the restart date depends on current capacity. Newly discovered conditions may require an updated risk assessment, price, timeline, or technical approach. No material expansion is included without clear written authorization.
Email: privacy@nadellaglobal.com
Address: 3285 Thorneridge Trl, Douglasville, GA 30135
Phone: +1 443 606 8654
