Service Delivery & Client Responsibilities

1. Delivery Model

All services are delivered remotely through video meetings, email, secure file exchange, shared documents, screen sharing, or other agreed digital channels. No on-site work, managed operation, software hosting, hardware installation, or continuous technical support is included unless expressly stated in a signed project document.

2. Scope Confirmation

Before work begins, the parties identify the operating question, service type, primary contact, intended users, known constraints, deliverables, estimated schedule, fees, and important assumptions. The client must review the scope carefully. An ambiguous or incomplete request may require a discovery step before a reliable proposal can be prepared.

Only the workflow, department, tool category, or training audience stated in the project document is included. Additional business units, extra workflows, custom development, vendor implementation, extensive data cleaning, policy drafting, and ongoing monitoring require separate written approval.

3. Delivery Process

A typical engagement may include intake, document review, remote interviews, workflow mapping, option research, draft preparation, review discussion, revisions within scope, and final delivery. The exact sequence depends on the service. AI Tool Selection Support may focus on documented comparison; Remote AI Training may be delivered in a single session; an Implementation Plan may require multiple review points.

Deliverables may include written assessments, strategy recommendations, workflow maps, tool comparison notes, phased plans, prompt templates, operating instructions, training materials, or meeting summaries. Format and depth are defined by the approved scope.

4. Estimated Timelines

Delivery estimates begin after required payment, information, access, and scheduling are complete. Estimates assume timely client responses and stable project requirements. Third-party outages, vendor changes, incomplete materials, expanded stakeholder review, or delayed decisions may extend the schedule.

Clear Summit Strategies will communicate a material known delay and provide a revised estimate. A date is a good-faith planning target unless the project document expressly identifies it as a guaranteed contractual deadline.

5. Client Project Lead

The client must appoint one authorized project lead who can provide information, coordinate participants, consolidate feedback, approve decisions, and receive deliverables. Conflicting instructions from multiple participants may pause the work until the client provides a single direction.

The client represents that participants are authorized to discuss the relevant processes and that required internal notices, permissions, and approvals have been obtained.

6. Accuracy and Completeness of Information

Recommendations depend on the information available. The client must provide accurate descriptions of current tasks, systems, constraints, policies, costs, risks, and intended outcomes. Material omissions or incorrect information may make a recommendation incomplete or unsuitable.

The client should promptly disclose changes to the workflow, software environment, vendor account, responsible personnel, legal requirements, or business objective. Reanalysis caused by changed or previously withheld facts may require added time and fees.

7. Access and Security

The client should provide the minimum access reasonably necessary. Whenever possible, demonstrations, screenshots, redacted samples, sandbox accounts, or client-controlled screen sharing should be used instead of permanent credentials. Passwords and multifactor codes must not be sent through ordinary project forms or email.

The client is responsible for account administration, backups, endpoint security, access revocation, and approval of any third-party vendor. Clear Summit Strategies does not assume control of client production systems under a consulting engagement.

8. Sensitive and Regulated Information

The client must not provide protected health information, full payment card data, government identification numbers, authentication secrets, information about children, highly sensitive employment records, export-controlled material, or other regulated data unless a written agreement specifically authorizes the category and safeguards. If unnecessary sensitive information is received, it may be returned, deleted, redacted, or excluded from the work.

9. Review and Feedback

The client must review a draft for factual accuracy, scope alignment, and operational feasibility. Feedback should be specific, consolidated, and provided within the agreed period. Unless otherwise stated, the review period is five business days. A delayed review shifts later milestones.

Included revisions correct or refine work within the original objective. A new objective, new workflow, different audience, substantial format change, or implementation request is a scope change.

10. Testing and Implementation

The client retains responsibility for deciding whether and how to implement a recommendation. Before production use, the client should test tool outputs, permissions, data flows, exception handling, human review, rollback procedures, and vendor terms in its own environment. No plan replaces internal approval, legal review, cybersecurity review, financial approval, or subject-matter validation where those are appropriate.

11. Training Participation

For training, the client must provide a suitable remote meeting environment, confirm the participant count, communicate relevant skill levels, and ensure attendees have authorized access to any tool used. Recording is prohibited unless both parties agree in writing. Training materials may be used internally by the authorized participants but may not be resold or publicly distributed.

12. Completion and Acceptance

A service is complete when the agreed final deliverable or session has been provided. The client should report a material scope discrepancy within five business days. Acceptance does not depend on a third-party tool remaining unchanged, management approving implementation, or a particular commercial result occurring.

13. Ongoing Maintenance

AI products and business processes change. Unless ongoing support is expressly included, the client is responsible for monitoring vendor changes, reviewing outputs, updating prompts and instructions, training new staff, maintaining access controls, and reassessing the workflow when conditions change.