The earliest stages of a project get less structure than almost any other part, and they're the ones everything downstream gets measured against.
That's not really a surprise. Stage 0 and Stage 1 often happen fast, over a phone call, a site visit, an email thread, before there's a fee agreed or a formal instruction in place. Both are informal by nature. The problem is that informal capture has a habit of staying informal for the rest of the project, and everything from budget expectations to who actually signs off a decision traces back to what did or didn't get written down here.
Separate the enquiry from the brief
An initial enquiry and a proper brief actually sit in two different RIBA stages, even though they often get treated as one conversation. The enquiry belongs to Stage 0, Strategic Definition: is this the right project, the right client, the right scope for the practice, before a design team's even involved. The brief belongs to Stage 1, Preparation and Briefing: what's actually being built, for whom, under what constraints, once you've confirmed the project's worth doing.
Trying to do both in one conversation is usually where things go wrong. A practice ends up on a site visit before anyone's confirmed there's a realistic budget, Stage 0 work skipped straight into Stage 1 territory, or a full brief gets attempted before anyone's agreed the project's even a good fit. Treating them as genuinely separate stages, not just two vague phases of "getting started," makes both easier.
Ask the boring questions first
The questions that matter most at enquiry stage aren't the interesting ones. They're things like:
What's the realistic budget, not the hoped-for one?
What's the timeline, and is it driven by anything fixed, like a lease ending or a family event?
Who's actually making the decisions, and is everyone with a say in the room, or on the email thread?
What's non-negotiable versus what's a nice-to-have, if it comes down to a trade-off later?
None of these are exciting. All of them save hours later, because they're the questions that, left unasked, tend to surface as problems at Stage 3 or 4 instead, when they're far more expensive to solve.
Write down what's negotiable, not just what's wanted
A brief that only records what a client wants today is missing half the point. The more useful version also records how firm that want actually is.
A client who says they want a specific feature is giving you one piece of information. A client who says they want a balcony but would happily trade it for a bigger budget elsewhere is giving you something much more useful, because now you know where the flexibility actually is. Capturing that distinction at Stage 1 is what stops "scope creep" later, most of it isn't really new scope, it's scope that was always there and never written down clearly enough to plan around.
Get sign-off that actually holds up
A brief that only exists in someone's memory, or scattered across a notepad and a few email threads, doesn't hold up months later when a client says "but we agreed that." Not because anyone's being difficult, but because there's no shared record either side can point back to.
The fix isn't complicated: capture the brief somewhere structured, timestamped, and visible to both the practice and the client, and get an explicit sign-off on it before moving to the next stage. It sounds obvious. It's also the single most skipped step in Stage 1, because it feels like paperwork getting in the way of the actual work, right up until it's the thing that would have prevented a tough conversation six months later.
Where this fits with Pilotis Forms
This is exactly the gap Pilotis Forms' Initial Enquiry stage (Stage 0) and Developed Brief stage (Stage 1) are built around: structured capture from the first conversation, with everything timestamped and visible to both sides. If you're doing this on paper or across email today, the process above works regardless of the tool, but it's considerably less effort with one built for it.
See how it works on our Pilotis Forms Features Page.
