How to use a Righthand with Confluence

Review a runbook against its current version

Use Righthand with Confluence to prepare a runbook review, concentrating on missing owners, outdated references, and unclear steps. The deliverable is a page-specific change proposal, not an unsupported claim that the documented process works in production.

Confluence's page reference includes page identity, space context, status, and version information. Keep the version beside each proposal. A suggestion based on an earlier page can overwrite a newer correction if the assistant does not refresh the source before editing.

Collect the document and its evidence

Give the page URL, intended reader, approved operational sources, and review criteria. For an illustrative incident runbook, the criteria might include a named escalation owner, a clear prerequisite, and a result check for each action. The owner supplies those standards.

Check available page reads through integrations. If the connection cannot expose page body or version information, provide an approved export and its snapshot time or authorize a browser review. Note when embedded macros, diagrams, or attachments are not present in the export.

A complete example brief

At 10 AM America/Los_Angeles on Wednesday, review the linked Confluence runbook and the attached approved service guide. Produce a private change worksheet with page ID, title, current version, section heading, proposed wording, rationale, and source link. Flag missing prerequisites and unverified operational statements. Do not change the page or execute its instructions. Send to me for runbook-owner review. Reconcile the reviewed sections and identify inaccessible macros or attachments.

The example is illustrative. Documentation review does not authorize the assistant to perform an incident response, restart a service, or contact an escalation recipient.

Show proposals that can be inspected

An example row might say: “Recovery section; prerequisite absent; proposed text asks the operator to verify the named service and environment before proceeding; owner must confirm the actual check.” The assistant should not invent a command or endpoint merely to make the runbook feel complete.

Keep current text and proposed text separate. A broken reference can be flagged without substituting a similarly named page from another space. If the source and runbook disagree, show both and ask the owner which is authoritative.

Reconcile before publication

If the owner approves supported page updates, refresh the version and compare it with the proposal's source. A changed version calls for a new comparison rather than automatic replacement. After the update, retrieve the page again and confirm the intended sections and resulting version.

An inaccessible page may reflect permissions rather than deletion. An export can flatten dynamic content. Report those limitations and avoid claiming a comprehensive review when important material is missing.

Set document authority through Righthand connection permissions, and review pricing for ongoing documentation maintenance. Keep execution of the runbook a separately defined responsibility.