Skip to content
Property development Step plan

Property development step plan: the information each phase needs

A project runs from subdivision through construction to sales and aftercare. Each phase needs its own permits, plans, contracts and certificates. This step plan shows per phase which information belongs to it, and how you follow it up in Lean per subdivision, block and home.

Where property development often goes wrong

Developers coordinate large projects with many phases and many parties. The same questions keep coming back.

  1. A complex scheduleKeeping track of deadlines, parties and dependencies across several phases quickly gets confusing. A step waiting for a permit or a plan pushes everything else back.
  2. Many parties, one projectArchitect, engineering firm, contractors, subcontractors, notary and buyers each supply part of the information. Who has to supply what is often written down nowhere.
  3. Communication and coordinationInformation sits in e-mails and folders. Whoever has a question first has to find out who has the answer.
  4. Plans that changeNew rules, a buyer who changes a choice or a revised plan: whoever works with the previous version makes mistakes.

Subdivision, block and home in one file

In the step plan, every piece of information belongs to a level. Planning permission belongs to the subdivision, an execution plan to the block or building project, an energy certificate or notarial deed to the home of one buyer.

In Lean, those three levels form one structure. A document is recorded once and is visible where it is needed. Per process you see how many documents have come in and which are still missing, and through the file's planning also when they are needed.

**Real screen from the demo environment**, with fictitious data. A subdivision with its blocks and plots as one file. Click to enlarge.
Real screen from the demo environment, with fictitious data. A subdivision with its blocks and plots as one file. Click to enlarge.

All phases in one schedule

The phases of the step plan are in the file's planning, with the steps they depend on. So you see which step is waiting for which information.

Across all your projects, management sees every subdivision in one schedule, with the points of attention per block, such as a buyer's choice that is late.

**Real screen from the demo environment**, with fictitious data. The schedule of a subdivision, with the steps and their dependencies. Click to enlarge.
Real screen from the demo environment, with fictitious data. The schedule of a subdivision, with the steps and their dependencies. Click to enlarge.

Frequently asked questions about the step plan

How many phases does a property development project have?

In this example: preparation, administration and works of the subdivision, preparation and works of the construction phase, administration and finishing per home, sales and after-sales service.

Do I have to use this step plan as it is?

No. It is an example. You model your own processes in IRP, with per step the information that belongs to it. This is set up with you at the start.

Does the buyer see any of this step plan?

The buyer sees his own documents and reports in his home portal, with their status. The rest of the file stays internal.

More about property development in Lean

See how buyers, project management and management work with the same information.

Bring one bottleneck. See how Lean handles it.

We start from a situation in your work. You see what works in the software today, and we discuss how it fits your process.

Book an online demo