Architecture Project Timeline FAQ: How to Answer the Questions Clients Ask Before Design Really Starts

Clients almost always want to know the same thing early: how long is this going to take?

A useful architecture project timeline FAQ helps answer that question without pretending every project follows the same schedule. It gives people enough structure to trust the process while leaving room for the realities of approvals, decisions, scope changes, and construction conditions.

For the wider system, start at the homepage. Then read Architecture Project Timeline Explainer and Architecture FAQ Checklist for connected guidance.

Why timeline FAQs matter

AIA guidance on basic services and RIBA’s Plan of Work both frame architecture as a staged process with briefing, design development, documentation, procurement, and construction-related phases. That matters because many clients imagine “design time” as one simple block.

It is not.

A timeline FAQ helps firms explain that architecture moves through decisions and dependencies, not just calendar dates.

Questions worth answering on the page

How long does an architecture project usually take?

The honest answer is: it depends on the project type, complexity, review requirements, consultant coordination, and client decision speed.

That said, your FAQ should explain the major timing buckets instead of hiding behind “it depends.”

What happens before design starts?

Clients often underestimate this phase.

Explain that the early period may include:

• project briefing
• site or existing-condition review
• collecting available documents
• clarifying goals, priorities, and constraints
• deciding what the first formal phase should be

Why can timelines change after the first conversation?

Because the first conversation is not the same as a full scope definition.

Once zoning, consultant needs, site realities, or phased goals become clearer, the timeline may become more accurate and sometimes longer.

That is normal. It is better than pretending certainty too early.

Does permitting count as part of the architecture timeline?

Usually yes, at least from the client’s point of view.

Even when review durations are outside the architect’s control, they still affect the total project calendar. A strong FAQ explains that some phases are led by the firm and others are influenced by review agencies, consultants, contractors, or owner-side decisions.

What slows projects down most often?

Useful answers include:

• delayed decisions
• scope changes midstream
• incomplete existing information
• consultant coordination needs
• permit review timing
• contractor pricing or bid cycles

Can the project move faster?

Sometimes, but only if the conditions support it.

A fast project usually still needs:

• clear decision-makers
• quick feedback cycles
• realistic scope
• available documentation
• aligned expectations about tradeoffs

A simple way to present the answer

A strong timeline FAQ page usually works best with three layers:

1. a short summary answer
2. a plain-language explanation of why timing varies
3. a stage-based breakdown of what affects each phase

That gives people both reassurance and realism.

What not to do on a timeline FAQ page

Avoid:

• promising exact durations too early
• turning every answer into legalese
• using internal phase names without translation
• implying the architect controls every external dependency
• making the page sound defensive

Clients do not need a disclaimer page. They need a trustworthy explanation page.

Where this page fits best

An architecture project timeline FAQ works well:

• on a services page
• in a consultation follow-up email
• as a linked resource on the contact page
• on a kickoff prep page for new clients

If you are building the surrounding system, Architecture Fee Conversation Guide and Architecture Project Brief Template are useful companion pages.

Clarify your architecture timeline messaging →

Bottom line

A strong architecture project timeline FAQ gives clients a better answer than either false certainty or vague dodging.

Show the stages. Explain the dependencies. Give people a realistic picture of how timing actually works.

Sources

• AIA — Defining the architect’s basic services
• AIA — How to work with an architect
• RIBA — Plan of Work