Skip to content

Sign-off

Sign-off is for the person who looks and decides: a founder, a client, a product owner. It gathers everything waiting on you in one place, so you can get through twenty or a hundred finished issues without opening each one.

  • Everyone in the workspace has Sign-off in the sidebar. The number beside it is what waits on you. Turn sidebar numbers off under Settings › Preferences.
  • In review works on every plan. It lists open issues in the review stages you decide: stages that name you as a reviewer under Settings › Workflow, and stages that name nobody, which every member decides.
  • The environment tabs need Solo Pro with environments turned on. You get a tab for each environment that names you as an approver under Settings › Workflow.
  • New and Your notes work on every plan and sit after the other tabs. Their numbers are yours alone and never count toward the sidebar number.
  1. Open Sign-off. In review lists those issues grouped by project, with the stage, who it’s assigned to and how long it has waited. A wait over three days shows in orange.
  2. Press Accept on a row to move it to the next review stage, or to Done when there isn’t one. With a mouse, Accept shows when you point at the row or tab into it; on a touch screen it always shows.
  3. To send one back, open the row by its title. It shows the issue’s brief (What changed, How to check, Not done), or the last handoff comment when nobody wrote one, then the pull request, checks and an Open the issue link. Send back asks what needs to change, posts your note on the issue and returns it to Ready (Backlog if it still needs refinement). Whoever built it gets told.
  4. To accept many at once, tick rows and press Accept N selected, or press Accept the rest for everything you haven’t ticked, up to 100 at a time.
  1. Pick the tab for the environment, such as On Staging. The strip at the top says whether the next promotion is ready, how many issues are approved, passed, behind a flag, waiting or held, and when work last landed there.
  2. Press Approve on a row, or open the row by its title to see its brief, its pull request, checks, flag and the environment’s Open link, with every answer in one group: Approve, Approve with a follow-up…, OK behind flag, Hold…, Pass and Reject…. Hold and Reject both need a reason. Approve with a follow-up… asks what the follow-up should fix, then approves the row and files that as a new, related issue in Backlog; Decided shows it as Approved · follow-up #N. It’s one row at a time: the bulk buttons only approve. Hold keeps the issue Done where it is and makes the release wait; Reject sends it back to Ready. Pass says it isn’t yours to judge: it’s recorded as not reviewed by you, never holds up the release, and still waits for any other approver who hasn’t answered.
  3. To decide many at once, tick rows and press Approve N selected, or press Approve the rest or Pass on the rest for everything you haven’t ticked, including rows further down the list, up to 100 at a time.

If an admin set what you review there, the tab lists only that work and says so under the strip: You review Checkout and Reports here. Everything else on Staging is passed for you. The strip still counts the whole environment, with work nobody reviews counted as passed. Anything else on Staging is a click away on its issue page under Answer anyway.

Keyboard: ↑ and ↓ move between rows, Space ticks the row you’re on, and Enter opens it.

A docket is a few issues with one brief: What changed, How to check and, when there is one, Not done. Whoever finished the work writes it, a person or their agent, so you get five things to try instead of fifty tickets.

Cockpit previews up to three dockets awaiting your review. Its links open the matching Sign-off tab, expand the docket and focus its heading. Fully answered dockets are not included in that preview.

  1. Dockets come first on a tab, the first one open. The line beside each says how far along it is, such as 1 of 3 decided, and becomes the tally (3 approved) once every issue has an answer.
  2. Read the brief, try it, then answer the whole docket: Approve all 3 (or Approve the other 2 once some are decided), OK behind new-receipts when every undecided issue ships behind the same flag, or Pass. In review, Accept all 3 accepts the docket. Answers are still recorded per issue, and Undo works as it does for a row.
  3. To hold, reject or send back one issue, open its row inside the docket and answer it there. The rest of the docket waits for you.

Everything not in a docket is listed below under Not in a docket. Approve the rest and Pass on the rest only cover those.

Any member can, and agents can over Hydrant’s MCP tools (list_dockets, get_docket, create_docket, edit_docket, delete_docket, add_docket_issues, remove_docket_issues).

  1. Tick issues and press Make a docket, then write a title and the brief. If one of them is already in a docket, Hydrant asks whether to move it or leave it where it is. A docket lives in one place: one environment, or one review stage.
  2. Use a docket’s ⋯ menu to Edit its title and brief, or Delete it. Deleting a docket only removes the grouping: its issues stay where they are, with their answers.
  3. To move one issue between dockets, open its row and pick a docket under Docket, or Not in a docket to take it out.

A docket follows its issues: when engineering promotes the environment, its dockets move to the next one with them. An issue that’s reopened, rejected, sent back, accepted into another stage or trashed leaves its docket, and a docket whose last issue leaves is gone. In the last environment, such as Production, a docket closes: as soon as it arrives when nobody approves there, or once every issue still in it is answered when someone does. Its brief stays in its history, and the release it went out in can draft its notes from it: Draft from N dockets in the release’s Edit dialog fills the notes with each docket’s title, what changed and what’s not done, for you to edit before you save. You can’t make a docket in a last environment nobody approves: there’s nobody to brief.

Choose History in a docket’s ⋯ menu to see who made it, changed its brief, added or removed issues, moved it or closed it. Agents appear with the person they act through. Edited fields show Before and After, including when optional text was cleared.

Past dockets, beside the Sign-off heading, finds closed and deleted dockets even when nothing is waiting. Each keeps its recorded events and available brief snapshots. “Every remaining issue answered” can include holds and passes; it does not mean every issue was approved. History records what happened to a docket; it does not draft release notes.

Both lists start with the newest 20 entries. Load older adds earlier entries; close and reopen to see newer changes. Place names use their current names because earlier names weren’t recorded. Missing places and unavailable issues are labeled unavailable; their recorded issue numbers stay readable.

Agents can use list_dockets with history: true for past dockets and get_docket with history: true for a current or past docket’s recorded history. These reads use the same workspace access as the live docket reads. Follow the returned next/cursor or older/before cursors; historical pages contain 20 entries.

When you’re happy with what’s on an environment, tell engineering it can go. Clearing moves nothing: no issues, no code. Promoting stays engineering’s move, theirs or their agents’.

  1. On the environment’s tab, press Clear for Production (or whatever comes next) at the end of the strip. It’s the filled button once nothing is waiting or held.
  2. If anything is still waiting or held, the strip says how many first, and Clear anyway goes ahead. The clearance keeps those issue numbers, so the release can say what was still open.
  3. The strip then says who cleared it and when. Press Take back to withdraw it. Any approver of the environment can take it back, not only the one who cleared.

An agent clears for you only with your sign-off grant across the workspace; a grant on one issue isn’t enough. It can always take a clearance back.

What went out is remembered. A release, and each promotion on the Environments page, says how many issues went out held, never reviewed or passed, and whether the environment was cleared and by whom; each issue on the release is tagged the same way. An issue that went out held or never reviewed says so under its Environment for as long as it stays there.

A clearance stands for exactly what was there when you cleared. If an issue arrives, leaves or changes verdict afterwards, or the environment’s approvers or order change, the clearance is taken back, and the strip says which issue and what happened. Changing what someone reviews, or an issue’s project or labels, can count too: it can move an issue between waiting and passed for everyone, and the reason names that issue’s new state. Clear again once you’ve looked. One approver’s clearance is enough, and clearing notifies nobody: engineering sees it when they promote, and agents read it over MCP before they do. The workflow pack teaches them to stop and ask without one. The last environment has nothing after it, so it has no Clear.

Engineering sees the same thing without opening Sign-off: on Environments, the step out of an environment with approvers says who cleared it and when, that it isn’t cleared yet, or why the clearance was taken back, then how many issues are approved, passed, behind a flag, waiting and held (select the counts to open those issues). Its dockets are listed read-only, with only what still blocks open. For an approver of that environment the page leads with Review on Sign-off: verdicts, clearing and docket edits stay here.

When an issue is waiting for your answer, its page leads with a box for you: What changed, How to check (with the environment’s Open link when it has one), Evidence and Not done, and your answers right under them. Evidence is filled in for you: the pull request, its checks and the review stages it came through. The rest of the ticket (spec, acceptance checks, receipts) is folded under The whole ticket; open it whenever you want the details.

The box shows on an issue waiting in a review stage that names you, or on an environment you approve, unless the issue is assigned to you. A stage that names nobody shows it to nobody. Everyone else sees the issue page as usual.

When the issue is in a docket, the words come from the docket’s brief, and the box says which docket. Otherwise they come from the issue’s own brief. Whoever hands the work over writes it: Actions › Write the brief… on the issue, or an agent over MCP. What changed and How to check go together; Not done is optional. No brief yet? The box says so and shows the last handoff comment instead, with a link to it.

  1. Pick New. It lists issues written (Captured) or made ready to build (Refined) since you last opened New or Your notes, Refined first, newest first. The line at the top says when that was, such as Since Tuesday, 4:12 PM. Your first look covers the last 7 days.
  2. Each row has the title, who wrote or refined it and when, and the description’s first line.
  3. Press Looks right once you’ve read a spec. The row turns to You read this, and the issue’s history says you read it, so whoever wrote it, person or agent, knows it landed. It approves nothing, changes no status and notifies nobody. Press Comment to say more; it opens the issue at the comment box.

What counts: an issue being created, or going from Needs refinement to Refined. Edits and comments don’t. Your own work in the browser is left out; work by agents, yours included, is not, since reading what they wrote is the point. The window moves forward once per visit, so reloading within the hour shows the same list.

Pick Your notes. Answered lists comment threads you started or wrote in where someone else has answered since you last looked, with the start of their reply. Still waiting lists open threads where the last word is yours, with how long it has waited; over three days shows in orange. Resolving a thread takes it off Still waiting. Each row opens the issue at that comment.

At the bottom of every tab, Is anything moving? answers a reviewer’s other question: is the team getting through it? The line counts the issues captured and delivered in the last 7 days. The tiles show how many were delivered in that time, the weekly rate over the last 4 weeks, the median time from capture to Done and how long review takes. They cover the whole workspace and are counted exactly as on Insights.

If you approve an environment, Your calls shows the median time from an issue reaching it to your first answer (approve, OK behind flag, hold or reject), including answers your agents gave for you. Changing your mind later doesn’t count again. Open Insights has the full picture.

  • A decided row leaves the list and lands in Decided, folded at the bottom; a docket’s issue stays in its docket with its answer. On an environment tab, an approval, a hold or your pass there keeps Take back for as long as it stands. A toast offers Undo right after you decide; after Approve with a follow-up… it also moves the follow-up to Trash if nobody has touched it yet. On In review it moves the issues back to the stage they left, and a send-back’s note stays.
  • The strip reads Ready. Nothing waiting, nothing held. once nothing is waiting or held, and Cleared by … once someone has cleared it.
  • Clear the last row while you watch and the page says Pile cleared, with how many you decided. The stamp lands with a little motion unless you’ve turned off Celebrations or your device asks for reduced motion.
  • If nothing waits on you at all: Nothing needs your sign-off.
  • If every waiting issue is in a docket: Nothing loose. Somebody did the paperwork.
  • A spec that changed after you read it shows Edited since you read it, and Looks right comes back.
  • Nothing new: Nothing new since Tuesday. No threads open or answered: No loose threads.
  • If you approve an environment or are named as a reviewer, something is waiting there for you and you have no open work of your own, opening the workspace takes you to Sign-off instead of Cockpit. A stage that names nobody never does this. Cockpit is still one click away.
  • A row says it changed since it was read. Someone else decided it or it moved. The list refreshes; look again.
  • An issue on Staging isn’t in your list. It’s outside what you review there, so it’s passed for you. Who reviews what is set under Settings › Workflow. Changing it never rewrites answers you already gave.
  • There’s no tab for an environment. You’re not one of its approvers, or environments are off. An admin sets approvers under Settings › Workflow.
  • Only Pass on the rest on your phone. On purpose. Approving a pile you can barely read is how bugs ship, so approve rows one at a time, answer a docket after reading its brief, or use a larger screen. Passing is honest about not looking, so it stays. Making dockets needs a larger screen too.
  • “Staging changed while you looked.” Something arrived or a verdict changed between reading the strip and pressing Clear. The strip refreshes; look again, then clear.
  • “Clearance taken back: #406 was held after you cleared.” Someone changed what you’d cleared. Look at that issue, then clear again if you’re still happy.
  • “Someone changed this docket while you were editing.” Your words are still in the form. Look at the docket again, then save.
  • “… isn’t waiting on Staging, so it can’t join this docket.” A docket only holds issues waiting in its own environment or review stage.
  • “Pick issues from one stage.” In review spans several stages; a docket lives in one, so tick issues from the same stage.
  • The numbers didn’t load. The list above still works. Press Try again.
  • A figure says “too few to trust”. Fewer than 5 issues or answers went into it, so read it as a hint.
  • An issue in review isn’t on your list. Its stage names other reviewers. You can still open it and move its status.
  • “Only … can accept or send this back.” The stage’s reviewers changed while you looked. The list refreshes.
  • Something new isn’t in New. You made or refined it yourself in the browser, it was trashed, or it was only edited. New shows creations and refinements.
  • New shows the same issues after a reload. On purpose: the window moves once per visit, at most once an hour.