Coordination Terms

1. What coordination means

“Coordination” on this platform refers to the structured operational relationship between a business and a professional after a work brief has been awarded. This includes: milestone planning, progress tracking, structured communication, optional payment facilitation, and dispute resolution pathways.

The platform provides infrastructure for this coordination — it does not supervise, guarantee, or take responsibility for the underlying work or its outcomes.

2. Layer 3 — Active Coordination

Layer 3 coordination features include:

• Milestone tracking: Sequence-based phases, each with an agreed scope and optional payment amount.
• Staged payout: Client approves each milestone before funds are released to the provider.
• Audit trail: All milestone approvals, disputes, and releases are logged.
• Coordination hold: Optional escrow — funds held through regulated payment processors until release conditions are met.
• Dispute pathway: Formal process for raising and resolving disagreements within a coordinated engagement.

3. Milestone agreement

Milestones represent agreed deliverable stages — not legal contracts in themselves. Both parties are responsible for defining milestones clearly. The platform records milestone status; it does not adjudicate whether a milestone has been “adequately completed” except in formal dispute pathways.

Releasing a milestone is an irreversible action. Clients should only approve release when satisfied with the deliverable. Once a milestone is released, funds transfer to the provider; disputes after release require a separate refund or chargeback process.

4. Coordination types and oversight

Different coordination types carry different platform oversight levels:

• Task / Remote: Standard flow, bilateral settlement permitted, optional escrow.
• Shift / Contract: Elevated coordination; milestone recommendations shown.
• Construction / Corporate / Managed Project: High-touch; admin review may be triggered; milestone enforcement recommended.
• Ongoing: Recurring coordination; renewal pathways; payroll-style coordination in development.

5. Operational records

Coordination records — messages, milestone logs, audit trails, and payment metadata — are retained per our Privacy Policy and may be used in dispute resolution. Records may be required by law for tax, employment, or regulatory purposes; participants are responsible for their own record-keeping obligations.

6. Recurring coordination (future)

Recurring agreement features — weekly/monthly coordination cadences, attendance logs, renewal workflows — are in development. When live, separate terms may apply for ongoing and employment-style coordination. Beta users will be notified before these features are activated.

7. Facilitator role — not employer or agent

Ecovira Global provides the coordination infrastructure. It is not a party to any work agreement between business and professional. It does not supervise work, guarantee outcomes, or assume liability for the conduct of either party during an engagement.

8. Contact

For coordination-related support: ecoviranalytics35@gmail.com