Platform

From an approved loan to a cleared draw.

Seven steps. Each one exists because something has to be provable at that point, and each one refuses to proceed when it is not.

1

Project created

Your system posts an approved loan — your loan reference, the borrower, the contractor, the amount, the property, and how the draws should be structured. Renny refuses the project if that contractor is not actively enrolled in your program, because merchants originating without vetting is the finding these consent orders turn on.

2

Scope agreed before work starts

A scope of work is a list of line items, each with a description and an amount. Both parties agree it before work begins, and it is then frozen as a signed version. Exclusions and allowances are recorded explicitly, so “that was never in the price” has an answer that is not a memory.

3

Draw requested against the scope

A draw claims a percentage of completion per line item rather than a lump sum. Cumulative completion per item cannot exceed 100%, so nobody can be billed twice for the same work.

4

Evidence captured

Photographs and documents attach to the specific line item they evidence, not to the draw as an undifferentiated bag. The set relied upon is sealed with a fingerprint, so it can be identified again years later.

5

Both parties attest, and the release is authorized

The contractor and the homeowner each sign independently. Renny records what document each of them saw, when, from where, and how they authenticated. Only then can a release authorization exist — and only if every check on the previous page passes.

6

You disburse

Your system is notified the moment the release is authorized. You pay on your own rails, on your own schedule, and pass back your payment reference.

7

The record closes

Renny records the movement it was told about against the authorization that permitted it. That ledger is append-only: a correction is a reversing entry, and the original stays visible.

Scope and change orders

Where most exposure actually appears

A funding limit is set per contractor across every project they hold, not per project. Exposure accumulates, so five modest draws cannot arrive at a number one large draw would have been refused for.

The scope grows after the loan closes and nobody tells the lender. Renny treats that as a first-class event rather than a note in a file.

A change order is a new agreement

  • It creates a new agreed version; the previous one stays exactly as it was signed
  • The homeowner approves every one, in plain terms, before work continues
  • You approve once a project’s cumulative growth passes the threshold you set
  • Draws re-derive from the new version, and work already completed is not double-counted
  • The chain from the original scope to today is reconstructable at any date

Limits belong to the contractor, not the project

A contractor’s funding limit applies across their whole book with you, not job by job. Every open project counts against the same limit, so exposure cannot be spread across several small jobs to stay under a per-project cap.

The limit is set by underwriting and revisited on a schedule, not fixed at approval. Standing is recomputed from the record already held, so it reflects how a contractor has behaved rather than how they looked on the day they were onboarded.

Contractors whose scopes consistently grow after signing surface as a pattern, not as unrelated change orders.

In the product

What your team actually looks at

A held draw shows the specific check that failed and what would clear it. Nothing sits behind a status word that requires a phone call to interpret.

rennyai.com/app/dashboard
Renny
Dashboard Projects Draws Contractors Evidence Audit trail Reports

Operations overview

Everything waiting on a person today, across your programs

24Draws awaiting attestation
6Blocked — evidence incomplete
3Open resolution requests
2Credentials expiring in 30 days
ProjectContractorDrawStatus
PRJ-4182
Kitchen remodel
Cedar Point Builders2 of 3 · $18,400Cleared
PRJ-4176
Roof replacement
Blue Ridge Exteriors1 of 2 · $12,750Awaiting homeowner
PRJ-4168
HVAC replacement
Northgate Mechanical2 of 2 · $9,300Over limit
PRJ-4155
Bathroom remodel
Fairview Home Services3 of 3 · $7,120Dispute open
PRJ-4149
Window replacement
Union Park Renovations1 of 2 · $21,050Cleared
rennyai.com/app/projects/PRJ-4176/draws/1
Renny
Dashboard Projects Draws Contractors Evidence Audit trail Reports

Draw 1 of 2 · $12,750

PRJ-4176 · Roof replacement · Blue Ridge Exteriors

Scope line itemAgreedClaimedEvidence
Tear-off and disposal$3,200100%4 photos
Decking repair$1,850100%3 photos
Underlayment and shingles$9,40060%6 photos
Gutters$2,1000%Not claimed

Release checks

Contractor attestation — completeD. Okonkwo · 14:02 UTC · document a3f1…9c2e
Homeowner attestation — pendingSent to M. Delgado · reminder due in 18 hours
Training currentCertificate TC-78C6A4E5 · expires 28 Jul 2027
Inside funding limitOpen exposure $34,200 of $60,000 across 3 projects
No open dispute on this projectChecked at request time

Release cannot be authorized until the second attestation exists. This is refused by the database, not by this screen.

rennyai.com/app/projects/PRJ-4155/audit-trail
Renny
Dashboard Projects Draws Contractors Evidence Audit trail Reports

Audit trail

PRJ-4155 · hash-chained, append-only · 41 events

project.createdLender integration · loan ref HL-88213 · 7c1a…04bf
scope.agreedBaseline v1 · 9 line items · $7,120 · both parties signed
change_order.raised+$980 tile substitution · homeowner approved 11:40 UTC
scope.agreedBaseline v2 supersedes v1 · v1 retained unchanged
evidence.sealedPack EV-4410 · 11 photographs · seal b8e2…71d9
attestation.signedcontractor · 203.0.113.9 · password + session
attestation.signedhomeowner · 198.51.100.24 · password + session
release.authorizedRA-8F31C0 · all six checks passed
complaint.raisedHomeowner · grout finish · pending releases paused automatically
complaint.resolvedRework agreed · 4 days 6 hours · releases resumed

Each event carries the hash of its predecessor, so a removed or altered event breaks the chain visibly.

rennyai.com/app/contractors/applications
Renny
Dashboard Projects Draws Contractors Evidence Audit trail Reports

Contractor onboarding

Activation is refused while any blocker remains — and the blockers are listed, not implied

ApplicantStageLicenceStanding
Redstone Remodeling
General · TX
Checks runningTX-104-8823712 blockers
Lonestar Contracting
Roofing · TX
TrainingVerified1 blocker
Copperline Construction
General · OH
ApprovedVerifiedTier 1 · active

Redstone Remodeling — outstanding

Training not completeAuthorization and consent · 3 of 5 lessons read
Insurance certificate expires in 11 daysRenewal requested 24 Jul · contractor notified
Licence verifiedTX-104-882371 · expires 31 Mar 2028
Application completeSubmitted 18 Jul · 4 principals recorded

Illustrative interface with demo data. These are rendered from the product’s own design system rather than being photographs of a screen, and the projects, contractors and amounts shown are fictional. Ask for a live walkthrough of your own book.

Merchant lifecycle

Vetted before they can participate, watched after

Onboarding

Invitation, application, licence verification with a tracked expiry, and program enrollment. Activation is refused while any blocker remains, and the blockers are listed rather than implied.

Training

A curriculum per program. Lessons carry full transcripts so they can be read as well as watched. The assessment is scored server-side, every attempt is kept, and passing issues a certificate with an expiry.

Underwriting

A standing derived from the record Renny already holds — licence status, complaint history, change-order patterns, current exposure. Revisited on a schedule, with suspension and downgrade available immediately.

The training gate is yours to set

It is per program and off by default. Turned on, a release for an uncertified contractor is refused by the database. Certificates expire, and the gate re-closes when they do.

Enrollment is a gate, not a form

A merchant who has not been vetted cannot originate

Not “is flagged for review”. The release attempt fails, and it names what is missing.

Before they participate

Application, license with its expiry tracked, insurance, principals, and your program’s training requirement if you set one.

While they participate

A license that lapses, a dispute pattern, or scope behavior that stands out against their own history all surface without anyone running a report.

When something changes

A suspension takes effect on the next release attempt, not on the next review cycle. Limits are revisited on a schedule you control.

Disputes

A complaint program, not a complaints table

These consent orders require a program: something with a clock, an owner, a resolution, and a pattern view. Renny treats a resolution request as a workflow with consequences.

  • Raised by the homeowner, the contractor, you, or Renny
  • Acknowledged, with time-to-acknowledge and time-to-resolve both measured
  • Pending releases on that project pause automatically
  • Triaged with a priority and an owner; unassigned requests surface in an operations queue
  • Both parties heard, structurally rather than as a courtesy
  • Resolved with a reason, after which releases resume
  • Complaint history feeds the contractor’s standing and prompts re-underwriting

Why funding pauses

Money moving over an unresolved disagreement is exactly what creates the complaints that end in enforcement action.

So the pause is automatic and the resumption is automatic. It is not a favor to the borrower and it is not a punishment for the contractor — it is the behavior that keeps a disagreement from becoming a regulatory finding.

Documents and reporting

The artifacts your teams already ask for

Audit pack

Per project. Every signature, every fingerprint, every event in order.

Completion certificate

Per draw, from a template you control, recording exactly what was relied on.

Document library

Licences, insurance, signed documents, training certificates — scoped to what each party may see.

Report builder

Your own views over your own book, exportable, with schedules.

Generated documents are not stored, because a stored copy can drift from the record it describes. What is stored is the fact of issuance and the fingerprint of the exact bytes delivered — so years later you can confirm whether a copy someone produces is the copy Renny issued.

Ask us for the audit pack.

Pick a closed project. We will show you the document you would hand a regulator. If it does not answer the question, nothing else matters.