Solo workflows break when scaling to 5+ people. What the solo designer kept in their head now needs to be written down. What they remembered between projects is now forgotten the next day, because team members do not share the full picture.
Below is a working approval workflow for an interior design studio. From experience with 200+ studios.
Three maturity levels
Teams move through three levels:
Level 1: "Everyone knows everything" (1 to 3 people) Communication through messengers, files in Google Drive, deadlines in head. Works until you have fewer than 5 concurrent projects.
Level 2: "Everyone owns their part" (4 to 8 people) Role separation appears. Designer, visualizer, manager. But the process is still chaotic: "Hey, what phase is that project in?" "Hmm, let me check." Without a shared dashboard, projects get lost and deadlines slip.
Level 3: "Process over people" (9 to 30 people) Any project can be picked up, status checked, work continued. Replacing a person does not kill the project. This level requires a formalized process and single source of truth, a dashboard reflecting status of all projects.
Most studios stall at level 2. Growth without process is painful.
Base roles
In a studio of up to 15 people, typically 5 roles:
1. Head designer / art director
- Approves concepts
- Controls quality of final mood boards
- Resolves disputes with clients
- Mentors junior designers
In a small studio this is often the founder.
2. Lead designer per project
- One project, one lead
- Makes final decisions within their project
- Delegates tasks to team specialists
- Approves phases with clients or delegates to the manager
3. Visualizer / mood-board specialist
- Creates mood boards and 3D visualizations
- Does not communicate with clients directly (through the lead)
- Has a task queue across multiple projects
4. Layout designer / drafter
- Layout decisions, working drawings
- Specifications, details
- Coordination with engineers (electrical, plumbing)
5. Project manager
- Client communication
- Deadlines and calendar
- Financial side (invoices, payments)
- Contractor coordination during implementation
Project flow by phase
Typical project lifecycle:
[Brief] → [Layout] → [Concept] → [Mood boards] → [Drawings] → [Author supervision]
↓ ↓ ↓ ↓ ↓ ↓
Manager Layout Lead Visualizer Layout Lead
+ Lead designer designer designer designer
At each phase:
- Internal task distribution
- Internal review before sending to client (never send to client what the art director has not reviewed)
- Send to client tied to a version
- Collect feedback
- Decide on iteration or phase closure
Controlling "whose turn"
The studio's main pain: the project is stuck, nobody understands whose turn it is. Designer thinks it is the client. Client is certain it is the designer.
The fix: "ball side" metric per project. It auto-switches:
- Designer sent mood board → ball to client
- Client approved or sent revisions → ball to designer
- Client silent for 7 days → "lost" flag
This metric is the only one that matters for the founder's dashboard. Everything else (revision count, days in work) is secondary. If for a week "ball with client" projects exceed 60%, the studio is stalling due to client communication, not designer capacity.
Approval log
In a studio every project must have a log, a chronological list of key events:
- Brief uploaded (12.03.2026)
- Layout V1 sent to client (14.03.2026)
- Layout V1 approved (16.03.2026)
- Concept V1 sent (21.03.2026)
- Concept V1, revisions requested (22.03.2026)
- Concept V2 sent (25.03.2026)
- Concept V2 approved (26.03.2026)
- ...
This log is the evidence base in any dispute. When the client says 3 months later "we never approved that," you open the log: date, time, user, action. Closes 80% of claims.
More on legal validity of the log: article on electronic approvals.
Internal vs external approvals
Important distinction:
Internal approval: the art director reviews the junior designer's work BEFORE sending to the client. If there are ergonomics or aesthetic errors, the client should not see them. Otherwise the next iteration is your fault, not theirs.
External approval: what is sent to the client after internal review. Only internally approved becomes external.
In studios where this filter works, the number of iterations with the client drops 30 to 40%. A simple art-director eyeball, 15 minutes per mood board, saves 2 to 3 hours of iteration.
Metrics worth tracking
Most studios try to measure everything and drown in data. Useful metrics:
- Average phase approval time: days from send to approval. If rising, brief or communication issue.
- Average iterations per phase: norm is 2 to 3. If 5+, concept or internal review issue.
- Visualizer utilization: hours in work vs calendar hours. Norm 60 to 75%, higher means burnout, lower means slack.
- Days without activity: indicator of "lost" projects.
- Brief to signed contract conversion: manager performance metric.
Everything else is noise.
How Roomix Studio handles this
Roomix Studio (plan for studios from 3 people) covers the basics:
- Single dashboard with all projects, statuses, "whose turn" metric, lost-project flags
- Participant roles (designer / studio lead / decorator) with different permissions
- Approval log with server-side fixation of time and actions
- Internal comments (visible to team, hidden from client) for internal review
- Mood board versioning, history is preserved
- Studio metrics: average times, iterations, utilization
Deployable in a day, no training required, familiar messenger patterns plus proper fixation.
What to do right now
If you are in a studio of 3+ people, minimum plan:
- For 2 weeks, log every "stall," where the project loses, who misunderstood whom
- Compile a top-5 problem list
- Choose a tool that solves at least 3 of them
- Migrate 1 to 2 projects to the new process, not all at once
- After a month, expand or replace
CTA
Roomix Studio has a 14-day trial with full functionality. See the studio plan: 30 USD/month for a team of up to 5, 100 USD/month for up to 30.
See also: 7 mood board approval mistakes, 47-question brief.