1,000+ Engineers at Rivian Use Flow as the Requirements System of Record

We’re pleased to share that Rivian selected Flow as its requirements system of record across R1 and R2 vehicles, bringing the full 1,000+ person engineering organization into one live platform for cross-functional systems engineering.

Rivian builds some of the most advanced electric vehicles in the world. Each program brings together mechanical systems, embedded software, autonomy, and manufacturing at real production scale. As that complexity increases, so does the pace of iteration. Designs change continuously, interfaces evolve rapidly, and verification must keep up.

Traditional requirements management tools were intended to be Rivian’s system of record but they failed to meet the demands of an iterative engineering organization.

To operate at that speed, Rivian needed a system that could match how its teams actually work today, and match how they will work as AI becomes a bigger part of engineering.

Flow became that foundation.

“Flow really opened up our collaboration around product requirements. It got teams involved beyond just the systems engineers and brought everyone into the conversation without the headache of prepping formal presentations.”

Scott MacKenzie
Director, Product Development Process and Tools, Rivian

One System Built for Iteration & AI Readiness

Rivian’s engineering teams iterate rapidly across vehicle programs. That requires more than documentation: a live system of record that reflects the current state of the product and can adapt as designs evolve.

Flow supports this by keeping requirements, verification, and cross-team collaboration connected in one place. Engineers can see changes as they happen, understand impact across disciplines, and move forward without waiting on slow handoffs or manual reconciliation.

Just as importantly, this structure creates the foundation needed for AI to be useful in engineering. AI systems depend on connected, up-to-date data. By applying engineering context to a live system, Rivian is ensuring that emerging AI capabilities can reason over real design intent, not stale documents.

“With traditional solutions it always felt like we were fighting the tool. With Flow, making a change, seeing what it affects across teams, and keeping verification in sync is quick. It’s part of the workflow, and you see the impact right away.”

Scott MacKenzie

The Search: Built for Pace and Scale

Rivian ran a structured evaluation to find a system that could match both the speed of iteration and the scale of its engineering organization. The tools were evaluated against clear, non-negotiable requirements.

The platform needed to:

• Scale to 1,000,000+ requirements across hardware and software.

• Support 1,000+ concurrent users without performance degradation.

• Fit seamlessly into iterative, cross-disciplinary workflows.

• Deliver enterprise-grade reliability with a consumer-grade user experience.

• Enable a transition from existing tools without disrupting live vehicle programs.

Flow stood out as the best  platform that met these requirements while aligning with how Rivian teams work day to day.

“Flow was the system that could best handle our scale without forcing us into slow, sequential processes. It fits how our teams build complex vehicles, with hardware, software, and testing tightly linked.”

Scott MacKenzie

The Implementation: Strategic Partnership

Rolling out a new system while multiple vehicle programs were already in motion required a careful approach. Rather than a disruptive replacement, Rivian and Flow worked side by side through a staged rollout.

The engagement began with a focused pilot to validate workflows and establish scalable patterns. From there, FDEs embedded directly with Rivian teams, supporting training, adapting workflows, and migrating data incrementally as teams were ready.

Programs transitioned one by one, allowing adoption to build organically while minimizing risk. Over time, Flow expanded across vehicle lines and functions, becoming the shared system of record for requirements and collaborative system engineering.

“From the planning & architecture of the system, through migration and onboarding of our teams Flow has really impressed us with the thoroughness, quality and urgency that they've acted with. We're excited about the roadmap over the coming months.”

Scott MacKenzie

Looking Ahead

By bringing the entire engineering organization into one shared system, Rivian has created consistency across programs without sacrificing team autonomy. Engineers work in the same environment across disciplines and vehicle lines, making it easier to manage change, maintain traceability, and track progress as programs scale.

With Flow as a common engineering backbone, Rivian has aligned its teams around a single, trusted system of record that supports high-speed iteration today and AI-enabled engineering tomorrow.

We are proud to partner with Rivian as they design and deliver the R1 and R2 vehicles.