CRE Website Maintenance: Who Handles the Routine Work?

By Brandy Quick · 2026-10-28

Commercial real estate website maintenance helps keep your brokerage’s information useful when every routine task has a clear owner.

A site can look fine while an update request sits unanswered and a contact change never reaches the right person.

I’d start with a simple question: Who handles the work after launch?

The answer should cover your staff, your website provider, and any outside service that keeps part of the site running.

You don’t need a giant operations manual to sort this out.

You need a workable agreement that names the task, the person responsible, the timing, and the proof that it’s done.

I create commercial real estate websites, and I’d rather help you plan that routine now than leave your team guessing later.

If your current arrangement leaves routine work unclear, I can help you plan a CRE website around the responsibilities your team can handle.

Start with website design pricing and ask for the proposed support scope alongside the design details.

Maintenance needs a clear division of duties.

The word maintenance can hide several different jobs inside one neat line on a proposal.

One person may mean software updates, while another expects new property pages and help with every brochure change.

Before comparing support offers, write down the actual work your brokerage expects someone to do.

Separate keeping the website running from keeping the information correct and helping visitors complete a useful action.

Those jobs overlap, but they don’t always belong to the same person.

Your provider can publish a revised contact number, but someone at the brokerage still needs to confirm that it is the right number.

Likewise, an approved change is not finished simply because it entered a support queue.

Someone must check the published result and confirm that it matches the request.

I suggest giving each recurring task one accountable owner, even when several people help complete it.

Otherwise, a shared responsibility can become a shared assumption that somebody else handled it.

Make the arrangement specific enough to survive a busy week or an unexpected absence.

Name a backup contact who can approve a correction when the usual decision-maker is away.

Keep the task list somewhere both your staff and the support contact can find it.

You can start with a shared document rather than buy another system.

A useful record tells a new employee how an update moves from a broker’s request to a checked public page.

If that path is unclear, the support arrangement needs more detail before you rely on it.

A completed task needs a visible result.

For a contact update, completion means the correct details appear in the agreed locations and the contact route works.

For a software change, completion includes checking the agreed website functions afterward.

The definition should match the job instead of treating every request as the same kind of ticket.

Support arrangements should match available staff time.

A self-managed arrangement puts your brokerage in charge of arranging the routine work.

That can suit a team with an experienced website contact and protected time for the job.

It still requires a plan for technical problems that exceed that person’s skills or access.

A provider-managed arrangement can put more of the execution with an outside company, depending on the written scope.

Your staff still need to supply accurate information and approve changes that require a business decision.

A shared arrangement divides tasks between an internal editor and an outside support contact.

For example, staff might handle approved text changes while the provider handles software work and problems with the page layout.

That example is a possible division of duties, not a promise about any particular service package.

I’d compare these arrangements against a normal week at your brokerage rather than an unusually quiet afternoon.

Can the designated employee make the edits when several brokers need help at once?

Who takes over when that employee leaves or goes on vacation?

A low recurring fee doesn’t tell you how much staff time the arrangement needs.

An extensive support offer doesn’t tell you whether anyone will chase missing approvals.

Ask each provider to explain the same ordinary request from start to finish.

Use a small change such as replacing a service-page contact and its downloadable brochure.

Then ask how a larger change would be handled, such as creating a new service page with a different layout.

The difference reveals where routine support ends and a separate project begins.

Shared support needs a handoff rule.

When your team and a provider both edit the site, agree who checks for conflicting work.

A clear handoff helps prevent one person from undoing a change another person has just approved.

A responsibility list makes support offers comparable.

I’d ask providers to complete the same responsibility list before choosing between their offers.

Use real tasks from your website rather than a vague request for full maintenance.

Include content edits, technical checks, renewal notices, contact-route testing, and urgent corrections.

For each task, record who supplies the information, who performs the work, and who confirms the result.

Those can be three different people without making the process complicated.

Consider a fictional brokerage replacing an agent’s phone number across several pages.

The office manager confirms the new number, the website editor makes the changes, and the support contact checks any affected form routing.

The office manager then reviews the public pages and confirms that the request is complete.

This is a planning example, not a report of a client result.

If the number also appears in a downloadable brochure, that file needs its own assigned action.

A request that mentions only the contact page could leave the old document untouched.

Add a due date and any dependency, such as waiting for a replacement file from the marketing team.

That makes it easier to distinguish work that is delayed from work that cannot start yet.

The responsibility list should describe the actual website.

A brochure site, a manually edited property directory, and a site using an outside listing service need different task lists.

Ask the provider to identify which parts they can edit and which require another company’s help.

For an outside service, name the person who opens the request and follows it through.

Your brokerage should not have to guess which help desk owns a broken page element.

Review the list after a major feature is added so the support arrangement keeps pace with the site.

A task that appears after launch still needs an owner, even if it wasn’t in the original estimate.

Routine reviews should follow business changes.

A maintenance calendar should support your work rather than create busywork.

I suggest pairing regular reviews with clear triggers for changes that cannot wait for the next scheduled check.

An incorrect contact route deserves attention when it is found, even if the next monthly review is weeks away.

A new service announcement can follow a planned approval and publication date.

Start by identifying what changes often and what creates a real problem when it becomes wrong.

Then agree on a practical review rhythm with the people doing the work.

A monthly content review can be a starting point for a small site, but it is a suggested routine rather than a universal standard.

A busy brokerage may need more frequent checks for the information it changes most often.

After a significant edit, review the page on a phone and a larger screen.

Check whether the text is readable, the revised document opens, and the next step still makes sense.

For an inquiry route, use an authorized test message and confirm its arrival with the intended recipient.

A success message on the website does not by itself confirm that the right person received the inquiry.

Agree who will remove test records where appropriate and avoid putting sensitive information into a test.

Keep a short record of the page checked, the result, and any follow-up work.

A review should close an open loop.

If a problem appears, assign a next action and a person rather than leaving a note that says the page needs attention.

When it is repaired, repeat the affected check before closing the request.

The point of the calendar is a dependable habit, not a growing collection of unchecked boxes.

Technical work needs checks after changes.

Content support and technical support deserve separate lines in the agreement.

On a self-hosted WordPress site, software work can involve WordPress itself, themes, and plugins.

Other platforms have different arrangements, so ask your provider to describe the duties for your actual setup.

The official WordPress update guidance calls for a backup before updating.

The official WordPress backup guidance explains that a typical full recovery needs both the site’s files and its database.

Those are useful facts to bring into a support conversation without turning your broker into the system administrator.

Ask who performs the work, who can restore the site, and which checks follow a change.

I’d want the agreed checks to include the pages and inquiry routes the brokerage depends on.

An update being installed does not answer whether those functions were checked afterward.

For a static website, ask how the source files, built pages, and published version are retained and recovered.

Do not assume that a process described for WordPress applies to a different setup.

Access also needs a responsible owner when duties change.

The official WordPress roles documentation explains how roles control the actions users can perform.

Use that principle to ask whether an editor has the permissions needed for the assigned work.

The technical contact should review access when a staff member or provider stops working on the site.

Technical reports should explain what the brokerage needs to know.

Request a brief record of completed work, unresolved issues, and decisions waiting for your team.

It should tell you what changed and what was checked in plain language.

That record is more useful than a reassuring message that never identifies the work performed.

If you prefer seeing website ideas explained on screen, explore my helpful video walkthroughs and tools as you prepare questions for your website provider.

Use the discussion above to keep your own support checklist specific to your site.

Requests need priorities and a closing check.

Agree on a normal request route before a problem appears.

A provider may use a support mailbox or a ticket system, but the important point is that your team knows where to send the request.

Name the approved contacts who can authorize work and approve any extra cost.

Ask what information the provider needs to begin, including the affected page, the requested change, and the approved replacement material.

A screenshot can help explain a layout problem, while the actual page address helps the provider find it.

Keep passwords and sensitive prospect details out of ordinary request messages.

I’d also agree on what counts as urgent for this website.

A broken inquiry route, a public contact error, and a requested design improvement may need different treatment.

Ask the provider to explain response targets and completion targets separately.

A promise to acknowledge a request does not establish when the problem will be repaired.

If the timing depends on diagnosis or another supplier, ask how your team will receive progress updates.

Confirm support hours and the route for a serious problem discovered outside those hours.

Do not assume that an ordinary support subscription includes round-the-clock attention.

Closure should include a public-page review.

Before approving completion, compare the published page with the requested change.

If the provider cannot finish because another party must act, record that dependency and the next follow-up date.

A short closing note should identify what changed, what was checked, and whether anything remains open.

That makes the next request easier because nobody has to reconstruct the last conversation.

When your review shows that a marketing page needs fresh material, explore my free commercial real estate marketing resources.

Choose material that fits your campaign, then assign someone to adapt it, approve it, and check the finished page.

The support scope should explain extra work.

Routine maintenance and a new project can both be valuable, but your agreement should show how each is handled.

Ask which kinds of edits are included and whether limits apply to time, volume, complexity, or turnaround.

Then ask what happens when a request exceeds the allowance.

A provider should explain the approval process for extra work before starting it.

Compare the same sample month across offers rather than guessing from the headline fee.

Your sample might include a document replacement, several text corrections, a technical check, and a new page request.

Ask which items belong to routine support and which need a separate estimate.

Do not treat that sample as a claim about what any package includes.

I’d also ask whether unused time carries forward and how partially completed work is recorded.

If an outside service causes the problem, ask whether coordinating with that company is included.

The answer matters even when the website provider cannot directly repair that service.

A short trial routine can expose missing responsibilities.

Before relying on the process, walk one ordinary change through the agreed route.

Confirm that your team can supply the material, the provider can act, and the right person can check the result.

Use what you learn to clarify the task list and approval steps.

You can review that arrangement as the brokerage grows instead of waiting for an urgent problem.

For a deeper look at purchase rights, read the CRE website ownership article.

Keep those ownership questions separate from the practical question of who does tomorrow’s work.

A reliable maintenance plan gives your team a clear next step when something changes.

If your website needs a clearer editing setup, I can help you plan the pages and responsibilities together.

Request website design pricing and bring your routine task list so the conversation starts with the work your brokerage actually needs.

Common website maintenance questions have practical answers.

What does commercial real estate website maintenance include?

The scope depends on the agreement and the website setup.

Ask for a written list covering content edits, technical work, contact-route checks, renewal responsibilities, and the approval process for extra work.

Can brokerage staff handle routine website updates?

Staff can handle assigned updates when they have the time, training, and appropriate access.

Name a backup editor and identify who handles technical problems that exceed the internal team’s skills.

How often should a brokerage review its website?

Set a review schedule around the information that changes and the effect of an error.

A monthly review can be a starting point for a small site, while incorrect contact details or broken inquiry routes need attention when discovered.

Does hosting include content changes and technical support?

Do not assume those duties are included in hosting.

Ask the provider to identify the included tasks, exclusions, support hours, and process for approving additional work in writing.

How can a brokerage compare website support providers?

Give each provider the same sample month of routine tasks and one urgent problem.

Compare who does the work, what your staff must supply, how timing is defined, and how the published result is checked.