Project Delivery & Client Responsibilities

1. Project Onboarding

Work begins after the required agreement, deposit, brief, primary contact, and necessary access have been received. The client must identify one authorized decision-maker who can approve scope, design direction, content, and launch.

Kickoff information should be complete and internally approved. Conflicting instructions from multiple stakeholders may pause the project until the client provides a consolidated decision.

2. Content and Materials

The client is responsible for supplying final text, logos, photographs, product data, pricing, policies, disclosures, credentials, brand guidelines, and other required materials in usable formats by the agreed dates.

Sitecraft Studios may organize or lightly format supplied content but does not verify factual, medical, financial, legal, regulatory, or advertising claims unless a separate service expressly includes that work.

3. Access and Credentials

The client must provide lawful, authorized access to relevant platforms. Access should be granted through collaborator accounts, staff accounts, or other secure methods whenever available. Passwords should not be reused across systems.

The client remains responsible for account ownership, subscription status, administrator recovery information, domain registration, billing contacts, and revoking access after the engagement.

4. Feedback and Approvals

Feedback must be specific, consolidated, and submitted through the agreed channel. Statements such as “make it pop” or “try something different” may require clarification before production continues.

An approval authorizes progression to the next stage. Reopening an approved stage may be treated as a change request. Silence beyond the review period may delay the project and release reserved production time.

5. Revisions

Included revisions apply only to the deliverable and revision stage identified in the proposal. A revision adjusts an existing approved direction; it does not include a new concept, new feature, new template, expanded content, or change in business strategy.

Requests submitted separately may be grouped into a single revision round. Additional rounds or out-of-scope requests require approval of additional fees and schedule.

6. Timelines

Schedules are good-faith estimates based on timely cooperation and stable requirements. Dates may change due to late content, delayed feedback, technical limitations, third-party review, platform outages, expanded scope, force majeure, or dependencies outside our control.

An accelerated deadline requires written acceptance and may involve a rush fee. A missed client deadline automatically shifts dependent production dates.

7. Browser and Device Testing

Unless otherwise specified, responsive testing focuses on current mainstream versions of major browsers and representative desktop, tablet, and mobile viewport sizes. Exact visual uniformity across every device is not guaranteed because browsers, operating systems, font rendering, and screen characteristics differ.

Support for obsolete browsers, uncommon embedded browsers, special hardware, or legacy enterprise environments must be agreed separately.

8. Forms, Integrations, and E-Commerce Testing

The client must provide valid test accounts, test products, shipping rules, tax settings, payment gateway access, notification recipients, and any required API credentials. Live payments must not be processed during testing unless specifically authorized.

Before launch, the client must independently verify form destinations, autoresponders, product details, prices, discounts, shipping, tax behavior, policies, inventory, checkout settings, and transactional communications.

9. Accessibility and Compliance Review

We apply reasonable design and development practices within the approved scope. Formal accessibility auditing, legal certification, privacy compliance, regulated-industry review, or jurisdiction-specific consumer disclosures require specialized engagement and may require qualified third-party counsel or auditors.

10. Launch Authorization

Launch occurs after written authorization and receipt of required payment. The client’s authorization confirms that it has reviewed the website and accepts the content, layout, links, functionality, pricing, contact information, and policies.

DNS changes, platform propagation, cache behavior, app synchronization, and third-party systems may require additional time after launch.

11. Handoff

Handoff may include theme files, approved assets, credentials, documentation, recorded guidance, or other items specified in the proposal. The client must download and securely retain delivered files.

Sitecraft Studios is not a permanent archive service. Working files, backups, and project environments may be deleted after a reasonable retention period.

12. Post-Launch Corrections and Support

A limited correction period may apply if stated in the proposal. It covers reproducible defects where delivered work does not materially match the approved scope. It does not cover new requests, third-party changes, client edits, misuse, content changes, platform updates, or environmental changes.

Ongoing updates, monitoring, troubleshooting, and management require an active maintenance plan or separate support authorization.