Project client

A Project client brings:

• a clear value proposition covering time and cost;
• a clear functional goal for the building;
• a funding plan covering provision and operation;
• a site;
• a delivery timeframe; and
• a building lifecycle plan.

The value proposition provides the basis for judging cost, time and emerging design choices.

The Project client is responsible for:

• engaging a Building designer;
• working with the Building designer to determine whether the proposal is viable;
• maintaining the financial basis for the project;
• making the strategic decisions needed for progress; and
• establishing a Site office once the project is sufficiently viable.

Initial proposal→viability exercise→decision to proceed→establish Site office

The Project client launches the building specification with the help of the Site office. The Site office provides the administrative and document-control support needed to establish the version-controlled document using the current specification format and schema.

The Project client and Building designer then populate its initial version with an agreed expression of:

• the functional goal;
• the site;
• the delivery timeframe;
• the value proposition and financial constraints;
• the funding plan;
• the lifecycle intent; and
• strategic approvals and decisions.

Together, they give the first concrete form to that intent. Early work may establish:

• accommodation-module dimensions;
• the number and arrangement of accommodation cells;
• the required mix of accommodation units;
• the module combinations needed to create them;
• the broad foundation approach; and
• initial ideas for roofing and facades.

The client defines the required outcomes, constraints and accommodation needs. Specialist designers and engineers determine the technical means of achieving them. The Site office supports the document and versioning process; responsibility for the information remains with the roles that contribute and approve it. The client and Building designer can use the ExoSett Sketch app to explore early ideas about scale, frame arrangement and capacity.

Cost is considered from the outset. Early building ideas are compared with indicative costs and the client’s value proposition, allowing scope and design to be revised while the project is still fluid.

The ExoSett building specification is a living document. Its early versions capture the project intent; as the project develops, it evolves to capture the detail needed to realise that intent.

The Project client initiates its strategic requirements. Specialist project participants contribute and approve the portions for which they are responsible and appropriately qualified. The Site office administers the approved specification through procurement, delivery, operation and later change.

The ExoSett modelling repository is the authoritative technical source for its format, schema, examples and versioning guidance.

Copy this prompt into an AI model of your choice. It asks the model to work from current technical information and to keep client and specialist decisions distinct.

Show the complete Project client prompt

Copy prompt

Guide me through the Project client role for an ExoSett building project. Use the ExoSett modelling repository as the primary technical reference for the building specification, schema, examples and versioning guidance: https://github.com/ExoSett/modelling Before guiding me through the specification, inspect the current contents of that repository, including the schema and relevant documentation and examples. Do not assume that the schema or documentation has remained unchanged since this prompt was written. If you cannot access the modelling repository or ExoSett Sketch app directly, say so clearly and ask me to provide the relevant files, documentation or outputs. Do not infer their current contents from this prompt. Base your description of ExoSett and the building specification on the current ExoSett sources rather than on assumptions about conventional modular construction. Do not introduce characteristics that those sources do not specify. In particular, do not assume or state that ExoSett frame structures are permanent, or that accommodation modules are temporary. Frames, modules, services and other parts of an ExoSett building may have different intended lifecycles according to the particular building specification. When information is not defined by the ExoSett sources, identify it as something to be established for this project rather than filling the gap from general knowledge. Ask me for missing information or explain which source needs to be consulted. Begin by introducing the Project client role, including what a Project client brings to the project, what they are responsible for, and what they are expected to deliver. Distinguish between the knowledge and authority the client brings and the clear, agreed expression of that knowledge which the client delivers to the project. Then explain the ExoSett building specification and how it is used. Describe it as a living document whose early versions capture the project intent and which evolves to capture the project detail. Explain that, once the Site office has been established for the project, the Project client launches the building specification with its help. The Site office provides the administrative and document-control support needed to establish the version-controlled document using the current specification format and schema. The Project client and Building designer then populate its initial version with the agreed functional goal, site, delivery timeframe, value proposition, financial constraints, funding plan, lifecycle intent and their early work. The Site office supports the document and versioning process; responsibility for the information remains with the roles that contribute and approve it. The specification is ultimately owned by the Project client and administered by the Site office through procurement, delivery, operation and later change. Help me understand which parts of the building specification I am expected to initiate, contribute to, review or approve as Project client. Make clear that specialist technical portions must be completed and signed off by appropriately qualified project participants. Work through the process in a sensible sequence. In particular: * help me articulate the functional goal and value proposition for the building, including how value, time and cost relate and how the proposal may need to respond to changing circumstances; * establish the site, delivery timeframe, funding plan and lifecycle plan; * help me prepare the information needed to engage a Building designer; * guide me through the early viability stage with the Building designer, using the ExoSett Sketch app where useful to explore and communicate initial building ideas; * help me compare emerging building ideas with indicative cost estimates based on professional experience, precedent and available market pricing, and revise the proposal where necessary; * help me launch the version-controlled building specification with the Site office after it has been established for the project; * explain how the Project client and Building designer populate its initial version, including the emerging module dimensions, proposed cell arrangement, accommodation mix, foundation approach, roofing and facade ideas; * identify the point at which the project is sufficiently viable to justify proceeding; and * help me understand when and why a Site office should then be established. Do not assume that every project forms its team in the same order. A Building designer may begin work before implementation staff are in place, or a Site office may already exist when the Building designer is engaged. Assign responsibilities according to the nature of the work: the Building designer leads design development, the Site office leads implementation planning, and both should work flexibly while responsibilities are emerging. During the early viability stage, use the ExoSett Sketch app where helpful to explore simple building ideas visually: https://www.exosett.com/design/sketch/ Use it as an exploratory tool rather than as a substitute for professional design. It can help the Project client and Building designer discuss possible frame arrangements, scale and accommodation capacity before the building specification becomes more detailed. Explain how information moves from exploratory to agreed and, eventually, locked as the building specification develops. The Building designer should communicate design maturity and dependencies. The Site office should communicate implementation, procurement, programme and construction consequences. Before suggesting that a locked element be reopened, explain the likely cost and effects on related decisions and completed work. Changing accommodation-module dimensions late in a project, for example, may have extensive consequences and be very expensive. When the building specification begins to take shape, use the current ExoSett modelling schema and documentation in the repository to show me how the relevant information should be represented. Ask questions where information is missing rather than inventing project details. Distinguish clearly between decisions that belong to the Project client and technical decisions that should be made by the Building designer or other specialists. If I provide an existing ExoSett building specification, identify the schema version used by that document and work with that version. Do not silently migrate it to a newer schema. If a newer schema may be useful, explain the difference and present migration as an explicit choice.

Return to ExoSett project roles.