Project management for freelance designers: briefs, concepts and revisions that stop looping

A client replies to your second round of a logo: 'Love it — just make the logo bigger and we're done.' The mark is already 4mm tall on the business card, 'we're done' has meant three different things this month, and you have four other projects open in tabs.

Project management for a freelance designer is the small set of records that stops that message from becoming an unpaid afternoon. Four of them: what the brief asked for, which version the client is looking at, which revision round you are in, and which file was actually approved. Get those four right and the software becomes almost interchangeable.

Design work differs from video or generic freelance work in one way that shapes everything below. The deliverable is a static file with pages or artboards, and feedback arrives spatially — move this block, this crop is wrong, this page feels empty — rather than along a timeline. Review has to bind a comment to a page and a version. If it only binds to a project, you will re-litigate the same note twice.

Four records, and what each one has to prove

• Brief record. What was agreed, in writing, with one named approver. Not a call, not a mood board in a chat thread.
• Version record. One file with named versions, so 'the current one' is unambiguous.
• Round record. A numbered change list per round, with a status on each item.
• Approval record. The exact version approved, by whom, on what date.

Boards, columns and automations are just a way of making those four visible at a glance. If you are still choosing the tool, the questions that matter for layout work are covered in design agency management software — this article assumes you already have somewhere to put the work.

A worked example: one 12-page brochure

Assume a solo designer with four to six active clients and projects running one to three weeks. The unit of work is one card per deliverable, not one card per client.

Concretely, the brief card for a product brochure holds: approver 'Dana, marketing lead'; format 'A4 portrait, 12 pages, 3mm bleed, print PDF plus screen PDF'; mandatory content 'product photography from the 24 October shoot, legal line on page 11, pricing table supplied by client'; hierarchy 'product name, then key benefit, then price'; two references and one anti-reference; and 'two revision rounds included'.

That is not bureaucracy. Every one of those fields is a question you would otherwise answer by guessing and then rebuild for free.

Brief intake: the fields that prevent the 'make it bigger' cycle

'Make the logo bigger' is rarely a client being difficult. It usually means the brief never defined hierarchy, so the client is reacting to the only thing they can articulate. Fix it at intake and the note mostly stops appearing.

The fields worth having on every design brief:

• Final use and format. Print size and bleed, screen sizes, file types delivered. A logo at 4mm behaves differently from the same logo on a 1920px hero.
• Mandatory content. Copy, legal lines, logos, data — and who supplies each, with a date.
• Hierarchy. What a viewer must read first, second, third. This is the field that kills most size arguments.
• Constraints. Brand rules, colour limits, minimum type sizes, character counts, print tolerances.
• References and one anti-reference, each with a note on why.
• Concept count and revision rounds included, written as a number.
• One approver. One name, and confirmation they can make review rounds.
• What 'approved' means and what happens after it.

Design brief intake checklist

Complete this before starting any design project so scope, hierarchy and approval are fixed before the first concept.

Run that list before you open a design file. If the client cannot answer the hierarchy question, that is the conversation to have now, not in round two.

Concept stage: how many directions, and what you ask for

Two directions is the honest default when the brief is tight. Three is defensible when the client genuinely does not know what they want and has told you so. More than three shifts the work from designing to decorating, and it invites the worst outcome: a request to combine elements of A, B and C.

Each direction should be a distinct idea, not the same layout in a second colourway, and each should carry one short paragraph explaining what it is doing and why. Then ask one question per direction — keep, kill, or change — instead of 'thoughts?'. Open-ended prompts produce paragraphs of prose, and prose is where revision rounds go to die.

Decide in advance how you treat 'combine A and B'. Two workable options: it starts a new round, or it becomes a change order. What you should not do is absorb it silently, because it resets the concept stage while the round counter says you are nearly finished.

Revision rounds: one current version, comments bound to pages

Version naming does more work than any tool feature. A convention that survives a real project: Northline_brochure_v01_2026-10-06.pdf. Two digits so files sort correctly, date so you can find the one the client actually saw, and a new version uploaded to the same file so the earlier ones stay intact and a reviewer can switch between them.

The highest-leverage habit in this whole workflow: when feedback arrives as prose, convert it into a numbered list and send the list back for confirmation before you start. Nine items in a numbered list produce nine answers. Nine items buried in three paragraphs produce a fourth round. The wider mechanics of binding a decision to a specific file version are in creative approval workflow with file version history.

For the review itself, attach the PDF to the card and open it in Review rather than emailing a fresh copy. Comments stay on the file, @mentions work, and because the file keeps its version history, nobody has to ask which round a note refers to. If your team also reviews layout alongside video or campaign assets, the tradeoffs are set out in this InDesign review workflow comparison.

An illustrative round, using your own numbers: you quoted two rounds and estimated six hours of layout changes in total. R1 comes back with nine items. Six are accepted, two need a clarifying question, one is a new page that was never in the brief. If R1 alone takes five hours, you already know the quote is short — and you know it in week one, while there is still room to renegotiate, rather than at delivery.

Approval: what sign-off means, and locking the file

Approval is a sentence with three parts: the version, the person, the date, in writing. 'Approved as is' is approval. 'Looks great, let's go' followed by three more notes is not; those notes are round N+1, and if you included two rounds, they are a change order.

After sign-off, lock the reference: the approved version stays as-is, finals are exported from it, and the card moves to Delivered. Keep the change-order decision outside the design file so a late tweak does not quietly reopen a closed round.

Client access matters here. On a workspace where card visibility is enforced per person, a guest without the view-all permission sees only the cards they are assigned to. That means a client guest can be given the single review card for their project without seeing any of your other clients' work — a much smaller exposure than sharing a whole board. The tradeoff is that unassigned cards are invisible to them, so the assignment is the access control.

Running several clients without cross-contamination

Two structures work, and the choice depends on one question: will the client ever log in?

• One board per client. Files, permissions and guest access stay separated. Sharing is safe because a board can be restricted to a member list. The cost is that you need a second view to see everything across clients.
• One board with a client field. Single view across all work, easier weekly review. The cost is that sharing it with anyone exposes every client on it, so it stays internal.

If a client logs in at all, isolate by board. A single mis-shared link costs more than the extra view ever saves. For the cross-client isolation mechanics in more detail, see freelancer project management across multiple clients.

Then run one weekly sweep, about ten minutes: for each active card, confirm whose court it is in and set a next-action date. Anything sitting in the client's court past three business days gets a chase. Anything in your court with no date gets one now.

Finally, track time by stage rather than by project — brief, concept, revisions, finals. If revisions are consistently eating the hours you allocated to concepts, you have a brief problem, not a design problem, and you can fix the intake form instead of working later. The setup for tagging time across clients is in tracking time for multiple clients.

What to do with your next live project

Do not rebuild your whole system this week. Take the project that is currently open, create one card for its deliverable, and fill in the brief fields above — especially hierarchy and the approver's name. Rename the current file to the version convention. Take the client's last feedback email and convert it into a numbered list, then send it back for confirmation before you touch the layout.

Where this breaks: clients who will not write feedback down, or a project where the approver is not the person with real authority. Both are survivable, but they need the round counter and the change-order rule agreed early, in writing, while the relationship is still easy. Discovered in round four, neither is a project management problem any more — it is a renegotiation.