Milestone and scope protection
Prevent scope creep with evidence-backed agency milestones
Define what done means before delivery, attach evidence to each condition and let the Pact follow the agreed milestone rules.
No outcome, no fee. The stated Covalt Work platform fee is 3.5% when the agreed outcome lands. Covalt is non-custodial; configured payment rails process authorisation, capture and payout.
The difference
From payment friction to agreed conditions.
The old way
- Scope changes live in chat threads and ambiguous PDF SOWs.
- Approval depends on memory, subjective interpretation or whoever follows up most.
- Payment deadlines can drift because the trigger for completion was never explicit.
The Covalt Work way
- Record each milestone's completion conditions before work starts.
- Agree the evidence expected, such as a GitHub pull request, Figma link or staging URL.
- Keep verification and release rules tied to the Pact rather than changing the definition after delivery.
Explore the flow
Build an evidence checklist for your milestone
Select examples you intend to include in the Pact. This checklist is a planning aid; selecting an item does not itself verify the evidence or guarantee acceptance.
Example evidence to agree
1 evidence example selected. Record the required source and acceptance conditions in your Pact.
Questions, answered
Before you start a Work Pact
Can a client change the definition of done halfway through?
The purpose of the Pact is to record the agreed conditions up front. Any change should be handled through the applicable Pact amendment or change process, not treated as a unilateral rewrite.
Does a GitHub PR or Figma link automatically prove completion?
No. These are evidence examples to reference in the agreed conditions. Whether evidence can be checked automatically depends on the configured source and verification path; a link alone is not proof that every condition has been met.
Does Covalt Work hold client funds?
No. Covalt is non-custodial: it records the Pact, agreed conditions and outcome. Authorisation, capture and payout are handled by the configured regulated payment rails; availability and timing depend on the transaction and corridor.
What happens if a milestone is disputed?
The Pact keeps the agreed conditions and submitted evidence together so the parties can review the same record. Sonar and Guard Dog can provide matching and risk signals where configured; they are not a court, arbitrator or substitute for an agreed dispute process. A disputed outcome should follow the terms agreed by the parties and any applicable rail procedures.
Which payment rails can I use?
Available rails and settlement corridors depend on the parties, currency, transaction and current provider support. The available option is confirmed during setup; do not assume every rail or country is supported for every Pact.
Put the conditions in writing before work begins.
Use the existing wizard to define the parties, project value, milestones, completion conditions and evidence.
Start a Work Pact