# How to Brief an Assistant Before a Client Meeting Brief an assistant for client meetings with current scope, confidential boundaries, explicit objectives, and approval-aware follow-up. By Righthand Team · 2026-10-06 Source: https://www.righthand.ai/blog/how-to-brief-an-assistant-before-a-client-meeting A client-meeting brief gives an assistant enough context to support the conversation without guessing what you promised. The best brief identifies the relationship, the purpose of this meeting, the latest facts, and which decisions remain yours. It should also say what the assistant must keep internal. ## Quick answer Brief the assistant with current scope, the client's stated objective, unresolved issues, approved materials, and authority limits. Ask it to prepare or attend only within the capabilities configured for your account. Avoid treating a calendar invitation as a complete delegation instruction. For preparation and follow-through, Righthand's [executive assistant role](/roles/executive-assistant) is a relevant starting point. Connected-account access and any meeting participation still require a supported setup and the right permissions. ## Explain why the client is meeting “Join the weekly client call” leaves too much unstated. Is the client reviewing work, approving a direction, discussing a delay, or considering more scope? Each purpose changes what the assistant should watch for and what information it needs. Describe success in observable terms: capture consolidated feedback, confirm the next review date, or identify the person who can approve the draft. Do not equate a pleasant conversation with an accepted deliverable. Include the client's preferred terms and the current version of the work. If the meeting concerns draft three, do not supply an unmarked folder containing drafts one through five and expect the assistant to identify the intended version. ## Give the factual and confidential context separately The factual packet may contain the scope, schedule, recent notes, and open questions. The internal packet might explain your negotiation limits or a staffing constraint. Label internal material clearly and state whether any part can be discussed with the client. A useful boundary is explicit: “Do not mention our internal resourcing options; ask the client whether Tuesday or Thursday is the required review date.” That turns confidential context into a permitted question without exposing the internal issue. If the source materials conflict, resolve the conflict or instruct the assistant to flag it. It should not decide which contract interpretation to present as settled. ## An illustrative agency briefing A branding agency is reviewing two visual directions. The client has not selected either one and has asked whether both can be developed further. The assistant's brief says the existing scope covers one selected direction; additional development needs the agency lead's approval. During preparation, the assistant assembles the two current files and the feedback questions. If permitted to participate, it can ask which direction best fits the client's launch objective. It should not promise two finished systems or quote an extra fee. Afterward, its summary distinguishes “client prefers direction B” from “client formally approved direction B.” If approval was ambiguous, it drafts a confirmation request for the account lead to review. ## A client-meeting brief template > Support the visual-direction review with Cedar Studio on Wednesday. Purpose: collect consolidated feedback and identify the direction the client wants to pursue. Use the linked scope and the two approved presentation files. The client has not approved either direction. You may prepare questions and summarize the discussion. Any attendance depends on our supported meeting setup and the host's rules. Do not promise extra deliverables, discounts, or revised deadlines. Keep internal staffing notes private. Afterward, list explicit decisions, open questions, requested changes, and proposed next steps for my review. Add the exact meeting link, time zone, and responsible client contact when attendance is part of the task. A wrong link is an operational failure that better writing cannot fix. ## Review and refresh before the meeting Ask the assistant to restate the current objective and boundaries. Check the factual claims that could embarrass the team: version names, approval status, deadlines, and commercial terms. Confirm that sources are available through the connected accounts. Keep the final brief concise, with links for detail. If an important correction arrives, update the brief directly rather than burying it in a long unrelated conversation. ## FAQ ### Does the assistant need all historical correspondence? Usually it needs the current agreement and relevant recent context first. Add older material when it explains a live dispute or decision. ### Can it speak for us in the meeting? Only within supported participation capabilities and explicit authority. Preparing questions does not authorize making commercial commitments. ### What if the client changes the scope verbally? Capture the request accurately and route it for review. A request is not an approved change simply because it was discussed. ## Related resources See [task delegation](/features/task-delegation) and [follow-up management](/use-cases/follow-up-management) to preserve the meeting's boundaries afterward.