HourTab

Blog › ICP guides

Architect on retainer: how to track pre-drawing hours and communicate ongoing value to development clients

July 13, 2026 · ~13 min read

The building permit is the first visible milestone most real estate development clients can point to as evidence that an architectural engagement produced something. Before the permit application — often months before it — an architect on retainer may have evaluated a dozen sites the developer did not acquire, attended pre-application conferences with three different planning departments, researched code compliance paths for designs that were never built, and provided ongoing advisory on zoning strategy, entitlement risk, and project feasibility across an active acquisition pipeline.

None of that work produced a drawing. None of it produced a submittal. It produced informed development decisions: which site to buy, which project size is code-compliant, which design approach minimizes entitlement risk, which variance is likely to succeed. The developer who made those decisions based on the architect’s advisory may not connect the advisory to the decisions because the advisory happened in meetings and emails rather than in drawings.

This creates a specific billing dynamic in architecture retainers with development clients. Full design services — schematic design, design development, construction documents — produce visible deliverables that clients expect to pay for. Pre-design advisory — site feasibility, code research, pre-application consultation, entitlement strategy — produces decisions and avoided mistakes, which are harder to make visible on an invoice. When an architect’s retainer invoice arrives for a month in which no drawings were produced, the client who does not understand what the advisory consisted of will ask what was produced.

This guide covers what ongoing architectural advisory for real estate development clients actually consists of, what categories of work are most commonly underlogged, how to structure and communicate retainer hours so development clients understand the pre-design advisory their retainer covers, and the contract clauses that prevent billing disputes in architect retainer engagements.

Why architecture retainers are distinct from project-based architectural services

Most architectural services are engaged project-by-project: a specific building, at a specific site, with a defined design and permitting scope. The architect is hired when the developer has already acquired the site, defined the program, and made the decision to proceed. Services are scoped, milestones are defined, and fees are structured around deliverables.

An architect on retainer operates upstream of that engagement. The retainer covers the advisory that happens before a project is ready to be scoped: evaluating potential acquisition sites for development capacity, advising on the zoning and code constraints that will define what can be built, consulting with planning departments before a project is formal enough to submit, and providing ongoing advisory on entitlement strategy and regulatory risk across the developer’s entire active pipeline.

The value proposition is different. A project-based architectural engagement produces a building. A retainer engagement produces the developer’s ability to make faster, better-informed decisions about which sites to acquire, which project types are feasible, which entitlement approaches are viable, and which risks are worth taking. That value is real, but it is diffuse and invisible in a way that a set of construction documents is not.

An architect who cannot document the advisory advisory work that produced those decisions will face a retainer conversation in any month where no drawings were produced and no permit was submitted.

What ongoing architectural advisory for developers actually consists of

Site feasibility analysis

Real estate developers evaluate far more potential acquisition sites than they purchase. A development firm actively pursuing infill residential, mixed-use, or commercial opportunities may assess 10 to 20 sites for every one it acquires. Each site evaluation requires architectural analysis: what zoning applies, what development capacity the zoning allows (maximum FAR, height limits, setbacks, lot coverage, parking requirements), whether any overlay districts or special regulations apply (historic districts, coastal zones, earthquake hazard zones, affordable housing requirements), and what constraints will define the development envelope before design begins.

This analysis takes 3 to 8 hours per site depending on complexity. A straightforward infill residential site in a standard zoning district may take 3 hours to evaluate thoroughly. A commercial-to-residential conversion in a historic district with multiple overlay zones and a pending area plan revision may take 8 to 12 hours. The analysis for sites the developer does not acquire still consumed those hours — and in many cases, the decision not to acquire was the direct product of the architect’s analysis.

Log site feasibility entries at the site address or identifier level, with the specific zoning and code findings and the development capacity conclusion. A client who sees monthly entries for the five sites evaluated in June understands that the site selection process is actively managed; a client who only sees entries when a site is acquired understands nothing about the advisory behind the acquisition pipeline.

Code compliance research

Building codes — local amendments to the International Building Code, fire and life safety codes, energy codes, ADA accessibility requirements — govern what can be built and how it must be built. For development clients, code compliance research answers the question of what a specific project type requires before design begins: what type of construction is allowed for a 5-over-1 multifamily building, what the maximum travel distance to egress stairs requires in a given occupancy, what energy code compliance pathway the project will pursue, what accessibility requirements apply to specific unit types.

The most invisible code research is the research that finds constraints rather than solutions. Analyzing a proposed project approach, identifying that it requires a code variance or modification that is unlikely to be granted, and advising the developer to adjust the project program is advisory work that produces no drawing but saves significant cost. Log code research at the specific code section, project type, and finding level.

Pre-application consultation with planning departments

Pre-application conferences — meetings with city or county planning department staff to review a proposed project before formal application submission — are one of the most valuable and least visible services an architect provides in a development retainer. A productive pre-application conference identifies entitlement issues early, establishes staff’s interpretation of ambiguous code provisions, and reveals the informal design preferences that will affect project approval, none of which appears in published regulations.

What does not appear on the retainer invoice without explicit logging is the preparation work: researching the site-specific zoning and applicable design guidelines, drafting the questions and preliminary design description for the pre-application meeting, preparing exhibits that describe the proposed project without constituting a formal design submittal. This preparation often takes 2 to 4 hours and precedes a 1 to 2 hour meeting. Log the preparation and the meeting separately, with notes on the findings and planning staff’s positions on key questions.

Entitlement strategy advisory

Entitlement — the process of obtaining discretionary approvals for a development project (conditional use permits, variances, design review approvals, environmental clearances) — is where development projects succeed or fail before construction begins. An architect on retainer provides ongoing advisory on entitlement strategy: which discretionary approvals will be required, which are routine and which are contested, what the precedent record suggests about variance success rates for specific project types, how to sequence the entitlement process to minimize cost and timeline risk.

Entitlement strategy advisory produces no drawing and no application. It produces the developer’s decision about how to sequence approvals and whether a specific project program is worth pursuing given the entitlement risk. Log entitlement strategy entries at the project and approval type level, with the specific risk assessment and recommended strategy.

Design advisory and third-party review

Development clients who employ design teams for specific projects may retain an architect separately to provide advisory review of the design team’s work: reviewing schematic design alternatives for code compliance and entitlement risk, identifying design decisions that create construction cost implications the developer may not anticipate, and advising on the regulatory response to design choices before the project is too far along to change them. This is distinct from serving as the architect of record on the project.

Third-party architectural review is one of the least understood retainer services because the developer may not fully grasp that code compliance review of a design team’s work is a separate service from producing the design. Log design advisory entries at the specific design issue, the code or entitlement concern identified, and the advisory recommendation.

What architect retainer work is most commonly underlogged

Site feasibility for sites not acquired. An architect may evaluate 8 to 15 sites in a quarter for every one the developer acquires. Each evaluation represents real advisory hours spent on zoning analysis, development capacity calculation, and constraint identification. These hours are systematically underlogged because the site was never acquired — the natural inclination is to log advisory work that led to a project, not advisory work that led to a pass. Log site feasibility work for every site evaluated, not just the ones acquired.

Pre-application meeting preparation. The pre-application conference itself is typically logged. The 2 to 4 hours of preparation — zoning research, question drafting, exhibit preparation, planning precedent review — that made the meeting productive is frequently absorbed into “client meeting: 1 hour.” Log the preparation cycle as a distinct entry with a note on what was prepared and what the meeting produced.

Code research for designs not built. Analyzing whether a proposed design approach is code-compliant, concluding that it is not, and advising the developer to modify the program is genuine advisory work that consumed research time and produced a constraint finding. The absence of a drawing does not make the research invisible — but the absence of a visible output means the research is rarely logged with the specificity needed to explain it to a developer who sees an invoice for code research without a drawing.

Variance strategy research. Research into whether a specific design approach might qualify for a variance, code modification, or alternative means of compliance — reviewing the applicable variance criteria, identifying precedent cases, assessing the probability of approval at the specific planning body — takes 3 to 6 hours and may conclude that the variance is not worth pursuing. Log the research and the finding, not just the cases where a variance application is filed.

Planning department comment response drafting. When a planning department issues comment letters on a permit application, reviewing each comment, identifying the applicable code basis, and drafting a response that addresses the comment while minimizing design impact is a specific advisory work cycle that consumes 1 to 3 hours per substantive comment. Projects with 10 to 20 comments can require 15 to 40 hours of response drafting. Log response drafting at the specific comment set level, not as a generic “permit coordination” entry.

Historic district overlay research. Projects in or adjacent to historic districts require research into applicable design guidelines, Secretary of the Interior Standards compliance, and local historic preservation commission requirements before any schematic design is produced. This research is distinct from design work and is routinely absorbed into early project overhead rather than logged as a discrete advisory activity.

How to log architect retainer hours

Architectural advisory work log entries should capture the site or project, the advisory category, the specific work performed, and the finding or recommendation. The goal is to make the advisory record legible as a concrete development advisory history that explains each retainer invoice in terms of specific decisions and findings.

Effective format: [Site or project] + [Advisory category] + [Specific activity] + [Finding or recommendation]

Poor entry: “Site research — 4 hours”
Good entry: “2847 Oak Street site feasibility: R-3 medium-density residential zoning analysis — confirmed maximum FAR 2.0, height limit 40 ft, front setback 20 ft; calculated maximum development envelope at 18,400 GSF with surface parking or 24,000 GSF with structured/underground parking; flagged 10-ft additional setback requirement from rear alley as binding constraint on unit depth; development program viable for 16-unit townhouse or 22-unit stacked flat with single level below-grade parking: 4 hours”

Poor entry: “Planning meeting — 2 hours”
Good entry: “Riverside Commons pre-application conference prep: reviewed project site zoning and applicable design guidelines; drafted 8 questions for pre-app meeting covering FAR calculation methodology, ground-floor commercial requirement interpretation, affordable unit placement flexibility, and parking reduction availability; prepared preliminary massing description for staff review; attended pre-application conference with planning staff (1.5 hours); key findings: staff confirmed FAR calculation excludes basement; commercial requirement is advisory for this block face; parking reduction to 0.75/unit likely approvable given transit proximity: 4 hours total”

Poor entry: “Code research — 6 hours”
Good entry: “Harbor District mixed-use project: IBC Type IIIA construction compliance analysis for 5-story building with ground-floor retail — analyzed maximum allowable area per floor per IBC Table 506.2 with sprinkler increase and open perimeter increase; confirmed 5-story Type IIIA is compliant for planned program; identified requirement for 2-hour fire-rated occupancy separation between residential and commercial (not initially in project program); advised project team to incorporate fire-rated separation in structural design at schematic design stage: 6 hours”

Poor entry: “Variance research — 3 hours”
Good entry: “Hillcrest project rear setback variance strategy: reviewed applicable variance criteria under Municipal Code Section 28-1450; researched 12 variance applications within 500 ft of subject site over prior 5 years via planning department records (9 approved, 3 denied); analyzed common approval factors in approved cases (hardship documentation, neighborhood compatibility); concluded 10-ft rear setback variance is approvable based on lot shape constraint (triangular lot reduces buildable depth); recommended pursuing variance; drafted variance hardship statement outline for client review: 3 hours”

Pricing architect retainers for development clients

Architect retainer rates for real estate development clients reflect the scope of advisory services, the firm’s relevant project type expertise, and the complexity of the development markets where the client operates:

Emerging firms and junior architects providing pipeline feasibility advisory and general code research to smaller development clients: $100–$160 per hour. Best suited to infill residential and light commercial projects in straightforward regulatory environments.

Mid-career architects with entitlement experience advising on multifamily, mixed-use, or commercial development: $150–$250 per hour. This range covers pre-application consultation, entitlement strategy advisory, and design advisory for developers pursuing projects requiring discretionary approvals.

Senior architects and principals with deep local entitlement expertise advising on complex mixed-use, high-rise, or historically sensitive projects: $225–$400 per hour. Development clients who face contested entitlement processes, historic district reviews, or complex environmental review requirements pay a premium for architects who have navigated the specific regulatory environment multiple times.

Typical monthly retainer hours by engagement mode:

Contract clauses that prevent billing disputes in architect retainers

Site feasibility for sites not acquired. This is the most common source of billing disputes in development retainers. Define explicitly whether the retainer covers architectural advisory for sites the developer evaluates but does not acquire. If the developer evaluates 10 sites per quarter and acquires 2, the 8 uneventful site analyses represent the majority of the advisory work. A contract silent on this point will generate an invoice dispute when the developer receives a monthly invoice covering advisory for sites they chose not to pursue.

Scope of pre-application services. Define whether the retainer covers pre-application meeting preparation, attendance at pre-application conferences, and follow-up analysis of planning department feedback, or only meeting attendance itself. Pre-application preparation is often 2 to 3 times the hours of the meeting; if the client understands only the meeting attendance, the preparation hours will appear as unrecognized billing.

Advisory vs. design services distinction. Define clearly what constitutes advisory retainer services (feasibility analysis, code advisory, pre-application consultation, design review) versus full design services (schematic design, design development, construction documents, permitting, construction administration) that trigger a separate project contract. The transition point — when the project is ready for full design services — should be defined so the client understands when the retainer ends and a project-based contract begins.

Pipeline scope and site coverage. Define whether the retainer covers advisory for all sites in the developer’s acquisition pipeline, only sites above a defined size threshold, only sites in specific geographic markets, or only sites that have been formally put under contract. A developer with a broad acquisition pipeline that expects the retainer to cover advisory on every site under consideration will generate substantially more retainer hours than a developer who expects advisory only on sites in active due diligence.

Hours visibility access. Provide the developer with a shared retainer hours dashboard URL showing current hours consumption and the advisory work log for the month. For a retainer that covers pre-design advisory across multiple sites — where the work is continuous but the visible outputs are sparse — mid-month hours visibility is the most effective tool for making the advisory work legible before the invoice arrives.

The five most common architect retainer billing mistakes

1. Not logging site feasibility work for sites not acquired. If 70 percent of the advisory work in a quarter covered sites the developer did not buy, and those entries don’t appear in the work log, the invoice looks expensive relative to the single acquired site that appears in the record. Log all site feasibility work, including the analysis that produced a pass decision.

2. Logging pre-application meetings without the preparation. “Pre-application conference: 1.5 hours” looks like a 1.5-hour line item. The 3 hours of preparation that made the meeting productive are invisible if not logged separately. Log the preparation as a distinct entry before the meeting entry, with a brief note on what was prepared.

3. Using generic category labels for code research. “Code research: 5 hours” tells the developer nothing. “IBC Type IIIA construction analysis for Harbor District project: confirmed floor area allowances, identified occupancy separation requirement, advised schematic design team: 5 hours” tells the developer exactly what the research covered and what it produced. Always log code research at the specific code section, project, and finding level.

4. Not tracking planning department comment cycles as discrete work items. Responding to a planning department comment letter with 15 substantive comments is a specific work cycle that may consume 20 to 30 hours of review, research, and response drafting. If those hours are absorbed into a generic “permit coordination” entry, the developer cannot understand what the hours produced.

5. Failing to brief development clients on the pipeline advisory model at onboarding. A developer accustomed to project-based architectural services will default to expecting retainer billing to look like project billing: hours that correspond to visible deliverables. An explicit conversation at retainer inception about the scope of pre-design advisory, why site feasibility hours for non-acquired sites are legitimate retainer work, and what the monthly log will look like prevents the first invoice from generating a dispute about the billing model itself.

Making pre-design advisory work visible

The challenge in an architecture retainer with a development client is that the most intensive advisory months are often the months with the fewest visible outputs. A month spent evaluating six potential acquisition sites, attending two pre-application conferences, and drafting a variance strategy memo for a project that is still in due diligence produced significant advisory value — but it produced no drawing, no permit application, and no construction.

A shared retainer hours dashboard with a running advisory work log makes that pre-design work visible between invoices. When the developer opens the dashboard mid-month and sees six site feasibility entries, two pre-application conference preparation entries, and a variance strategy entry, each with the specific site, the specific code or regulatory question addressed, and the specific finding, the month’s advisory work is legible as a concrete set of development decisions supported.

Over twelve months of a development advisory retainer, the accumulated log becomes the primary record of what the architect’s advisory produced across the acquisition pipeline: which sites were evaluated and why specific ones were passed, what entitlement strategies were developed for the projects that moved forward, what code constraints were identified and how the project program was adjusted in response. A developer reviewing their advisory budget who can read that record understands that the retainer covered not just the buildings that were built but the far larger set of development decisions that shaped which buildings were worth building.

Frequently asked questions

What does an architect on retainer typically do for a real estate developer?

An architect on retainer for a developer typically provides site feasibility analysis across the acquisition pipeline, code compliance research for potential projects, pre-application consultation with planning departments, entitlement strategy advisory, and design advisory on projects moving toward full design services. The retainer covers advisory and pre-design services; full design services (schematic design through construction administration) are typically engaged separately as a project-specific contract when a project is ready to proceed.

How many hours per month does an architect on retainer typically work?

Feasibility and pipeline advisory mode runs 10–20 hours per month across a developer’s active acquisition pipeline. Active entitlement (a specific project in the pre-application and permit application process) runs 30–60 hours per month. Construction document phase advisory runs 40–80 hours per month. A development firm with multiple projects at different phases simultaneously can absorb 60 to 100 architect retainer hours per month across the portfolio.

What architect retainer work is most commonly underlogged?

Site feasibility analysis for sites not acquired, pre-application meeting preparation hours, code research that produces a constraint finding rather than a compliance path, variance strategy research for variances not pursued, and planning department comment response drafting cycles. These categories represent the continuous pre-design advisory work that justifies the retainer and is systematically underlogged because it produces no drawing and no permit application as a visible output.

What should an architect retainer contract with a developer include?

Site feasibility scope for sites not acquired, pre-application services definition, the advisory vs. full design services distinction, pipeline site coverage parameters, and hours visibility access. The site feasibility and advisory vs. design distinction clauses are the most critical: they define whether the developer understands from the outset that retainer advisory covers pipeline analysis and pre-design work, not just the projects that result in permit applications.

How should architect retainer hours be logged to justify the invoice?

Log entries should name the specific site address or project identifier, the advisory category (site feasibility, code compliance, pre-application, entitlement strategy, design review), the specific activity performed, and the specific finding or recommendation. A work log structured at the site and regulatory question level makes the retainer record legible as a concrete development advisory history rather than a collection of unattributed hours.