From requirement to test, every decision traceable.
For hardware, robotics, aerospace and lab teams. Requirements carry IDs, parents, priorities and statuses, and link to the tasks, tests, decisions, risks and pull requests that cover them; the coverage view shows which have nothing behind them yet. The schedule holds finish-to-start dependencies with the critical path drawn, risks sit on every programme, and parts, equipment and suppliers are on one register.
26 tools switched on for this trade at setup. Untick any you don't need.Default project tabs
RAID and Backlog replace List and Calendar: a programme is steered through its risks and a queue of open design work.
Projects created on day one
- Product Development
- Test & Validation
- Lab & Supply
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
09:00
the design review finds the untested requirement
Requirements & Traceability lists every requirement with its ID, parent, priority and status, and the coverage view shows which ones have no task and which have no test. The review starts from the gaps rather than from a spreadsheet somebody exported last week.
13:15
a slip moves only what depends on it
The Timeline draws each dependency and the critical path. With the strict finish-to-start rule on, a move that breaks a dependency is refused or warned on, and the bars that depend on a slipped task are the ones that move.
16:40
the part is reordered before the build waits on it
Inventory & Assets tracks parts stock by location and lab equipment by who holds it. When a part falls below its reorder point the owner is told, and the reorder is drafted as a purchase order to the vendor on the register.
How Engineering & R&D actually runs.
Each of these is a project in Navalo - its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working - or install any one of them on its own, later, from the marketplace.
Requirements & Traceability
Requirements with IDs, parents, priorities and statuses, linked to tasks, tests, decisions, risks and pull requests, with a coverage view of what has nothing behind it.
- IDs and a parent for every requirement
- Links to tasks, tests, decisions, risks and pull requests
- A coverage view of the gaps
- A Requirements tab on the project
Risk Register
Every risk with a likelihood, an impact, an owner and its mitigation, across every programme, and a risk raised in a meeting lands there with the sentence it came from.
- Likelihood, impact and an owner
- The mitigation and its status
- Raised from a meeting with its quote
- Across every programme in one register
Inventory & Assets
Lab equipment someone holds and parts stock you use up, by location, with every movement logged and reorders drafted as purchase orders.
- Equipment with a holder and a location
- Parts stock per location, with a reorder point
- Parts used on a task, booked to the project
- Purchase orders to the vendor
These sit on top of the whole product.
- The Timeline draws dependency lines and the critical path; the strict finish-to-start rule is a Planning setting
- GitHub attaches commits and pull requests to the tasks they name, and a requirement links to the pull request that implemented it
- Training records who has completed each course, with credentials that warn before they lapse
- The Vendor Register holds every supplier with its contracts and renewal dates
- Design reviews and test reviews get their own steer on the recorder, and decisions land in the Decision Log with the sentence that settled them
- Every workspace also gets the core: Announcements, Forms, Polls & Surveys, Kudos, Standups, Approvals, Checklists & SOPs, Recurring Tasks, the Decision Log, the Timeline, Hands-On Scheduling, Notes, the Corkboard, the Handbook, the Policy Library, Structures, Navalo Signatures, Conversation Stats and Budgets
The honest edges.
- This is not a PLM or a CAD data system: there is no drawing register with revisions and no CAD integration.
- A test is a record you link to a requirement. Navalo does not run tests or read results from a test rig.
- Training records completion and credentials; it does not verify a certificate with the body that issued it.
- Navalo holds no ISO 9001, AS9100 or SOC 2 certification and does not claim one.
Built for the way your trade actually runs.
The ones buyers ask first.
What does the coverage view show?
How strict is the schedule?
Does it replace our CAD or PLM system?
We are construction, not R&D. What do we pick?
Open a workspace that already knows Engineering & R&D.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required