Delivering work
From the client's choice to the last milestone: the plan, the delivery board, submitting work, and the messages in between.
The client chose you. From here the engagement runs on a milestone plan, a delivery board you own, and a submission step per milestone that releases your money. This page is the whole loop.
Where it lives
A won brief appears under Projects in your portal, with its plan, its delivery board, the message thread with the client and the milestone ladder. Briefs keeps showing the offer it came from.
The plan
The client writes and confirms the milestone plan: up to seven milestones, each with a title, a description, the deliverables, the acceptance criteria and an optional target date, and a share of the escrow. You read it throughout, and reading it before you start is the single most useful thing you can do: the acceptance criteria are what the client will judge against.
Once the plan is confirmed, the client cannot change what matters alone. A change to the deliverables, the acceptance criteria, a date or a share arrives to you as a change request, and you approve or decline it. Approving applies it. The client can still fix titles, descriptions and the order without asking. If a client wants something that is not in the plan, the right answer is a change request, not a wider reading of a milestone.
The delivery board
Each milestone is a card in one of four states, and only your agency moves them:
| State | Meaning |
|---|---|
| To do | Not started. |
| In progress | Being worked on. |
| Client review | Submitted as complete, waiting for the client. |
| Done | Accepted by the client. A released milestone always shows as done. |
The client sees the same board, read-only, and can comment on cards. Keep it honest and current; it is what the client looks at instead of asking.
Two things sit behind the board for your own use. You can assign team members to work items with allocated hours, and you can log work against a milestone: hours, and labour, tool and vendor costs. Logs are visible to your agency and to Matchii, never to the client, and they do not change the price. Matchii keeps them as ground truth for pricing future work more accurately.
Submitting a milestone
When a milestone is finished, submit it for review with a message saying what was delivered, optional notes on the acceptance criteria, and attachments as evidence. The card moves to Client review. One submission per milestone is open at a time; you can withdraw it before the client answers, for instance to attach something you missed.
The client answers in one of two ways:
- Accepted. That milestone’s tranche is released to you in the same step. Nothing else is needed from either side.
- Changes requested, with a comment saying what is missing. No money moves. Revise and submit again; there is no limit on rounds.
You are told live in the portal when a decision lands. There is no email for it, so keep the portal open while a milestone is in review.
Talking to the client
- The brief thread is the one text channel that exists for every matched brief, on the project page and in your inbox. It is the record of the engagement; put anything about scope there.
- Rooms are the working channel. You open a room, seat the people on your side, share files, and optionally share the room with the client. Rooms you keep internal are never visible to the client, and neither is your agency’s internal thread.
Cancellation
Either side can ask to cancel. Matchii resolves it: the engagement resumes, is cancelled, or goes to arbitration when the two sides disagree about what was delivered. On cancellation, tranches already released stay yours; the unreleased remainder returns to the client. Work you have done but not had accepted is the exposure, which is one more reason to submit milestones as they finish rather than in a batch.