Tenant Build-Out Basics for Landlords and Tenants
Plan a commercial tenant build out with clear scope, approvals, cost responsibilities, schedule assumptions, and handoff expectations for both parties.

A tenant build out can make a commercial space work better for a business, but the phrase alone does not say what work is included or who controls it. Landlords and tenants need a shared written plan for the space, decisions, cost treatment, coordination, and handoff. This guide explains the basics for Texas property owners and project participants, with practical steps for reducing misunderstandings before construction moves forward.
Discuss your construction project
What does tenant build out mean?
A tenant build out is construction or improvement work that adapts a commercial space for a tenant’s intended use. The work may be limited to selected finishes or may involve a larger set of changes to rooms, surfaces, systems, or building components. There is no single standard package. The specific work depends on the space’s existing condition, the tenant’s needs, the lease, and any separate written project agreement.
Consider two different starting points. A business moving into an already configured suite may need only a small number of agreed changes before using it. Another business may need a different layout and more extensive coordination. These examples do not establish who selects a contractor, who pays, or which work the landlord will approve. The parties should specify those terms rather than treating the words tenant build out as a complete scope.
Landlords may want to prepare a property for occupancy or meet a delivery condition. Tenants may request changes to support how their business will operate. One arrangement could have the landlord manage the work while the tenant supplies requirements and reviews selections. Another could give the tenant a role in commissioning some work, subject to the approvals in the lease. The arrangements vary. A written scope and decision process make the actual arrangement easier to understand.
It also helps to distinguish the project’s physical work from the agreement governing it. Drawings, a proposal, or a finish list can describe what someone expects to happen, but they do not necessarily resolve contractual duties. Review the lease and any work letter or construction exhibit with the people qualified to interpret them. This article is general planning guidance, not legal advice.
What should each party decide before work starts?
Begin with the intended use and the proposed delivery condition. Describe how the tenant expects to use the space, what is there now, what needs to change, and what should be complete at the agreed handoff. Replace vague labels such as move-in ready with visible or otherwise verifiable requirements. If an item is not yet known, call it an open question rather than presenting it as settled.
- Landlord: identify the areas and building elements included in the agreed work, the relevant property constraints, who can approve changes, and how work in shared or landlord-controlled areas will be coordinated.
- Tenant: explain the operational reason behind each request, separate essential needs from preferences, identify who will make selections, and provide information and decisions by agreed dates.
- Both parties: record the scope, responsibilities, approval route, cost treatment, schedule assumptions, access expectations, and process for changes in the lease or another written project document.
A useful first exercise is to create a needs list. For every requested improvement, note what is wanted, why it matters, when it is needed, who decides, and whether it must be complete before the tenant can use the space. This exposes disagreements while they are still questions. A finish that one party sees as a preference may be important to the tenant’s planned operation; a change that sounds essential may have an acceptable alternative.
Use a short project brief to keep the discussion focused. Include the space or areas covered, the purpose of the work, the current information available, known constraints, participants, decisions still needed, and the next review. The brief does not need to replace the formal agreement or technical documents. Its role is to help the parties notice missing information and give the appropriate professional a clear starting point.
Before commissioning work, compare the brief with the lease and any work letter or construction exhibit. Those documents may describe delivery conditions, approval rights, deadlines, and how changes are handled. If the brief and contract appear to say different things, do not assume the brief changes the parties’ obligations. Ask a qualified legal professional to interpret the contract or help resolve a disagreement.
How do landlord and tenant responsibilities differ?
There is no universal division of responsibility. The lease and project documents control. The table is a planning aid, not a statement that either party must perform a particular task in every transaction. Use it to identify topics that need an explicit owner and an agreed way to close decisions.
| Planning topic | Landlord questions | Tenant questions | Written outcome to clarify |
|---|---|---|---|
| Space condition | What condition and included work are being offered? | What conditions support the intended use? | Defined delivery condition and scope |
| Design and decisions | Which proposed changes require property approval? | Who supplies requirements and selects options? | Decision-makers, review steps, and response dates |
| Contracting and coordination | Who may engage or direct contractors? | May the tenant commission any work directly? | Authorized parties and coordination route |
| Cost and changes | Which costs are included in the agreement? | Could requested additions have separate cost treatment? | Responsibility, documentation, and change approval |
| Schedule and access | What access and building coordination are available? | When must information and selections be provided? | Milestones, dependencies, and communication contacts |
| Completion and handoff | What review or record is expected at completion? | What needs to be checked before accepting the space? | Walk-through, open-item list, and handoff record |
For each row, write down one responsible contact and one approval contact, even when those roles belong to the same person. This prevents a common gap: everyone knows a decision is needed, but nobody knows who is expected to make it. If one party manages construction and the other reviews decisions, state how the review works, how comments are collected, and what happens when a response is late.
Take the contracting and coordination row as an example. A tenant may ask a trade to price an idea, while a landlord believes all work must be directed through a property representative. Even if neither person intended to authorize construction, the conversation can create different expectations. State who may request a proposal, who may authorize work, and whether a contractor should receive instructions from one designated contact.
Similarly, a party named as a reviewer is not necessarily responsible for finding every technical issue. Define the purpose of each review and who is expected to provide technical, legal, or property-specific advice. The goal is not to give everyone the same role. It is to make sure the roles do not depend on guesswork.
How should the scope be defined?
A useful scope is specific enough that the parties can recognize what is included and what is outside the agreement. Improve the space is too broad to guide decisions. Describe the areas involved, the intended result, the known constraints, and any express exclusions. If drawings or other supporting documents exist, identify the version and date so the parties know which information they are reviewing.
Separate requirements from preferences
Divide requested changes into three groups: essential to the intended operation, desirable if feasible, and optional. Add a short reason for each item. For example, a tenant might distinguish a requirement that supports an everyday workflow from a preferred finish that could be changed if it conflicts with another project constraint. This prioritization helps the parties discuss alternatives without losing sight of what the business needs.
Then ask what would count as an acceptable alternative. If a request cannot be approved as written, does another configuration meet the same need? The tenant can explain the functional purpose, while the landlord can explain the property concern or review constraint. Recording both the request and the agreed alternative makes it less likely that one party will later remember only the original idea.
Record existing conditions and unknowns
Document the space before work starts. A dated set of photographs, a written observation list, and a plan marked with the relevant areas can create a shared reference. Be clear about what the record does and does not show. Photographs may capture visible conditions, but they do not replace a technical assessment when one is needed. Flag a suspected issue for qualified review instead of treating a casual observation as a conclusion.
Separate confirmed information from assumptions. A simple register can label each item as confirmed, awaiting verification, or not yet reviewed. For instance, if the parties do not know whether a proposed change interacts with an existing building element, list that question, identify who will investigate it, and note what decision depends on the answer. This keeps uncertainty visible instead of allowing it to disappear inside a broad scope description.
Mark interfaces, exclusions, and dependencies
Many misunderstandings happen where one scope ends and another begins. Note where proposed work meets existing construction, which party’s work stops at a boundary, and which items need separate review. If one improvement depends on another, record that relationship. A finish decision, for example, may depend on an earlier layout decision; a handoff expectation may depend on completion of a clearly identified task.
List exclusions in plain language as well. If an item is not included, say so and identify whether it is outside the project entirely, deferred for a later decision, or awaiting a separate agreement. Not included and not decided yet mean different things. Marking the difference helps both sides avoid assuming an unresolved item will be handled automatically.
One Real Roofer and Construction describes pre-construction consulting and project support among its services. The company’s services overview provides information about its construction and roofing work. A specific tenant-space scope still needs to be discussed in light of the property, agreement, and project requirements.
How can the parties handle approvals and decisions?
Agree on who can make decisions and how each approval will be recorded. A tenant may identify an operational requirement, while the landlord reviews a proposed change under the property’s agreed process. A contractor may provide technical input, but that does not automatically make the contractor the decision-maker for either party. Each participant should know whether they are recommending, reviewing, approving, or simply supplying information.
Create a decision list with the item, responsible party, reviewer, due date, status, and record of the final decision. Include selections, layout questions, access arrangements, proposed scope changes, and questions about existing conditions. Keep the list in one agreed location or circulate its current version after meetings. A dated decision log gives people a shared reference for what is settled and what remains open.
For example, imagine that the tenant asks for a change after the parties have agreed on a layout. Record the request, the reason, the specific location or document it affects, who needs to review it, and the decision deadline. If approved, link the decision to the updated scope or drawing. If it is declined or replaced with an alternative, record that outcome too. This prevents a verbal conversation from being mistaken for an approved instruction.
Define one route for project questions. Requests might go through a landlord representative, a tenant project contact, or an agreed project manager. Avoid giving conflicting instructions directly to different trades. When questions are sent through a single route, the recipient can direct them to the person with authority and distribute the answer to everyone who needs it.
Approval timing matters because decisions can depend on one another. The decision list should show the date a response is needed and what subsequent action relies on it. If the due date passes, the parties should use their agreed communication process to understand the effect. They should not assume a contractor can absorb the delay or that the original choice remains approved without a response.
A concise meeting note can include decisions made, open questions, assigned owners, due dates, and changes to the current plan. Circulate it promptly and ask participants to correct factual errors. The objective is not to create paperwork for its own sake. It is to maintain one usable record that connects the original request to the approved direction.
How should cost and changes be discussed?
Do not infer the cost arrangement from a tenant allowance, a headline lease term, or a verbal summary. Confirm how the lease and project documents treat the work, who is responsible for particular expenses, and how additional requests are priced and authorized. Actual project costs depend on scope and circumstances; there is no responsible universal price for a tenant build out.
Ask that proposals or estimates refer to a defined scope. Review what the document includes, what it excludes, what assumptions it uses, and which decisions remain pending. When comparing alternatives, compare like with like. A lower starting figure may describe less work, rely on different assumptions, or omit an item that another proposal includes. If the documents are not comparable, first identify the differences rather than treating the totals as a direct contest.
- Identify the areas, tasks, and materials described, as well as items explicitly excluded.
- Ask which existing conditions, decisions, or access assumptions could change the described work.
- Check whether the document is a preliminary estimate, a proposal for a defined scope, or another type of planning document.
- Confirm who may request additional work, who reviews it, and who is authorized to approve it.
- Record the stated cost and schedule effects of an approved change in the project record.
- List unresolved items separately so they do not appear to be included by implication.
A change process should be clear before work begins. Define who can request a change, what information must accompany it, who reviews it, and when written approval is required. A complete change record might identify the requested adjustment, why it is needed, which part of the scope it affects, what approvals are outstanding, and the known cost or schedule implications. Do not present an unapproved proposal as a settled commitment.
Consider a simple comparison. The tenant asks for a preferred finish after the original scope has been discussed. Rather than immediately asking whether it costs more, first confirm whether it changes the defined work, whether the landlord’s review is required, and whether the selected product or detail is available under the project assumptions. Then ask for any change in cost or timing to be documented before deciding. This order helps everyone compare the same choice and understand its consequences.
Keep contractual interpretation separate from construction pricing. A project estimate can describe proposed work, but it does not decide what the lease requires one party to pay. If the agreement’s cost language is unclear or disputed, seek qualified legal advice. Do not rely on a contractor or informal project note to resolve a legal disagreement between landlord and tenant.
One Real Roofer and Construction provides information about its construction offerings on the services page and examples of commercial work on its commercial projects page. Those pages are company information, not a price list or a promise that a particular scope or cost applies to a tenant space.
How can you coordinate the work without making this only a timeline exercise?
A useful schedule is more than a list of desired dates. It connects each milestone to an owner, a needed decision, and any dependency. Work backward from the date the space is expected to be ready, but do not treat that date as a promise unless the responsible parties have agreed to it. Actual sequence and duration depend on the project and its conditions.
Start with milestones rather than guessing at a construction duration. Depending on the project, milestones may include confirming the lease scope, collecting requirements, documenting existing conditions, reviewing the proposed work, resolving open decisions, coordinating access, carrying out the agreed work, and conducting the handoff review. Add a responsible contact and the decisions or information that must precede each one.
To make the plan usable, check it for dependencies. If the next step requires a selection, name who makes it and the date it is needed. If access depends on coordination with the property, assign someone to confirm the arrangement. If a scope question must be answered before a proposal can be reviewed, show that dependency rather than placing the proposal review on the schedule as though it could proceed immediately.
Use a simple three-part status for each milestone: not ready to begin, in progress, or complete. Add a short note when the status changes and identify any decision that could affect the next step. The value is not in complex tracking software; it is in seeing where a decision or missing input may interrupt the agreed sequence.
Ask what could change the plan. Incomplete information, a revised scope, an unresolved existing condition, or a late selection may require the parties to review assumptions and timing. Do not assume that a schedule is reliable because it contains dates. Check that each date has an owner, a defined deliverable, and known dependencies. If an assumption changes, record the update and share it with the people affected.
Keep communication regular and practical. A short update can state what is complete, what decisions are needed, what questions remain open, who owns them, and what comes next. If work touches landlord-controlled areas or requires building access, clarify the coordination route in advance. The tenant should know where to send questions, and the landlord should know when the tenant must make a decision.
For broader context on planning before a project begins, see One Real Roofer and Construction’s article about pre-construction planning. Keep the tenant build out’s decision and coordination questions connected to the actual scope rather than treating a date list as a substitute for project planning.
What should a tenant check before accepting the space?
Plan a handoff review against the written scope and approved changes. Walk through the relevant areas with appropriate representatives, note visible incomplete items, and agree on how each open item will be tracked. Distinguish between work described as complete and items that remain unresolved. Keep the record dated and share it with the contacts responsible for follow-up.
- Compare visible completed work with the agreed scope and documented changes.
- List each open item with a clear description, location, and responsible contact.
- Ask for documents or information that the parties agreed would be delivered.
- Confirm access arrangements and the communication route after handoff.
- Review the lease and project documents for acceptance, notice, or other agreed steps.
- Identify who will confirm that listed items have been addressed and how the record will be updated.
Make the open-item list specific. Finish work may be too vague to guide follow-up. State the location and what remains to be checked or completed, without making technical judgments beyond what the reviewer can observe. If a concern needs specialist evaluation, identify the type of qualified professional the parties should consult rather than relying on an informal walk-through.
Keep the handoff record separate from assumptions about ongoing maintenance, warranties, or responsibility after occupancy. Those topics should be addressed in the applicable agreement. A signed walk-through note should not be treated as changing contractual terms unless the parties have deliberately documented such a change through the appropriate process.
Some projects involve more than interior work. If the agreed scope includes roofing or other work connected to the larger property, clarify how that work interfaces with the tenant’s space, who controls building decisions, and how its completion is recorded. One Real Roofer and Construction describes its commercial roofing services; the relevant work and responsibilities still need to be established for the specific property.
What mistakes can landlords and tenants avoid?
Assuming the same phrase means the same thing
Words such as finished, standard, or ready can mean different things to different people. Replace shorthand with an observable scope or an identified document. If the parties cannot tell how they would verify completion, the description may need more detail.
Starting before scope and authority are clear
Unclear authority can create conflicting instructions and uncertainty about whether a request was approved. Before work starts, confirm who may direct it, who reviews changes, and how those decisions are recorded. Do not assume that being copied on a message gives someone authority to approve the work.
Treating an estimate as a complete project plan
An estimate may cover only part of the work or depend on assumptions. Read its scope and exclusions and compare them with the parties’ written requirements. Ask what information remains necessary before treating the document as a basis for a decision.
Leaving changes in informal conversations
Talking about an improvement is not the same as approving it. Record the request, decision-maker, outcome, and known cost or schedule effects through the agreed process. This applies even when the proposed adjustment seems small; a small request can affect another decision or the agreed handoff.
Planning only around the desired opening date
A target date does not resolve outstanding selections, approvals, scope questions, or access arrangements. Build a milestone plan with owners and dependencies, and revisit it when assumptions change. A date without an assigned action is not a complete coordination plan.
Failing to preserve a current record
Several old versions of a scope, decision list, or drawing can create confusion about what is current. Use a dated version or another clear way to identify the latest agreed information. When a decision changes the plan, update the relevant record and tell the people who rely on it.
How can the parties compare different ways to organize the work?
The parties can compare project arrangements by asking who coordinates, who approves, and how information reaches the people doing the work. The lease and written agreement determine which arrangement is permitted. These are planning patterns to discuss, not universal options or recommendations for a particular contract.
One party coordinates the agreed scope
In an arrangement where one party coordinates the work, the other party still needs a clear route to provide requirements and review decisions. Set out what the coordinator may decide independently, which items need approval, and how updates are shared. A tenant should know where to send a requested change; a landlord should know who can answer for the tenant. Without those boundaries, central coordination can still produce confusion.
Decisions are reviewed jointly
Some decisions may require input from both parties. Identify those in advance, then define who gathers information and who records the final outcome. A joint review does not mean every participant has identical authority. The written process should show whether a person is providing input, reviewing a proposal, or giving formal approval. That distinction matters when a decision affects the scope, cost treatment, or handoff expectations.
Some questions remain open pending investigation
When information is incomplete, the parties can document the open question, assign someone to obtain the needed information, and specify which later decision depends on it. Mark the item as unresolved rather than assuming it is included or excluded. If the answer could change the proposed work, ask the appropriate technical or legal professional to review it before the parties make a commitment.
To compare arrangements fairly, write down the same questions for each: who communicates with the contractor, who approves changes, how decisions are logged, what information each party must supply, and who updates the other party. A short comparison makes gaps visible. The best fit still depends on the lease, property, and specific project; no format removes the need for clear authority and documentation.
When can construction project support be useful?
Organized project support may be useful when work involves several decision-makers, related scopes, open questions, or coordination that needs a consistent record. Support can help keep responsibilities, decisions, and updates connected to the defined scope. It does not replace a landlord’s or tenant’s authority under their agreement, and it does not remove the need to review contracts or obtain appropriate technical or legal advice.
One Real Roofer and Construction serves residential and commercial customers in Texas, including Dallas–Fort Worth. Its service descriptions include pre-construction consulting, project management for short-term engagements of up to six months, and special-project support. Learn more about the company’s capital improvement work and other construction offerings. Whether a service fits a particular tenant space depends on the project scope and should be discussed directly.
Before asking for support, prepare a concise summary: the property and intended use, the current stage, what is already agreed, what remains unresolved, which party has authority, and what kind of coordination is needed. This helps keep an initial discussion focused on the actual project rather than assuming that the same approach fits every tenant space. It also helps distinguish a need for project organization from a legal question about the lease or a technical assessment of building conditions.
What about insurance-related questions?
If a tenant build out involves damage or an insurance question, keep each role clear. A contractor can discuss technical information about proposed work and estimates, but a customer should not assume that a roofing contractor can act as a public adjuster, negotiate a settlement, or file a claim on the policyholder’s behalf. The Texas Department of Insurance provides consumer and industry information at its official website. For a particular policy or claim question, contact the insurer or an appropriate licensed professional.
One Real Roofer and Construction describes help discussing the claim process and preparing or discussing contractor estimates. That description should not be read as a promise that the company files or negotiates a claim. Keep insurance questions separate from the landlord-tenant agreement about who is responsible for the work and its cost. If a claim is part of the background to the project, record what work is being considered and seek guidance from the appropriate parties about the claim itself.
Frequently asked questions
Who pays for a tenant build out?
There is no single answer for every lease. The lease and related written agreements determine which party is responsible for particular work or costs. Review those documents and ask a qualified legal professional to clarify unresolved contractual language before authorizing construction.
Does a tenant build out always mean a full renovation?
No. The term can refer to a limited set of improvements or a broader project. The exact scope depends on the existing space, the tenant’s intended use, the lease, and the written agreement between the parties.
Can a tenant hire a contractor directly?
That depends on the lease, property rules, and written approvals. Confirm who may engage contractors, who may direct work, what review is required, and how the parties will record authorization before work begins.
What should a tenant improvement agreement clarify?
As applicable, clarify the work and delivery condition, the responsible parties, approval authority, cost treatment, schedule assumptions, access, change process, and handoff expectations. Have a qualified legal professional review contractual terms rather than relying on a project summary to interpret the lease.
When should planning begin?
Begin when the parties can review the intended use, existing conditions, and lease requirements. Early discussion gives them a chance to identify missing information, resolve decision roles, and document scope questions before those issues become construction coordination problems.
Explore construction and roofing services
A well-planned tenant build out starts with a shared written understanding of the work, responsibilities, approvals, and handoff. Resolve those basics before construction begins, and update the record whenever the scope or known conditions change.
