9 September 2026

SCQA in one scroll

Situation, Complication, Question, Answer mapped to a single page structure.

SCQA is the consulting standard for structuring an argument: Situation (the context everyone agrees on), Complication (what changed or went wrong), Question (what decision that raises), Answer (your recommendation). It started as an outline for slide decks. It works even better as a vertical scroll.

Each piece becomes a page section. The reader moves through the story linearly, or jumps straight to the Answer if the Situation is already agreed.

What each section does

**Situation**: the facts everyone accepts. 'Your Benelux revenue is up 34% year-on-year. You're the category leader in Amsterdam and Rotterdam.' This is the part the client nods through. Keep it to two or three sentences. The job here is shared context, not discovery.

**Complication**: what broke or what's at risk. 'The France pilot burned €220k in six months and CAC is still 2.1× your Benelux average. Three local competitors own the Paris SEO keywords and you're bidding against all of them.' This is the tension. If there's no complication, there's no decision to make.

**Question**: the choice the complication forces. 'Do we keep funding the France expansion, or do we cut it and reinvest the budget?' Frame this as a genuine fork. The client should be able to imagine arguing either side.

**Answer**: your recommendation with the reasoning compressed. 'Cut France. Move the €220k to Benelux paid acquisition and hire two Dutch account execs. You'll hit profitability in Benelux eight weeks faster and the expansion budget stays available for a market that's actually ready.'

How to structure it as a page

Put all four section names in a sticky nav at the top. Situation / Complication / Question / Answer, each one an anchor link. The reader who already knows the Situation clicks Answer and gets your recommendation in two seconds.

Use actual headings on the page for each section, not just the nav chips. The heading anchors the scroll position and makes it obvious when one section ends and the next begins.

The Situation and Complication can be short. Two paragraphs each is often enough. The Answer section is where the detail lives, because that's where you're making the case.

Why it works as a scroll

The linear structure maps to how people already read on a screen. Slide decks force the reader to hunt through tabs or a thumbnail sidebar. A page scroll is just 'keep going down.'

Jump navigation respects the client's context. If they were in the planning meeting where the Situation was established, they skip it. If they're a new stakeholder joining late, they start at the top and the story makes sense without a presenter.

Updating one section doesn't break the others. Slide decks are brittle. Change one number on slide 8 and suddenly slide 12's chart is out of sync. A page structure keeps each section independent.

Turn your next proposal into an SCQA scroll.

Start with docfarm