Contract review & approval portal for legal teams

A contract lifecycle portal is where contract owners submit agreements for legal review, legal approves or rejects each one with a reason on the record, and a reminder goes out before a contract renews.

Pattern: Requests

Describe it to Pory

“Our team leads send vendor contracts to legal before anything is agreed. Legal approves or rejects each one, and we want a reminder before any contract renews.”

Viewing as

Contracts

Contracts to decide

Submitted2
Legal review2
Changes requested1
Approved1
Active5
Rejected1
Powered by Pory

In plain English

How Pory sets it up

Pory gives every contract owner and legal counsel a sign-in of their own. Each contract owner sees only their own contracts. It covers draft → review → approve. Contracts, questions from legal, supplier invoices, templates and guides and legal team live in Pory's own database, so there's no spreadsheet to keep in sync.

What it does

01

Legal approves or rejects each contract, and says why on it

Contracts used to reach legal as forwarded email attachments, and approvals came back as "fine by me" with no note of what was checked. Legal counsel sees every contract on a board by status, opens one, reads the attached file and the owner's answers, and approves or rejects it, writing the reason on the record. The contract owner reads the answer on their contract instead of chasing legal in the hallway.

Approve / reject with a reasonDone by: Legal counsel
02

Legal hears about a renewal date before the notice period slips by

Auto-renewals used to be noticed on the credit card statement, a year too late to cancel. Each contract carries its renewal date and the date notice is due, and legal gets a reminder in their portal inbox and by email before it arrives, naming the contract and the date. There's time to renegotiate or give notice, instead of another year of a tool nobody opens.

Notifications & remindersDone by: Legal counsel

Who sees what in a contract lifecycle portal

Every person signs in to their own view. This is what each role in the demo gets.

Contract owner

Sees only their own contracts.

Pages
Home, My contracts, Questions from legal, Renewals, Legal playbook
Can start
Send a contract to legal, Send an answer or a document

Legal counsel

Sees every contract in the portal.

Pages
Home, Contracts, Renewal calendar, Active contracts, Questions to owners, Templates
Decides
Marks contracts Approved or Rejected, with a reason

What’s in the contract lifecycle portal template

The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.

Contracts

  • Contract (text)
  • Counterparty (text)
  • Type (choice: SaaS subscription, Services agreement, NDA, Lease)
  • Renewal date (date)
  • Annual value ($) (number)
  • Contract owner (link)
  • Contract file (file)
  • Status (choice: Submitted, Legal review, Changes requested, Approved, Active, Rejected)
  • Give notice by (date)
  • Sent to legal (date)
  • Legal notes (long text)

Questions from legal

  • Question (text)
  • Contract (link)
  • Answer by (date)
  • Kind (choice: Question, Document)
  • Your answer (long text)
  • File (file)
  • Contract owner (link)
  • Status (choice: Requested, Answered, Checked)

Supplier invoices

  • Invoice (text)
  • Contract (link)
  • Received (date)
  • Amount ($) (number)
  • Status (choice: Received, Approved to pay, Paid, Queried)
  • Contract owner (link)

Templates and guides

  • Template or guide (text)
  • Kind (choice: Template, Guide, Policy)
  • Updated (date)
  • File (file)

Legal team

  • Name (text)
  • Role (text)
  • Email (text)

The parts behind this portal

Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal

Decide

2 parts
  • Approve / reject with a reason

    Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

  • Reminders by date

    Renewals, expiries and overdue work, in an in-app inbox and by email.

Control

3 parts
  • Who sees which records

    Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.

  • Passwordless sign-in

    A sign-in link by email, by default. Password sign-in if you'd rather.

  • Your brand

    Your domain, your colors, your logo. Members see you.

Frequently asked questions

A contract owner signs in with a link sent to their email and lands on Home. They see Home, My contracts, Questions from legal, Renewals and Legal playbook, and only the contracts that are theirs. From there they can use “Send a contract to legal” and “Send an answer or a document”.

Legal counsel decide: they mark each one Approved or Rejected and give a reason. Everyone else sees the decision and the reason on the record, without the buttons to change it.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your contract lifecycle portal with Pory

Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited contract owners.

See pricing · How Pory builds a portal