Practice & Project Management, Mapped

Everything in the business of architecture divides cleanly into two territories, and holding them apart is the single most useful map you can carry. The practice side is about the firm as a lasting enterprise: what the profession is and how it is regulated, how you set a practice up, how you win and do the work, and how you run the office year after year. The project side is about any single job: its stages from first idea to handover, how you manage it to time and budget, how you assemble and lead the team, and how the contracts hold everyone to their word. The first three lessons of this module lived mostly on the practice side - the profession, the role, the money. From here the course will move between the two territories deliberately, and this lesson gives you the map so you always know which one you are standing in. The distinction matters because the skills are different: running a practice is a marathon of small, repeated disciplines, while running a project is a sprint with a defined finish line. Confuse them - manage the firm like a project, or a project like a firm - and both suffer. A firm run like one long project lurches from deadline to deadline and never builds the systems that outlast any single job; a project run like a firm drifts without the discipline of a finish line. See them instead as two connected territories, each with its own rhythm, and the whole field becomes navigable rather than an overwhelming heap of disconnected topics.

The practice side has four natural regions, and the course devotes modules to each. First, the profession: the statutory frame within which you operate - in India the Architects Act 1972 and the Council of Architecture, registration, the code of conduct, professional ethics and liability - the ground rules of being an architect at all. Second, setting up: choosing a legal form (proprietorship, partnership or LLP via the MCA), registration and tax (GST, income tax), insurance, and the practical scaffolding of a new studio. Third, getting and doing the work: marketing and reputation, winning commissions, writing fee proposals and appointments, and managing the production of drawings and services to a professional standard. Fourth, running the office: people and teams, finances and cashflow, quality systems, technology, and the leadership that keeps a firm healthy over decades. These four regions answer the enterprise questions raised in lesson one - they are how you build the machine that produces projects, rather than any single project itself. If lesson one told you a practice is a system, the practice-side modules are the instruction manual for building and maintaining that system deliberately.

The project side is about delivering one job well, and it too has four regions. First, the stages: every project moves through a recognisable sequence - inception and brief, feasibility, concept design, detailed or developed design, tender and procurement, construction, and handover - and knowing where you are keeps everyone aligned. Second, project management: the disciplines of scope, time (programme), cost and quality, plus risk and communication - much of it drawn from bodies of knowledge like PMBOK from the Project Management Institute, adapted to design and construction. Third, the team: the client, the design consultants (structural, MEP and specialists), the contractor and supply chain, and the authorities - assembling them, defining who does what (a discipline captured in tools like the RACI matrix), and leading them. Fourth, contracts and procurement: how the project is bought (the procurement route), the standard forms that govern it (FIDIC, JCT, NEC internationally; and Indian forms and CPWD conditions), and the administration of the contract on site, including the architect's certifying role from lesson two. Together these turn intention into a finished building, on time, on budget and on brief - and they are the sprint to the practice side's marathon.

Because projects always move through stages, the profession has standard frameworks that name those stages so a whole industry can speak the same language. The best known internationally is the RIBA Plan of Work (2020), which organises a project into eight stages, from Stage 0 Strategic Definition through Stage 7 In Use, each with defined outcomes, tasks and information exchanges. The AIA documents describe a comparable sequence for the US context, and different countries and clients - including large Indian public bodies such as the CPWD - use their own stage nomenclature. The exact names and boundaries vary, but the underlying logic is universal: define before you design, design before you detail, detail before you build, and confirm before you hand over. Learning one stage framework well lets you translate any other, and it gives you the scaffolding on which fees (stage payments), programmes (the schedule) and responsibilities (who does what, when) all hang. When later modules discuss when to take a fee instalment or when a particular risk peaks, they will refer to these stages, so it is worth getting comfortable with the sequence now. Treat the Plan of Work as a shared vocabulary, not a straitjacket - adapt it honestly to the project and the local context in front of you.

Now put both territories on one page, as the figure does. On the left sits the practice side - profession, setup, work, office - the enduring enterprise. On the right sits the project side - stages, management, team, contracts - the individual job. This course walks across the map roughly left to right and top to bottom: it grounds you in the profession and the business (where you are now), then equips you to set up and run a practice, then takes you through delivering projects and administering contracts. Every module you meet from here has a home somewhere on this map, and whenever a topic feels abstract you can locate it - 'this is a project-side, team-and-contracts question' or 'this is a practice-side, running-the-office question' - and the confusion usually clears. The map also reveals why the course is ordered as it is: you cannot sensibly run projects for a firm that does not exist, so practice foundations come first; but you cannot run a firm without delivering projects, so the two must eventually interlock. Keep this figure in mind as your table of contents made visual - a single glance that tells you where any lesson belongs and how it connects to the rest.

The two territories are not walls; they are neighbours with a busy border, and the most important lessons happen at the crossing. A fee proposal is where practice (how the firm charges) meets project (the scope and stages of the job). A programme is where project timing meets practice cashflow, because stage payments fund salaries. A variation is where project scope-change meets practice profitability. Resourcing is where the office's people (practice) are assigned to a job's stages (project). Even risk lives on the border: a risk carried on a project can threaten the whole firm if it goes wrong. This is why treating the two sides as entirely separate is a mistake - the health of the practice is the sum of how its projects go, and the fate of each project depends on how well the practice supports it. The mature principal reads both maps at once: every project decision is also a practice decision, and vice versa. As you learn each side in depth, keep asking how it touches the other; that habit of double vision, first met in lesson one, is what turns a competent designer into someone who can actually run the whole enterprise.

A few practical notes on how to use what follows. If you are a student or aspiring architect, read broadly and in order - the sequence is designed to build intuition before detail, and the practice foundations will make your later technical modules make sense. If you are a practising architect or principal, you may dip into the module that answers today's problem - a fee dispute sends you to the getting-and-doing-work region; a struggling delivery sends you to project management - and the map tells you exactly where to go. If you are a project lead or manager, the project-side territory is your home ground, but the practice-side lessons will show you why your delivery decisions matter to the firm's survival. Every lesson carries three tiered readings for exactly these audiences, plus workshops that turn ideas into artefacts you can actually use - a fee proposal, a programme, a risk register. The point of a map is not to admire it but to travel; from the next module onward we start walking, beginning with the profession itself - what it means to be a registered architect and to practise within the frame the Architects Act and the Council of Architecture set. A final word on how to read the tiers: they are not three difficulty levels but three vantage points on the same idea, so glance at all three even when only one is 'yours' - the principal's view teaches the student where they are heading, and the student's plain framing often clarifies things for the principal too. Skim the workshop and misconception in every lesson even when you are short of time; between them they carry much of the practical value. You now have the whole territory in view. Let us begin crossing it.