What owners should have ready before a preconstruction meeting

A preconstruction meeting does not require a finished set of answers. It does require enough information to understand the property, the owner’s priorities, the decisions still open, and the work needed to move from an idea toward a buildable scope.

The goal of the first meeting is not to force an immediate price or promise a schedule. It is to identify what is known, what must be verified, who decides, and what the next planning step should produce.

Start with a one-page project brief

Prepare a short summary that a person new to the project can understand. Include:

• The property and approved access contact
• The current use and intended use
• The type of work being considered
• The spaces or systems expected to change
• The owner’s highest priorities
• Known occupancy or operating constraints
• Target timing and the reason behind it
• The people who will approve scope, design, budget, and schedule decisions

If an item is unknown, mark it as unknown. A visible question can be assigned and resolved. A hidden assumption usually reappears later as a change.

Gather the current property record

Bring the documents already available. Depending on the property and project, that may include surveys, drawings, floor plans, finish schedules, prior reports, photographs, equipment information, lease or operating constraints relevant to construction, and records of earlier work.

Do not assume an old plan reflects current conditions. Identify its date and what has changed since it was prepared. The construction team can then decide which dimensions, systems, and details need field verification.

Create one shared file location with clear names and dates. The latest plan should be easy to distinguish from a superseded option.

Describe the intended use in operating terms

“Renovate the building” does not explain how the finished property needs to function. Describe who uses each area, when it is used, what must remain available during work, and what the owner expects at handoff.

For a home, this may include room relationships, storage, daily routines, and finish priorities. For an apartment property, it may include unit release, resident access, common areas, and turnover. For a church or small commercial building, it may include service hours, events, staff access, deliveries, and spaces that must stay open.

These facts shape scope and sequence. They also help the contractor identify questions that need design or trade input.

Separate priorities from preferences

Owners often bring a long wish list. Sort it into clear levels:

1. Required for the project to proceed: work tied to the core intended use or a condition the owner has decided to address.
2. Strong priority: work the owner wants included if scope and budget support it.
3. Option: work that should be priced separately or held for a later phase.
4. Needs investigation: a condition or idea that cannot be defined from current information.

This is more useful than asking every item to compete equally inside one number. It gives the estimator a way to structure base scope, alternates, allowances, and later phases.

Bring a budget framework, even when it is early

A budget discussion is most useful when it explains what the number includes. State whether the owner has a target range, a maximum authorization, financing constraints, owner-purchased items, design costs, permit or review costs, contingencies, and work outside the construction contract.

An early range is not a final price. It helps the team test whether the current scope direction and finish expectations belong in the same conversation.

When a selection or condition is unknown, decide how it will be carried: excluded until defined, included as an allowance, priced as an alternate, or investigated before the proposal is completed.

Explain the schedule constraint behind the date

A target completion date by itself does not show what drives it. Tell the team whether the property has a lease event, planned occupancy, sale preparation, financing milestone, seasonal concern, scheduled program, or another fixed constraint.

Then identify the inputs that affect the construction sequence:

• Access and occupancy
• Design and owner decisions
• Required reviews or approvals
• Long-lead selections and materials
• Utility availability or shutdowns
• Existing-condition investigation
• Work by others
• Owner-furnished items

The first schedule conversation should identify dependencies and decision dates. A dependable schedule comes later, after the scope and conditions are clear enough to sequence.

Name the decision-makers and communication path

Projects slow down when several people give direction without a defined approval path. Identify who can approve scope, price, design, finish, access, change, and schedule decisions.

Agree on where current information will live and how field questions will be recorded. A practical communication record includes the question, affected area, options or recommendation, requested decision date, final direction, and effect on scope or timing.

The project may have many stakeholders, but the field team still needs one clear source of authorized direction.

Prepare the property for a useful walk

Confirm how the team will enter, which areas can be inspected, and whether keys, escorts, ladders, utility access, or special scheduling are needed. Clear enough access to see the areas under discussion.

If a space cannot be entered or an item cannot be tested, record that limit. Decide whether the next step is a return visit, owner-provided information, trade review, testing, or an estimate assumption.

Photograph existing conditions with wide and detailed views. Label the area so the photographs can be matched to the notes and scope.

Leave the meeting with assignments, not loose conversation

A useful preconstruction meeting should produce a short action list:

Use actual names and dates in the working version. Confirm what the next meeting will review: a revised scope, field findings, plan update, selections, estimate structure, or preliminary sequence.

The minimum useful package

If time is limited, bring the one-page brief, available plans, current photographs, intended use, priority list, budget framework, target timing, access details, and decision-maker list.

That package will not answer every construction question. It will help the team spend the meeting on the property and the work instead of searching for basic information.

Houston application

For a Houston project, identify the actual jurisdiction and review path instead of assuming every address follows the same process. Bring known property records and current drawings, then assign responsibility for verifying permits, trade requirements, utilities, and inspections. KIBA uses the first meeting to expose these dependencies early.

KIBA begins the construction conversation with the property, intended use, scope priorities, constraints, and available documents. Review residential construction, review multifamily renovation, or send the information available today.