Release Management · Available now

Plan release packages and keep delivery decisions visible.

Release Management organizes a project into release packages, assigned tasks and scheduled deployment windows. A delivery lead can see package progress, effort and exceptions in Operations Overview while project managers keep dates and owners current.

Start now Download Proto

No per-user fees
Manual work is free
Configure it in Proto

OverviewActive Projects

Release Management · Projects

Active Projects

Projects in one list

New project

Projects in view

Active

At risk

Active3

PRJ-PORTAL-26Customer portal refresh

31 Oct

PRJ-SCANNER-26Warehouse scanner rollout

03 Nov

PRJ-SCHEDULE-26Field service scheduling

23 Oct

Add

At risk3

PRJ-ROUTING-26Order routing modernization

02 Nov

PRJ-LEDGER-26Billing ledger migration

01 Nov

PRJ-PARTNER-26Partner API integration

15 Oct

Add

PRJ-PORTAL-26Projects · PRJ-86164

Active

Project nameCustomer portal refresh

OrganizationElm Quarry Logistics

OwnerMarcus Flynn

Start date31 Oct

End date03 Nov

Record review decisionPRJ-86164 · PRJ-PORTAL-26

The Delivery Lead decides whether the reviewed release subject is Approved, Rejected or Returned.

Waiting for Delivery Lead

ApproveReturn

Example screen with sample data

Tables, ready to use: 13
Saved views: 14
Roles with set permissions: 6
Reports and dashboards: 8

Features

Release work in view

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

Release planning

Plan releasable work under a project, with an owner and effort estimate.

Owner
Record
Decision

Projects
Release packages
Organizations
Team members

Explore release planning

OverviewMy projects

Release Management · Release planning

My projects

Projects

New

Project code	Project name	Organization	End date	Status	Owner
PRJ-PORTAL-26	Customer portal refresh	Juniper Freight Systems	18 Oct	Planned	Farah Saleh
PRJ-ROUTING-26	Order routing modernization	Juniper Freight Systems	18 Oct	Active	Felix Romero
PRJ-SCANNER-26	Warehouse scanner rollout	Juniper Freight Systems	02 Nov	At risk	Farah Saleh
PRJ-LEDGER-26	Billing ledger migration	Slate River Services	25 Oct	Completed	Anjali Rao
PRJ-SCHEDULE-26	Field service scheduling	Oriole Supply Network	11 Oct	Planned	Felix Romero

6 of 6 records

PRJ-PORTAL-26Projects · PRJ-37109

Planned

Project nameCustomer portal refresh

OrganizationJuniper Freight Systems

End date18 Oct

OwnerFarah Saleh

Example screen with sample data

Delivery tasks

Follow assigned tasks from backlog through review and completion.

Owner
Record
Decision

Tasks
Release packages
Team members
Time entries

Explore delivery tasks

OverviewBlocked Tasks

Release Management · Delivery tasks

Blocked Tasks

Tasks

New

Task key	Title	Release package	Assignee	Due date	Priority
PORTAL-184	Finalize portal account navigation	Order routing rules 1.8	Leo Marin	30 Oct	Low
ROUTE-276	Add routing fallback for backorders	Partner webhook support 2.0	Anjali Rao	11 Oct	Medium
SCAN-309	Validate scanner offline sync	Stock reservation service 1.9	Cora Bennett	19 Oct	High
LEDGER-142	Reconcile migrated invoice totals	Scanner offline sync 3.1	Naomi Okafor	26 Oct	Critical
CAL-221	Review technician calendar rules	Order routing rules 1.8	Samir Das	11 Oct	Low

6 of 6 records

PORTAL-184Tasks · TSK-20802

Low

TitleFinalize portal account navigation

Release packageOrder routing rules 1.8

AssigneeLeo Marin

Due date30 Oct

StatusBlocked

Example screen with sample data

Deployment windows

Track a planned deployment date and record whether its window was met.

Owner
Record
Decision

Deployment windows
Projects
Release packages
Team members

Explore deployment windows

OverviewMy release packages

Release Management · Deployment windows

My release packages

Release packages

New

Release code	Release package name	Project	End date	Status	Owner
REL-PORTAL-2.4	Portal account settings 2.4	Field service scheduling	28 Oct	Not started	Yuna Park
REL-ROUTE-1.8	Order routing rules 1.8	Field service scheduling	17 Oct	In progress	Leo Marin
REL-SCAN-3.1	Scanner offline sync 3.1	Partner API integration	20 Oct	Blocked	Yuna Park
REL-LEDGER-2	Ledger migration phase 2	Field service scheduling	19 Oct	Done	Samir Das
REL-CAL-1.6	Scheduling calendar 1.6	Billing ledger migration	12 Oct	Not started	Cora Bennett

6 of 6 records

REL-PORTAL-2.4Release packages · RP-87523

Not started

Release package namePortal account settings 2.4

ProjectField service scheduling

End date28 Oct

OwnerYuna Park

Example screen with sample data

Time and capacity

Review submitted hours and compare assigned work with weekly capacity.

Owner
Record
Decision

Time entries
Team members
Tasks
Projects
Review decisions
Operation receipts

Explore time and capacity

OverviewTimesheets Awaiting Approval

Release Management · Time and capacity

Timesheets Awaiting Approval

Approval conditions

New

Entry number	Team member	Project	Task	Work date	Hours
TE-72727	Farah Saleh	Billing ledger migration	Document partner webhook retries	26 Oct	11
TE-36393	Yuna Park	Field service scheduling	Resolve console search latency	23 Oct	7
TE-90889	Leo Marin	Customer portal refresh	Test stock reservation updates	25 Oct	8
TE-97496	Leo Marin	Billing ledger migration	Finalize portal account navigation	30 Oct	1
TE-60941	Anjali Rao	Warehouse scanner rollout	Reconcile migrated invoice totals	15 Oct	9

6 of 6 records

Billing ledger migrationTime entries · TE-72727

Submitted

Team memberFarah Saleh

TaskDocument partner webhook retries

Work date26 Oct

Hours11

Example screen with sample data

Review and evidence

Keep delivery decisions and attachments beside their subject records.

Owner
Record
Decision

Review decisions
Operation receipts
Record attachments
Projects
Team members

Explore review and evidence

OverviewReview decisions by outcome

Release Management · Review and evidence

Review decisions by outcome

Review decisions

New

Decision number	Subject type	Subject reference	Decision	Reviewer	Decided at
RD-38692	Project	Customer portal refresh	Approved	Naomi Okafor	13 Oct
RD-65828	Work Package	Order routing modernization	Returned	Yuna Park	15 Oct
RD-31697	Task	Warehouse scanner rollout	Approved	Leo Marin	18 Oct
RD-60311	Milestone	Billing ledger migration	Returned	Anjali Rao	30 Oct
RD-74049	Deliverable	Portal account settings 2.4	Approved	Cora Bennett	15 Oct

6 of 6 records

Customer portal refreshReview decisions · RD-38692

Project

DecisionApproved

ReviewerNaomi Okafor

Decided at13 Oct

Related projectWarehouse scanner rollout

Example screen with sample data

Process

From package plan to window review

Plan and review a release ships ready to use. One step needs a named approval before the work moves on: Record review decision (Delivery Lead).

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

Establish project

Name the project owner and working dates.

PRJ-PORTAL-26PRJ-86164 · Project Manager
Establish projectBy Project Manager
Plan release package

Group releasable tasks under one package.

PRJ-PORTAL-26PRJ-86164 · Project Manager
Plan release packageBy Project Manager
Deliver tasks

Follow assigned work through review.

PRJ-PORTAL-26PRJ-86164 · QA Engineer
Deliver tasksBy QA Engineer
Triage issues

Move qualified open issues into triage and keep a receipt.

PRJ-PORTAL-26PRJ-86164 · QA Engineer
Triage issuesBy QA Engineer
Record review decision

The delivery lead records an approval, rejection or return with its subject.

PRJ-PORTAL-26PRJ-86164 · Delivery Lead
Record review decisionBy Delivery Lead
ApprovalThe Delivery Lead decides whether the reviewed release subject is Approved, Rejected or Returned.
Review deployment window

Record whether the planned window was met.

PRJ-PORTAL-26PRJ-86164 · Project Manager
Review deployment windowBy Project Manager

Start with Plan and deliver a package

Inside a record

Keep execution evidence linked

Open any project to see its deployment windows, the roles that work on it, its process stages and its approvals on one page.

1
Record details
Project name, Organization, Owner and Start date.
2
Deployment windows
Each line is linked to this project.
3
Who works on it
Delivery Lead, Project Manager and Developer, each with their own permissions.
4
Process stages
Establish project and Plan release package, with the role that acts.
5
Approvals
Record review decision, with who decides.

Active ProjectsPRJ-PORTAL-26

Release Management · Projects

PRJ-PORTAL-26

Customer portal refresh · Active

Log activity

Record details

Project nameCustomer portal refresh

OrganizationElm Quarry Logistics

OwnerMarcus Flynn

Start date31 Oct

Deployment windows

PRJ-PORTAL-26

Window name	Project	Owner
Portal rollout, Oct 22 evening	Field service scheduling	Benji Hart
Routing update, Oct 24 morning	Warehouse scanner rollout	Yuna Park
Scanner pilot, Oct 28 overnight	Support console rebuild	Anjali Rao

Deployment windows: 6

Who works on it

Delivery LeadManage Projects, release packages, deployment windows
Project ManagerManage Projects, release packages, Risks, deployment windows
DeveloperManage Tasks, Issues, time entries

Process stages

Establish projectProject Manager
Plan release packageProject Manager, Delivery Lead

Approvals

Record review decisionDelivery Lead
Approved

Example screen with sample data

Approvals

Record the release decision

The time approver checks automatic approval results and failed attempts; delivery leads review package outcomes and decisions.

OverviewApprovals

Release Management · Overview

Approvals

Signed in as Delivery Lead

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine

0 selectedApproveReturn

TE-72727Billing ledger migration
Document partner webhook retriesRequested by Farah Saleh
Submitted0dActions
TE-36393Field service scheduling
Resolve console search latencyRequested by Yuna Park
Submitted2dActions
TE-90889Customer portal refresh
Test stock reservation updatesRequested by Leo Marin
Submitted3dActions
TE-97496Billing ledger migration
Finalize portal account navigationRequested by Leo Marin
Submitted5dActions

Who approves what

	Decision	Approver
	Record review decisionThe delivery lead records an approval, rejection or return with its subject.	Delivery Lead
	Approve review decisions	Delivery Lead

2 approval rules · set per role in Proto

Example screen with sample data

Who can approve what

Roles

A workspace for each role

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

Delivery Lead

Owns the release plan, exception review and delivery handoff.

This is the first screen this role sees.

OverviewTimesheets Awaiting Approval

Timesheets Awaiting Approval

Time entries · Delivery Lead

Entry number	Team member	Project	Task	Work date	Hours
TE-72727	Farah Saleh	Billing ledger migration	Document partner webhook retries	26 Oct	11
TE-36393	Yuna Park	Field service scheduling	Resolve console search latency	23 Oct	7
TE-90889	Leo Marin	Customer portal refresh	Test stock reservation updates	25 Oct	8
TE-97496	Leo Marin	Billing ledger migration	Finalize portal account navigation	30 Oct	1
TE-60941	Anjali Rao	Warehouse scanner rollout	Reconcile migrated invoice totals	15 Oct	9

6 of 6 records

Example screen with sample data

Project Manager

Maintains project schedules, package assignments and delivery risks.

This is the first screen this role sees.

OverviewTimesheets Awaiting Approval

Timesheets Awaiting Approval

Time entries · Project Manager

Entry number	Team member	Project	Task	Work date	Hours
TE-72727	Farah Saleh	Billing ledger migration	Document partner webhook retries	26 Oct	11
TE-36393	Yuna Park	Field service scheduling	Resolve console search latency	23 Oct	7
TE-90889	Leo Marin	Customer portal refresh	Test stock reservation updates	25 Oct	8
TE-97496	Leo Marin	Billing ledger migration	Finalize portal account navigation	30 Oct	1
TE-60941	Anjali Rao	Warehouse scanner rollout	Reconcile migrated invoice totals	15 Oct	9

6 of 6 records

Example screen with sample data

Time Approver

Monitors time approval outcomes and follows failed receipts.

This is the first screen this role sees.

OverviewTimesheets Awaiting Approval

Timesheets Awaiting Approval

Time entries · Time Approver

Entry number	Team member	Project	Task	Work date	Hours
TE-72727	Farah Saleh	Billing ledger migration	Document partner webhook retries	26 Oct	11
TE-36393	Yuna Park	Field service scheduling	Resolve console search latency	23 Oct	7
TE-90889	Leo Marin	Customer portal refresh	Test stock reservation updates	25 Oct	8
TE-97496	Leo Marin	Billing ledger migration	Finalize portal account navigation	30 Oct	1
TE-60941	Anjali Rao	Warehouse scanner rollout	Reconcile migrated invoice totals	15 Oct	9

6 of 6 records

Example screen with sample data

Roles and permissions

Reports

Read the delivery state

Use project, package and review records to explain delivery state.

Overview

Release Management · Overview

Release Management dashboard

This quarter

Time entries in view

Total hours

Submitted

Projects by status

How far records got this quarter

Stage	Reached	Step
Planned	34
Active	22	65%
On hold	11	50%
At risk	8	73%

Number of projects by status

Sample counts per stage

900

60Planned

40Active

30On hold

70At risk

90Completed

Example screen with sample data

All reports and dashboards

Who it's for

Built for delivery teams

See how Release Management fits your kind of team.

Software delivery teams

Coordinate packages, issue triage and deployment windows across a delivery team.

Internal platform teams

Keep internal change work and review evidence together.

Client delivery groups

Track release work across client projects and their assigned teams.

Controls

Trace decisions and exceptions

Each stage of plan and review a release names the role that acts and the status it records, so a change is never anonymous.

OverviewPlan and review a release

Release Management · Process

Plan and review a release

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

Process stages

Approval steps

Roles involved

Tables touched

Establish project

Project Manager

StatusPlanned → Active

RecordsOrganizations, Team members, Projects

Plan release package

Project Manager, Delivery Lead

StatusNot started → in progress

RecordsRelease packages, Projects

Assign delivery tasks

Project Manager, QA Engineer, Developer

StatusBacklog → in progress

RecordsRelease packages, Team members, Projects

Plan and review a release

Start
Establish projectPlanned → Active
Organizations
Step
Plan release packageNot started → in progress
Release packages
Step
Assign delivery tasksBacklog → in progress
Release packages
Step
Deliver tasksIn progress → in review
Tasks
Step
Triage issuesOpen → Triaged
Operation receipts

Example screen with sample data

See each stage in detail

AI agent

Ask Proto about your release

Ask Proto to help organize and inspect release records.

It can

Delivery Lead: Find packages in progress, blocked tasks and pending deployment windows for a project.
Project Manager: Compare estimated and actual task hours before moving a package date.
QA Engineer: Gather open issues by severity and show the related operation receipts.
Time Approver: Show time approval outcomes and failed attempts with their project, task, date and hours.

Stays with a person

The delivery lead decides whether a window was met.
The time approver reviews the automatic hour approval results and exceptions.
Proto can show the linked records and prepare an action, but the team checks the subject, owner and evidence before recording a consequential decision.

Set up an agent

agent · release management

Show my blocked tasks for the current release package.

Which open issues affect the project with the next pending deployment window?

Show submitted time entries for review with their project and hours.

The delivery lead decides whether a window was met.

Integrations

Connects to the tools you use

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

Release Management
Source control
Build and deployment tooling
Document 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 13 tables

13tables

Release planning4
Delivery tasks4
Deployment windows4
Issues and risks5
Time and capacity6
Review and evidence5

Implementation

Roll out one team at a time

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

Set the project
Create the organization, team members and project with an owner and dates.
Plan a package
Put releasable tasks under a package and name the people who maintain each status.
Run the exceptions
Raise an issue with severity, rehearse triage and inspect its receipt. Record one risk with an owner and mitigation.
Review hours
Submit time with positive hours, then inspect the resulting approval decision and receipt.
Review the window
Schedule a pending window, check the package and issues, then record the actual outcome.

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
Usage	Per $1
Record reads (list, filter, get)	20,000
Search or aggregate queries	4,000
Record writes	4,000
Imported or synced records	200,000
Workflow runs	2,000
AI agent runs	2,000
Scheduled jobs or webhooks	20,000
File uploads (MB)	2,000
CSV or PDF exports	100

FAQ

Questions, answered

Scope, rollout and pricing for Release Management.

All questions

How do I get started?

Click Get started, then use Proto to configure Release Management for your business. Begin with one project, one release package, assigned tasks and a pending deployment window.

What is a release package?

It is the releasable unit of project work with an owner, planned dates, effort estimate and status. Tasks sit under the package.

Where can we see blocked work?

Use Blocked Tasks and the task board. The package status can also be Blocked when the release unit needs attention.

How are issues triaged?

An open issue with severity can move to Triaged through the issue triage action. The action records an operation receipt, including a failed attempt when its guard fails.

Who reviews submitted time?

The workflow approves a submitted entry with positive hours and records a review decision and operation receipt. The time approver reviews outcomes and failed attempts.

How do we track a deployment date?

Create a deployment window with a project, owner and due date. Record Met or Missed after the planned event and keep the reason in notes.

How do we connect deployment tooling?

Connect the team's deployment tooling and keep its execution evidence with the release case. Record the window outcome after checking that evidence.

Where do supporting files go?

Record attachments can store a file link, kind, parent table and parent record ID. Confirm the parent before filing.

Can we review team load?

Team members carry weekly capacity and assigned and logged hour totals. Compare them with package and task estimates when planning the next window.

Set up Release 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

Find your application

Plan release packages and keep delivery decisions visible.

Active Projects

Release work in view

Release planning

My projects

Delivery tasks

Blocked Tasks

Deployment windows

My release packages

Issues and risks

Open Issues

Time and capacity

Timesheets Awaiting Approval

Review and evidence

Review decisions by outcome

From package plan to window review

Establish project