Should a Commercial Construction Website Show Project Values?

Whether a construction project values website should publish exact contract amounts is not a question with one answer. Project values can help owners, developers, consultants, and general contractors understand your scale, but they can also create confidentiality, contractual, and context problems if they are published without approval.

The right approach is to decide what a project value is meant to communicate, then choose the least sensitive format that still gives the reader useful context.

Key Takeaways

• Project values can help a reviewer compare your experience with the scale of work they are considering.
• Exact values should only be published when they are accurate, current, approved, and unlikely to mislead without additional context.
• Value bands, approximate scale, floor area, schedule, scope, or project type can often communicate size without disclosing sensitive contract information.
• A value number is weak proof on its own; it becomes useful when paired with your role, delivery method, scope, sector, and project constraints.
• Do not use project values to imply responsibility for work delivered by a partner, joint venture, or another contractor.
• Create an internal approval process so project values and related details are reviewed before publication.

Construction project values website: when values help

Why project values can be useful

A project value gives a reviewer a point of reference. “Commercial construction” could describe a small tenant improvement, a major institutional expansion, or a multi-year industrial build. A value band helps the reader understand where your experience sits.

For example, these details communicate different things: project value: the approximate financial scale; floor area: the physical scale; duration: the scheduling and management context; scope: the work your company performed; delivery method: how the project was organized; sector: the type of buyer and facility involved.

A project value is most useful when it helps answer a qualification question: has this company worked at a comparable scale?

It is less useful when presented as a decorative number beside an image with no explanation.

When exact values may be appropriate

Exact values may be reasonable when: the client or project owner has approved publication; the information is already public; the number is accurate and has a clear definition; your company’s role is accurately stated; the amount will not be mistaken for your own contract value when it represents the entire project; the number is unlikely to change because of later adjustments; the project does not involve sensitive procurement or commercial information.

Even then, define what the number means. Is it the total construction value, your contract value, the original budget, the final value, or an approximate project cost?

Without that definition, an exact number may create more confusion than confidence.

Why exact values can create problems

Contractual confidentiality

Many projects have restrictions around client names, pricing, budgets, or public statements. A project may be visible in the public realm while the commercial terms remain private.

Scope confusion

A project valued at $50 million does not mean every contractor involved delivered $50 million of work. If your company completed the concrete package, site work, or a defined trade scope, say so.

Changes over time

Construction budgets, change orders, phasing, and project scope can change. An old number may become inaccurate even when the project page remains online.

Competitive sensitivity

Some clients or contractors may not want budgets, contract values, or capacity signals published. The fact that a number is available internally does not mean it belongs on a public website.

False comparison

A value number without sector, schedule, complexity, or scope may encourage the wrong comparison. A smaller project in an occupied hospital can require more coordination than a larger, straightforward build.

Alternatives to exact project values

When exact values are sensitive, consider publishing: value bands such as “$10 million–$25 million”; approximate project scale; floor area; number of units or facilities; project duration; phased delivery context; your contract scope; sector and building type; equipment or workforce requirements; approved schedule milestones.

The alternative should still be specific enough to help a reviewer understand the work. “Large commercial project” is almost as vague as no information at all.

A value band is often the best compromise. It communicates scale while reducing the risk of publishing a precise figure that is confidential, outdated, or easy to misinterpret.

How to write a project value into the page

A useful project summary might say:

> A multi-phase healthcare expansion in [region], delivered under [delivery method]. [Company] managed [approved scope] over [duration]. The project falls within the [approved value band] range and required coordination around an active facility.

This gives the number context. It also makes the company’s role clear.

Avoid writing:

> We built this $50 million hospital.

That statement may be inaccurate even if the total project value is correct.

Create a project-information approval workflow

Before a project page goes live, identify who approves: client and partner references; project name and location; photographs; value or value band; scope and role; delivery method; schedule; safety or performance metrics; outcomes and claims.

Add a review date where information can change. If a project page is reused in proposals, capability statements, and social content, one approved source record helps keep the details consistent.

When not to show a value

Leave the number out when: the client has not approved it; the source is uncertain; the project is still changing; your role is difficult to separate from the overall project; the number could create a misleading impression; the project is governed by a confidentiality agreement; the value is not actually useful to the audience.

A project page without a value can still be strong if it explains scope, complexity, sector, delivery method, and role.

+## Decide what the number is meant to prove

Before adding a value field to every project, ask what a qualified visitor will do with it. For some contractors, a value band is a quick signal that the team has worked at a familiar level of procurement, coordination, and financial responsibility. For others, it distracts from the more relevant evidence: a specialized scope, unusual access restrictions, a complicated phasing plan, or an established relationship in a priority sector.

That distinction matters because construction value is not a universal measure of difficulty. A modest renovation in an operating laboratory, hospital, or secure facility can require a level of planning that a large but straightforward greenfield project does not. A project page should therefore put the number beside the information that explains it. Readers should be able to see whether the figure represents the total project, a contract package, a phased program, or only a broad scale category.

It also helps to set an internal publication rule before the portfolio grows. Give project teams a short information form that asks what can be named, what must stay confidential, what role language is approved, and whether a range can be used. The review should occur while the team still has direct knowledge of the project rather than years later, when staff and records have changed.

If the company decides not to show values publicly, the page can still answer the scale question with verifiable context. State the building type, area, number of phases, schedule window, delivery method, or technical constraint. A reader who understands what the work involved is more likely to trust the portfolio than one who sees an impressive number without a clear relationship to your company’s contribution.