Questions, answered

Click Get started, then use Proto to configure Requirements Management for your business. Begin with one project, its current requirements and a baseline review so the team can check ownership, revisions and decisions together.

A requirement holds the requested outcome, project, owner, revision, dates and lifecycle status. Requirement items break it into assignable work.

Create requirement items with a title, priority, assignee and due date. Use the status board to review work in backlog, progress, review, blocked and done states.

The Business Analyst adds acceptance criteria and a revision to a baseline, then submits it. Submission stamps the review time and writes an operation receipt tied to the expected revision.

The Project Manager reviews the submitted version and criteria, then records approval or rejection on the baseline with a decision date and notes.

QA Engineer records verification findings against a project with severity and owner. The finding remains visible while it is open, triaged or in progress.

Use a change impact record for the category, probability, impact, mitigation and owner. Review the related requirement and baseline when acceptance scope changes.

The approval action checks positive hours and submitted status. Eligible entries become approved with a review decision and operation receipt; failed checks leave a receipt with the reason.

Yes. It requires a team member and project, and can also reference a requirement item. Check that the item belongs to the intended project before submitting.

Open the failed operation receipts and inspect the operation, reference and failure reason. Correct the source record before another attempt.