Skip to content
cotechra

Governance

Trust and safety

We are building the rails, not leaving collaboration to informal chat threads.

How we run trust in the pilot

Trust is operational, not decorative. That means written defaults, human review while cohorts are small, and enforcement tools spelled out before money moves.

We bias toward transparency between Partner and Talent: who owns client communication, how milestones are accepted, and what happens when facts on the ground change.

Trust and safety

The three pillars every pilot participant agrees to before money moves.

Verification and onboarding

Pilot participants complete identity and capability checks. We reject noisy or high-risk profiles.

Dispute path

If milestones slip or expectations diverge, you escalate through a documented review—not a guessing game.

Code of conduct

Harassment, misrepresentation, and fraud are zero-tolerance. Enforcement includes removal and fund holds where applicable.

Operational safeguards

Pilot discipline

Small cohorts let humans review edge cases. Automation increases only after playbooks exist.

Evidence-based disputes

Tickets require artifacts: messages, deliverables, milestone definitions. Rulings reference those artifacts.

Removal and fund holds

Fraud, harassment, or material misrepresentation can trigger removal and holds pending review—terms spell this out plainly.

Escalation ladder (pilot)

  1. 1. Partner–Talent resolution (48 hours)

    Raise the issue in the agreed channel with a concise summary, desired outcome, and links to artifacts (SOW, messages, deliverables).

  2. 2. cotechra ticket with evidence (5 business days)

    If step 1 fails, either party opens a pilot ticket. A reviewer acknowledges receipt within one business day and requests missing evidence.

  3. 3. Written determination

    We issue a decision referencing the contract clauses and evidence submitted. Fund movement follows the determination unless an appeal window applies.

  4. 4. Appeal (where contracted)

    Some templates include a narrow appeal for factual errors or procedural defects—not relitigation of taste. Appeals are resolved within 10 business days.

Review principles

  • Evidence over rhetoric: screenshots, commits, design files, and timestamps beat long narratives.
  • Contracts over chat: if chat disagrees with the signed SOW, the SOW wins unless a written change order exists.
  • Minimize collateral damage: we prefer partial releases and scoped pauses over scorched-earth account closures when safety allows.

Data, confidentiality, and access

Client data stays on need-to-know. Talent receives the minimum access required for the milestone—repos, Figma files, analytics views—not blanket account passwords unless a specific engagement requires it and contracts allow it.

We recommend rotating credentials after engagements end when access was broad. Your onboarding packet includes a default offboarding checklist.

Enforcement toolkit

Warnings and remediation plans

First incidents with ambiguity get a written remediation plan with dates and owners.

Suspension

Active engagements pause when fraud is suspected or when safety risk is elevated—funds may be held per contract.

Removal

Zero tolerance outcomes apply for harassment, hate, illegal activity, or deliberate misrepresentation.

Network bans

Severe violations can exclude you from future matching across the program, not just one Partner–Talent pair.

What we publish and update

  • Economics and fee structure for the pilot.
  • Country availability for Partners and curated global intake for Talent.
  • Material changes to dispute SLAs with 14 days’ notice unless a safety issue requires immediate action.

Questions before you apply? Read the FAQ or start an application—we reply to complete forms first.

TermsPrivacy