The Pre-Design Pipeline: Feasibility → Space Program → Concept, All in Your Browser

There's a phase of every project that has no glamour, no renders, and more influence over the outcome than everything that follows: the stretch between "we have a project" and the first real sketch. Call it pre-design. Done properly, it's a pipeline — each step's output feeding the next, each cheap to change — and by the time geometry begins, the big questions are already answered. Done casually, it's a vibe, and its gaps surface later as redesigns, budget shocks, and the client sentence every architect dreads: "but I thought we agreed..."

The excuse for doing it casually used to be tooling — pre-design work fell between software, living in emails, whiteboards, and whichever spreadsheet was open. That excuse is gone: the full pipeline now runs free in a browser, with nothing installed and nothing uploaded. Here's the sequence, what each stage hands to the next, and where the discipline actually pays.

Stage 1: Interrogate the brief (before believing it)

Input: the client's document, emails, and the meeting where they said the important things out loud. Output: a requirements baseline, a question list, and a map of assumptions.

The brief you received is an artifact — stated wants wrapped around unstated assumptions and at least one contradiction. Stage 1 takes it apart: explode every claim into a node in AnchorMind, preserve the client's exact words, then tag every node as fact, assumption, or question and draw the dependency links between requirements that constrain each other. The high-stakes assumptions and open questions go back to the client in writing before anything else happens.

Why first: every downstream stage consumes numbers from the brief — occupancies, unit counts, budget, the site itself. Interrogation is how you find out which numbers are real. (Full method: mind mapping a client brief before your first sketch.)

Stage 2: Establish what the land allows

Input: the site (or shortlist of candidate sites) and the local zoning parameters. Output: the buildable envelope — allowable footprint, maximum floor area, height — as a PDF record.

Before sizing the building, size the permission. In the Site Feasibility Calculator, draw the lot boundary, enter the setbacks, site occupancy percentage, floor-area ratio, and height limit for the zone, and read the envelope: which rule governs, how much floor area is genuinely reachable, and — crucially — how sensitive the answer is when any parameter moves. Fifteen minutes per site; export the report.

Why second: the envelope is the hard ceiling every later decision lives under, and its most common failure mode is being computed late — after a program exists that doesn't fit, or worse, after a concept the client has fallen in love with. When the project involves site selection, this stage runs as a filter across the shortlist, and the program in Stage 3 gets built for a site that can actually hold it. (Walkthrough: from vacant lot to feasibility report in 15 minutes.)

Stage 3: Build the space program

Input: the interrogated requirements (Stage 1) and the envelope (Stage 2). Output: a space program — every space, its area, its relationships — with a gross total tested against envelope and budget.

Now, and only now, the building gets sized. In SpaceFlow, the brief's confirmed requirements become named spaces with target areas anchored to standards; the map's cross-links become explicit adjacency relationships; and the live bubble diagram lets the organisational logic — the clusters, the service spine, the space with too many competing pulls — resolve itself while changes still cost nothing.

Then the two reconciliations that make Stage 3 the pipeline's keystone: program vs envelope (net areas grossed up by a realistic factor — does it fit inside Stage 2's ceiling?) and program vs budget (gross area × benchmark cost per square metre — does it fit inside the money?). If either fails, the negotiation happens here, on bubbles and totals, with the client — not in month four, on a scheme. (Worked example: building a school space program.)

Input: everything above. Output: the first sketch that deserves the name.

The pipeline doesn't produce the concept — that's design, and it's yours. What it produces is a concept that starts constrained: the sketch inherits an organisation (the bubble diagram's clusters), a size (the reconciled program), a legal shape (the envelope), and a set of client agreements already in writing. The difference shows at the first presentation: instead of the scheme surfacing the misunderstandings, the scheme answers requirements the client recognises as their own — because they confirmed each one, in sequence, as the pipeline ran.

Pro tip: The pipeline's real product is the paper trail. Question list answered in writing (Stage 1), stamped-dated feasibility report (Stage 2), client-signed program with its reconciliations (Stage 3). When scope drifts mid-project — and it will — these three documents are the difference between "as agreed on the attached program dated March 3rd" and an argument about memories. Run the pipeline for the design discipline; keep the exports for the contractual one.

The loop nobody draws

One honesty note: the pipeline diagram is a line, but real projects run it as a loop. The feasibility check kills a site, so the shortlist reopens. The program-vs-budget reconciliation fails, so the brief's numbers reopen. This isn't the pipeline failing — it's the pipeline working, forcing the loops to happen now, in browser tools where an iteration costs an afternoon, instead of later, in construction documents where an iteration costs a fee dispute. The stages are cheap precisely so you can afford to run them more than once.

All three tools are free, account-free, and local-first — the brief, the site, and the program never leave your machine:

Start the pipeline → — AnchorMind, Site Feasibility Calculator, and SpaceFlow, in your browser.

Feasibility figures, grossing factors, and cost benchmarks used in pre-design are screening estimates. Verify regulations with the local planning authority and have programs and budgets confirmed by licensed professionals before commitments are made.