Every brief and approval in one place. Emily is almost offended this wasn’t already true.

The operational problem

The brief lives in a deck. The change to the brief lives in a call nobody minuted. The approval lives in a WhatsApp thread. The extra round of work lives nowhere — which is why nobody charged for it. The studio does the work well and still loses money on it, because the record of what was agreed is scattered across five tools and three memories.

What Emily watches

• Briefs, revisions and the differences between them
• Approvals given in messages, email or meetings
• Scope changes that have not been reflected in the fee
• Deliverables promised against dates in the calendar
• Blockers sitting unresolved for longer than the team expects
• Decisions made verbally that never landed anywhere written

What Emily produces

• A single working record per project: promised, changed, approved, outstanding
• Alerts when work drifts outside the agreed scope
• A weekly studio status that nobody had to compile
• Drafted change-of-scope notes for the account lead to review and send
• An answer to "who approved this, and when" in seconds

The working view

What remains human

• The team decides what counts as an approval — the system records it
• Scope conversations with the client stay with the account lead
• Nothing is shared outside the studio without a person sending it

Indicative implementation

A configuration like this begins with an audit of how the work actually moves, followed by a focused build against the systems involved, then ongoing care as tools and people change. Scope and timeline depend on the systems, access and approval rules of the business.

How the three stages work →