docs / deliver-work-and-get-it-approved
Deliver work and get it approved
Fiilz takes the approval out of somebody's chat. Every piece carries its versions, one named person is responsible for signing off, and the client answers on a screen of their own — reached by a link, with no account of yours.
before you start
What this guide covers.
// Fiilz is where the work you owe someone lives, together with its decision.
This guide covers organising deliverable work, putting it in front of a client, and closing the loop on 'is this approved'. The problem it solves is not storage — it is that the decision usually lives in a chat and the file lives somewhere else.
step one
Organise the work the way you deliver it.
// Projects with their own sections — not the shape a folder tree forces on you.
A project has its own sections, defined by how you actually deliver rather than by a folder hierarchy. The point is that someone opening it should recognise their own process, not learn yours.
step two
Stack the versions on the piece.
// A file you upload, or a Figma link. Versions stack on the piece itself.
Each piece carries its versions in order. This is the mechanism that ends the 'final_v3_REAL' problem: there is no need to encode the version in a filename, because the piece knows its own history and the latest one is not in question.
step three
Name who signs off.
// One assigned approver per piece.
Every piece has an assigned approver, so 'who signs off on this' stops being a question anyone has to ask. An unnamed approver is how work sits for a week with everyone assuming somebody else is looking at it.
step four
Let the client decide on their own screen.
// Reached by a link — no account of yours to create.
The client opens a link and approves or asks for changes on a screen of their own. Feedback lands as threads anchored to the piece, and threads get resolved — unlike messages, which scroll away and take the context with them.
The client portal exists as a frame — its sections are still being filled in. The decision itself already happens on the review screen.
What this guide doesn’t cover
Running in production: projects, sections, pieces with their versions, assigned approvers, the client's review screen and feedback threads. What is not built yet:
- The client portal exists as a frame — its sections are still being filled in.
- A closed milestone reports that there is something to bill; issuing that invoice is a step you take.
Last updated: 2026-09-02.