Approach — The Cost of Ambiguity: Protecting the Value of a Lighting Design Scope

A lighting design engagement is not simply a set of documents, a list of luminaires or an occasional presence on site. It involves reading a place, forming an intention, making judgements, developing technical prescriptions, coordinating with the architecture and other disciplines, and often maintaining close attention until the project becomes real.

Because light sits at the intersection of perceptual, spatial, technical, regulatory and economic dimensions, part of this work can easily dissolve into the general workings of a project. The phenomenon crosses project types and territories. It takes different forms in France, India, Tunisia and elsewhere, depending on contractual practice, team structures and site culture. In international projects it can intensify further: a contract established in one jurisdiction, execution in another, distributed teams, multilingual documents and decisions made to different timelines.

Precision is not an administrative burden in such circumstances. It helps maintain continuity between teams, phases and responsibilities. The mechanism remains remarkably consistent: when lighting design work is not defined and recognised as an identifiable contribution, the designer’s expected availability tends to expand faster than the scope that is recognised and paid for.

The issue, then, is not only insufficient fees. It is ambiguity. Ambiguity does not remove the work, the cost or the responsibility. It merely shifts where they become visible.

When the scope becomes the project’s adjustment variable

Lighting design often enters a project at a paradoxical moment. It may be sought very early, when the architecture is looking for atmosphere, identity or a relationship between material, use, landscape, heritage and movement. It then reappears at far more constrained moments: once suspended ceilings are already fixed, provisions have disappeared, budgets are tightening, interfaces between contractors are becoming uncertain, or the site reveals the gap between the documents and what has actually been built.

At such moments, lighting design becomes indispensable while still being treated, at times, as expertise that can be called upon on demand: a trained eye expected to solve quickly what the project did not anticipate sufficiently, a presence assumed to remain available because it is still committed to the final quality.

The designer is then close to the original intention while also being directly exposed to the consequences of the project’s successive transformations. It becomes easy to ask for reviews, checks, arbitration, explanations, visits, corrections or focusing and adjustment, without always asking whether those actions still fall within the agreed scope.

One question should precede every additional request: does this request fall within the agreed scope, or does it constitute an extension of scope? The answer determines who carries the time, the risk, the responsibility and, ultimately, the real cost of the project.

Before the contract: when early thinking already becomes professional work

Many projects begin with what appears to be a light request: a conversation, a first meeting, an opinion, a few intentions, a short orientation note, a feasibility principle or a quick estimate. These steps can be legitimate. They are part of getting to know one another and assessing an opportunity. They become problematic when they continue, become more specific and begin to support project decisions without any formalised appointment.

An initial qualifying conversation can remain brief and help clarify a place, a team or an ambition. A feasibility study, by contrast, already produces hypotheses capable of guiding a budget, a tender, an approval or the continuation of an operation. A competition or bid can also be a useful stage, provided that its level of detail, conditions of use, attribution and each partner’s contribution are understood.

The critical threshold is not the number of hours spent. It is the moment when thinking is mobilised to inform, guide or rule out a project decision. Developing a strategy, setting out placement principles, identifying constraints, defining a design approach, comparing options, estimating an allowance or contributing to decisions already constitutes design work.

That value exists even when the option studied is ultimately rejected. An abandoned alternative, a negative feasibility conclusion or a discarded hypothesis may have prevented an error, clarified a budget or enabled a decision. Work that disappears from the final project has not disappeared from the work produced.

The risk is particularly high when the designer joins a team that has not yet clarified its responsibilities, contracts or budget. Work may be requested “to move things forward”, “to frame the issue”, “to help convince” or “to secure the submission”. The phrase sounds provisional; its effect may be lasting: ideas, documents and decisions circulate and sometimes remain embedded in the project even though the appointment was never contracted.

A professional framework does not prevent early conversations. It distinguishes exploratory exchange from design work. A one-off gesture, freely chosen within a relationship of trust, is not the same as expected and repeated availability. Work carried out before formalisation does not become less real because it was requested early; it simply becomes harder to protect.

Scope: what the engagement actually contains

A contract should not be seen as a defensive document reserved for conflict. It is first an instrument of mutual understanding. In a lighting design engagement, the scope should make visible the elements that are often assumed to be obvious when they are not: project phases, deliverables, number of alternatives or validation cycles, meetings, expected coordination, site presence, visits, tests, focusing and adjustments, handover, possible training, additional documents, changes after approval, duration of availability, role in exchanges with contractors, level of detail and effective responsibility for the choices produced.

The framework should also identify who is authorised to request, approve or commit a change. In a complex organisation, receiving a request does not necessarily mean receiving a contractual instruction. This distinction prevents a succession of informal requests from committing work, time and sometimes responsibility without a clearly assumed decision.

Without such precision, a word such as “support” can contain radically different realities. Supporting a feasibility study is not the same as following a project through handover. Producing a design package is not the same as revising drawings every time the architecture evolves. Attending a coordination meeting is not the same as assuming responsibility for general coordination. Making a site visit is not permanent supervision of the works. Defining an intention does not mean guaranteeing, alone, that every later decision will remain faithful to it.

Scope also has a temporal dimension. A six-month engagement compressed into six weeks does not mobilise resources in the same way. An engagement paused for several months and then restarted may require the context, decisions and document versions to be reconstructed. A change of counterpart may require previous decisions to be explained, retransmitted and sometimes revalidated. The project itself may not have changed; its organisational memory may have.

Ambiguity creates an asymmetry: the party making the request retains considerable latitude to describe it as included, urgent or essential; the party receiving it must demonstrate that it is not. This becomes particularly difficult when the programme tightens and quality appears to be at risk.

A clear scope does not make a project rigid. On the contrary, it allows the engagement to evolve healthily. When a new need appears, it can be identified, described, priced and incorporated through an amendment. An amendment is not merely payment for additional time; it records a decision that changes the project, its responsibilities and sometimes its economics.

When the project changes: information, rework and responsibility

Projects evolve. The programme changes, areas increase or decrease, a material disappears, a ceiling changes, a facade is redesigned, a budget is revised, a contractor proposes a substitution or an accelerated programme forces new decisions. Direction can also reverse: an option is developed and then abandoned, an approved decision is reopened, several alternatives are requested in succession, or validation cycles begin again.

None of this is abnormal in itself. Every design process involves iteration. The point is not to treat every adjustment inherent in normal project development as an additional service. The question is when new information, reversed decisions or additional cycles materially alter the assumptions, workload or responsibilities on which the original scope was based.

Likewise, rework required to correct an error, omission or deficiency that falls within the original scope is not an extension of scope. The important distinction is between such a correction and rework made necessary by new information, a changed decision or an additional request.

The problem begins when substantial transformations are expected to be absorbed into the original lump-sum fee even though they alter the assumptions on which the work was developed. An architectural change may affect viewing directions, placement distances and geometries, light levels, integration supports, interfaces with services, ceilings, joinery, furniture or structures, product references, optics, finishes, power supplies and budget approvals.

In that situation, the work is not simply a matter of “updating” a package. It may require a coherent design to be rebuilt, sometimes after several cycles of work have become invisible in the final version retained.

Design also depends on being informed. A removed provision, a reduced height, a changed finish, a substituted product or a shifted position can have direct consequences for light. The problem becomes acute when the designer discovers these changes by accident: during a visit, in an exchange with a contractor, on an isolated drawing or once installation is already under way.

In a complex project, being able to design also means being kept informed. Without current drawings, budget decisions, substitutions and decisions affecting the work, the designer is no longer simply asked to design. They are asked to discover what changed after the fact and repair the consequences.

Design time then becomes investigation time: identifying discrepancies, reconstructing decisions, measuring their effects, locating interfaces and proposing a response under pressure. That time is real. It should not remain invisible or be presumed to be included.

Coordination is a collective responsibility. It requires reliable information flow, identifiable document versions, traceable approvals and people clearly authorised to decide. A significant change should be traceable to a decision: who requested it, when, on which document, what consequences were identified and who approved the decision.

Without this minimum traceability, the cost of a decision does not disappear. It is transferred to whoever identifies the problem last. The lighting designer may contribute to coordination; without an explicit mandate, they should not become the person expected to repair the failures of that coordination alone. Detecting a change does not, by itself, create an obligation to resolve it without complete information, instruction and an extension of scope.

Clarifying responsibilities is not about allocating blame before it exists. It is about enabling each participant to act at the appropriate level. Depending on the project’s contractual allocation, the designer designs, specifies and raises alerts within their scope; coordination is carried by those appointed to do so; the contractor executes the works and reports constraints within its remit; and the client or its representative decides matters falling within its authority.

After the scope ends: when availability becomes a permanent expectation

The end of an engagement is another area of ambiguity. A designer may continue to be contacted long after deliverables have been issued or the theoretical end of the appointment: a contractor query, an unavailable product, a finish variation, a change of use, an additional visit, a delayed handover, an unplanned focusing session or an operational difficulty.

A visit or focusing session is not limited to a few hours on site. It requires preparation, rereading the available documents, sometimes travelling, responding to unforeseen situations, recording decisions and then dealing with follow-up actions. Focusing, in particular, is not a decorative final gesture. It requires concrete prerequisites: a completed and accessible installation, functioning power and controls, luminaires actually installed, site conditions suitable for observation, available technical information and authorised people present where intervention is required.

When these prerequisites are not met, a second visit caused by an incomplete installation, impossible access or a still-unresolved decision cannot simply become an invisible extension of scope. The request may be justified. It is not automatically included.

A designer’s availability does not become unlimited simply because their name remains associated with the project. An engagement has a duration, deliverables, an end phase and a defined level of responsibility. Beyond that point, involvement can resume, but it should be reframed: targeted assistance, a visit, expert advice, a diagnostic, an adjustment to a specification, handover support, focusing, or a new scope for an evolved project.

This clarity protects the project as well. A later intervention identified as a distinct service receives the necessary time, information and resources. Treated instead as a favour or an implicit continuation, it risks being carried out under pressure, without current documents or clarified responsibilities. Knowing a project does not mean carrying all of its consequences indefinitely.

Payment, responsibilities and rights: the conditions for continuity

Continuing to work while payments are overdue or uncertain creates a direct contradiction: the designer is expected to maintain commitment, respond to urgency and protect quality while the economic counterpart to that work is no longer secure. The engagement continues and requests accumulate, yet the cash flow that makes the activity possible is not treated with the same urgency.

For a small practice, fees fund design time, possible salaries, overheads, tools, travel, insurance, software, research, testing and the ability to give projects real attention. Late payment is therefore not merely an accounting matter: it can require the service provider who continues to produce to advance part of the resources needed to sustain the engagement.

Continuity of service depends on continuity of payment. This does not mean that every difficulty must end the working relationship. Complex projects experience delays, slow approvals and cash-flow constraints. But such situations need to be named, documented and addressed through a clear timetable. When an overdue invoice, essential information or a decisive approval is missing, formally documenting the blockage and clarifying the conditions for continuing helps prevent the engagement from proceeding without the means required to perform it properly.

The existence of a contract does not, by itself, guarantee a balanced relationship. Low fees may be paired with heavy obligations, penalties, constrained response times or responsibilities over which the designer has no effective control: contractor selection, general coordination, delays caused by third parties, product availability, permanent supervision of the works or final performance dependent on decisions made by others.

A responsibility can only be reasonably assumed if the designer has the information, level of authority, site access, programme and resources needed to carry it. Performance obligations, warranties, insurance requirements and availability commitments therefore cannot be read in isolation from the scope, fees and operational conditions of the engagement.

The conditions governing use of the outputs produced through an engagement deserve the same attention: documents, studies, drawings, details, images and, depending on the applicable law and the degree to which they have been formalised, certain design elements. It is important to understand what uses are authorised, on which media, in which territories, for how long, for which site or operation, and with what rights of modification, transmission to third parties, reuse or attribution.

Transmitting documents for the purposes of a project does not, by itself, amount to unlimited permission to reproduce, adapt or reuse them elsewhere. The value of an engagement is not exhausted by the time spent producing it; it also lies in what continues to circulate after it.

The most discreet risk is not always the obviously excessive clause. It may be the agreement given too early, before the contractual, operational and technical information needed to understand its consequences has been received. An accepted proposal or an urgent start should therefore be followed by an explicit check of what has actually been communicated, understood and accepted. The precise legal effects depend on the law applicable to the project.

Urgency may sometimes require rapid action to protect people, the site or the project. It does not remove the need to record afterwards what was done, why it was necessary, the limits of the intervention and what follows from it.

Quality as an invisible resource

The system often holds together because designers keep going. They keep going because they care about the place, because they know what the project could become, because they see the consequences of a poor decision before others can, or because they do not want years of thinking to be compromised by an uncontrolled detail, a rushed substitution or an absent focusing stage.

This attitude lies at the heart of professional commitment. It explains why lighting design does not stop when a document is issued. But it cannot become an implicit business model.

When a project relies on the designer’s commitment to quality to obtain unforeseen corrections, unplanned travel or prolonged availability, it turns a professional standard into a free resource. The paradox is clear: the more conscientious a designer is, the more exposed they are to absorbing what was never planned.

That effectiveness can even hide the dysfunction. If the designer repeatedly detects, corrects and restores coherence without being asked, an inadequate organisation may appear to function precisely because they absorb its consequences. Protecting the framework of an engagement is therefore not a withdrawal from the project; it preserves the practical conditions that make commitment possible.

For younger lighting designers, the issue is particularly important. Early years often encourage acceptance in order to learn, build a network, avoid missing an opportunity, remain involved in a promising project or demonstrate commitment. Those reasons are understandable. They should not establish the idea that design work can expand without limit. Setting a framework takes nothing away from generosity, curiosity or ambition. It gives the practice a future.

Collaboration and availability are not the same thing

Setting a framework is not a refusal to collaborate. A healthy professional relationship depends on each party being able to name what it requests, what it provides, what it decides and what it assumes. A preliminary study can be a project phase. A significant change can require an adjustment of scope. A visit or focusing session after closure can become a separate service. A clause may need to be understood or limited before signature. An invoice may need to be brought up to date before new resources are committed. Responsibility for coordination does not become the designer’s merely because it is not being exercised elsewhere.

These positions do not close dialogue. They distinguish collaboration from simple availability. Collaboration recognises that responsibilities are shared, decisions have a cost and final value rests on identifiable contributions. Implicit availability leaves the designer carrying the burden of resolving what was not framed elsewhere.

Defining scope, requesting the necessary information, formalising extensions, clarifying responsibilities, setting payment terms and framing rights of use and intellectual property are not acts of mistrust. They protect the designer, but also the client against misunderstandings, the architect against undefined areas of responsibility, the contractor against late or contradictory instructions, and the project against a succession of improvised corrections.

The quality of light cannot depend indefinitely on the invisible endurance of those who design it. It depends on a framework in which expertise is mobilised at the right time, with the right information, within an understandable scope, with proportionate responsibility and remuneration capable of sustaining the work actually required.

A contract does not replace trust. It gives trust a workable form. And when a project evolves, that trust is not measured by the designer’s capacity to absorb everything. It is measured by the collective ability to recognise what is changing, decide who carries the consequences and give every contribution the real means to exist.

Disclaimer

The value of a lighting design scope is not determined by the contract alone. It is also shaped by the project’s wider economics, the moment at which expertise is mobilised, the quality of coordination and the way the construction process transforms the original intentions.

Also read: What Construction Sites Teach Us About the Economics of a Lighting Design Project, which extends this reflection through the practical conditions in which projects are produced.

This article offers guidance on professional practice. It is not a substitute for legal advice adapted to the applicable law, the type of procurement or contract, and the responsibilities specific to each project.