Plan Review Overview
Some applications require a plan review to evaluate the proposed project. The documentation is reviewed by all pertinent city departments to ensure compliance with applicable codes and regulations before permits are issued or for planning and zoning.
Plan reviews are tracked in Oracle Public Sector Licensing and Permitting as part of permit and planning application workflow. Agency setup determines whether a plan review is required for a permit or planning application type. For more information, see Setting Up Permit Types and Setting Up Planning Application Types.
Any review cycle for a permit or planning application can be conducted with or without an integration with Bluebeam Studio™, an electronic document review tool.
This is what the steps for a plan review look like:
A registered public user submits a permit or planning application that requires review by agency staff.
A permit technician or assigned planner assigns a status to the transaction that requires a plan review. This triggers the automatic creation of the first plan review cycle. For more information, see Using Workflow.
If configured by the agency, the system automatically assigns departments and reviewers to the first cycle of the plan review. The plan coordinator can also manually assign reviewers to a plan review cycle in the permit or planning application details, or on the Plan Review Console. See Managing Plan Reviewers and Using the Plan Review Console.
The plan coordinator attaches documents, if any, to the plan review cycle from the application attachments. See Managing Plan Review Documents.
When an integration with Bluebeam Studio™ exists, the plan coordinator can initiate an electronic Studio Session for the plan review cycle at any time until the review cycle is complete or continue with a manual review cycle. See Working with Electronic Plan Reviews.
The assigned plan reviewers complete their review. See Performing Plan Reviews.
The plan coordinator adds new plan review cycles and repeats the review process as necessary until the review is complete. See Managing Plan Review Cycles.
Plan reviews can be created and updated in application statuses in addition to Plan Review as long as the permit or planning application isn't in a pre-submittal or terminal status.
Permit statuses:
Yes, you can create or update plan reviews for permits in these permit statuses: About to Expire, Accepted, Delinquent, Expired, In Process, Inspection, Permit Issued, Plan Review, and Submitted.
No, you can't create or update plan reviews for permits in these permit statuses: Certificate of Occupancy, Completed, Denied, Payment Pending, Pending, Pending Submittal, Void, or Withdrawn.
Planning application statuses:
Yes, you can create or update planning application plan reviews in these planning application statuses: About to Expire, Application Accepted, Delinquent, Expired, Hearing, In Process, Plan Review, and Submitted.
No, you can't create or update planning application plan reviews in these planning application statuses: Completed, Denied, Payment Pending, Pending, Pending Submittal, Void, or Withdrawn.
Plan Review Workflow
The plan review workflow for the plan coordinator appears on the Task Management page.
As a plan coordinator, you sort tasks by Workflow. For more information about workflow, see Using Workflow.
When the last reviewer provides a decision status for a plan review cycle, it is automatically closed. Upon closing, the overall review status changes to Complete. If a review cycle uses a Bluebeam Studio™ Session, the plan coordinator finalizes the cycle.
The system also updates the plan review cycle details with the most severe decision status from the individual plan reviewers. The decision statuses are listed here, from most to least severe: Rejected, Revision Required, Approved with Comments, Approved, and Not Required.
Workflow is automatically moved forward to the next step when all of the following criteria are met:
The current plan review cycle status is Complete.
The plan review decision is Approved, Approved with Comments, or Not Required.
The review cycle has been finalized, if a Bluebeam Studio™ Session was used.
If plans have one or more rejections, or revisions are required, the plan coordinator may require the applicant to correct the plans and resubmit them for another review cycle.
The workflow process definition must identify the plan review task and the action to take when auto-advancing. For more information, see Using Custom Properties.