How Podcast Editors Use iPhone Notes to Manage Multiple Shows and Client Preferences

The Podcast Editor's Multi-Client Juggle

A freelance podcast editor might work on six or eight shows simultaneously. Each show has its own editorial style, host preferences, format requirements, technical specifications, and client communication history.

The client for one show wants heavy noise reduction. Another explicitly doesn't — they like the room tone. One host wants all filler words cut; another wants natural pauses preserved. One delivers raw files in WAV; another uploads compressed MP3. One uses a consistent template; another has a new segment every few episodes.

All of that context lives in the podcast editor's head until it doesn't. The moment you misapply one client's preferences to another show, you've eroded trust that takes weeks to rebuild.

What Podcast Editors Track Per Show

Editorial preferences: How aggressive to edit filler words. Whether to preserve natural pauses or tighten. How to handle cross-talk. Where the host's natural energy sits and what editing maintains versus kills it.

Technical specifications: Export format and bitrate, file naming convention, delivery folder structure, platform destination (RSS feed versus direct upload). Getting this wrong creates downstream problems for the client.

Recurring elements: Intro and outro handling, music bed levels, recurring segments and their formats, ad slot timing, chapter marker conventions.

Client communication history: What feedback has been given, what was appreciated, what changes were requested and why, what to avoid. Each feedback thread builds a richer understanding of the client's preferences.

Show format notes: Guest introduction style, any regular features, how live audience shows differ from studio recordings, how to handle remote recordings versus studio.

Production workflow: Which software presets work for this show's audio signature, any processing chains that work well, plugins that help with common problems in this recording environment.

Nemos as Your Client Context Repository

Per-show reference notes: Each show gets a note with all the editorial preferences, technical specs, and client quirks in one place. Before starting an episode, pull up the note — you're editing with full context, not relying on memory.

Feedback integration: After each feedback round, update the show's Nemos note with new preferences surfaced. The note grows more accurate over time. New editors covering for you can access the same context.

Template and workflow capture: Processing chains, EQ approaches, noise reduction settings that work for a particular recording environment. Capture it the first time you figure it out so you're not re-deriving it six months later when the client's microphone sounds different after they moved studios.

Client communication summaries: After client calls or feedback emails, a two-minute Nemos capture of the key decisions. When questions arise about why something was done, you have the record.

What Podcast Editors Capture in Nemos

• Per-show editorial style guides (filler words, pacing, energy)
• Technical export specifications per client
• File naming and delivery conventions
• Feedback history and preference evolution per show
• Processing chains and software settings per show type
• Recurring segment formats and their handling
• Guest introduction conventions
• Ad read formats and timing expectations
• Common audio issues per client's recording setup and how to address them
• Rate structures and invoice preferences per client
• Communication preferences — how clients like to receive deliveries

The iPhone Advantage for Multi-Client Management

Podcast editors often do client management, scheduling, and planning outside the edit suite — on transit, between sessions, at times when the DAW isn't open.

Quick reference to a client's preferences before a call. Capturing feedback on a client call via voice note. Reviewing upcoming deliverable deadlines. All of this happens more naturally on iPhone than at the edit station.

The Nemos note for each show is a reference document that lives on your phone, accessible anytime — including when a client calls with urgent questions about the episode you delivered.

Setting Up Nemos for Podcast Editing

Core tags: - `#[show-name]` — tag per client show - `#editorial` — style preferences - `#technical` — specs and export requirements - `#feedback` — client feedback history - `#workflow` — processing chains and approaches - `#client` — communication and relationship notes

Workflow: Set up per-show notes on client intake. Update after every feedback round. Review before each edit session. Build processing notes as you solve new problems.

FAQ

How do podcast editors use Nemos differently from a client brief document? Nemos captures the evolving relationship, not just the initial brief. The brief tells you how the client described what they wanted. The Nemos note tells you what the client actually prefers based on feedback over months of working together.

Can Nemos help when handing off a show to another editor? Significantly. A well-maintained per-show note gives a covering editor everything they need to maintain the show's editorial standards without extensive client re-briefing.

How do I track audio technical issues that recur with a client's recording setup? Note the issue, the root cause, and your processing approach. "Client records in a reflective home studio — always need heavy room correction. This EQ approach works." When they record in a new location, you know what baseline to compare against.

What's the best way to capture client feedback during a review call? Voice note in Nemos during the call, then convert to text notes immediately after. Voice captures the nuance; text makes it searchable and usable in future.

How do podcast editors use Nemos for their own business development? Rate notes per client type, proposal approaches that won work, client acquisition channels that work, skills to develop for the shows clients keep requesting. Business development notes alongside client service notes.

Can Nemos help manage delivery deadlines across multiple shows? Create a delivery calendar note updated weekly. Each show's episode cycle, delivery expectations, and upcoming deadlines. A weekly review prevents missed deliveries.

How do I manage the transition when a show's format changes significantly? Update the show's Nemos note with the change date and the new format details. Keep the old format notes underneath with a date — useful context if episodes from the old format come up for archival or repackaging.

Related Reading

• /blog/podcaster-notes-iphone — podcast production from the host side
• /blog/audio-engineer-notes-iphone — audio engineering workflow
• /blog/freelancer-notes-iphone — freelance client management
• /blog/video-editor-notes-iphone — video editing workflow

Sources

• Podcast production workflow documentation
• Freelance multi-client management research
• Audio editing best practices for podcast production