How Do You Know When Your Revenue Management System Settings Need to Change?

You implemented a revenue management system.

The settings were configured.

Pricing went live.

Done, right?

Not exactly.

Revenue management systems are built to respond to changing conditions. That's one of their greatest advantages.

But the settings and parameters that guide the system also deserve periodic review.

A property changes.

A market changes.

Ownership objectives change.

A lease-up becomes stabilized.

Competitive conditions shift.

Operational strategies evolve.

And sometimes settings that made perfect sense when the system was implemented no longer support what the asset needs today.

That doesn't mean we should constantly change settings every time performance moves.

In fact, too much intervention can create its own problems.

The goal is to understand the difference between:

The system responding to changing conditions as designed

and

The strategy behind the system needing to change.

First: Don't Confuse a Pricing Outcome With a Settings Problem

This is important.

A Revenue Manager sees a price they don't like.

The immediate reaction may be:

We need to change the settings.

Maybe.

But not necessarily.

A price moving up or down doesn't automatically mean the system is configured incorrectly.

The system may be responding exactly as intended based on:

• Exposure

• Demand

• Leasing velocity

• Availability

• Lease expirations

• Competitive conditions

• Other inputs used by the platform

Before changing a setting, understand why the system produced the outcome.

Otherwise, you can end up changing the underlying strategy simply because you disagreed with one recommendation.

Settings Should Create Guardrails, Not Handcuffs

I think about RMS settings as strategic guardrails.

They help tell the technology:

Here's how we want to approach pricing.

Here's our risk tolerance.

Here's how we want to manage lease expirations.

Here's how much flexibility we're comfortable giving the system.

Here's how we want different inventory situations handled.

The specific settings vary by revenue management platform.

But the principle is the same.

Good settings give the technology room to work within the strategy of the asset.

Too restrictive, and the system may not have enough flexibility to respond effectively.

Too loose, and the results may move beyond what ownership or operations considers appropriate.

The goal is balance.

Implementation Settings Are a Starting Point

A lot of thought may go into configuring a revenue management system during implementation.

But implementation represents a moment in time.

The property may have been:

92% occupied.

In lease-up.

Offering six weeks free.

Recovering from operational issues.

Carrying significant exposure.

Entering peak leasing season.

Under a particular ownership strategy.

A year later, that same property may look completely different.

If the business has changed significantly but the configuration hasn't been revisited, it's reasonable to ask:

Do these settings still support today's strategy?

A Lease-Up Becoming Stabilized Is a Natural Review Point

This is a big one.

The settings appropriate for a property at 35% occupied may not be appropriate when that property reaches stabilization.

During lease-up, the strategy may prioritize:

Absorption.

Delivery schedules.

Velocity.

Concessions.

Large amounts of available inventory.

As stabilization approaches, priorities may shift toward:

Rate growth.

Retention.

Expiration management.

Long-term occupancy.

More normalized exposure.

The property has changed.

The strategy has changed.

The RMS configuration deserves another look.

A Change in Ownership Strategy May Require a Review

Not every setting decision is driven by market performance.

Sometimes the business plan changes.

Ownership may shift from aggressive occupancy growth to rate preservation.

A property may be preparing for disposition.

A value-add program may begin.

Capital improvements may change the product.

A new owner may have different risk tolerance or performance objectives.

Revenue management technology should support the business plan.

If the business plan changes materially, the settings should at least be reviewed to make sure they're still aligned.

Persistent Overrides Are a Signal

This is one of the biggest clues that something deserves investigation.

If the Revenue Manager or onsite team occasionally overrides a recommendation, that doesn't necessarily indicate a problem.

There will always be situations where human context matters.

But if the same type of recommendation is being overridden repeatedly, ask why.

Are teams uncomfortable with the system?

Is there a training issue?

Is important operational information missing?

Is a particular setting producing outcomes that no longer align with the strategy?

Has the market changed?

Is the business plan different?

Repeated overrides are information.

Don't just count them.

Understand what's causing them.

But Don't Change Settings Just to Reduce Overrides

This distinction matters.

The objective isn't to get override activity to zero.

And settings shouldn't be changed simply to make every recommendation match what a person already wanted the price to be.

If we continually adjust the system until it agrees with us, we're not really using revenue management technology.

We're using expensive software to validate manual pricing decisions.

The better question is:

Why are we disagreeing with the recommendation?

Sometimes the system needs adjustment.

Sometimes the human needs more confidence in the methodology.

Sometimes operations knows something the system doesn't.

Sometimes no change is needed at all.

Look for Patterns, Not One-Offs

One strange recommendation is a data point.

A repeated pattern deserves attention.

Maybe one floor plan consistently prices in a way that doesn't make sense.

Maybe short-term lease premiums repeatedly create problems.

Maybe expiration premiums aren't strong enough to influence term selection.

Maybe pricing consistently moves beyond ownership's intended boundaries.

Maybe certain inventory isn't responding as expected.

Patterns help distinguish a strategic configuration issue from a single pricing outcome.

Don't redesign the strategy around one recommendation.

Expiration Management Settings Deserve Attention

Lease expiration management is one area where settings can have significant downstream consequences.

If the property has too many leases expiring in a particular month, are term premiums strong enough to influence resident behavior?

Are alternative terms being priced meaningfully differently?

Are expiration limits aligned with the property's strategy?

If every lease term is priced almost identically, renters have little financial reason to choose the term the property needs.

Sometimes the system is working perfectly.

The strategy we've configured isn't strong enough to change behavior.

That's a settings conversation.

Lease-Term Pricing Should Be Intentional

The same applies to lease-term premiums.

What is the property trying to accomplish?

Does it want more 12-month leases?

Longer terms?

Shorter terms during certain seasons?

Does it need to move expirations?

Are certain lease lengths intentionally discouraged?

The system can help execute the strategy.

But somebody has to define what the strategy is.

Technology can execute rules. It can't decide the business objective for you.

Floors and Ceilings Need Periodic Review

Many revenue management strategies use some form of boundaries or pricing constraints.

Those can be helpful.

But boundaries established years ago may eventually become irrelevant or counterproductive.

Maybe market rents have changed significantly.

Maybe renovations have repositioned the property.

Maybe ownership's objectives changed.

Maybe the original guardrails were overly conservative.

Or perhaps they're now too aggressive.

A guardrail only works if it's protecting the strategy you actually have today.

Market Changes Can Justify Another Look

A property may operate in a very different competitive environment than when the system was configured.

New supply enters.

Concessions increase.

Demand slows.

Major employers enter or leave the market.

Seasonality changes.

Competitor positioning shifts.

That doesn't mean settings should be changed every time a competitor changes a price.

But a sustained change in market dynamics may justify reviewing whether the existing strategy still makes sense.

Operational Changes Matter Too

Revenue management doesn't operate separately from the property.

Suppose the property had significant make-ready delays when the system was implemented.

Now operations has improved dramatically.

Or maybe the opposite has happened.

Staffing changed.

Unit readiness deteriorated.

A renovation program began.

Large blocks of units became unavailable.

Lead management improved.

Conversion changed.

Those operational conditions can affect the strategy.

Software can identify the outcome. Experience helps diagnose the cause.

Data Quality Should Be Checked Before Strategy Is Changed

Before changing the RMS settings, make sure the information feeding the system is accurate.

Are unit statuses correct?

Are notices accurate?

Are leases properly entered?

Are concessions reflected appropriately?

Are unit amenities correct?

Are future availability dates realistic?

Is the PMS integration functioning correctly?

Bad inputs can create strange outputs.

Changing the strategy to compensate for a data problem can make the situation worse.

Before changing the settings, make sure you trust the data.

Sometimes the Problem Is Training

This happens more often than people realize.

A team may believe the system is behaving incorrectly when they simply don't understand what is driving the recommendation.

Maybe a price increased because exposure improved.

Maybe a lease term is expensive because the property doesn't want another expiration in that month.

Maybe a unit is priced differently because of amenities.

Maybe a recommendation reflects conditions the user wasn't considering.

Before changing configuration, make sure the people using the system understand how it works.

Sometimes the best settings change is no settings change at all.

The solution is education.

Automation Requires Trust — and Good Guardrails

Many revenue management platforms offer varying levels of automated pricing or recommendation acceptance.

Automation can be incredibly powerful.

But automation works best when the organization has confidence in:

• The data

• The configuration

• The strategy

• The guardrails

• The escalation process

• The review cadence

The goal isn't to remove people from revenue management.

It's to allow technology to handle what technology does well while people focus their attention where judgment and context add value.

Automation without thoughtful configuration can create anxiety.

Thoughtful configuration plus consistent review can create confidence.

Don't Overcorrect

Revenue management is dynamic.

There will be good weeks.

Slow weeks.

Unexpected traffic.

Unexpected notices.

Competitive changes.

A large move-out.

A sudden burst of leases.

Not every change requires intervention.

If we constantly adjust settings based on the most recent few days of activity, we may prevent the system from doing exactly what we bought it to do.

Review consistently. React intentionally.

That applies to configuration just as much as pricing.

Document Why Settings Change

When a meaningful setting is changed, document the reason.

What problem were we trying to solve?

What was the previous configuration?

What did we change?

What result do we expect?

When will we evaluate it?

Without documentation, teams can end up changing settings back and forth without remembering why the original decision was made.

A decision log creates institutional memory.

It also helps determine whether the change actually worked.

Measure the Result

A settings change should have an intended outcome.

If expiration premiums are increased, are lease selections changing?

If pricing flexibility is expanded, is leasing performance improving?

If a boundary changes, what happened afterward?

If automation is increased, are overrides declining for the right reasons?

Don't make a configuration change and immediately move on.

Give it an appropriate amount of time, then evaluate the result.

Strategy without measurement is just activity.

Different Properties May Need Different Settings

Portfolio standardization has value.

But identical configuration across every property isn't always the same thing as good governance.

A lease-up in Austin may have different needs from a stabilized property in Denver.

A highly occupied asset may have different risk tolerance from one carrying significant exposure.

A luxury high-rise may behave differently from a suburban garden community.

The portfolio should have a consistent methodology, but that doesn't necessarily mean every property needs identical settings.

Standardize the framework.

Then allow the strategy to reflect the asset.

Who Should Own Revenue Management Settings?

Someone should.

That's the important part.

Whether it's an internal Revenue Manager, Revenue Advisor, centralized revenue team or another designated leader, there should be clear ownership of:

• Configuration

• Changes

• Approvals

• Documentation

• Performance review

Without ownership, settings can either become completely neglected or changed by too many people.

Neither is ideal.

How Often Should RMS Settings Be Reviewed?

There isn't a universal schedule for every setting on every platform.

And a settings review does not mean settings must be changed.

A good review asks:

Do these still align with the business plan?

Are we seeing repeated override patterns?

Has the property materially changed?

Has the market materially changed?

Are lease expirations behaving as intended?

Are term premiums influencing behavior?

Are boundaries still relevant?

Is automation performing as expected?

Are there recurring outcomes we don't understand?

The purpose is validation.

Sometimes the conclusion should simply be:

Everything is working as intended. Leave it alone.

That's a successful review too.

How The Revenue Method® Approaches RMS Settings

At The Revenue Method®, we work across revenue management platforms rather than approaching strategy through the lens of one software provider.

Our Revenue Advisors look at the technology in the context of the asset.

We evaluate settings alongside:

• Pricing outcomes

• Exposure

• Leasing velocity

• Lease expirations

• Term selection

• Overrides

• Concessions

• Market conditions

• Operational performance

• Business objectives

We're not looking for reasons to change settings.

We're looking for evidence that they either do or do not still support the strategy.

Sometimes we recommend a change.

Sometimes we recommend training.

Sometimes we identify a data issue.

Sometimes the strategy itself needs to change.

And sometimes our recommendation is:

Don't touch it.

That's what system-agnostic revenue advisory should do.

The goal isn't to make the software behave the way we want.

It's to make sure the technology and the business strategy remain aligned.

The Bottom Line

Your revenue management settings shouldn't change every time you disagree with a price.

But they shouldn't be treated as permanent either.

Properties change.

Markets change.

Business plans change.

Lease-ups stabilize.

Expiration patterns develop.

Operational conditions evolve.

And the strategy behind the technology may need to evolve with them.

Look for patterns.

Understand overrides.

Validate the data.

Review the business objective.

Document meaningful changes.

Measure the result.

And don't change something simply because you can.

Your settings aren't set in stone.

But every change should have a reason.

Frequently Asked Questions

How often should revenue management system settings be reviewed?

There is no universal schedule, but settings should be reviewed periodically and after meaningful changes to the asset, market or business plan. A review does not necessarily mean a change is needed.

When should RMS settings be changed?

A change may be appropriate when repeated patterns show that the current configuration no longer supports the property's objectives, such as persistent override patterns, changing expiration needs, stabilization after lease-up or a material change in the business plan.

Should revenue management settings be changed when pricing looks wrong?

Not automatically. First determine why the system produced the recommendation and confirm the underlying data is accurate. A single pricing outcome may not indicate a configuration problem.

Are frequent revenue management overrides a problem?

Not necessarily, but repeated overrides of the same type can be an important signal. They may indicate a configuration issue, training need, data problem, operational condition or misalignment between the technology and business strategy.

Should every property in a multifamily portfolio use the same RMS settings?

Not necessarily. A portfolio can maintain consistent governance and methodology while allowing configuration to reflect individual asset conditions, business plans and market dynamics.

Should revenue management settings change after a lease-up stabilizes?

They should at least be reviewed. Lease-up objectives around absorption, concessions and large inventory exposure may differ significantly from the priorities of a stabilized property.

Can bad data affect revenue management recommendations?

Yes. Incorrect unit status, availability, lease, amenity, concession or other source data can affect system outputs. Data quality should be validated before changing strategy to compensate for unexpected recommendations.

Should revenue management systems be automated?

Automation can be effective when data, configuration, guardrails and strategy are trusted and performance is reviewed consistently. The appropriate level of automation depends on the platform and organization's operating strategy.

Who should be allowed to change RMS settings?

Organizations should establish clear ownership, approval processes and documentation requirements for meaningful configuration changes to avoid inconsistent or undocumented adjustments.

Should revenue management setting changes be documented?

Yes. Documenting the reason, expected outcome and timing of meaningful changes makes it easier to evaluate whether the adjustment worked and prevents teams from repeatedly changing configuration without understanding previous decisions.