PVA
All insights

Owner's Guide Owner-side insight

What to Send a Consultant for a Project Review (Drawings, Budget, Pro Forma, Bids)

A concise, organized document set helps a reviewer understand the decision, test assumptions, and identify what information is still missing.

By Ivan DuschatzkyPublished Updated 8 min read

Start with the decision you need to make

Before sending a large project folder, explain the decision the review should support. Are you considering whether to proceed with a design, checking an estimate, comparing bids, reviewing a proposed GMP, or reassessing feasibility? A focused question helps the consultant select relevant documents and identify missing information.

Include the decision maker, the date a recommendation is needed, and any constraints. Describe the project stage, current scope, and what has changed since the last approved baseline. State whether you want observations, a comparison, a risk review, or recommendations for next steps. Avoid asking a reviewer to “look at everything” without saying why.

Organize documents by topic and version. Give each file a clear name, date, and status such as draft, issued for bid, approved, or superseded. A cover index can list the document, version, author, and purpose. Keep superseded versions separate from current documents so no one mistakes a prior plan for the controlling set.

Agree on secure sharing after contact. Do not send sensitive information through an unapproved channel. Confirm access, transfer method, and confidentiality terms.

Drawings and scope documents

Send the current drawing set and specifications relevant to the review. Include the issue date, revision, and purpose of issue. If construction documents are not complete, say so and identify what remains under development. A partial set can still support a focused question, but conclusions should reflect its limits.

Include a short description of intended use, area or capacity assumptions, key program requirements, and owner standards. If the owner has approved a particular layout, system, finish, or performance requirement, identify the approval and source. Distinguish requirements from preferences that are still open to discussion.

For a design review, include consultant narratives, outline specifications, schedules, and relevant coordination information. If the concern involves structure, systems, envelope, parking, or access, point to relevant sheets and state the concern.

Provide addenda, bulletins, requests for information, and approved changes that affect the current design or scope. If a drawing has been revised to address an issue, include the earlier reference only when needed to understand the change. Do not mix unapproved markups with issued documents without labeling them.

An owner-side design efficiency review can examine whether the design aligns with the owner’s program and decision criteria. The consultant should state what disciplines and documents are within scope and which technical questions must be confirmed by the responsible design professionals.

Budget and estimate information

Send the current budget and supporting estimate. Include scope categories, quantities or assumptions, allowances, contingency, escalation assumptions, exclusions, and date. If it is a summary, identify who can provide detail.

Include prior estimate versions if the review concerns movement over time. A short variance summary can explain additions, deletions, design development, procurement updates, and known corrections. Keep changes in scope distinct from changes in pricing assumptions. The reviewer needs to know whether the comparison is like for like.

Share the commitment status. Identify executed contracts, purchase orders, pending proposals, approved changes, and unapproved changes. Show whether each amount is included in the current forecast. State how contingency and allowances are tracked and whether any amount is reserved for a defined risk.

If a cost model is connected to development assumptions, include the pro forma and identify which version is current. Explain the inputs the owner wants tested, such as program, schedule, financing assumptions, or revenue assumptions. A reviewer can check arithmetic and consistency, but should not treat uncertain inputs as verified facts.

When the concern is whether the development assumptions still align, a pro forma review can help clarify how assumptions interact. Provide source notes for important inputs and flag information that is preliminary or supplied by a third party.

Bids, proposals, and procurement records

For a bid comparison, send the complete proposals, bid form, issued drawings and specifications, addenda, and any instructions to bidders. Include the bid tabulation if available, but do not rely on a summary that omits qualifications or scope notes. The full proposal can contain assumptions that change what a headline number represents.

Provide written bidder questions and answers, clarifications, alternates, exclusions, and post-bid communications. Identify whether revised proposals were requested and which version is under consideration. Mark any verbal understanding as unconfirmed until it is documented.

Include the procurement plan and schedule when timing affects the question. Note packages already awarded, anticipated award dates, long-lead decisions, and interfaces among packages. The reviewer should understand whether the owner is comparing complete bids, partial scopes, or proposals prepared under different assumptions.

A bid-leveling review is only as useful as the documents and comparison rules behind it. Ask the consultant to identify gaps, qualifications, and unresolved scope rather than forcing incomplete proposals into a false ranking.

For an existing GMP or negotiated contract, include the draft or signed agreement, exhibits, schedules of values, scope matrix, allowances, assumptions, exclusions, and clarifications. The GMP review should use the contract set that will actually govern, not a presentation summary that omits attachments.

Pro forma, schedule, and decision records

When feasibility or timing is in question, provide the current pro forma, source assumptions, development schedule, and status of approvals. Indicate which inputs are owner-approved, consultant-estimated, or still under discussion. Include relevant site information and third-party correspondence only when it bears on the defined question.

Share the current master schedule and any recent updates. Point out milestones that drive decisions, procurement, financing, or occupancy. Include schedule narratives explaining critical dependencies where available. Avoid presenting an old schedule as current simply because it is the only formal version.

Decision records can be as important as formal drawings. Include meeting minutes, owner approvals, decision logs, change registers, and relevant correspondence. Identify decisions that were provisional or conditional. If the review concerns a disputed issue, provide the record of each party’s position and the contract communication path.

Do not overwhelm the reviewer with every email or file created since project inception. Curate the information, but do not omit a record because it may complicate the analysis. Make clear what was not included and where it can be found. The reviewer can request the next layer if the first review identifies a need.

Explain context and what is uncertain

A document set needs a short briefing. Explain the project’s purpose, stage, participants and roles, owner priorities, and reason for review. Name key questions and decisions that need confirmation.

Separate facts from assumptions. For example, say a proposal was received on a stated date, while noting that scope alignment remains unverified. Explain if a figure is an allowance, an estimate, a contract amount, or an owner target. If a schedule date is aspirational rather than committed, label it.

Tell the reviewer about known constraints and sensitivities, including approval status, operating requirements, financing or procurement deadlines, and decisions that cannot easily be reversed. Include only appropriate confidential details and use the agreed transfer channel.

Be candid about missing information. A missing geotechnical report, incomplete design, or unresolved utility issue can affect what a reviewer can conclude. Listing gaps up front helps the consultant qualify findings and avoid treating absence of evidence as proof that an issue is resolved.

Use a simple document index

An index reduces confusion and helps you retain control of versions. A basic table can include file name, date, status, discipline, and relevance to the review. Put current controlling documents first, then background and superseded references.

Use consistent naming such as “Project_Discipline_DocumentType_Revision_Date.” Keep original files intact. If you create a combined or redacted copy, identify it as a copy and preserve the source file. Note whether a document is draft, issued, approved, or for information only.

Set expectations for findings

Ask what deliverable the review will produce. It may be a written issue list, a meeting, a comparison, or a recommendation memo. Agree how findings will distinguish confirmed facts, assumptions, questions, and actions. Ask the reviewer to identify the source document and responsible person for each material observation.

Clarify whether the review includes independent calculations, site visits, interviews, or coordination with the project team. Do not assume those tasks are included. If a question needs a licensed professional, legal counsel, contractor pricing, or agency confirmation, identify who will obtain that input.

Agree how the reviewer can contact the project team and who may share findings. A reviewer should not issue direction to the contractor or change design documents on the owner’s behalf unless the parties have established that authority. The owner remains responsible for authorizing actions through the project’s agreed process.

When the review ends, record the owner’s disposition of each finding. Mark accepted actions, declined recommendations, items requiring more information, and risks the owner elects to retain. Update drawings, budgets, procurement records, and schedules through the appropriate channels. This closes the loop between review and execution.

Frequently asked questions

Do I need to send every project file?

No. Start with the documents tied to the decision and provide an index of what is included. Do not conceal relevant records. Tell the reviewer what is missing and provide additional material when the review identifies a need.

Can a consultant review an incomplete design?

Yes, if the assignment reflects the design’s status. Identify the issue date, incomplete areas, and open assumptions. Findings should be qualified, and technical conclusions should be confirmed by the professionals responsible for the design.

How should I share confidential project documents?

Agree on confidentiality and a secure transfer method after initial contact. Confirm intended recipients and access, then share only the files needed for the assignment. Do not assume that an ordinary email attachment is an approved secure channel.

About the author

Ivan Duschatzky

Co-Founder & Managing Partner

Leads client relationships and brings a national construction leadership network.

Meet the PVA team

Keep reading

A second set of eyes

Your next project decision deserves a closer look.

Scope and commercial terms are agreed in writing.

Request a project review
Confidential fit discussionRequest a project review