Skip to content
Skill Reality
Request a demo

Forge authoring

Your SOPs, turned into guided procedures in minutes

Paste or upload an existing procedure document. Forge parses it into numbered steps, flags branch conditions, and queues it for your team's review. Nothing reaches the floor without approval.

Apply for a 2027 pilot

How it works

From document to approved procedure in three steps

  1. Paste or upload your existing SOP

    Bring in a PDF, a Word document, or plain text. Forge accepts the formats your procedures already exist in.

  2. Forge parses each task into numbered steps and flags branch conditions

    The AI reads the document, extracts each action as a numbered step, and identifies conditional logic such as 'if the valve does not seat, call maintenance.' Branch points are flagged for your team to review.

  3. Your team reviews and approves before the procedure goes live

    Nothing is published to the floor automatically. A designated reviewer checks the parsed steps, adjusts wording or sequence as needed, and approves the version. Only approved versions are available to workers.

Why SOP digitisation stalls

Converting paper SOPs to digital procedures is slow and inconsistent

Most operations have hundreds of SOPs. Converting them to structured digital procedures by hand takes months and produces inconsistent results. The format depends on whoever did the work.

  • Manual conversion of each SOP into a digital format takes hours per document.
  • Different authors produce different step structures, making procedures inconsistent across the operation.
  • Branch conditions and exceptions buried in paragraph text get missed during manual conversion.
  • Version control is often informal, so the floor may be running a procedure that was superseded months ago.

Forge capabilities

Authoring built for operations teams, not developers

  • AI-assisted SOP parsing

    Forge reads your existing document and extracts each action into a numbered step. What used to take hours of manual formatting takes minutes.

  • Branch condition detection

    Conditional logic buried in paragraph text is flagged automatically so your team can confirm the correct branch structure before the procedure goes live.

  • Team review and approval workflow

    Every parsed procedure goes through a review step. Approvers can edit steps, add context, set verification flags, and sign off before the procedure is published.

  • Version control for procedures

    Each approved procedure has a version number. Previous versions are retained. When a procedure is updated, the floor always runs the current approved version.

  • Supports multiple languages

    Step text appears in whichever language is configured for the procedure. This allows the same base SOP to be deployed to workers who read in different languages.

Use cases

Where this fits on the floor

Common questions

What document formats does Forge accept?
Forge accepts PDF, Word documents, and plain text. If your SOPs exist in another format, contact us to discuss your specific situation.
Do we need to rewrite our SOPs before uploading them?
No. Forge is designed to work with the procedures you already have. The AI handles the structural conversion. Your team's review step is where you refine the output.
What if a parsed step is wrong or unclear?
The review workflow exists for exactly this reason. Reviewers can edit any step before approving the procedure. No parsed procedure reaches the floor without a human sign-off.
How does version control work when a procedure is updated?
When a procedure is revised and re-approved, it gets a new version number. Workers on the floor see the current approved version. Previous versions are retained in the system for audit purposes.