openmasu
solutions · design & creative
Take creative work from request to approved, with feedback in one place.
Collect briefs with a public request form, move every piece through review stages on a kanban board, and keep feedback on the record with @mentions. Link to your design files with URL fields, so the latest version is always one click away.
- Request form that creates a brief record
- Kanban board of review stages
- Feedback in comments with @mentions
| Deliverable | Request | Designer | File link | Due | Stage |
|---|---|---|---|---|---|
| Homepage hero banner | Autumn campaign | Sofia | design.example.com/f/hero-v3 | Oct 22 | Internal review |
| Event poster A2 | Open house | Marco | design.example.com/f/poster-v2 | Oct 24 | Client review |
| Social carousel, 5 slides | Autumn campaign | Sofia Ana | design.example.com/f/carousel | Oct 27 | In design |
| Product one-pager | Sales kit | Ana | design.example.com/f/onepager-v4 | Oct 20 | Changes requested |
| Email header | Newsletter Nov | Marco | design.example.com/f/email-final | Oct 18 | Approved |
Everyday workflows
Briefs that arrive complete
Share a form view of «Requests» with the fields you always end up asking for: format, sizes, channel, deadline, a link to reference material and a long text brief. Anyone in the company can fill it in from the public link, and each brief arrives as a new record in the studio's queue, live.
Review stages on one board
Each deliverable has a «Stage» single select: Brief, In design, Internal review, Client review, Changes requested, Approved. The kanban view turns those into columns. Designers drag a card to Internal review when a version is ready; the reviewer drags it back to Changes requested or forward to Approved.
Feedback that stays with the work
Reviewers leave notes in the record comments and @mention the designer, who gets a notification. The thread stays on the deliverable, next to its file link, instead of scattered across chats. The field-by-field history shows when the stage changed and who moved it, so approvals are easy to trace.
Files linked, versions tracked
OpenMasu doesn't store files, so keep them where they live and paste the link into a «File link» URL field. Add a «Version» number and a formula like CONCATENATE({Deliverable}, " v", {Version}) for a clean name. When a new version is uploaded, update the link; the history keeps the earlier ones.
A delivery calendar for the studio
A calendar view by «Due» shows what ships each day and week. Drag a deliverable to another day when a deadline moves, and the requester sees it instantly. A grid view filtered to «Stage is not Approved and Due is before today» lists everything that's late.
Views & structure
Key views
- Form A public request link so every brief arrives with the same details.
- Kanban Move deliverables through design and review stages by dragging cards.
- Calendar See delivery dates by week and drag them when deadlines change.
- Gallery Browse deliverables as large cards with brief, stage and file link.
- Grid Filter late work and group by designer to balance the load.
Recommended fields
- Stage (Single select) Colored review stages that become the kanban columns.
- File link (URL) Points to the design file wherever it's stored.
- Request (Link to another record) Ties each deliverable back to its original brief.
- Brief (Long text) The full ask: goal, audience, copy and must-haves.
- Format (Multiple select) Sizes and channels needed, like A2, Story or Web banner.
- Due (Date) Drives the calendar and the late-work filter.
Your agent over MCP
Connect your own agent (Claude, ChatGPT, Codex or Cursor) over MCP. It can set up the studio base, turn a long brief into separate deliverables linked to the request, and tell you what's stuck in review. Its changes show up live and are marked in history.
create_table create_view create_records link_records query_records
Give your studio one place for every brief
Share a request form, open the review board and keep feedback where the work is.