Citizen vs. Expert: Designing Qualification Gates That Route Work to the Right Builders

A qualification gate should do more than approve or reject automation candidates — it should route them. Candidates that score simple on complexity and low on risk (single system, no sensitive data, reversible actions, stable rules) route to the Citizen path: built by trained business-side makers on sanctioned low-code tooling under guardrails. Candidates that score complex or consequential (multi-system orchestration, regulated data, irreversible actions, judgment-heavy logic) route to the Expert path: the CoE's professional developers and architects. Programs can use this split to target delivery capacity and reduce avoidable risk, but throughput and incident outcomes should be measured rather than assumed.

The Twin Failures of Ungated Programs

Route everything to the CoE and a backlog can form: a small Power Automate flow may wait behind a much larger agent build, business teams may lose faith, and demand may go underground. Route nothing — let every department build freely — and sprawl can follow: unmonitored flows may touch production data, credentials may be handled insecurely, and ownership may be unclear after an incident. Programs can oscillate between these failures; a gate offers a criteria-based split to test and refine.

What the Gate Actually Scores

• System footprint: one sanctioned SaaS tool with connectors → Citizen; multi-system orchestration, legacy interfaces, or custom APIs → Expert.
• Data sensitivity: public or departmental data → Citizen; PII, financial records, regulated or patient data → Expert, regardless of technical simplicity.
• Reversibility: read-and-report or draft-for-review actions → Citizen; payments, external communications, record deletion → Expert (or agent patterns with strict human-in-the-loop controls).
• Logic complexity: stable, enumerable rules → Citizen; judgment calls, ML/agent components, or many exception branches → Expert.
• Volume and blast radius: a limited-scope team convenience → Citizen; an enterprise process where downtime has a severe impact → Expert.

Designing the Citizen Path So It's Safe

The Citizen route only works if it is a paved road, not an open field: sanctioned platforms with pre-approved connectors, mandatory training before build rights, templates for the common patterns, an environment policy that keeps citizen assets out of production data they don't need, and a lightweight registration so every flow has a named owner and shows up in inventory. The CoE's role on this path shifts from builder to enabler — reviewing at registration, monitoring the inventory, and promoting citizen builds to the Expert path when they outgrow their guardrails. The platform economics of this model are covered in Low-Code, BPM, and the Citizen Developer.

Designing the Expert Path So It's Fast

Use IntakeOS to gather systems, rules, exceptions, and process context before deciding who should build. Review the qualification and maps with a technical lead, especially for boundary cases. This reduces manual reconstruction of the request while preserving your actual citizen-development controls and the specialist review required for sensitive or complex work.

Gating may help the Expert side because arriving work is pre-qualified — problem statement, root cause verified, pattern recommended, baselines captured, complexity classified — potentially reducing time spent on scope discovery. Expert capacity can then concentrate on work that genuinely needs it: multi-system architecture, agentic components with governance requirements, and automations with a large failure impact. Whether the queue shortens or items move faster should be verified with program data.

Handling the Boundary Cases

Some candidates score Citizen on complexity but Expert on one risk dimension — a simple flow that touches payroll data, say. The rule is: any single Expert-level risk flag routes Expert, but with an expedited lane for technically simple builds so the requester doesn't experience the routing as punishment. And routes are re-scoreable: when a citizen-built flow's volume grows materially or its scope creeps into new systems, re-qualification moves it — with its documentation — onto the Expert inventory. The gate is a living control, not a one-time stamp.

Frequently Asked Questions

The Bottom Line

The question is never whether business users will build automations — they already are, sanctioned or not. The question is whether a scored gate routes each piece of work to builders equipped for its risk. Score complexity and risk at intake, route deterministically, pave the Citizen road, and reserve Expert capacity for work that earns it. That's how programs scale delivery and governance at the same time, instead of trading one for the other.