FlareForgeDocs

Mandates overview

The Mandates module tracks your active commercial mandates — formal agreements where you have been engaged to sell, lease, or trade an asset on behalf of a principal. It gives you a live view of your mandate pipeline value and estimated fee income.

Interactive demo — read only
Mandates

Total Pipeline

$125.4M

Est. Fees

$1.45M

MandateTypeFee StructureExpiryEst. Fee
Atlas Air — 737 FleetSaleSuccess 1.5%2026-09-30$276,000
Avolon — A320 PackageLeaseRetainer $8,000/mo + 0.75%2026-12-15$96,000+
Air Lease — Widebody BlockSaleSuccess 2.0%2026-07-01$1,080,000

What is a mandate?

A mandate is a formal engagement with a principal (asset owner or buyer) to represent them in a transaction. In aviation trading and brokerage, mandates typically define:

  • Which asset(s) you are mandated on.
  • What type of transaction you are pursuing (sale, lease).
  • Your fee structure (success fee, retainer, or both).
  • The mandate expiry date — after which you are no longer engaged.

FlareForge tracks all of this and alerts you when mandates are approaching expiry.

KPI header

At the top of the Mandates page, two headline metrics:

  • Total Mandate Pipeline — The sum of all asset values across active mandates.
  • Estimated Fees — The total estimated fee income if all mandates transact successfully.

Both figures update immediately as you add or edit mandates.

Mandate list

Each mandate record shows:

FieldDescription
Mandate nameDescriptive name (e.g. "Atlas Air — 737 Fleet Sale")
TypeSale or Lease
Asset(s)Aircraft or engine(s) covered
PrincipalWho engaged you
Fee structureSee Fee structures
Expiry dateWhen the mandate expires
StatusActive, Expiring (within 30 days), Expired
Estimated feeYour projected fee income from this mandate

Expiry alerts

Mandates with an expiry date within 30 days are flagged as Expiring and appear in the Critical Dates feed. This gives you time to negotiate an extension before the mandate lapses.

Linking mandates to deals

A mandate can be linked to one or more deals. This is useful when a single mandate covers a transaction that exists as a deal in your pipeline. Linking keeps the two records in sync — deal status changes are visible from the mandate record.