At 3:15 p.m., an agency strategist has one assistant turn approved campaign research into three creative routes. A second assistant will pressure-test the chosen route and tighten the presentation copy. The first session also mentions another client’s launch, an internal margin concern, and the creative director’s private reaction.
One worker can hand off one client project without carrying the rest of the agency into the package.
Define one client boundary first
Use a separate briefing for each client and matter. Start with the approved client name or project code, then state what the destination assistant may receive. Do not rely on a model to notice that a useful example came from a confidential engagement.
This workflow is for one agency worker using two or more of their own assistants. Their RelayLink account represents that worker. It is not a shared agency login, a client account, or permission to speak as the client.
Split the project into reviewable stages
A practical sequence might be:
- Analysis: organize the approved brief, audience evidence, channel constraints, and source references.
- Creative development: propose routes against the brief without presenting invented audience reactions as research.
- Quality review: test the selected route for claim support, brand fit, accessibility, production constraints, and required approvals.
- Client-ready drafting: shape the rationale and copy without exposing private agency notes.
Each stage should end with a decision record. “The client likes bold ideas” is not enough. Name the source and whether it is an approved brief, a direct client statement, an agency interpretation, or an assumption still needing confirmation.
Build the self-handoff
Include:
- one client, project, deliverable, and audience;
- the approved brief and current objective;
- artifact titles, job numbers, URLs, frames, or versions;
- verified claims and their sources;
- mandatory brand, legal, channel, and accessibility constraints;
- routes considered and why they were closed or advanced;
- internal decisions that may be shared;
- non-goals, unresolved questions, and the next review task.
Strip notes about fees, staffing, performance, personalities, other clients, and negotiation posture unless the task genuinely requires them and the destination provider is approved. Private working notes do not belong in the briefing.
RelayLink carries text, not decks, design files, media, research recordings, or project permissions. The second assistant needs its own authorized access to any source artifact.
Move it across your own assistants
Connect the worker’s assistants to the same RelayLink account and address the package to the worker’s own email on that account. Draft, review, and confirm it. The model never sends autonomously. Approval is the moment to catch cross-client fragments, unsupported claims, internal notes, and language that impersonates the client.
The package creates no contact request, email, magic-link page, or second account. It remains unread until one of the worker’s assistants pulls it; the account portal is the fallback. RelayLink does not synchronize sessions. A self-handoff carries only the selected briefing the worker approved.
Keep real approvals outside the shortcut
A second assistant can find inconsistencies or offer another creative opinion. It cannot supply client approval, legal clearance, rights confirmation, accessibility sign-off, or evidence that a concept will work. Verify source claims and follow the agency’s review path before anything becomes client-facing or public.
If the next decision belongs to a teammate or client stakeholder, this is no longer a self-handoff. An agency PM writing to a client stakeholder is correspondence between people, with approval on each side.
When this workflow is a poor fit
Do not use an assistant that the agency, client contract, data agreement, or rights holder has not approved. RelayLink approval does not override those rules. Sanitizing is useful only when enough authorized context remains to do honest work.
Keep the task in the project or asset system when it depends on live comments, licensed media, visual layouts, audience data, or production files the second assistant cannot inspect. Never combine clients merely to give a model “helpful context.” The boundary is part of the work.