What is the difference between a note and a flag in a lease abstract?

A note is free text added by an analyst to provide context, explain an interpretation, or record a non-standard provision. It is visible to anyone reading that specific record but is not structured data and cannot be queried, sorted, or included in portfolio-level reporting. A flag is a structured field value, typically a boolean or a tag from a defined taxonomy, that marks a record as requiring attention on a specific dimension. Flags can be filtered across a portfolio to identify all leases with a specific risk. Notes cannot. When a note contains information with operational consequences, converting it to a flag preserves its value at the portfolio level.

How do I identify which analyst notes contain CAM risk information worth flagging?

Look for notes that contain any of the following: specific numbers, percentages, or timeframes related to expense recovery (management fee capped at 3%, controllable expenses only, 90-day objection window); limiting language that qualifies a standard field (subject to gross-up at 95%, denominator excludes anchor tenant space); consequence language that overrides a default assumption (binding unless disputed within 60 days, final and conclusive after statement delivery); or language that explicitly contrasts with standard market terms (notwithstanding the above, management fees shall include corporate overhead). These phrases signal that the note carries structural significance, not just contextual color.

What should happen to the note once it is converted to a flag?

The note should remain in the record as context for the flag. The note explains where the language came from, what clause it modifies, and why the flag was set. The flag is the queryable signal; the note is the supporting documentation. Deleting the note after creating the flag removes the audit trail that connects the flag to its source provision. The correct approach is to retain both, with the flag providing the structured searchability and the note providing the interpretive context.

How often do analyst notes contain CAM-relevant information that was not also captured in structured fields?

Based on patterns described in lease administration and abstraction workflow documentation, it is common for 20 to 40% of NNN lease abstracts in a typical portfolio to contain analyst notes that include expense-relevant information not reflected in the primary structured fields. This is particularly common for provisions captured in riders or exhibits that were abstracted after the main body, for amendments that modified specific expense terms, and for non-standard definitions that the template fields could not fully accommodate.

Can note-to-flag conversion be automated?

Partially. Pattern matching on common note phrases, such as "subject to gross-up," "management fee capped," "final and binding," or "controllable expenses only," can flag records for human review. Full automation is not appropriate because notes often require judgment to interpret correctly. A note that says "landlord represents that expenses are typically within controllable cap" describes a representation, not a lease provision, and should not generate the same flag as "controllable expenses capped at 5% annually." Pattern detection can identify candidates; a human reviewer should confirm the flag.

Lease Abstract Notes That Should Become CAM Review Flags

Analyst notes often contain the most operationally important information in a lease abstract. The standard fields capture what the template expected. The notes field captures what the template did not. For expense-heavy leases with non-standard provisions, rider overrides, or unusual definitions, the notes field frequently holds the exact language that determines whether a CAM review is worth running and whether a challenge would succeed.

The problem is that notes are invisible to any workflow that depends on structured data. They cannot be filtered, queried, or included in automated triage. When a note says "management fee capped at 3% of gross revenues per rider," that information exists in the record but does not appear in the management fee cap field, which remains blank because the template did not prompt the analyst to populate it for a rider-based provision.

This article covers the common note phrases that signal CAM risk, how to identify them, and how to convert them into structured flags that make the information actionable at the portfolio level.

Note Phrases That Signal Expense Recovery Risk

These phrases, when they appear in analyst notes, indicate that the note contains information with direct financial consequence for CAM compliance review.

"Subject to gross-up at [percentage]"

This phrase indicates that variable operating expenses are normalized to an assumed occupancy level. If this appears in a note but the gross-up provision field is blank or marked "not present," the note is correcting an omission in the structured fields. The correct response is to populate the gross-up fields and add a flag indicating a base-year-plus-gross-up combination.

Context that matters: the specific percentage (90% and 95% are common; higher percentages inflate the base year more), and whether the gross-up applies to all variable expenses or only specific categories like utilities and janitorial.

"Management fee capped at [percentage]"

This phrase indicates that the recoverable management fee has a contractual ceiling. If the management fee cap field is blank and this phrase appears in the notes, the cap was captured in the wrong place. Populate the management fee cap field with the stated percentage and add a flag for management fee cap present.

Context that matters: whether the cap is expressed as a percentage of operating expenses, a percentage of gross revenues, or a fixed dollar amount, because each produces a different cap ceiling for any given year.

"Controllable expenses only" or "controllable expenses subject to cap"

This phrase signals that the expense cap applies to a specific subset of costs. If the cap rate field is populated but the controllable categories field is blank, this note is pointing to a structural gap in the abstraction. The reviewer who reads only the cap rate will not know which expenses it covers.

Context that matters: what the lease defines as controllable. If the note does not include the category list, the source clause must be consulted to identify which categories belong on each side of the line.

"Binding unless disputed within [number] days"

This phrase appears in notes when the analyst identified final-and-binding language but the consequence-of-silence field is blank or the dispute deadline was recorded without its consequence. This is a high-priority conversion because the consequence of missing the deadline is permanent and irreversible.

Context that matters: the number of days, the trigger event (delivery of statement, end of lease year, etc.), and whether the binding provision applies to each year's statement independently or accumulates across the tenancy.

"Denominator excludes [anchor/type of tenant/specific building]"

This phrase indicates that the denominator is not the total rentable area but a subset from which certain tenants or buildings are excluded. If the denominator description field shows only a percentage without capturing the exclusion, the allocation basis is not fully documented.

Context that matters: which tenants or spaces are excluded, whether the exclusion is permanent or contingent, and whether the exclusion can change if the anchor tenant's space is released to other tenants.

"Notwithstanding the above, [provision that overrides standard language]"

This phrase pattern is common when a rider or addendum modifies the main lease body. The "notwithstanding" construction signals that the following language supersedes whatever appeared earlier. When this appears in a note, the note is documenting an override that should be reflected in the primary fields.

Context that matters: what specific field or provision the override affects. A note that says "notwithstanding Section 7.3, management fees shall be capped at 3% per the Rider" requires both updating the management fee cap field and adding a source reference to the rider rather than Section 7.3.

"Per amendment dated [date]"

This phrase indicates that a field value was derived from an amendment rather than the base lease. If the primary field shows the amended value but there is no source reference or amendment currency note, the note is the only evidence that the value was amended. Adding an amendment currency flag and an effective date field ensures downstream reviewers know the value may differ from earlier periods.

Context that matters: the effective date of the amendment, which determines which reconciliation periods use the original value versus the amended value.

"Auditor restricted to [CPA/non-contingency/specific requirements]"

This phrase documents auditor restrictions that belong in the structured audit-right fields rather than in notes. If the audit right is marked as present but the auditor restrictions field is blank, the note is carrying operational information that should be a structured field.

Context that matters: specifically whether contingency-fee arrangements are prohibited, because this affects the practical economics of exercising the audit right.

How to Run a Note Audit

A note audit is a targeted review of all analyst notes in a portfolio to identify phrases that should become structured flags. The process has three steps:

Step one: extract all notes fields from the portfolio dataset. For large portfolios, this may require a data export. For smaller portfolios, it can be done by opening each record systematically.

Step two: scan for the phrase patterns above. Pattern matching can be done manually for small portfolios or with text search tools for larger ones. The target is any note that contains quantitative terms (percentages, dollar amounts, day counts), limiting language (capped at, subject to, controllable only), or consequence language (final, binding, conclusive, deemed accepted).

Step three: for each note that matches, determine whether the information is already captured in a structured field. If yes, verify the structured field matches the note and add a source reference if missing. If no, create or populate the appropriate structured field and set the relevant review flag.

The note audit is not a one-time exercise. New notes are added whenever abstracts are updated for amendments or catches. Building note-to-flag conversion into the QA workflow ensures that new notes with operational significance are converted when they are created rather than discovered during a later audit.

What Structured Flags Enable

Once note-based information is converted to structured flags, several downstream capabilities become possible:

Portfolio-level risk filtering: identify all leases with a management fee cap flag, all leases with a final-and-binding flag, or all leases with a base-year-plus-gross-up combination.

Automated pre-screen triggers: flag any reconciliation from a lease with a final-and-binding flag as requiring expedited review given the permanent consequence of inaction.

Consistent QA checks: a structured flag can be included in QA checklists and confirmed against the source clause during the QA pass. A note cannot be checked systematically.

Client reporting: a summary of which leases in the portfolio carry specific risk flags provides an advisory deliverable that is grounded in structured data rather than a manual review of each record.

For lease abstraction firms that want to add advisory value without significantly increasing per-lease review time, note-to-flag conversion is one of the most efficient ways to extract additional value from work already completed. The notes exist. The information is there. Converting it into structured fields costs time once and pays dividends every time the portfolio is reviewed, filtered, or reported on.

Firms applying this guidance can run a free audit through CAMAudit to verify how the detection engine handles these clauses on a real reconciliation statement.

Lease Abstract Notes That Should Become CAM Review Flags