What kind of project proposal are you preparing?
Identify whether the proposal covers professional fees, concept design, specification, equipment supply, coordination, or a combination. Each carries different responsibilities. A fee proposal describes work and deliverables; a supply proposal needs a clear product and commercial basis. State the boundaries before reusing a previous document.
Record what is being proposed before opening the last deck. Include the project stage and the decision the recipient is expected to make. Approval to explore a concept is different from authorization to proceed with a defined package.
The UIA’s procurement guidance connects the definition of architectural services with fee negotiation. That principle supports resolving scope before price presentation; it does not supply universal contract terms.
What should a proposal brief contain?
A proposal brief should establish the client objective, proposed deliverables, required inputs, open assumptions, specialist decisions, and the decision requested from the recipient. The NATA Proposal Preparation Record below organizes those six questions. An unresolved answer should be visible rather than silently inherited from the previous project.
| Question | What the team needs to establish |
|---|---|
| What is the client trying to achieve? | A project-specific outcome and constraints |
| What will we deliver? | Deliverables, stages, and the boundary of the service |
| What do we need from others? | Documents, access, decisions, and responsible people |
| What is still uncertain? | Assumptions that affect scope, effort, or timing |
| What requires our judgment? | Work that cannot be settled by copying a previous proposal |
| What decision follows this document? | Recipient, authority, and basis for agreement |
An unresolved answer does not automatically prevent a proposal. It tells the team what must be clarified, qualified, or offered as a separate stage.
Which parts of a project proposal can you reuse?
Reuse maintained descriptions of the studio, credentials, document conventions, and approved explanations of the working process. Reassess project scope, exclusions, dependencies, technical assumptions, and the recommended approach for each assignment. A stable component is reusable only when it still applies to this client and this work.
This also changes how proposal automation should be assessed. A system that inserts the correct team biography may remove administration. A system that silently carries forward a service exclusion can change the commercial meaning of the proposal.
How do you scope a lighting proposal when the request is unclear?
Separate concept design, detailed specification, equipment supply, and installation coordination before committing to a price. In an illustrative residential request, floor plans alone would not establish which of those services the client expects. Clarify the service boundary and the inputs needed to propose it responsibly.
Preparing a single price would hide that uncertainty. The preparation record instead establishes the proposed service boundary, the information needed to develop it, and the responsibilities held by others. If equipment supply is separate, the proposal makes that distinction visible. If a site visit is necessary before committing to a defined scope, that dependency is explained.
The proposal can then describe a coherent assignment. It does not need to pretend that every later product decision has already been made.
How can you check whether the proposal is clear enough to send?
Ask a reader outside the drafting process to identify the deliverables, exclusions, client inputs, and next decision. Then ask the delivery lead whether those commitments are feasible on the stated basis. Differences between their answers reveal scope or preparation issues that presentation polish will not resolve.
Different answers reveal a preparation problem worth resolving before design polish. A client should not need the author in the room to understand what is included. A project team should not discover its obligations for the first time after acceptance.
What should happen to the proposal brief after submission?
Retain the submitted version with its assumptions and approval history. Record negotiated scope changes and link the final agreed basis to onboarding and delivery. The receiving team should be able to understand what was promised without reconstructing the assignment from several files and someone’s memory.
The resulting record becomes useful beyond winning the work. It gives onboarding and delivery a common starting point: what the client expected, what the studio agreed to do, and which decisions still need to be made.
Frequently asked questions
Is a proposal preparation record the same as a contract?
No. It organizes the assignment and open decisions before submission. The applicable agreement governs the engagement; the record does not replace project-specific contractual or professional review.
Can a studio send a proposal with unresolved questions?
Yes, when it makes the uncertainty and its consequences explicit. Clarify whether the proposal is preliminary, limited to an initial stage, or dependent on named inputs before later work can be committed.
Will this preparation guide produce a finished proposal template?
No. It helps establish what the proposal should say and what must be resolved. The final format and terms depend on the service, project, and studio.
Sources and case basis
This guide presents a working method, not measured client results. Examples are illustrative unless explicitly attributed. Sources linked in the text support the stated principle or published example; they do not validate the NATA worksheet as an assessed instrument. Prepared and revised November 4, 2026.