Before you start
- A managed client, a recorded request and workspace write access.
Choose the request
Open Work, then Client assistant, and choose a request, or choose Prepare a draft with the assistant on its record. Use Add a client request when the message has not been recorded yet. The page shows the job’s title once, with Original request closed underneath; open it to read the recorded wording and, when it differs, the current scope.
Prepare the draft
Under What do you need prepared?, say what needs preparing. Under More options, optionally select a Working method and up to three captured sources, then choose Prepare draft. The assistant uses that client’s request, workflow context and selected sources. Safe workflow structures omit parameters and routing values; missing details should become questions.
Work through the questions
Before you use this draft lists the questions to answer and the assumptions the draft makes. To answer or correct them, select Ask for changes, say what should change, and choose Prepare revised draft. Under its More options, leave Revise this version selected to carry forward its earlier sources. Each version remains under Versions. Each section’s Sources shows what its statements were drawn from; a source reference supports inspection, it does not prove the draft interpreted the source correctly.
Save the reviewed preparation
Edit Scope for the client, select Review checks, then edit Checks to carry into Verify. Switching between Scope and Checks keeps your edits and saves nothing. On the Checks step, choose Save reviewed scope and checks. This updates Current scope and saves proposed checks. Original request as recorded stays read-only; scope revisions remain in the timeline. The client has not approved anything and no checks have passed.
Hand it to your team
Under Hand it to your team, choose Download Excel. The file holds the request title, the saved scope and the proposed checks, with empty Checked by, Date and Notes columns for your team to fill in. It needs no Google account and changes nothing in AgentHub. Filling it in does not verify anything: a check counts only when someone records it on the request.
Continue the client work
Open the request record for the client decision. Use the approval link when needed. It freezes the scope for the decision and includes the original recorded request for reference; read both before sharing it. New briefs keep these separate too, and you review which completed changes are included before publishing. Existing approval receipts and published brief snapshots keep their saved content. During Verify, the reviewed checks join the suggested plan when the scope still matches. A human verification plan takes precedence. Record what actually happened before preparing the client brief.
Verify it worked
- Reopen a preparation version from Versions and inspect its instruction under Draft details and its Sources. Use Older versions to page through history. Confirm under Original request that the original wording and a changed current scope are shown separately, and that the timeline retains scope revisions. Older records may show Earlier saved wording when the original could not be established. The workspace owner’s JSON export includes preparations, captured sources and reviewed edits; it excludes connection account records and other operators’ private action receipts.
- Check that the request status has not changed to approved or verified merely because you saved a draft.
Common issues
The request changed after the draft.
Prepare a fresh version. AgentHub will not overwrite a newer request with a stale draft. Scope already sent for approval remains protected.
A draft is pending or failed.
Refresh and check its history. Calls are not repeated automatically. After three minutes, a stalled preparation no longer blocks a fresh attempt. Failed attempts count toward the daily limit and may still incur provider usage.
The assistant is read-only.
Check workspace write access, the managed-client selection and assistant settings. Closed requests remain available to review.
Preparing was refused with an AI limit message.
Before any AI step is sent, AgentHub sets aside the most it could cost. It refuses the step when the workspace has reached its AI limit for the last 24 hours or 31 days, a trial has used its AI allowance, or AI features are paused. The message says what stopped the step and, where it can, when room frees up. Nothing is charged automatically, and your records are not affected. A very large request can need several AI actions of room to start, even though it usually uses one.
The request has too much context.
Start a fresh draft with fewer sources, or shorter ones. Text in some alphabets takes more room, so fewer characters fit.
Download Excel is missing.
The request’s scope changed after this version was saved, so the file would be out of date. Prepare and save the scope again; Download Excel then comes back. You can download it in a read-only workspace too.