LEGAL  /  SCOPE & RESPONSIBILITIES

Project Scope and Client Responsibilities

Last updated: July 2026

This policy sets out how project scope is defined for Zentarix Engine engagements and what we rely on from clients to deliver quality work. A shared understanding of scope and responsibilities is the foundation of every successful advisory engagement.

01How scope is defined

Every engagement begins with a written scope of work that describes the deliverables, the systems in question, the timeline, and the fee. Nothing is assumed to be included that is not written into that document. If a need emerges during the engagement that falls outside the agreed scope, we will discuss it and, if you wish, capture it in a written change.

02What our engagements cover

Depending on the scope you choose, our engagements cover workflow assessments, preparation of user documentation, familiarization workshops, and operational process reviews. All of this work is advisory, documentation, or training in nature.

03What our engagements exclude

Our engagements never include manufacturing, hardware installation, automation integration, custom software development, equipment maintenance, or operating your machinery. If your project depends on any of these, they must be handled by a qualified provider outside our engagement.

04Client responsibilities

To keep an engagement on track, we rely on you to:

• Provide a designated point of contact with authority to make decisions
• Give timely access to the systems, documents, and staff relevant to the work
• Supply accurate and complete information about your processes and equipment
• Review drafts and provide consolidated feedback within the agreed windows
• Ensure any site access we need is arranged safely and lawfully

05Access and safety on site

Where an engagement involves visiting your premises, you are responsible for site safety, for any required inductions, and for ensuring that the environment is safe for observation. We observe and document; we do not operate equipment or enter restricted areas without appropriate supervision.

06Change requests

If either party wishes to change the scope during an engagement, the change is recorded in writing along with any effect on timeline and fee before the additional work begins. This keeps expectations clear and avoids surprises on either side.

07Timelines and dependencies

Timelines in the scope of work assume that information and feedback are provided when agreed. Delays in access, information, or review may move delivery dates, and we will keep you informed if a dependency is affecting the schedule.

08Acceptance of deliverables

On delivery, you have a defined review period to confirm that a deliverable meets the agreed scope. Feedback within that period that relates to the original scope is addressed as part of the engagement. Requests beyond the original scope are treated as a new or expanded engagement.