Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This article provides information about how eplansoft REVIEW (EPR) manages projects, plan review documents, supporting attachments and the plan review cycle.

Additionally, information about how EPR typically integrates to other back-office applications is described below. 


In this article:


High Level Overview

A typical plan review Project undergoes this basic process:

  1. Create a Project: A project record is created that includes at minimum, one primary Contact.
  2. Conduct Intake on the new plan review documents.
    1. Plan review documents (in PDF format) are uploaded to the project.
    2. Supporting attachments (any file type) are uploaded to the project.
    3. Trigger Distribution Workflows to create group and/or named-user assignments.
    4. Multiple assignments are created for each plan review document.
  3. Conduct plan review.
  4. Complete assignments.
    1. Each assignment is given a pass/fail status by the reviewers.
  5. A deliverable package with the marked up documents is prepared, this completes the 1st submittal cycle.
    1. Return the deliverable package to the customer for corrections.
  6. Corrected documents are provided by the customer as the next submittal. Repeat from step 2.
    1. Existing assignments are reopened with a Not Started status and markups are carried forward to the latest version.
    2. Comments found to be resolved are marked ‘closed’.
    3. Plan Review Assignments are completed.
      • The process repeats until all noted issues are resolved.
  7. The project is closed.


Integrated Environments

Variations on the process described above include the following scenarios when EPR is integrated to another application using our Connect API toolkit:

Integration Option 1:

The integrated application pushes project data, documents and plan review assignments to EPR. The integrated application manages document versioning.

No manual data entry of projects, upload of documents or creating plan review assignments is necessary in EPR.

Plan review is conducted in EPR.

Plan review deliverables are checked in to the integrated application using API calls.


Integration Option 2:

The integrated application pushes project data and documents to EPR using API calls.

EPR manages document versioning.

EPR's Workflow Distribution module is configured and enabled to auto-create assignments.

Plan review is conducted in EPR.

Plan review deliverables are checked in to the integrated application using API calls or downloaded to another network location.


Integration Option 3:

EPR is connected to the e-PlanSoft goPost Customer Portal.

goPost pushes new project data and documents created by the customer to EPR using Connect API.

goPost manages document versioning.

Manual data entry of projects/contacts and uploading documents to EPR is unnecessary.

Plan review is conducted in EPR.

Plan review deliverables are sent back to goPost. The customer logs into goPost to download the reviewed plans, etc. and can optionally be downloaded to another network location.


Best Practices

In some cases, a project may need to be reopened for plan review of revised drawings after a project has been closed. For instructions on how to handle documents submitted as revisions, see: XXXXX



Best Practices

For stand alone deployments, email notifications should be configured to alert the appropriate project team members when a project cycle is set to Cycle Complete so that a deliverable package can be prepared.


































  • No labels