Project Delivery and Client Responsibilities Policy

EFFECTIVE DATE: JULY 15, 2026

1. Purpose and Application

This Project Delivery and Client Responsibilities Policy explains how Delmion Advisory organizes remote consulting projects, establishes delivery schedules, manages dependencies, receives feedback, handles revisions and change requests, and closes completed engagements. It also sets out the Client cooperation required for timely and useful delivery.

This Policy applies unless a specific Engagement Document states a different process. Because consulting projects vary, the Engagement Document may add milestones, review periods, meeting requirements, or technical delivery details.

2. Project Start

A project begins after the Engagement Document has been accepted, required payment has cleared, the primary Client contact has been confirmed, and the information reasonably needed for onboarding has been received. A proposed date is not a guaranteed start until these conditions are satisfied.

We may provide an onboarding request listing documents, questions, system access, stakeholders, meetings, and decisions needed to proceed. The Client should identify any access restrictions, confidentiality requirements, or internal approval procedures at the outset.

3. Delivery Schedule

The project schedule may include discovery, assessment, analysis, draft development, Client review, revision, and final delivery. Dates are estimates based on the known scope and assumptions unless expressly identified as fixed deadlines in the Engagement Document.

The schedule may change when the Client requests additional work, delays a dependency, changes instructions, adds stakeholders, submits new information, or requires a different approval process. Third-party outages, emergencies, and other events beyond reasonable control may also affect timing.

4. Milestones and Dependencies

Each milestone may depend on specific inputs, approvals, meetings, or payments. We are not required to begin a dependent stage before the relevant prerequisite is complete.

When a dependency is late, the affected milestone is automatically extended by at least the period of delay. We may revise the broader schedule according to consultant availability and may charge reasonable remobilization or additional project-management fees where the delay causes duplicated effort.

5. Client Project Lead

The Client must appoint a project lead who can coordinate internal participants, provide information, consolidate feedback, approve routine decisions, and escalate matters requiring executive authority. We may rely on the project lead’s instructions unless told in writing that authority has changed.

The Client is responsible for ensuring that the project lead and other participants have sufficient availability and authority. Internal disagreement does not excuse missed deadlines or nonpayment.

6. Accuracy and Completeness of Information

The Client must provide accurate, complete, current, and lawfully obtained information relevant to the engagement. This includes material risks, existing commitments, known constraints, prior analyses, and facts that could affect our recommendations.

We may rely on Client information without independent audit or verification unless verification is part of the scope. If information is inaccurate, incomplete, or materially changes, the Client must notify us promptly. Reanalysis or rework may require additional fees and time.

7. Access and Permissions

Where the project requires access to documents, systems, shared drives, reports, personnel, or third-party platforms, the Client must provide lawful and appropriately limited access. The Client represents that it has authority to grant such access and to instruct us to process the relevant information.

The Client should use secure access methods, avoid sharing unnecessary credentials, and revoke access when it is no longer needed. We may decline access methods that create unreasonable security or compliance risk.

8. Confidential and Sensitive Information

The Client should classify materials where special handling is required and should avoid providing personal, regulated, privileged, or highly sensitive information unless it is necessary for the agreed work. The parties may establish additional safeguards in the Engagement Document.

The Client remains responsible for determining whether disclosure to us is permitted under its contracts, internal policies, and applicable law.

9. Communication Channels

The parties may use email, video conferencing, shared documents, project-management tools, or other agreed channels. Important decisions, approvals, and scope changes should be confirmed in writing.

The Client must monitor the agreed channels and promptly notify us if a communication method is unavailable or compromised. We are not responsible for delays caused by an unmonitored or incorrectly provided contact address.

10. Meetings and Attendance

The Client must ensure that relevant decision-makers and subject-matter participants attend scheduled meetings when their input is required. Meetings may be recorded only with the express consent of all participants and subject to applicable law.

Late cancellations, missed meetings, repeated rescheduling, and attendance without required decision-makers may delay the project and may consume included meeting time or result in additional charges.

11. Decisions and Approvals

The Client must provide decisions and approvals within the period stated in the Engagement Document. If no period is stated, routine approvals and responses should ordinarily be provided within five business days.

We may pause work while awaiting a decision. We are not responsible for consequences of proceeding based on an approval later reversed by the Client, or for declining to proceed where no authorized approval has been received.

12. Draft Review

Drafts are provided for review and may contain placeholders, alternatives, assumptions, or incomplete sections. They should not be treated as final, distributed externally, or implemented without appropriate review.

The Client must review drafts carefully for factual accuracy, operational feasibility, names, figures, assumptions, and alignment with business requirements. Final responsibility for approving Client-specific facts and decisions rests with the Client.

13. Consolidated Feedback

Feedback should be specific, actionable, and consolidated through the designated project lead. Conflicting comments from multiple stakeholders may require clarification and can create out-of-scope revision work.

Feedback must be provided within the agreed review window. If feedback is late, the project may be rescheduled. If no feedback is received after reasonable follow-up, we may treat the relevant draft as accepted for purposes of moving to the next milestone or closing the project.

14. Included Revisions

The number and type of included revisions are stated in the Engagement Document. A revision means a reasonable adjustment to bring a deliverable into alignment with the approved scope and direction.

A revision does not include a new strategy, replacement deliverable, new audience, new business unit, new dataset, reversal of an earlier approval, extensive reformatting, or rework caused by newly disclosed information. Those items may require a change request.

15. Change Requests

A change request may be initiated by either party when the work, assumptions, deliverables, stakeholders, schedule, or technical requirements materially change. We may provide a written summary of the change, additional fee, and revised timetable.

No material change is binding until approved in writing. We may pause the affected work while awaiting approval and payment.

16. Client-Caused Delay

A Client-caused delay includes late payment, missing information, unavailable personnel, delayed access, unresolved internal decisions, missed meetings, late feedback, or changed instructions. During a delay, we may reallocate consultant capacity to other projects.

Restart timing will depend on current availability. If a delay exceeds thirty days, we may close the engagement, invoice accrued amounts, and require a new proposal before resuming.

17. Delivery Format

Deliverables will be provided in the format stated in the Engagement Document, which may include PDF, presentation, spreadsheet, text document, shared workspace, or another digital format. Editable or source files are included only when expressly stated.

The Client is responsible for maintaining compatible software, downloading delivered files, and creating its own backups after delivery.

18. Acceptance and Completion

A deliverable is accepted when the Client confirms acceptance, uses or distributes it, proceeds to a dependent stage, or does not identify a material scope deficiency within the review period. Acceptance does not waive concealed defects that could not reasonably have been identified during review.

An engagement is complete when final deliverables have been issued, included revisions have been addressed, final payment is received, or the engagement is otherwise closed or terminated under the applicable terms.

19. File Availability and Archiving

We may retain project files for a reasonable administrative period but do not guarantee indefinite storage. The Client should download and securely retain final deliverables promptly.

Restoring archived materials, recreating lost files, or supporting later versions may be unavailable or may require a separate fee.

20. Third-Party Dependencies

Delivery may depend on third-party software, data, vendors, or platforms. We are not responsible for their outages, changes, discontinued features, licensing terms, or security practices. The Client must maintain required accounts and permissions.

Where a third-party change materially affects the project, the parties will discuss a reasonable adjustment to scope, timing, or method.

21. Quality Review and Correction

We perform reasonable internal review consistent with the nature and scope of the engagement. The Client must report a suspected material error promptly and provide the relevant evidence.

Where an error is attributable to us and falls within scope, we will have a reasonable opportunity to correct the affected deliverable. Changes based on new information, changed conditions, or Client preference are not errors.

22. Force Majeure

Neither party is liable for delay caused by events beyond reasonable control. The affected party should communicate the impact when reasonably possible, and the parties will attempt to adjust milestones or delivery methods.

If the disruption continues for a period that makes the project impracticable, either party may terminate subject to payment for work performed and unavoidable commitments.

23. Client Implementation Responsibilities

The Client is responsible for evaluating recommendations, obtaining legal or regulated professional advice where needed, planning implementation, assigning accountable personnel, managing change, and monitoring results.

We are not responsible for implementation performed outside the agreed scope or for alterations made after delivery.

24. Project Closure

At closure, we may issue final deliverables, an outstanding-items summary, and a final invoice. Any post-completion support, updates, implementation assistance, or new analysis is outside scope unless included in the Engagement Document or separately agreed.