Back to app
Review a portal form request

Review a portal form request

Approve a clean submission or send it back with reviewer notes — without losing any earlier version.

Reviewed AdminVertiqa 1.74.4+

The review page is where a submission from the client portal gets a decision. Open it from any row in the Form requests tab of the portal console. Back to Portal Settings takes you back to the console.

The review page for Q4 onboarding assessment, status Submitted, for Priya Raman on the Client onboarding questionnaire, due Oct 27, 2026, with the answers grouped under About your business and Your project on the left, and Reviewer Notes, Approve, Request Changes and a Version History of Version 2 and Version 1 on the right.
Version 1 carries a marker because it was sent back with notes.

Layout

  • Header: the request title, its status, the portal user (with portal access removed if you've since removed them), the template, the due date, and the message you sent with the request.
  • Answers (left): the submitted answers, read-only, in the template's order and grouped by section or step. Choices show their labels, so a multi-select reads ERP, CRM. Each field has a flag button.
  • Reviewer panel (right): Reviewer Notes, a Flagged Fields list once you flag something, Approve and Request Changes, and the Version History.

A request the client hasn't submitted yet says "This form hasn't been submitted yet", and the panel reads "Awaiting submission from portal user."

Review it

  1. Read the answers. Select a version in Version History to see an earlier attempt; a banner says which version you're viewing, with View latest to return.
  2. Write Reviewer Notes for anything the client should know: what to fix, or a document to attach next time.
  3. Select Approve for a clean submission, or Request Changes to send it back.

Approve and Request Changes appear only while you're looking at the latest version of a request that is waiting for review.

The flag button on a field marks it for the client and opens an optional note for that field; the field joins the Flagged Fields list. Select the flag again to remove it. When you select Request Changes, every flagged field is sent: the client sees it outlined, with your note under it, or "Your reviewer flagged this field. Please check it." if you left the note empty.

What each decision does

  • Approve marks the submission reviewed, records who reviewed it, and closes the request as Approved. The answers stay on the request; they aren't copied onto the contact or opportunity, so make any record updates yourself.
  • Request Changes reopens the form for the client with their previous answers filled in, your reviewer notes at the top, and your flagged fields outlined. Their correction comes back as a new version, and nothing is overwritten.

Versions

Every submission is numbered. Open an earlier version to compare what changed between attempts. The client sees the same history, with the reviewer notes you left on each version.

Tip

Be specific. "Wrong date" is hard to fix; "The start date should be when your team is available, not the contract date" gets it right the first time.

Learn more about the client portal →