Before publishing a finished SOP, you can have AI verify it aligns with what your organization has decided. You can check not only the phrasing of the text, but also alignment with internal rules, the export format, storage folder, reason for publishing and summary, and tags—all on one screen. This replaces the former "Consistency check" feature.
It appears to users who can edit SOPs. You access it from your PC browser.
How to access it
- Open the SOP editing screen
- Click "More" to the right of "Publish" in the upper right
- "Pre-publish check"select
7 axes
The screen is divided so you select axes on the left. Only the axes you open will run, so you can quickly check only the axes you want to see. On the left, each axis shows a status like "Not run", "Checking", "No issues", "None", and so on. Features in higher-tier plans show a lock icon. Before opening, you can see what can be checked for this SOP right now.
What is decided
It displays the purpose, readers, type, and scope decided in "AI consultation before you build". The following axes, if things have been decided here, will judge based on them as criteria.
Rules
While AI reads the original text of registered internal rules page by page, it checks whether the SOP conflicts with the rules. Findings always include the source (rule name and page number) and a quote from the original text that is the basis. From "Target rules" you can open the rules themselves right there and verify the original text.
Findings show which field of that step (step name / work content / tips / cautions / safety) needs to be fixed and a proposal for the corrected text. For each field, you can collectively apply findings by checking "Apply to this field". If a proposal could not be made for a field, you can write it yourself from "Fix it here". There is no limit on the number of findings.
Writing style
Each step's text is compared against writing style (phrasing / writing style, prohibited items, common phrasing). Places that should be improved appear step by step, and you can immediately apply them to the body with "Apply".
Export format
It checks whether the current content fits the format. If there is a better match among registered export formats, it shows it as "Form that fits better". If the selected format lacks containers for certain items, it displays "Exporting in this form will drop what you wrote". If there are no issues, it displays "Everything you wrote goes into the output".
Storage folder
It shows a folder that contains many SOPs of similar content. By comparing with "Current folder", you can decide whether to move. You can move immediately from the candidate row. For SOPs where you decided the creation destination before creation, if it is in a different location, it displays "It is in a different place from the destination decided at creation".
Reason for publishing and summary
It outputs a draft of the "Reason for publishing" and "Summary" entered in the publication request. The reason is selected from reasons for publishing registered in the team, and from there the approval workflow is drawn. The summary becomes "Summary of the first version" for first edition or "Summary of changes" for revisions. The summary is not automatically filled; you copy and use it. If what was decided includes a reason for publishing, it also displays whether there is any conflict with it.
Tags
It checks whether tags that should be attached based on the SOP content are not missing. You can attach them on the spot with "Add this tag". For teams that have not registered tag vocabulary, it displays "No tag vocabulary is registered".
2 ways of judging
The judgment criteria change depending on whether the SOP has "content decided before creation". Which way it is judging is displayed on the screen.
- Checking against what was decided at creation: An SOP where you decided the purpose, type, creation destination, and format in "AI consultation before you build" before creation. It judges by the differences from what was decided
- For now this is judged by guessing from the SOP content.: An SOP that has no decided content. It judges from the SOP content
Usable axes
For each axis, judgments are made when you use that feature.
- Rules, writing style: Enterprise plan
- Export format: Enterprise plan
- Reason for publishing and summary: Pro and Enterprise plans
- Tags: Core, Pro and Enterprise plans (attaching tags itself is possible in all plans. What differs here is the part where AI makes suggestions)
- What is decided, storage folder: All plans
Adopting or passing on findings
You can adopt or pass on the findings that appear. Choose "Fixed" or "No action needed" one by one. Which one you choose is recorded and becomes the basis for updates to writing style and rule reading suggestions. If findings that are repeatedly passed on in the field exist, they become material to reconsider the decided policy.
The more you use pre-publish check, the more writing style and rule reading grow closer to the field. It is a relationship where you can refine the criteria themselves while checking.
Respond to findings and complete item by item
For each finding that appears, choose "Fixed" or "No action needed". You can also choose them in bulk. When you fill all of them in, "Mark the check complete" at the bottom of the screen becomes available. When marking complete, you can leave a brief note about the reason for the decision (optional).
The list on the left shows the result, execution date, and completion time for each item. You can always return with "Undo completion". If you want to redo an item, you can also revert it to "Not run" along with the result.
Items whose confirmation failed cannot be marked complete. Use "Check again" to try again.
How results are retained
Confirmation results are saved. Even if you close the screen, it will not disappear, so you can read it as is when you open it again. You do not need to run confirmation multiple times with the same content.
- If you fix the SOP after confirming it, "The SOP has been edited after this" will be displayed, and the completion judgment is removed
- When you revise the results are carried forward. When you copy as a separate SOP the results are not carried forward (so that an SOP that has never been checked does not appear as if it has been checked)
- When rules are revised, results are not reliable even if you do not fix the SOP. A message to that effect will be displayed on the screen, so please check again
What approval users see
Users who cannot edit SOPs can also read the creator's check results in the same list. The content can only be opened for items where the creator has marked "Check complete". Confirmation execution requires edit permissions, so it cannot be run at the approval stage.
Insights during editing
The SOP editing screen has a panel to accumulate insights. Nothing appears during writing, but when you finish writing one step, only the count is shown as a badge.
What appears here is only what can be understood without calling AI (a required field is empty, type not decided, rules have been updated, unresolved points in the rules, original rules text not yet checked against, previous check result is out of date). Checking against the original text of rules is executed from this pre-publish check.
Related
Define how to write SOPs (reflect your organization's phrasing and standards to AI)
Output SOPs in your own format (export format)