01 · The Problem Nobody Talks About
The NR/L2/CIV/003 Form G represents the single most consequential document a civils engineer produces on a Network Rail project. It is a design certificate that requires professional judgment across twelve sections addressing standards, risks, and site constraints.
Yet young engineers encounter this critical document without formal instruction. The typical approach is to copy a previous example and hope for the best. The knowledge gaps this creates lead to systemic omissions during the design assurance process — omissions that cost time, money, and programme confidence.
02 · The Solution
Scribtive’s Full Walkthrough mode transforms document creation into interactive learning. Rather than presenting blank templates, it guides engineers through structured conversations, surfacing considerations they wouldn’t independently recognise while building competence through real project work.
03 · Inside the Full Walkthrough
The platform provides:
- Section briefings explaining requirements and applicable standards
- Guided conversations addressing site-specific engineering questions
- Surfaced risks engineers typically overlook
- Evidence traceability linking facts to source documents
- Formal synthesis converting discussions into professional language
04 · What You Didn’t Know You Didn’t Know
The system identifies overlooked considerations including mining risk assessments, unexploded ordnance compliance, and utility diversion documentation — critical factors absent from university curricula but essential for a compliant Form G.
05 · The False Trade-Off
Speed and quality aren’t mutually exclusive. The tool eliminates time spent searching standards and formatting while preserving active engineering judgment. It compresses two-to-three years of supervised learning into contextual practice — the engineer still makes every decision, but with the right information surfaced at the right time.
06 · The Builder’s Perspective
Bill Guo developed Scribtive from extensive experience across multiple roles — graduate engineer, CRE reviewer, CEM manager, DPE approver — witnessing the same recurring failure patterns throughout his career. Every role revealed a different angle on the same problem: knowledge trapped in people’s heads, not in systems.