All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Change Request Management
Start now
More

Features

Industries

Reference

More

Change Request Management · Available now

Keep each change tied to its scope and decision.

Change Request Management gives delivery teams a governed record for changes to project work. An organization owns the project, and each work package states the subject, scope, due date, budget hours, owner and revision.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewPackages by status
Change Request Management · Work packages

Packages by status

Work packages in one list

New work package
Work packages in view
6
Total budget hours
58
Draft
2
Planned
1
Draft2
Billing approval rule changeWarehouse intake rollout
6
23 Oct
Invoice validation rule updateBilling workflow modernization
7
12 Oct
Add
Planned1
Portal access control updateBilling workflow modernization
11
29 Oct
Add
Active1
Warehouse receiving revisionSupport operations refresh
14
16 Oct
Add
Review1
Reporting migration scope updateQuarterly reporting migration
4
30 Oct
Add
Accepted1
Field dispatch workflow changeInvoice controls upgrade
16
31 Oct
Add
Billing approval rule changeWork packages · WP-32888
Draft
CounterpartyWarehouse intake rollout
OwnerMateo Alvarez
Due at23 Oct
Budget hours6
Revision570
Review packageWP-32888 · Billing approval rule change

Independent Reviewer decides Approve, Reject or Return for the package revision.

Waiting for Independent Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
10
Saved views
12
Roles with set permissions
6
Reports and dashboards
8
Features

See every scoped change in context

Every feature works on the same records. Pick one to see the screen your team works in.

Organization and projects

Keep change work attached to the organization and affected project.

  • Organization first
  • Project context
  • Package link
  • Organizations
  • Projects
  • Work packages
  • Team members
Explore organization and projects
OverviewPackages awaiting review
Change Request Management · Organization and projects

Packages awaiting review

Acceptance waits for the delivery lead

New
Record numberSubjectCounterpartyOwnerStatusRevision
WP-83045Billing approval rule changeCustomer portal accessElena VargaReview300
WP-27669Portal access control updateCustomer portal accessAisha MensahReview820
WP-48902Warehouse receiving revisionMobile service experienceJonas BeckerReview300
WP-96426Reporting migration scope updateInvoice controls upgradeAisha MensahReview640
WP-52542Field dispatch workflow changeWarehouse intake rolloutAisha MensahReview250
6 of 6 records
Billing approval rule changeWork packages · WP-83045
Review
CounterpartyCustomer portal access
OwnerElena Varga
Revision300
Due at24 Oct
Example screen with sample data
Process

Follow scope through review

Scope to reviewed change ships ready to use. One step needs a named approval before the work moves on: Review package (Independent Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Set project context

    Identify the affected project and owning organization.

    Billing approval rule changeWP-32888 · Project Manager
    Set project contextBy Project Manager

  2. Draft work package

    Record the requested scope, owner, budget hours and due date.

    Billing approval rule changeWP-32888 · Project Manager
    Draft work packageBy Project Manager

  3. Assess impact

    Explain added hours and dollar cost effect.

    Billing approval rule changeWP-32888 · Business Analyst
    Assess impactBy Business Analyst

  4. Plan tasks

    Assign delivery work and compare planned effort with the package.

    Billing approval rule changeWP-32888 · Project Manager
    Plan tasksBy Project Manager

  5. Review package

    An independent reviewer examines the current revision and records a reasoned decision.

    Billing approval rule changeWP-32888 · Independent Reviewer
    Review packageBy Independent Reviewer
    ApprovalIndependent Reviewer decides Approve, Reject or Return for the package revision.

  6. Record outcome

    Keep the package status aligned with the reviewed decision.

    Billing approval rule changeWP-32888 · Delivery Lead
    Record outcomeBy Delivery Lead

Start with Scope to review

Inside a record

Connect project identity and evidence

Open any work package to see its impact assessments, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Counterparty, Owner, Due at and Budget hours.

  2. 2
    Impact assessments

    Each line is linked to this work package.

  3. 3
    Who works on it

    Admin, Delivery Lead and Project Manager, each with their own permissions.

  4. 4
    Process stages

    Draft work package, with the role that acts.

  5. 5
    Approvals

    Review package, with who decides.

Packages by statusBilling approval rule change
Change Request Management · Work packages

Billing approval rule change

Warehouse intake rollout · Draft

Log activity
1
Record details
CounterpartyWarehouse intake rollout
OwnerMateo Alvarez
Due at23 Oct
Budget hours6
2
Impact assessments

Billing approval rule change

TitleParentProject
Billing change cost assessmentPortal access control updateBilling workflow modernization
Portal access security assessmentSupport queue routing revisionWarehouse intake rollout
Warehouse rollout schedule impactInvoice validation rule updateBilling workflow modernization
Impact assessments
6
Total added hours
51
3

Who works on it

  • AdminManage Organizations, Projects, team members, Users
  • Delivery LeadManage Projects, work packages
  • Project ManagerManage Projects, work packages, Tasks
4

Process stages

  • Draft work packageProject Manager
5

Approvals

  • Review packageIndependent Reviewer
    Approved
Example screen with sample data
Approvals

Keep decisions tied to the reviewed revision

The package owner and analyst prepare the material; an Independent Reviewer records the choice on a named revision.

OverviewApprovals
Change Request Management · Overview

Approvals

Signed in as Independent Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • IA-37404Billing change cost assessment
    Portal access control updateRequested by Aisha Mensah
    Submitted2dActions
  • IA-86934Portal access security assessment
    Support queue routing revisionRequested by Ravi Patel
    Submitted3dActions
  • IA-88357Warehouse rollout schedule impact
    Invoice validation rule updateRequested by Caleb Brooks
    Submitted5dActions
  • IA-70122Reporting migration data impact
    Portal access control updateRequested by Elliot Chen
    Submitted5dActions

Who approves what

DecisionApprover
Review packageAn independent reviewer examines the current revision and records a reasoned decision.Independent Reviewer
1 approval rule · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Change Request Management to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintains organization context, access and the operating setup.

  • Manage Organizations, Projects, team members, Users
  • View work packages, impact assessments, Tasks, review decisions, record attachments, operation receipts

Roles and permissions

Reports

Read effort, decisions and exceptions

Read workload, effort, decisions and exceptions from the change records.

Overview
Change Request Management · Overview

Change Request Management dashboard

This quarter

Impact assessments in view
6
Total added hours
51
Submitted
6

Work packages by status

How far records got this quarter

StageReachedStep
Draft37
Planned1335%
Active538%
Review120%

Budget hours by status

Sample totals per stage

1.0k0
1.0kDraft
1.0kPlanned
1.0kActive
1.0kReview
-3000Accepted
Example screen with sample data
  1. 01Change workload by project

    Group work packages by project, owner and status with budget and actual task hours.

  2. 02Impact estimate by organization

    Sum added hours and cost delta from assessments by organization and status.

  3. 03Review decision history

    Compare decisions, reasons and source revisions by package and reviewer.

  4. 04Task effort variance

    Compare planned and actual task hours by package, assignee and status.

  5. 05Package due dates

    List active and review packages by due date, owner and project.

  6. 06Failed governed actions

    Group failed operation receipts by action, failure reason and parent package.

  7. 07Evidence register

    List attachment type, visibility, upload date and package.

  8. 08Project change summary

    Show organization, project, packages, their assessments and task effort.

All reports and dashboards

Who it's for

Fit the work to your delivery team

See how Change Request Management fits your kind of team.

Software delivery teams

Keep requested product changes tied to a project, impact and review decision.

Professional services teams

Control scope and effort changes during client delivery.

Internal transformation teams

Record changes to internal project work with clear ownership and decisions.

Controls

Keep revisions and action outcomes visible

Each stage of scope to reviewed change names the role that acts and the status it records, so a change is never anonymous.

OverviewScope to reviewed change
Change Request Management · Process

Scope to reviewed change

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
8
Draft work package
Project Manager
StatusDraft → Planned
RecordsWork packages, Projects
Assess impact
Business Analyst, Independent Reviewer
StatusDraft → Submitted
RecordsImpact assessments
Plan tasks
Project Manager
StatusPlanned → Active
RecordsProjects, Tasks
Scope to reviewed change
  1. Start
    Draft work packageDraft → Planned
    Work packages
  2. Step
    Assess impactDraft → Submitted
    Impact assessments
  3. Step
    Plan tasksPlanned → Active
    Projects
  4. Step
    Carry out workBacklog → in progress
    Tasks
  5. Step
    Submit packageActive → Review
    Projects
Example screen with sample data

See each stage in detail

AI agent

Ask Proto for the next review packet

Use Proto to help configure and examine your change workflow.

It can

  • Project Manager: Ask for packages in Review with their owners, due dates and source revisions.
  • Business Analyst: Ask for submitted assessments whose added hours differ from the related task plan.
  • Delivery Lead: Ask for failed operation receipts and the reason recorded for each attempt.
  • Independent Reviewer: Ask for the current package revision, assessment, tasks and attachments before deciding.

Stays with a person

  • Proto can organize records and prepare a review packet.
  • The Independent Reviewer still makes and records the decision.
  • A generated summary should be checked against the package and related records before anyone changes status or treats a revision as accepted.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Change Request Management
  • Project source
  • Identity service
  • File storage
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 10 tables
10tables
  • Organization and projects4
  • Scoped work packages6
  • Impact assessments6
  • Task delivery5
  • Review decisions5
  • Evidence and receipts5
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Set ownership

    Confirm organizations, project owners, team members and who may prepare or independently review a package.

  2. Load project context

    Establish project identity, status, dates and organization links. Check a sample against the original project record.

  3. Pilot a change

    Draft one package, add an impact assessment, plan tasks and attach evidence.

  4. Rehearse the decision

    Return a package for correction, revise it and record a new decision against the current source revision.

  5. Inspect exceptions

    Check failed operation receipts and confirm the team can explain what did and did not change.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Change Request Management.

All questions
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.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appChange Request Management

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.