Provency Preview · not yet live

Provency

Property management with proof built in.

The repair that never happened. The deposit itemized after the dispute started. The owner who finds out last.

Vendor credentials are checked at assignment. Overrides leave a written record.

Every dollar, message, and repair, on the record. That’s the product.

This is a preview. Provency isn’t open yet. Every screen on this page is the real application, running on sample data: no real people, properties, or money.

Why it exists

When someone asks what happened, show them the record.

Provency keeps records that an owner, tenant, or reviewer can trace back to the work, payments, and decisions behind them.

“The repair was done.”

It wasn’t, or it was done by someone unlicensed, and there’s no independent record either way. In Provency, a ticket cannot close without photographs and an invoice, and a vendor without current licence and insurance cannot be sent without a written reason the owner sees.

“Nobody has been in the home.”

And the manager’s own messages say otherwise. Here, every entry is scheduled, the tenant is notified in advance, and the visit is recorded on the timeline.

“That itemization was written at move-out.”

It was dated to look that way after the dispute started. Provency flags backdated entries and tracks the deposit deadline from the day the tenant hands back the keys.

“Everything’s fine.”

An owner three states away usually hears this from the one person with every reason to shade the answer. Here, the owner sees the same live ledger, tickets, and site visits that the manager sees.

How the proof works

A record that can’t be quietly edited, including by us.

Every change in the system is written to a log that can only be added to. Payments, ticket steps, messages, signatures, and deposit deductions all go there. Each entry carries a fingerprint (a SHA-256 hash) of its own content plus the entry before it. Change or backdate one entry, and every fingerprint after it stops matching.

Chain intact. Anyone with access can re-check every link, at any time, from the timeline page. (Shortened hashes, from the sample ticket below.)

Enforced by the database

The application connects as a database role with no permission to update or delete history. Corrections are new entries labelled as corrections; the original stays.

Documents are fingerprinted too

Photos, invoices, and leases are hashed when they’re uploaded. A signature records the exact hash of the document signed, so any later edit shows.

One-click evidence packet

Export the timeline and evidence for a supported record as a structured JSON packet for independent verification.

Walkthrough

One system, four people looking at it.

The property manager runs it, the owner watches it, the tenant lives with it, and an applicant meets it first. Pick a seat. Every screenshot below is the working application; scroll inside a screen, or click it to open it full size.

One place to run every client’s properties. The audit trail builds itself from the normal day’s work; nobody has to remember to keep it.

01

The day starts with one queue

New applications and open repairs sit together, each with its priority and response deadline. A ticket that stalls past its deadline escalates on its own and tells the owner.

  • Emergency 4 h · Urgent 24 h · Routine 72 h
  • Applications show who has and hasn’t heard back
provency.app/admin
02

A vendor without papers can’t be sent quietly

Licence and insurance are checked at the moment of assignment, not when the vendor was first added. Choose someone whose documents are missing or expired and the system says so in red.

You can still send them, but only with a written reason. The reason is recorded on the work order and shown to the owner permanently.

provency.app/admin/tickets/…
03

No proof, no close

A ticket only closes with completion photos and a line-item invoice attached. Each file is fingerprinted on upload. Once a ticket is closed, nothing more can be recorded against it; a correction is a new ticket, not an edit.

provency.app/admin/tickets/…
04

The timeline that checks itself

Every ticket, lease, and payment has a timeline: who did what, when, in order, each event linked to the one before. The page re-verifies the whole chain every time it opens, and one button exports it as an evidence packet.

provency.app/timeline/ticket/…
05

One trust ledger per owner

Each owner’s money is kept in a ledger of its own. The database makes it structurally impossible to pay Owner B out of Owner A’s balance.

Money that has been submitted but hasn’t cleared stays visibly separate, because an ACH payment that later bounces was never the owner’s money.

provency.app/admin/owners/…
06

The lease, start to finish

Send the lease for signature, record payments, add tenants, and walk the inspections, all from one page.

Recording the day the keys came back starts Georgia’s statutory deposit clock from that date, not from whenever someone got round to typing it in.

provency.app/admin/leases/…
07

Every applicant, every decision, every reason

Everyone who applies is recorded, not just the person chosen. A decline must name the published criterion it failed, or the database refuses it.

Identity is confirmed before any consumer report is ordered, so nobody is turned down on a report about somebody else.

provency.app/admin/units/…/applications
08

Screening criteria, published and versioned

The written standard every applicant is judged against. Applicants read it before they pay anything. Publishing a new version leaves the old one intact for decisions already made under it.

provency.app/admin/screening
09

Vendors, checked again at every assignment

Licence numbers, insurance policies, and their expiry dates. A blank date counts as missing, not as valid: the system won’t guess.

provency.app/admin/vendors
10

Year end, worked out from the ledgers

Who is owed a 1099, and what is missing before one can be filed. Payees fill in their own W-9s, and taxpayer numbers are encrypted before they’re stored.

Every ledger exports as CSV, QIF, or OFX for QuickBooks, Quicken, or an accountant.

provency.app/admin/year-end
11

Properties, and everything about the house

Units and leases, the association, warranties and service contracts, and local utility providers, so the tenant gets the right phone numbers on day one.

provency.app/admin/properties/…
12

Listings, and who the firm is

Vacancies go on the firm’s own site, with the screening criteria alongside, so applicants can decide before they spend anything. The firm’s licence and contact details are published too, which makes a scam copy of a listing easy to spot.

provency.app/admin/listings

At launch

What’s built, what’s being connected, and what comes next.

Provency launches with one firm, in Georgia, before it opens to other firms. Here’s where each piece stands.

Built working in the application today Connecting built, waiting on a live provider Next after launch
Built

Tamper-evident event log

Hash-chained, insert-only at the database level, re-verified on every timeline view.

Built

Verified maintenance

Submitted → triaged → assigned → scheduled → on-site → proof → review → closed. Response deadlines, escalation, mandatory proof.

Built

Vendor compliance gate

Licence and insurance checked at assignment. Overrides need a reason the owner can see.

Built

Per-owner trust ledgers

No commingling, enforced in the database. Pending kept apart from cleared. Disbursements and reconciliation.

Built

Owner portal & weekly digest

Live ledger, maintenance, site visits, inspections, document vault, tax details.

Built

Tenant portal

Lease, requests with photos, visit notices, lock log, utilities, payments, documents.

Built

Leases & e-signature

Every signature tied to the document’s fingerprint, with E-SIGN consent and an option to withdraw.

Built

Move-in, move-out & deposits

Photographed inspections with the tenant’s right of reply. Georgia’s deposit clock starts when the keys change hands.

Built

Applications & published criteria

Versioned criteria. Declines must name a criterion. Identity confirmed before a consumer report.

Built

Entry notices

Every scheduled entry notifies the tenant in advance; the notice and its acknowledgement are on the record.

Built

Year end

1099-MISC and 1099-NEC worked out from the ledgers, payee-completed W-9s, CSV/QIF/OFX exports.

Built

Security & backups

Taxpayer numbers and applicant income documents are encrypted at rest.

Connecting

Rent payments

Runs through Stripe Connect, so a licensed processor holds the money and Provency keeps the record. Working in test mode.

Connecting

Smart-lock one-time PINs

Single-use, time-boxed codes per visit; the lock itself becomes a witness. igloohome and Seam adapters to wire.

Connecting

Identity & income checks

Stripe Identity for ID, Truv for employer-verified income, Snappt for document forensics.

Connecting

Evidence packet as PDF

The export works today as structured data; packaging as a PDF binder is in progress.

Next

Lease renewals

Guide tenants through renewing a lease in the portal.

Next

More states, more firms

State rules are stored as data, so adding a state means configuration, not a rewrite. Opening to other firms comes after.

Georgia first

The law is data, not a guess.

State rules are kept as data in their own table, not buried in code. Georgia’s deposit deadlines, escrow handling, and inspection requirements are loaded first. The system counts the days and warns before a deadline, so the firm doesn’t find out after a forfeiture.

Deposit returned or itemizedO.C.G.A. § 44-7-34
Deposit held in escrow, location disclosed§ 44-7-31
Move-in list of existing damage§ 44-7-33
Move-out inspection within 3 business days§ 44-7-33
Trust account conduct for licenseesGREC rules
Entry notice where the statute is silentlease terms govern