Skip to main content
Depending on your settings, a draft procedure’s steps carry a row of improvement pills that ask ION Intelligence to rewrite the step you are editing. ION never writes the step itself. It returns a proposal: what it would change, why it wrote it that way, and the run history behind it. You decide whether the step takes it. Proposals are only made on a draft procedure, so revise a released procedure before asking. For more information on revisions, see Create and release a procedure.

​
Ask for a proposal

  1. Open a draft procedure’s Steps tab and select the step you want to improve.
  2. In the pill row above the step content, click the angle you want, such as Improve, Add safety warnings, or Specify tolerances. The row scrolls sideways to reach the rest.
  3. The ION Intelligence companion opens and the ask lands in it as your own message. Wait for the answer.
Clicking a second pill on the same step continues the same conversation, so the second ask sees the first proposal. Moving to another step starts a fresh one.
The same pills appear on a draft standard step. There, ION answers in the conversation instead of returning a proposal — proposals are only made on a procedure’s own steps.
A pill is repeatable: clicking it again after you have edited the step asks against the step as it now reads. Pills are unavailable while any answer is still streaming.

​
Read the proposal

The proposal arrives as a card in the conversation, headed Proposal · current. It carries the proposed title, a summary of the changes it makes, a Why line, any safety callouts and open questions ION raised, and an Evidence block linking the runs, issues, and comments the proposal rests on. To read the proposed wording itself, click Preview in step or Edit. Two headings mean the proposal is worth less than it looks:
Execution history follows a step into later revisions of the same procedure, so a step revised from a released version is grounded in what happened on that version’s runs. Procedures revised before this shipped have no link back to the steps they were copied from, so their steps are grounded only in their own runs.
ION declines rather than guessing when it cannot support a revision. The decline says why, such as that the procedure is not a draft, that the supporting records could not be read, or that a claim could not be tied back to a record.

​
Preview a proposal in the step

To read a long revision where it will actually live, click Preview in step. The step content area renders the proposal as a read-only difference against the current content, marked Proposed, and the editor is untouched underneath. Click Exit preview to go back. If the proposal is accepted, dismissed, or superseded while the preview is open, the preview closes itself. A proposal the step has already outrun stays readable in the preview.

​
Accept, edit, or dismiss a proposal

  • Accept writes the proposed title and content into the step. The card becomes Accepted into the draft with an Undo beside it.
  • Edit opens the proposed content in a text box so you can revise it first. Accepting your version records it as a proposal of its own that supersedes ION’s, so the step carries exactly what was written. Click Cancel edit to drop the revision.
  • Dismiss collapses the card to a single line and leaves the step alone. Expand it again to see the changes it would have made.
Undo returns the step to what it said before and reopens the proposal, so it can be accepted again. It refuses when the step has changed since the accept, when the proposal has been removed from the list, and when what the proposal replaced is no longer recorded, which is what a later accept on the same step leaves behind. ION says which, and nothing is written.
A proposal whose content already matches the step offers no Accept, because accepting it would change nothing. The card says so and offers Ask again instead.
Accepting a proposal invalidates the step’s other pending proposals: each was written against a different version of the step, so they no longer describe what it says.

​
Review every proposal on a procedure

A conversation is chronological, so a card scrolls away. To work through a procedure’s proposals instead, use the rail.
  1. Click Review all, which carries a count, in the procedure’s action bar. The companion’s proposals strip has the same control.
  2. The rail opens beside the page, headed Proposals with a live count. It lists the procedure’s proposals oldest first, up to the 100 most recent.
  3. A row offers Accept and Dismiss. A row you settle collapses in place, so the list does not reshuffle under you. To edit a proposal before accepting it, preview it in the step, or undo an accept, use its card in the companion.
  4. Click Hide proposals in the action bar, or the close control in the rail’s header, to give the space back.
A dot on each step in the step list marks the steps carrying live proposals, and carries a number when one step holds several. Review all counts proposals; the dots count steps, so the companion’s strip reports both when they differ. The rail needs a desktop-width column and is hidden below that width. On a narrower screen, act on proposals through the card in the companion.

​
Follow-up questions

An answer can also come back with up to three grounded follow-up questions under the proposal, drawn from the same evidence. Clicking one asks it about the same step. They go Out of date together with the proposal once the step changes, rather than disappearing.