Before you start
- One real client request that you can safely record.
- The name and platform of the workflow the request affects.
- The name of the client decision owner for the workflow.
- The client's authorization, or a channel where you can share a secure approval link.
- Evidence you can use to verify the requested outcome.
Bring one real change
Open Create → Client change and start with the client's request. Select the client and workflow if they already exist, or add either one from the same form.
One confirmed action creates only the missing client, workflow, and owners, then files the formal request to you. Existing records and owners stay in place.
Use a real client. Sample clients do not count toward setup progress or proof totals.
Review the created record
AgentHub opens the new change record in Requested state. It derives a short title from the first meaningful line of the request and leaves the original request intact.
If the wording is wrong or incomplete, choose Edit request before creating an approval link. AgentHub keeps the prior wording in the audit trail.
Open the client or workflow later to add contact email, purpose, business impact, source URL, repository, deployment, or different owners. Those details do not block the first request.
Record authorization and the work
On the change record, choose Start work if the request is already authorized. If client approval is still needed, choose Create client approval link, copy the link, and share it through the client channel you already use.
The client can approve the frozen scope or request changes without an AgentHub account. Approval stops at Approved; you still choose when to start work. A change request returns the record to editable review.
When implementation is finished, add the useful implementation details. Under Implementation evidence, use Add evidence to attach a pull request, commit, test, or deployment link. Evidence stays private unless you explicitly mark it for new client briefs.
Choose Ready to verify when the work is ready for testing.
Verify the result
Review the suggested verification checks, test the result in the source system, and record what you observed. Under Pass verification and reconcile scope, also record whether the implemented result matches the recorded scope.
Choose Yes, it matches when it stayed inside the recorded scope. If it differs, choose Revised approval was captured and file where that approval lives, or choose Close with an unresolved scope difference and explain the exception. AgentHub records your judgment but does not make it.
If the result fails, return it to work. If the evidence is not sufficient yet, choose Wait for evidence. AgentHub keeps uncertainty visible instead of treating missing evidence as success.
Create and publish the client brief
From the verified change, choose Prepare client brief. You can also open Briefs → Create brief. Select the client, recipient, and reporting period, then generate the draft.
Edit the executive summary so it sounds like you, add any context the record cannot infer, and review the workflow, change, incident, ownership, and recommendation sections. Choose Publish and create share link when it is ready.
Publishing freezes the brief but sends nothing. Copy the share link, or choose Send email now after checking the recipient.
Verify it worked
- The change record shows Verified passed and is closed.
- The scope reconciliation record shows a match, a revised approval reference, or a visible unresolved scope difference.
- Any implementation reference shows the correct Workspace only or Client brief label.
- The client brief shows Published and has a share link.
- The Operations desk proof panel counts one verified change and one published brief for the real client.
Common issues
The client or workflow already exists
Select the existing record in Create → Client change. AgentHub creates only the records that are missing and blocks normalized duplicate names.
I need to add more client or workflow context
Create the first record, then open the client or workflow to add contacts, purpose, systems, repository, deployment, and other optional details.
The approval link was not sent automatically
Copy the link when it is created and share it through the client's normal email, Slack, WhatsApp, or other channel. AgentHub does not choose the recipient or send it for you.
I lost the approval link before copying it
Choose Replace approval link. The old link stops working and AgentHub shows the new link once so you can copy it.
I entered the request incorrectly
Choose Edit request while the record is Requested or Triaged. If a link is already active, revoke it first. A canceled record offers Create replacement request with the same client workflow selected.
No before-and-after comparison appears
Structural history begins after a supported connected workflow is synced. Verify the result in the source platform and record the evidence you do have.
My GitHub work did not import automatically
GitHub is manual in this release. Add the repository to the workflow, then attach the relevant pull request, commit, test, or deployment link to the in-progress change.
The brief cannot be generated
The selected client needs at least one client workflow. Add or import the workflow, then try again.
Email delivery is unavailable
Add an email address to the client contact and confirm email delivery is configured. You can still copy the frozen share link.