Handle Revisions and Keep Client Chat in One Place

Revisions are part of the job — but chasing feedback across email, texts, and “wait, which version?” is the part that burns you out. When client chat lives right inside the project, every change request is captured, timestamped, and impossible to lose. Here’s how to run a clean revision loop without leaving Fee-Lion.

Open the conversation where the work lives

Each project has its own Discussions thread, so feedback always sits next to the deliverable it’s about — not buried in an inbox.

1. Go to Projects in the left sidebar and open the project you’re working on.
2. Switch to the Discussions tab to see the running thread for that project.
3. Post your first message — share a draft link, ask a question, or kick off the review with a clear “ready for your eyes” note.
4. Make sure your client can see it: from the project’s people, use Invite to portal so they get magic-link access (no password, no account to create).

From now on, anything the client wants changed goes in this thread. One place, one source of truth.

Turn feedback into trackable revisions

A discussion captures the ask — your sub-statuses and checklists capture the doing. Pairing them keeps a round of revisions from slipping through the cracks.

1. When a client posts changes, move the project to a sub-status like In Revision or Awaiting Approval so its stage is obvious at a glance.
2. Break the feedback into a checklist — one item per change requested. Tick them off as you go.
3. Reply in Discussions when the round is done: “All three updates are in — take a look.” The client sees it instantly in their portal.

Tip: Reply in the thread to confirm what you changed, then add a checklist item for anything still open. The conversation becomes a paper trail — if “we never agreed to that” ever comes up, the timestamped message settles it.

Keep rounds from spiraling

• Summarize each round in one message so the scope of a “revision” is written down, not assumed.
• If a request goes beyond the original estimate, say so in the thread and point back to what was approved — then build a fresh estimate for the extra work.
• Use the project as the boundary: feedback for a different deliverable belongs in its project’s discussion, not this one.

Close the loop and bill the work

When the revisions are signed off, the same project carries you straight to getting paid — no re-keying, no copy-paste.

1. Move the project to a Complete (or “Approved”) sub-status so everyone knows it’s landed.
2. If you tracked hours against the revisions, bill them straight onto an invoice from the project.
3. Post a final note in Discussions with the invoice on its way — warm, clear, and on the record.

Tip: Keep the discussion thread going even after delivery. The next time this client returns, you have the full history of what was built and agreed — the fastest way to pick up where you left off.

What’s next

• Discuss work with your client
• Track goals with checklists
• Create custom sub-statuses
• Bill tracked time to an invoice