ESOPSElectronic work instruction management platform

SOP approval, rejection and version changes

The auditors compare the product process and attachment changes in the "SOP audit", and form a valid version after passing the audit; after rejection, the maintenance personnel revise it according to the reasons and then submit it.

For tenant administrators and authorized employees

This chapter only introduces authorized operations within this enterprise. The entrance and buttons change with the scope of enterprise opening, employee roles and positions; the actual picture uses test data.
Actual interface for maintaining and renaming process attachments — Operation flow diagram
Operation flow diagram · View original interface screenshot (Chinese)

Entrance and preparation

Entering "ESOP Operation Guide → SOP Review" requires SOP review authority. The maintainer first completes the draft and preview and submits it for review. Prepare process standards and change basis before audit.

Query and comparison steps

  1. Find the version by product name and submission time on the Pending Review page.
  2. Click "Compare and Review" to check the product, version number and change process.
  3. Check "before change" and "this change" respectively, focusing on new, modified, deleted processes and attachments.
  4. Use the preview portal to check text, drawings, page sequences, videos or models. Don't just look at the attached file name.
  5. Click "Approval" after confirming that the requirements are met; click "Reject" if not, fill in the clear reasons and confirm.

What to do after rejection

  1. Maintenance personnel return to the SOP list to check the rejected products and reasons.
  2. Revise processes, attachments or sequences and regenerate necessary previews.
  3. After the inspection is completed, submit it again for review.
  4. The reviewer rechecks this change and cannot pass it based solely on the last comparison result.

Historical versions and records

Check the version, status, submission and review information in the "Historical Version" of the SOP list and the reviewed records on the review page. When querying the history, check the version number to distinguish the current valid content from the historical content; the history preview does not mean that the version is being executed on site.

Release after approval

After the version is valid, go to the production order and production schedule to check the products, processes and versions used. When changes to a published task need to be reissued, process them according to the available operations on the production scheduling page, and check the actual received documents on the terminal; successful review cannot be automatically regarded as an immediate version change for all on-site tasks.

Complete inspection

The audit results and reasons can be reviewed; the effective version of the product is correct; the actual display of relevant production schedules and workstations is in line with expectations. When changing the version for the first time, it is recommended to select a workstation and check it first.

Related information:Implementation Notes · Free resources and upgrades · Terminal download