These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Change Request Management
- Frequently asked questions
Questions, answered
Answers about setup, scope, review and change evidence.
Change Request Management
9 questions
Can't find it? Write to support@erp.ai.
How do I get started?
Click Get started, then use Proto to configure Change Request Management for your business. Pilot one active project, one scoped package and a review that includes an impact assessment, tasks and evidence.
What is the main record for a change?
A work package holds the scope, owner, project, budget hours, due date, status and revision. Related assessments, tasks and decisions explain its impact, work and outcome.
How is impact captured?
An impact assessment records added hours, a dollar cost delta and an assessment note under the package. Read it with the task plan and package budget.
Who makes the review decision?
An Independent Reviewer examines the package revision and records Approve, Reject or Return with a reason. The team should keep the reviewer separate from the package owner.
What happens when the scope changes after review?
Update the package revision and the related assessment or tasks. Present the new revision for another decision, keeping the earlier choice in the history.
Can I see tasks by status?
Yes. Task Board by Status groups tasks from Backlog through Done. A task’s completion is separate from package acceptance.
Where do supporting files go?
Record attachments connect files to a package with a title, evidence type, uploader, date and visibility.
How are failed actions investigated?
Operation receipts record the action, expected revision, result and failure reason. Delivery Lead or Admin can inspect a failed attempt beside the package.
Does the app keep projects separate by organization?
Projects, packages and team members have organization references. Agree access rules and rehearse cross-organization reads during setup.
Set up Change Request Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.