Signage rights are a small part of most leases and a disproportionate source of late surprises. A tenant negotiates building-top identity as part of a headquarters deal, the right arrives in a rider with several pages of conditions, and the abstract records that signage is permitted. The conditions, the exclusivity threshold, the maintenance standard and the removal obligation are not captured, because the abstraction template has no field for them.
Three things then tend to happen over the life of the lease. The tenant contracts its footprint for cost reasons and drops below the occupancy threshold that its exclusivity depended on. The illumination and maintenance obligations go unattended until the landlord raises them. And at expiry, a removal and restoration cost arrives that nobody budgeted, at the same moment as every other exit expense.
For a landlord the failure mode is different but related: signage rights granted across successive leases that overlap, discovered when a new tenant asks to install on a location already exclusively committed. In both directions the remedy is the same, which is to abstract the rider properly and hold its conditions as fields.
The data worth holding as fields
Five field groups capture what a signage rider actually commits both parties to, and each one supports a check that is otherwise never performed.
- Sign type and location, the permitted signage by type and specific location, with dimensions and illumination parameters as stated in the rider or approved drawings.
- Approval and permit status, landlord design approval, approved drawings on file, the municipal permit and its expiry or renewal requirement where applicable.
- Exclusivity and conditions, the scope of exclusivity, the occupancy or area threshold it depends on and the consequence of falling below it.
- Maintenance and utility duties, repair and appearance standards, illumination hours, who pays for power and the response window for a failed sign.
- Removal and restoration, the removal deadline after term end, the restoration standard required and any security or estimated cost held against it.
None of these fields is exotic, and all of them are readable from the rider in a few minutes. The reason they are missing from most abstracts is simply that the template never asked for them, so an abstractor working to a standard field list records the existence of a signage right and moves on. The fix is therefore upstream: extending the template once means every subsequent abstraction captures the conditions, and only the existing portfolio needs a remedial pass.
An occupancy threshold that supports signage exclusivity should be re-checked every time the demised area changes. A give-back negotiated to reduce rent can forfeit building identity worth considerably more than the saving, and the two decisions are usually made by different people.
The checks each field supports
Five recurring checks turn the abstracted fields into something that prevents a surprise rather than merely recording one.
- Approval and permit currency. Confirm approved drawings are on file and any permit remains current. Signs installed to drawings that were never formally approved are a recurring finding at building sale or refinancing.
- Exclusivity threshold against demised area. Re-run whenever space is added or surrendered. This is the check that prevents a quiet forfeiture, and it takes a query rather than a review.
- Landlord register of granted rights. For owners, maintain granted signage rights by location and check it before any new grant. Overlapping exclusivity is easier to avoid than to unwind.
- Maintenance compliance. Track illumination and appearance obligations against the standard in the rider. A landlord notice about a dark sign is easier to pre-empt than to answer.
- Removal cost accrual. Estimate the removal and restoration cost, hold it as a field and revisit it periodically. The cost belongs in the exit budget from the outset rather than in a variance report afterwards.
A five-step implementation path
Step 1, Find the riders
Identify every lease with a signage rider or exhibit. In portfolios abstracted to a standard template these are frequently unflagged, so a document search for signage terms is usually more reliable than filtering the abstract.
Step 2, Extend the abstraction template
Add the five field groups to the template so future abstractions capture them by default. This is a one-time change that stops the problem recurring on every new lease.
Step 3, Abstract the existing riders
Work through the identified leases capturing conditions, thresholds and removal terms. Prioritize the leases with prominent exterior identity, where both the value and the removal cost are largest.
Step 4, Estimate and hold removal costs
Obtain indicative removal and restoration estimates for the significant signs and record them against the lease. Even a rough figure changes the exit budget conversation materially.
Step 5, Wire the exclusivity check into space decisions
Make the threshold check part of any give-back or sublease approval. The check is trivial; the point is that it happens before the decision rather than after.
See rider obligations abstracted
Walk through signage field capture, exclusivity checks and removal accrual on a live lease portfolio.
Riders are where lease obligations hide
Signage is one example of a broader pattern: the obligations that cause late surprises tend to live in riders and exhibits rather than in the lease body, because that is where the negotiated specifics end up and where standard abstraction templates stop looking. Parking allocations, storage licences, rooftop and antenna rights, generator and fuel arrangements, and after-hours service terms all behave the same way. Extending the abstraction template once, and re-abstracting the riders for the leases that matter most, addresses the whole category rather than one clause within it. The test for whether a rider needs abstracting is simple: does it create a duty that falls due on a date, depend on a condition that can change, or generate a cost at exit. Signage does all three, which is why it is the useful worked example. The vendor-side equivalent is covered in CRE vendor service contracts and CAM recovery control, and the same field discipline underpins lease lifecycle management generally.
Signage obligations and when each one bites
The table below sets out the obligations a signage right creates for each party and the moment at which each is tested.
| Obligation | Owner | When it bites | Evidence to hold |
|---|---|---|---|
| Design approval and permit | Tenant, landlord cooperates | Before installation | Approved drawings, permit, landlord consent letter |
| Exclusivity threshold | Tenant to monitor | On any space change | Demised area record against stated threshold |
| Maintenance and illumination | Tenant, unless stated otherwise | Continuously; on landlord notice | Service records, repair response times |
| Landlord non-grant of conflicting rights | Landlord | On any new lease | Register of granted signage rights by location |
| Removal and restoration | Tenant | At term end, stated deadline | Removal completion evidence, restoration sign-off |
Signage is a minor clause with a major tail. The exclusivity that made the deal attractive depends on a threshold nobody checks, and the removal obligation arrives with the rest of the exit costs. Both are handled by the same modest change: extend the abstraction template, capture the rider conditions as fields, and put the removal estimate and the threshold check where somebody will see them. The same pass usually turns up two or three signs installed without documented landlord approval, which is far easier to resolve during a quiet abstraction exercise than during a building sale, when the buyer’s counsel is the one asking and the answer affects a price.
For related guidance, see Lease abstraction that holds up under ASC 842, ASC 842 and IFRS 16, the lease data auditors test and Lease expansion option tracking.
