Pertava
Live · monitoring portals, inboxes, documents & systems

Project changes slip through the cracks. Pertava makes sure they don't.

Pertava autonomously catches every change across emails, documents, and the systems no one's watching, routes it to the right owner with the source attached, and follows up until it's resolved. No one chasing, nothing missed.

Request a demoSee the 60-sec workflow
Built with experience from
Microsoft AIInstacartTesla
The problem

A change buried in an inbox isn’t the risk. The one nobody owned is.

01
Caught

Nothing slips. Pertava watches portals, inboxes, documents, and systems for the changes that actually matter.

02
Routed

The right ask reaches the right owner — in Teams, Slack, email, or SMS — with context and source attached.

03
Proof

Every decision lands in a durable, audit-ready trail. Resolved, blocked, or ready-with-exceptions.

Product story

See it work, end to end.

One vendor update becomes team-specific review items with evidence attached. Pertava catches the signal, reaches the right owner, and leaves a verified trail.

pertava.app / review / SJ-2047
AI review packet · 5 items

Updated Packet — SJ-2047

CedarFlow Services · Riverbend Service Site · 8:12 AM
Finance / APHold applied

Invoice exceeds PO by $4,850

INV-8842 · PO-3119
ProcurementDecision owed

PO variance requires approval

PO-3119 · blocks AP payment
Compliance / HSEDocument owed

Safety acknowledgement missing

Packet p.4 · blocks site access
OperationsApproved

Part ETA changed — date confirmed

Service note · SJ-2047
First workflow

Built for project changes first.

Capture the change, understand who it affects, route the exact ask to the right person, and know it's actually closed — before it turns into rework.

Step 1

Detect and register

The change is captured from email, a drawing revision, a portal, or a field update, and tied to the live project.

  • Revised drawingRegistered
  • Scope changeRegistered
Step 2

Triage what changed

Scope, drawing, schedule, pricing, and field changes are separated from noise.

  • Spec changeReview
  • Pricing impactReview
Step 3

Route and distribute

The right people — PM, field, subs, finance, legal — get the exact ask for their part, with the source attached.

  • Review ownerAsked
  • Affected subNotified
Step 4

Confirm and close out

Open items resolve into done, blocked, or ready-with-exceptions — so nothing slips and there's a record of what happened.

  • Field confirmationDone
  • Updated sub pricingBlocked
What Pertava watches

No single tool watches all the places a project change can land. Pertava does.

Email threads, drawing revisions, portal updates, internal messages, procurement systems, and spreadsheets — a project’s live state is scattered across every platform it touches. Today someone on your team is the integration layer: holding context in their head, manually checking each source, chasing what slipped. Pertava watches across the connected tools where changes actually land and routes what matters — so a human isn’t the glue anymore.

Pertava sits on top of Procore, Autodesk, or whatever system of record you already run — and watches the changes that land outside it, in email, portals, and threads, before they’re ever logged.

Pertava only connects to the sources you explicitly authorize, and only watches what you’ve given it access to — nothing more. You decide which tools it sees.

Email & inboxes

Vendor updates, client commitments, and scope clarifications buried in threads.

Drawing revisions & specs

Changed sections, revision clouds, and spec updates across project documents.

Project portals

Addenda, bid packages, and deadline changes from owner-managed systems and tools like Procore.

Teams & internal messages

Decisions, approvals, and context that live inside the channels you connect.

Procurement & ERP

Purchase order variances, vendor date shifts, and invoice anomalies in operational systems.

Spreadsheets & shared files

Schedules, trackers, and project documents where live project state quietly drifts.

Pertava connects to the tools where your project lives in writing — not every channel that exists, just the places where decisions and changes actually get recorded.

Integrations

How your team sees it in tools they already trust.

Pertava does not ask estimators, PMs, or subs to babysit another dashboard. It drops the right ask into Teams, email, Slack, or SMS with the context, deadline, and source trail already attached.

TeamsElectrical lead

Pricing impact captured

EmailConcrete sub

No-impact response logged

SMSBid manager

Deadline warning queued

How your team sees it

Search
Jordan Lee
iPertava is monitoring active bid deltas and addendum conflicts.Turn on+
Pertava Bot | Bid Alert...
Pertava Bot
Glazing spec no longer valid

Addendum 02 changed accepted glazing. GL-2 laminated is now GL-2A fire-rated laminated.

Project
Riverside Tower Renovation
Owner
Jordan Lee, Estimator
Due
Today, 10:00 AM
Source
Addendum 02 · Drawing A-402 · Spec 08 80 00
Open source trailUpdate estimateView bid impact
Jordan Lee
Jordan Lee

Does GL-2A change our glazing number or just the submittal note?

Pertava Bot

Treat it as pricing impact until confirmed. GL-2A is a different fire-rated laminated spec, so please update the glazing number or confirm no price change by 10:00 AM.

Search Riverside Build Co.
# bid-alertsRiverside Tower Renovation
Today
PertavaAPP 9:14 AM
Glazing spec no longer valid

Addendum 02 changed accepted glazing. GL-2 laminated is now GL-2A fire-rated laminated.

Owner
Jordan Lee, Estimator
Due
Today, 10:00 AM
Source
Addendum 02 · Drawing A-402 · Spec 08 80 00
Open source trailUpdate estimateView bid impact
Jordan Lee
Jordan Lee9:17 AM

Does GL-2A change our glazing number or just the submittal note?

PertavaAPP 9:18 AM

Treat it as pricing impact until confirmed. GL-2A is a different fire-rated laminated spec, so update the glazing number or confirm no price change by 10:00 AM.

Security & trust

Built for workflows where customer data and evidence matter.

The same follow-through loop that catches addenda can touch sensitive documents, emails, review packets, and proof trails — the data boundary stays explicit up front.

No training on customer data

Customer documents, emails, packets, and evidence are not used to train or fine-tune shared AI models.

Tenant isolation and audit trails

Customer workspaces are designed around tenant-aware access controls, least privilege, and audit-ready evidence.

Canada and US data residency

Pertava can align pilots to Canada or US data-boundary requirements, with private deployment conversations for sensitive workflows.

Read security details
FAQ

Common questions.

Pertava catches important changes across emails, documents, portals, and internal systems - like an addendum that changes a spec or an invoice that doesn't match the PO - figures out who needs to act and why, routes it to the right owner with the source attached, and follows up until it's resolved or flagged as still at risk.

No. Addenda are the first proof point because the workflow is concrete and high-stakes. The broader product is for any company promise, deadline, review, or obligation that needs an owner.

No. Pertava should meet people in Teams, Slack, email, SMS, and the systems they already use. The product is the follow-through loop, not another place to babysit.

Only the systems you choose. Pertava watches the tools and sources a customer explicitly authorizes — your email, portals, drawings, project channels, or whichever systems you want it to monitor — and nothing it hasn't been given access to. You stay in control of what it sees.

No. Pertava is designed so customer documents, emails, review packets, and evidence are not used to train foundation models. Customer context is used only to run the customer's workflow: detecting changes, routing review, tracking follow-up, and preserving evidence.

Pertava is designed to fit the customer's security and data-boundary requirements. We can start with secure cloud deployment where appropriate, and for sensitive operational or compliance workflows, we can support discussions around private cloud, customer-controlled storage, data residency, or on-prem deployment.

We follow up to schedule a demo, understand the workflow pressure you care about, and decide whether a narrow pilot makes sense.

Request a demo

Turn messy updates into reviewed actions.

We follow up to schedule a demo, understand the workflow pressure you care about, and decide whether a narrow pilot makes sense.

Request a demoSee the 60-sec workflow
Request a demo