What should you check before choosing Flow?
Review Flow Engineering against four records your hardware milestone needs: the exact requirement revision, the as-tested configuration, result provenance and the authorised acceptance decision. Flow Engineering documents requirements linked to tests and interfaces, with branches, reviewers and baselines. A useful evaluation checks whether the proposed setup preserves those records when a supplier or configuration changes.
Arc publishes this source-based review and has a commercial interest in teams choosing Arc. We reviewed Flow’s public material on 2 November 2026. We have not run Flow or Arc for this article. The checklist below is designed for an engineering manager or systems lead preparing a design review, supplier handover or verification decision.
The worked card uses a space payload because it makes configuration and interface boundaries clear. The same four checks apply to other hardware programmes when a supplier change, test article or software build changes the evidence needed for acceptance.
Start with one milestone and its owner
Write the decision before choosing screens to inspect. “Accept the revised payload-to-bus interface for the next design baseline” is more useful than “review traceability”. The first statement identifies the changed records, reviewer roles and accepted state the software must preserve.
The systems lead identifies the authoritative baseline and proposal. The discipline owner explains the technical change. The verification owner identifies the procedures, results and conditions being used as evidence. The milestone owner decides whether the resulting package supports progression with the recorded open work.
Agree which decision is in scope. A design review can accept further development while a verification activity remains open. A test result can meet a procedure’s acceptance criteria without authorising the revised design baseline. The software should keep these states recoverable rather than compressing them into one green status.
What the current Flow sources establish
Flow’s Requirements Management page describes a configurable model connecting requirements with systems, tests, interfaces and standards. It includes decomposition, source links, revision history and supplier work on branches. Its Branching page describes isolated proposals, required reviewers, differences, immutable baselines and variants or configurations.
Flow also distinguishes verification status from validation stage and documents PDF, DOCX and CSV branch exports. Its integration catalogue describes Excel cell checks, Jira ticket links and connections to model or analysis tools. These are relevant capabilities to include in an evaluation.
Product pages do not demonstrate the behaviour of your edition, roles, test-record fields or exported package. Inspect reviewer requirements and any administrative or API exception route in the proposed environment. Treat unanswered questions as unresolved scope, rather than evidence that a capability is absent.
Use this milestone checklist
Original resource: milestone fit card, FT-P02. The fictional example is a payload-to-bus design review. An earlier test report describes baseline B1, while a supplier proposal changes the payload demand. The card asks what the reviewers must recover before relying on either record.
| Check | Fictional review input | Required evidence | Owner |
|---|---|---|---|
| Requirement revision | B1 and a separate supplier proposal refer to PAY-PWR-014. | The accepted revision, proposed value, source reference and visible difference. | Systems and payload owners. |
| As-tested configuration | The earlier report covers the B1 test article. | Hardware/software state, procedure revision, operating condition and configuration identifier. | Verification owner. |
| Result provenance | A report is attached to TEST-PWR-02. | The original result, execution date, responsible person and requirement/criterion assessed. | Test engineer. |
| Accountable acceptance | The proposal awaits a design disposition. | Named decision maker, reviewed material, rationale and open actions. | Milestone owner. |
| Unresolved dependency | A thermal analysis exists but its relationship to the proposal is incomplete. | A visible gap, assigned investigation and a reasoned effect on progression. | Thermal owner. |
| Demonstrated product outcome | No product evaluation has been executed. | A dated record from the selected setup and an independent reviewer’s reconstruction. | Evaluation owner. |
Complete the demonstrated field from an actual artefact, with version and configuration. Source documentation belongs in the known-scope field. Use accept for the tested scope, request missing proof or retain the current system as the resulting fit decision. The card does not assign stars or vendor scores.
Apply the same checks to Arc
Arc’s connected programme model stores requirements, systems, interfaces and verification records with explicit relationships. Ask to open the same requirement from its parent intent, interface and verification activity, then identify the authoritative revision. The link meaning and source context should be inspectable.
Arc’s controlled change workflow keeps branches, differences, discussion and review before baseline merge. Its review records retain identity, decision, timestamp and reviewed context. Use those records to reconstruct a returned proposal and the outstanding work.
Arc also connects verification activities, executions, results and evidence to requirements and configurations. The verification owner still decides whether a result supports the proposed design. These mechanisms make Arc a candidate for this review workflow, while the actual evaluation determines fit.
Check whose decision changes the baseline
Ask each role to perform its permitted action. A supplier proposes a change. A reviewer records comments and a disposition. The authorised owner decides whether the proposal enters the controlled baseline. An administrator can have operating permissions that differ from the engineering authority.
Check how required reviewers, disagreements, returned work and exceptions appear in the record. A named approval without the reviewed revision leaves the decision ambiguous. A completed review with an unresolved mandatory criterion should not silently become full programme acceptance.
If the customer requires an external sign-off or regulated electronic signature, include that obligation as a separate gate. Neither an authenticated account nor an audit log alone establishes compliance with that contract or regulation.
Inspect the result, not just its link
For a Flow Engineering requirements verification review, distinguish a linked test from evidence accepted for the current requirement revision and configuration.
A verification link tells the reviewer which record to inspect. It does not establish that the result applies to the current proposal. Recover the requirement and procedure revisions, success criteria, test article, hardware/software configuration, operating condition and result disposition.
In the fictional payload review, B1 evidence remains evidence for B1. A report cannot become proof for the changed payload demand merely because the requirement ID stayed the same. The owner must justify reuse, obtain a new analysis or plan another test according to the programme’s criteria.
Look for a specific explanation when evidence is reused. Which changed condition matters? Which part of the old result remains applicable? What assumption is being relied on? What remains unverified? The verification evidence record and traceability fields give a reusable starting structure.
Include one incomplete relationship. If AN-THM-04 is available while the thermal dependency is unresolved, the finding should remain open with an owner. A connected power analysis cannot close a thermal obligation. Use the existing configuration guide when the evidence differs across variants.
Ask a reviewer to reconstruct these answers
- Which requirement is accepted? Recover its revision and source without relying on the presenter’s explanation.
- What exactly is proposed? Identify the changed fields, relationships, reason and responsible owner.
- Which result was produced? Open the original result with the procedure and conditions that generated it.
- Which configuration does it cover? Distinguish the as-tested state from the proposed design.
- Who accepted which decision? Identify the reviewer, reviewed material, rationale and unresolved actions.
- What remains unknown? Recover the missing dependency and explain whether it holds the milestone.
Repeat the reconstruction from the package a reviewer would actually receive. Flow documents branch exports, and Arc supports programme outputs and exportable review records. Confirm what the chosen package contains and what requires live application access. This article makes no export-completeness claim for either evaluated setup.
Keep assistance visible. If a vendor representative finds a record, fixes a mapping or supplies a missing field, record that step. It can be useful support, but it is different from a team maintaining and reconstructing the workflow unaided.
Choose for the assessed scope
Accept fit when the responsible owners can recover the required revisions, applicable evidence and accountable disposition, and maintain the same clarity through another change. Request proof when a mandatory field, permission boundary or configuration is unresolved. Retain the current tool when it already meets the milestone or an essential record cannot yet be reconciled elsewhere.
For a first dedicated tool, evaluate one maintainable work package. For a replacement, add history, attachment, integration and cutover checks before moving authority. Use the fictional change protocol to structure the exercise and the same-criteria comparison to inspect documented scope. The pricing worksheet then makes the proposed commercial packages comparable.
Frequently asked questions
Is this an independent or hands-on Flow review?
No. Arc publishes this source-based review and has a commercial interest in teams choosing Arc. Flow’s public product material was reviewed on 2 November 2026. The checklist and fictional milestone card are evaluation resources, not observations from a completed Flow or Arc product test.
What should a team check before a design or verification review?
Check the exact requirement revision, the as-tested configuration, the origin and scope of each result, and the named authority accepting the decision. Keep the accepted baseline separate from the proposal and retain unresolved evidence or dependency questions as open work.
Do recorded approvals establish compliance?
A recorded approval identifies a decision against reviewed material. Contractual acceptance, regulated electronic signatures, safety authority and programme compliance each require their own criteria and evidence. Confirm the required authority and process separately from the software review status.
When should an installed Flow team stay?
Retain Flow when its installed requirements, review and evidence workflow meets the milestone’s needs, or when a customer-mandated baseline or required integration depends on it. Move accepted history only after mapping, operating ownership and the proposed cutover are accepted.
How should an unresolved item affect the milestone fit decision?
An unresolved mandatory record or authority boundary holds the fit decision. A non-mandatory uncertainty can remain as a named follow-up when the milestone owner records why progression is acceptable. Documentation and an unexecuted checklist cannot be marked as demonstrated product outcomes.