Files & feedback

Feedback stays next to the file

Request files from the client, share your delivery, and keep comments, approvals and revision requests in one flow where it’s clear which delivery they belong to.

(co)wwwork

The problem

There are many messages; there is one context

WhatsApp screenshots and separate email threads blur which comment belongs to which design, which version and which delivery decision.

  1. (01)Feedback lives in a message apart from the file.
  2. (02)The final file and the previous version get mixed up.
  3. (03)The same revision comes again from a different channel.
  4. (04)Approval and change requests never become a clear state.

The Cowwwork approach

Not a message — context

File request, client upload, agency delivery, comments and the approval decision move around the same record. When the client opens a delivery, its state moves to “under review”; approval or a structured revision request stays under that delivery.

How it works

From file request to delivery decision

  1. (01)

    Request the file

    Create a file request that sets the accepted file type, size and count limits, and a due date.

  2. (02)

    Receive the upload

    The client uploads files straight from the portal to secure storage; when ready they hit “submit”.

  3. (03)

    Share the delivery

    Send the design to review with a delivery type — download-only, review, or approval required.

  4. (04)

    Record the decision

    The client approves the delivery or requests a revision with a title and description; comments stay next to the delivery.

Key benefits

Every comment has its file, every file its version

(01)

Context-bound comments

Feedback stays under the delivery being reviewed, not in a general inbox.

(02)

Version history

New uploads are kept in version history without deleting the previous delivery record.

(03)

Clear outcome

Approved deliveries are cleanly separated from work awaiting revision; the delivery moves to review on first open.

Features that work together

The rest of the client workflow

Agency panel

Client portal

Client briefs

Proposals

Contracts

FAQ

Yes. The authorized client uploads files straight from the portal to secure storage against a file request the agency creates, then submits.

Yes. The accepted file type, maximum size, maximum number of files and due date are set per request.

Yes. The client can approve a delivery or open a structured revision request with a title and description.

Yes. When a new version is added, the previous file and delivery history are preserved.

No. Comments stay in the context of the relevant delivery or file request; there’s no general chat stream.

(co)wwwork

Keep the next feedback round in context

Share the delivery, gather comments next to the file and record the client’s decision.

Start for free