Cross-border work, structured as a transaction
Distance does not break international work. Undefined completion does. This is how to define it, order it and settle it.
Most cross-border work fails in the same place: nobody wrote down what finished looks like. The scope lived in a call, the deadline lived in a thread, and the payment decision arrived with no shared record to point at. Currency, timezone and jurisdiction differences then amplify a problem that was never really about geography.
Covalt Work treats an international engagement as an ordered series of transactions rather than one long act of faith. Each milestone carries its own written conditions, its own evidence, and its own verification outcome. Payment follows the verified outcome — not a mood, a follow-up email or a favour.
Why cross-border engagements go wrong
The failure modes repeat across industries and contract sizes. They are structural, which is why better intentions rarely fix them.
- Completion was never defined
- "Finish the platform" cannot be verified by anyone. "The agreed pull request is merged to main and the staging deployment passes the agreed checks" can.
- Payment triggers are implicit
- The provider does not know what releases money, so they chase. The business does not know what it has received, so it delays.
- Evidence is scattered
- Approvals in chat, files in inboxes, decisions in memory. When a milestone is disputed there is nothing structured to examine.
- Order is unenforced
- Later work starts before earlier work is accepted, so exposure compounds instead of resetting at each milestone.
The structure that replaces trust
An engagement is split into milestones. Each milestone becomes one transaction with its conditions attached. There is no partial release inside a milestone — a milestone either satisfies its conditions or it does not, which keeps every conversation about the same question.
Milestones are ordered, and the order is enforced by the infrastructure rather than by goodwill. A later milestone cannot settle ahead of the one before it, so the amount at stake at any moment is one milestone, not the whole contract.
Evidence and verification are different things
Evidence is what was found: a merged pull request, an issue moved to done, a file attached with a written note. Verification is the conclusion about whether that evidence satisfies a specific written condition.
Covalt Work shows those separately, on purpose. You see the raw evidence exactly as it was retrieved, and next to it the verification outcome for each condition. Nothing is presented as a source "confirming the work was completed" — the sources supply facts, and the transaction's verification decides what those facts mean.
Where the money moves
Covalt is coordination infrastructure and non-custodial: it never holds funds. Authorisation, capture and payout happen on regulated payment rails. What Covalt owns is the record — the conditions agreed, the evidence submitted, the verification outcome and the settlement result.
That division matters for cross-border work specifically, because the parties are often under different regimes. The commercial agreement can be identical and legible on both sides even when the payout path is not.
Common questions
Is this an escrow service?
No. Covalt does not hold or move money at any point. It records the conditions attached to a transaction and the verified outcome, while regulated payment rails handle authorisation, capture and payout.
How many milestones should an engagement have?
Enough that each one can be described in a sentence a stranger could check. Milestones that need a paragraph of caveats are usually two milestones, and milestones worth a large share of the total usually need splitting.
What happens if evidence is inconclusive?
The condition stays unsatisfied and the milestone does not settle. The provider can add further evidence against that specific condition. Covalt Work never estimates or implies an outcome that verification has not returned.
Does this replace a contract?
No. It makes the operative part of a contract executable: what completion means, in what order, evidenced how. Keep your legal agreement and let the transaction carry the conditions.
Structure your next international engagement
Define the milestones and the conditions that mark each one complete, then invite your counterparty to review the same wording you wrote.
Related reading
- International contractor paymentsThe hard part of paying a contractor overseas is not the transfer. It is deciding, defensibly, that the work is done.
- Milestone paymentsSplitting a payment into stages only helps if each stage has a completion test someone else could apply.
- Verified work paymentsFour distinct steps that most platforms collapse into one vague status — which is exactly where disputes come from.
- Software development pactsEngineering is the rare kind of work that already emits verifiable evidence. Conditions should be written to use it.