How Architects Get Paid

Beginners obsess over the percentage: is it six, is it ten? But a fee figure is meaningless until it is tied to a defined scope of work, a defined basis of construction cost, a defined number of design iterations, and a defined schedule of when money changes hands. The fee follows the scope; it does not precede it. The commonest cause of an unprofitable, embittering project is not a low fee - it is a fee agreed against a fuzzy scope, so that every extra option, every redrawn layout, every 'small change' is absorbed for free until the hours dwarf the income. So before we survey the mechanisms of payment, hold the master principle: whatever the basis, you are agreeing to do a specific quantum of work for a specific sum, and anything beyond that quantum is a variation that should attract more fee. With that in mind, this lesson walks through the main ways architects charge - percentage of construction cost, lump sum, time-charge, and unit or other bases - then looks at how fees are drawn down in stages, how cashflow actually works, and how to choose and defend a basis. Throughout, we treat the Council of Architecture's scale of professional charges as a neutral reference framework, not a rule to be quoted from memory.

The traditional and still most common basis, especially in India, is a percentage of the construction cost - the architect earns an agreed percentage of what the building costs to build. Its logic is that fee scales with the size and complexity of the project: a larger, costlier building generally demands more work. The Council of Architecture publishes a scale of professional charges that has historically served as a reference for such percentages, varying by building type and project stage; treat the exact figures as something to read from the current COA guidance rather than assume, and remember such scales are typically indicative references rather than rigidly enforced tariffs. The percentage model has two well-known weaknesses to understand. First, it can appear to reward higher cost - a perverse incentive the professional must consciously resist, since the architect's duty is to design economically. Second, the 'construction cost' base must be defined precisely: does it include or exclude land, interiors, external works, consultants' items, taxes? Ambiguity here is a frequent source of dispute. Used honestly, with the cost base clearly defined and the architect's duty to economy kept front of mind, the percentage basis remains a fair, intuitive way to price whole-building projects where the final cost is not known at the outset.

A lump sum (fixed fee) is a single agreed price for a clearly defined scope, independent of the final construction cost. Its great virtue is certainty: the client knows exactly what they will pay, and the architect knows exactly what they will earn - if, and only if, the scope is genuinely well-defined and the hours are estimated realistically. That 'if' is everything. A lump sum against a vague brief is a trap: the architect carries all the risk of scope creep, and every unanticipated iteration erodes the margin. Lump sums work best where the deliverables are crisp and bounded - a defined set of drawings for a known building type, a feasibility study, a specific report - and where the practice has enough experience to estimate the effort accurately. The professional discipline with a lump sum is twofold: build the estimate from a realistic assessment of hours (not a hopeful guess), and write an explicit list of what is included and, just as importantly, what is excluded and will be charged as additional. Done well, a lump sum aligns beautifully with a client's desire for budget certainty. Done carelessly, it is the fastest way to work for nothing.

Time-charge bills the client for time actually spent, at agreed hourly or daily rates for different grades of staff (principal, senior, junior). It is the fairest basis when the scope genuinely cannot be pinned down in advance: exploratory feasibility work, complex approvals of unknown duration, expert advice, heritage or dispute work, or open-ended additional services beyond an agreed scope. Because the client pays for exactly what is done, the architect carries little scope risk - but that shifts a different burden onto the practice: you must record time honestly and rigorously, because unrecorded time is simply unbilled time, and unbilled time is the silent killer of small firms. Time-charge also demands trust and transparency; clients dislike open-ended bills, so it is good practice to set a fee ceiling or an estimate with regular reporting, and to update the client before crossing thresholds. Many practices use time-charge as the natural basis for handling variations - when a client requests work outside the agreed lump sum or percentage scope, the extra is billed at time-charge rates. Mastering timesheets is therefore not bureaucratic drudgery; it is the mechanism that turns effort into income and makes every other fee basis measurable.

Beyond the big three, several other bases appear in practice. Unit rates charge per measurable unit - per square foot or square metre of built area is common in Indian residential and interiors work, and per drawing or per housing unit in repetitive projects. Unit rates are simple to quote and easy for clients to grasp, but like percentages they must be tied to a clear definition of what the unit includes. Retainers are recurring fixed payments for ongoing availability or a rolling scope - useful with institutional clients or developers with a continuous pipeline. Blended or hybrid bases are extremely common and often the most honest: for example, a lump sum for a well-defined concept and schematic stage, converting to a percentage of cost once the project's scale is known, with time-charge for any additional services. Real fee proposals rarely use a single pure model; they match the basis to the certainty available at each stage. The skill is not memorising models but diagnosing the scope in front of you and choosing - or combining - the basis that fairly allocates risk between architect and client. A good fee proposal makes that logic explicit so the client understands not just the number but why it is structured as it is.

Whatever the basis, the total fee is almost never paid in one go. It is drawn down in stage payments tied to the phases of work - a common pattern being an advance or retainer on appointment, then instalments as concept, schematic design, detailed design, tender documentation and construction-stage services are completed. Structuring stage payments well is a survival skill, not an afterthought, because it governs cashflow - the timing of money in versus money out. The figure shows the classic mismatch: your costs (salaries, rent) accumulate steadily as an S-curve from day one, but if fees only arrive in big lumps at the end of stages, the practice can be starved of cash in between even on a profitable project. The defences are concrete: take a meaningful advance so you are not funding the client's project from your own pocket; bill promptly at each milestone rather than letting invoices drift; front-load the fee slightly toward early stages, which carry the heaviest thinking; and never let unpaid invoices pile up before pausing work, as construction is an industry notorious for late payment. Cashflow, not profit, is what actually closes firms - a practice can be profitable on paper and still die because the cash arrived too late.

Put the models side by side, as in the figure, and a simple decision logic appears. The question behind every fee basis is: how well-defined is the scope, and who should carry the risk of it changing? When the scope is crisp and bounded, a lump sum gives the client certainty and rewards your efficiency. When the whole-building cost will grow with the client's ambitions but is unknown now, a percentage of cost shares that uncertainty fairly. When the scope is genuinely open-ended, time-charge protects you from carrying unbounded risk for free. When the work is repetitive and measurable, unit rates are clean and quick. Defending a fee, then, is not defending a number - it is explaining why the structure fairly matches the work. A client who understands that you charge time-charge for exploratory work precisely so they do not overpay for a fixed scope you cannot yet estimate will trust you more, not less. The mark of a professional fee proposal is that its logic is transparent: this scope, this basis, this schedule of payments, these exclusions. Get that logic right and the percentage argument mostly disappears.

In the Indian context the Council of Architecture's scale of professional charges is the reference point most architects reach for, and it deserves an accurate, neutral description. It sets out indicative percentages and a structure for how fees relate to building type and to the stages of an architect's services, and it functions as guidance and a professional benchmark. Two honest caveats. First, the precise figures and their current status are matters to read from the COA's own published guidance and the framework of the Architects Act, not to quote from memory or from dated summaries - fee guidance and its enforceability have been discussed and can change, so defer to the current position. Second, published scales are best understood as references that inform a fee, not tariffs that override commercial judgement; the actual fee still turns on the specific scope, the client, the risk and the market. Alongside the scale sit the ordinary commercial realities of Indian practice: fees attract GST, professional income is taxed, and a written appointment or conditions of engagement protects both sides. The professional posture is simple - respect the COA framework, describe it accurately and neutrally, and build each fee on a clearly defined scope.