We've connected the entire procedure authoring workflow from the planning stage—where you "Decide before creating"—through to the review stage where you "check for gaps compared to what was decided." We've also made it easier to bulk import files of internal rules.

The biggest change is that running this workflow continuously helps the Procedure Authoring Policy itself grow and improve. Rather than a one-time rule written and frozen, field decisions accumulate day by day, and the standards for creating new SOPs gradually move closer to on-site reality.

[Note added 2026-09-20] The features introduced in this article were redesigned in the 2026-09-20 release. The screen names and available plans have changed.

• Consistency check → Pre-publish check: The number of evaluation axes increased from 5 to 7, and you can now verify SOPs against the original rule text (rule name and page number) of registered regulations. Address each finding one at a time by selecting "Fixed" or "No action needed," and finalize the check for each item with [Mark the check complete]
• "Decide before creating" → AI consultation before you build: Available from the Core plan and above. The "Pro and Enterprise plans" mentioned in this article are not your current plan terms (this continues to be offered as a beta feature)
• Internal rules → Regulations: In Dictionaries / Templates, we've added a new "Authoring rules" tab that consolidates regulations, writing style guidance, and export formats
• Procedure Authoring Policy → Phrasing / Writing style / Storage location → Storage folder / Approval route → Approval workflow

The following is content as of 2026-09-16. For the latest information, see 2026-09-20 [New Features] "Consistency check" redesigned as "Pre-publish check" and more.

① You can now decide before creating an SOP

Previously, creating an SOP always started by choosing a creation method—such as "Create from video" or "Create from file." This meant that the purpose, target audience, storage location, and output format were either decided while creating or corrected afterward.

We've added "If you haven't decided what to create yet, you can decide with AI" below the SOP creation screen (Please select a creation method). Opening this launches "Decide before creating," where you can organize key decisions through conversation with AI before choosing your creation method.

This feature is offered as a beta. We're actively improving the conversation flow and format selection. We'd appreciate feedback on examples that work well and any cases where the results seem off.

● What you can decide

• Purpose: What is this SOP for?
• Type: Work procedure, checklist, training material, etc.
• Audience: New employees, experienced staff, external parties
• Scope: What range should be included in one document
• Storage location: Which folder to place it in
• Form for file output: Which format to export in
• Approval route on publication: Default approval process

The conversation doesn't start from scratch. It begins after reading any existing internal regulations, output formats, and Procedure Authoring Policy, so decisions align with your company's standards.

Once you've decided everything, you can select "Proceed to create with this" to move directly to the creation method that matches your decisions. Those decisions are saved with the SOP and can be reviewed later in the "History" section.

Available to Pro and Enterprise plan customers. Free, Lite, and Core plans see only the entry point.

② We've redesigned "Policy check" as "Consistency check"

The previous "Policy check" only verified that SOP content followed the Procedure Authoring Policy. We've renamed it to "Consistency check" and expanded the review to five axes. Open it from the "..." menu in the top right of the editing screen.

● Five tabs

• Policy: Each step is checked against the Procedure Authoring Policy
• Form for file output: Verify the format matches current content and that exporting won't lose data
• Storage location: Shows folders that contain similar SOPs
• Revision and approval: Compares changes and revision reasons from the previous version
• Tags: Indicates missing tags that should be applied

Only the open tab runs. Since we don't execute all checks at once, you can quickly review just the axes you care about.

For SOPs where content was decided before creation (in section ①), evaluation compares against "what was decided when creating." For SOPs without pre-creation decisions, evaluation infers from current content as before. The screen shows which method is being used.

Tab behavior adapts to the features your team uses (Procedure Authoring Policy and file output formats are Enterprise-plan features; revision and approval are Pro and Enterprise).

③ The Procedure Authoring Policy grows from on-site records

Previously, the Procedure Authoring Policy was something administrators wrote and edited manually. On the ground, decisions like "the consistency check flagged it but we didn't adopt the suggestion" or "approval sent it back" happen daily, but those decisions never fed back into the policy.

We now record which consistency check findings were accepted or rejected, and the reasons for approval reversals, then use that to generate policy update suggestions. Updates run automatically once per day on the server.

Simply running your regular workflow—creating, checking, and publishing SOPs—causes the policy to grow naturally. You don't need to set aside separate time to rewrite the policy.

● How it works

• Only new entries are added. Existing content is never overwritten
• In admin settings, choose whether to "Update automatically" or "Only propose (review and adopt)" updates from on-site records (automatic is the default)
• For teams with no Procedure Authoring Policy yet, a first version is created from published SOPs. Teams with no published SOPs see no action

● Update history and restore

We've added an update history panel to the policy. Each line shows when, who, and what changed, and you can restore the policy to any previous point. Changes from automatic updates show as "System (automatic update)" so you can tell them apart from manual edits.

Procedure Authoring Policy is an Enterprise-plan feature.

④ Bulk import internal regulations

From [Dictionaries / Templates] → [Templates] → [Regulations], you can now read multiple internal documents that define SOP writing standards all at once. It supports PDF, Word, and Excel. The extracted content appears as a draft for you to review before saving.

● What it reads

• Type catalog: What document types exist in your organization and which formats support them
• Required items / Prohibitions / Phrasing / Writing style / Granularity

Where regulations contradict each other, we surface "Where the rules conflict" and show which file and location hold each conflicting statement. You can decide each conflict one at a time with "Use this one," but you can start operations with conflicts still unresolved. The system doesn't require you to decide everything before using it.

The imported regulations are referenced by ① "Decide before creating" and ② Consistency check.

Available to Enterprise plan customers.

⑤ Term changes

We've renamed the "Don'ts" section of the Procedure Authoring Policy to "Prohibitions". The content and how it's passed to AI remain unchanged.

Impact on existing data

Previously created SOPs and Procedure Authoring Policies continue to work as-is. No settings reconfiguration is needed.

Automatic updates to the Procedure Authoring Policy are enabled by default. If you prefer to receive only suggestions, change the setting in admin options to "Only propose (review and adopt)." Even after automatic updates have been applied, you can restore earlier versions using the update history.

Related information

Define the Procedure Authoring Policy (reflect your organization's phrasing and standards in AI)

Export SOPs in your company's format (Export format)

Approval workflow

Thank you for using Dive! ◎