After last week’s post on project charters in real estate development, the most common feedback I received was honest and unsurprising:
“We don’t really use them. Can you show an example?”
Fair enough.
In real estate development, scheduling and budgeting skills are rarely forgotten. What is often taken for granted is the upfront alignment work. The part where you clearly define what the project actually is, who it’s for, and how decisions should be made.
A project charter doesn’t need to be complicated. Mine are usually 2–3 pages. But they quietly do a lot of heavy lifting over the life of a project.
Here is a simple breakdown of what I ask my teams to document.
1. Project Overview – Why This Project Exists?
Start with a short narrative. One or two paragraphs is enough.
This answers:
- Why are we doing it?
- What problem are we solving?
Example:
This project involves the redevelopment of a former industrial site into a mid-rise rental apartment building. The objective is to deliver long-term rental housing in a transit-accessible location while maintaining entitlement certainty and cost discipline.
This section gives context, especially for consultants or team members who join later.
2. The Program – What Are We Actually Building?
Document the intent of the project:
- Building type(s)
- Height / density assumptions
- Use mix
- Parking strategy
- Any non-negotiables
Example:
- 6-storey wood-frame rental building
- Approximately 110 units
- Residential-only (no commercial)
- Target FAR aligned with existing zoning
Ensure all elements of the project (budget, schedule, communication plan) are aligned with this description.
3. Unit Summary – Be Directional, Not Perfect
Even if the numbers evolve, the initial direction should be clear.
Include:
- Unit count by type
- Bedroom mix
- Average unit sizes
- Tenure or affordability assumptions
Example:
- 40% one-bedroom
- 45% two-bedroom
- 15% three-bedroom
- Family-oriented mix prioritized
This anchors design, cost planning, and market conversations early.
4. Target User – Who Is This Actually For?
This is where many projects lose focus. Seems basic, but many miss this step.
Define:
- Who will you think will live or work here
- Income range or life stage
- What they value most
Examples:
- Families seeking stable rental housing near schools
- Industrial employees prioritizing proximity to work
- Downsizing seniors looking for simplicity and accessibility
Once the target user is clear, design trade-offs become much easier.
5. Market Positioning – One Short Paragraph
This sits between “target user” and “financials.”
Clarify:
- Rental vs. strata
- Premium vs. value-oriented
- Competitive positioning
Example:
Positioned as mid-market rental housing with durable finishes, neither luxury nor entry-level.
This helps prevent over-design or under-spec’ing later.
6. Project Objectives – Consider the Trade Offs
Objectives clarify priorities, not outcomes.
Examples:
- Minimize rezoning risk
- Accelerate approvals
- Maximize density (accepting entitlement risk)
- Protect schedule over marginal cost savings
This answers an important question:
When trade-offs arise, which way do we lean?
7. Decision Principles – How Choices Should Be Made?
This is a small addition can help clarify thinking.
Examples:
- Entitlement certainty is prioritized over marginal density gains.
- Livability will not be compromised to protect yield.
- Schedule certainty outweighs minor cost savings.
These principles guide day-to-day decisions without constant escalation.
8. Measures of Success – How Will We Judge This?
Be explicit and measurable.
Common metrics include:
- Target yield / IRR / profit margin
- Maximum total project budget
- Schedule targets (e.g. occupancy date)
- Lease-up or sales performance
If success isn’t defined early, it will be debated later.
9. Scope Boundaries – What This Project Is Not?
How many times have I seen real estate development projects miss results due to scope creep? Too many.
To protect yourself from scope creep, state what your project isn’t.
Document:
- Uses that are excluded
- Amenities you are not pursuing
- Density or height limits you are not testing
Example:
This project will not include retail, office, or shared amenity programming beyond code-minimum requirements.
This protects the team when “quick ideas” start to surface.
10. Approval Strategy & Risk Posture
This aligns planning, design, and ownership.
Clarify:
- Appetite for political risk
- Negotiation vs. compliance approach
Examples:
- Design to zoning compliance to reduce risk and increase speed.
- Pursue additional density with acceptance of entitlement risk.
11. Project Team & Governance
This doesn’t need to be formal, just clear.
Document:
- Who leads the project
- Who makes final decisions
- Who needs to be consulted on changes
Clarity here saves time and frustration later.
12. Key Milestones
Not a full schedule, just anchors:
- Rezoning submission
- Public hearing
- Development permit issuance
- Construction start
- Occupancy
This sets expectations without false precision.
13. Key Constraints, Assumptions & Risks
Optional, but extremely useful.
Include:
- Fixed constraints (budget, land cost, servicing)
- Major assumptions
- Known risks
This builds shared awareness instead of surprise.
Final Thought
Most late-stage redesigns, scope changes, and consultant frustration don’t come from bad intent. I don’t think I’ve worked on a project where any one on the team was trying to derail the project. But without clarity, the project will be derailed.
Do yourself a favour and go through the exercise of writing a project charter for your project.
Could Your Project Benefit From Expert Guidance?
If you’d like confidence before moving forward, SiteMentor Development Consultants provide industry-best development feasibility reports that identify what your property can realistically support, highlights potential constraints, and helps you determine the development strategy that makes the most sense for your goals.


