Quick answer
A custom software change request process compares a request with the agreed scope, assesses its dependencies and delivery impact, and records an authorized choice: add, exchange, defer, reject or investigate. Use one shared register from capture through closure. Revise scope and acceptance criteria before changed implementation, then retain tests, owner acceptance and release evidence. A developer saying “possible” is the start of assessment, not approval.
Start the custom software change request process with the agreed outcome
“Can we just restrict who joins?” sounds small because the buyer sees a join button. The delivery team may need to change how accounts, bookings and room entry work together. Before approving implementation, establish what differs from the agreement and which commitment must move to accommodate it.
The baseline is the agreed version of requirements, acceptance criteria and delivery commitments. If it specifies an open demonstration room, adding booked-user-only entry changes scope. If it already promises restricted entry and an unrelated account gets in, that is a defect candidate. A question that leaves the agreed behavior unchanged may need only a clarification in the existing task.
Neither label settles payment. Where acceptance wording is ambiguous, the buyer and vendor should agree a testable interpretation and commercial treatment before authorizing disputed work or extra fees. This process controls software delivery commitments; it does not replace the parties’ agreement. Without a shared decision, the buyer can be expecting a new outcome while the team is still estimating the old release.

Use one register to move from request to agreement
Use the existing shared spreadsheet or issue tracker. Give each request one record linking its rationale, impact, decision and delivery evidence. Small teams can combine roles, but someone must explicitly authorize business priorities and spending, review technical feasibility, commit delivery and accept the result.
Capture → classify → assess → decide → revise baseline → implement → verify → close. Assessment produces feasible options; the decision sets approved boundaries. Revise scope and tests before coding, then connect the released behavior to acceptance evidence. Approval to assess is not approval to implement.
In an illustrative tutoring-company release, the baseline includes an open demonstration room and an optional dashboard. The owner now wants lessons restricted to their assigned tutor and student. This completed register records the exchange and eventual closure demonstrated below; copy its field labels and link supporting detail.
- Request and rationale: replace open entry with access for the assigned tutor and student on an active booking; unrelated accounts must not enter lessons. Needed this release. Recording and group calls are excluded.
- Baseline and acceptance: B3 permits an open demonstration room, making this additional scope. Assigned participants must enter; unrelated accounts, logged-out visitors and cancelled bookings must be denied, including through copied links. Existing booking and session starts must still work on supported devices.
- Impact and estimate: identity, booking status, entry authorization and join interface. Assumed effort: 16 engineering and 8 testing hours, design through release. Technical lead confirms sequencing and capacity; no extra supplier charges assumed. Investigate material unknowns before approval.
- Decision and authority: tutoring owner approves priorities and spending and accepts delivery; vendor lead coordinates and commits delivery; technical lead confirms feasibility. Retain dated written approval and commercial treatment. Approve the exchange, not both features.
- Approved tradeoff and revised baseline: defer the unstarted dashboard; add restricted entry under B4 and the written scope-exchange agreement. Ceiling: 24 hours; release milestone unchanged. Re-decide if scope, ceiling, milestone, charges or risk limits change. Revisit dashboard at next-release planning.
- Verification and closure: link implementation review, failed copied-link test, correction, successful access and regression retests, tested build/environment, owner acceptance, support instructions and release checks. Close after release checks. Vendor lead owns deferred dashboard review.
Preserve earlier decisions and baseline versions. Unknowns can remain during assessment, but essential acceptance, ownership, impact and delivery boundaries must be resolved before implementation approval. Assign missing information a next-action owner and date rather than letting a blank field impersonate agreement.
As a proposed cadence, triage within two working days and review ordinary decisions weekly. Transfer substantive chat requests to the register and return the decision to the conversation. Give deferred work a review trigger. For unclear decision rights, custom software development team structure helps frame the responsibility discussion.

Work the decision: protect session access or keep the dashboard?
The owner initially wants the access restriction as an extra task. The estimate changes the choice: the team has enough capacity for either the optional dashboard or access control, alongside required work. It does not have an unallocated slot for both. The relevant comparison is remaining work by role and timing, not how modest the request sounds.
Assume 80 engineering and 40 testing hours remain, all billable at $100 per hour. Required work uses 64 engineering and 32 testing hours; the unstarted dashboard uses the other 16 and 8. Access control also needs 16 engineering and 8 testing hours, including design through release. These are illustrative planning assumptions, with no additional supplier charges. The amounts below are planned remaining vendor charges, not vendor labor costs, profit, prepaid cash or an invoice schedule.
| Release option | Engineering hours | Testing hours | Planned remaining vendor charges |
|---|---|---|---|
| Original plan: required work and dashboard | 80 | 40 | $12,000 |
| Add access control and retain dashboard | 96 | 48 | $14,400 |
| Exchange dashboard for access control | 80 | 40 | $12,000 |
Exchange only because protected access outranks the dispensable dashboard and removing it frees the required roles at the right time. The technical lead confirms dependencies and sequencing. Equal total hours cannot establish a release date: spare testing time cannot perform engineering work, and capacity arriving after release cannot rescue it.
Adding access control increases planned work from 120 to 144 hours and charges by $2,400; revise the schedule unless suitable extra capacity is confirmed. If the dashboard is substantially built, compare remaining work and removal effort, not its historical estimate. If it is required or frees the wrong skills, defer access control or revise budget and timing. Reject requests that conflict with the product goal or a fixed constraint.
The architectural question is whether the system can enforce the promised rule wherever entry happens. Ask the technical lead to trace the join action through account identity, booking status, shared components and the external calling service. Hiding a button only changes what a visitor sees. It does not prove that a copied room link cannot admit an unrelated account. Check cancellation behavior, tutor entry and existing sessions, not just the newly edited page.
Include security, privacy, performance, deployment and support effects in proportion to the change. Does another workflow rely on the open room? Will support instructions change? For integration boundaries, api sdk workflow integration architecture continues the question of why a visible change reaches beyond the page.
If enforceable entry remains unknown, authorize investigation separately. A proposed four-hour allowance would buy an entry-restriction demonstration, dependency findings and a revised estimate, followed by a build decision. It sits outside the 24-hour exchange and cannot inherit its unchanged-budget conclusion.
With feasibility confirmed, buyer and vendor approve this message: “We will replace the optional dashboard with booked-session access control. The planned remaining amount stays $12,000 and the release milestone stays unchanged. Only the assigned tutor and student may enter; recording and group calls are excluded. We will return for approval if the 24-hour allowance, milestone or agreed scope needs to change.” The vendor updates the scope and tests before coding.
Test permission and refusal: assigned participants enter on agreed supported phone and computer browsers; unrelated accounts, logged-out visitors and cancelled bookings cannot, even through copied links. Regression tests check existing booking and session-start behavior. Retain results with the tested build and environment so acceptance applies to a reproducible version.
In this example, an unrelated account initially enters through a copied link. The request remains open and release of that change is blocked. The team corrects the entry check within the approved allowance, then repeats the access tests and affected regression tests successfully. The owner accepts the result; release checks and updated support documentation support closure. If correction exceeds the ceiling or changes another approved boundary, obtain a new decision instead of weakening the test.

Common change-request questions
Contract type and urgency change the authorization route. They do not make business authority interchangeable with technical readiness. Use the register to preserve the decision and evidence, while adapting the amount of review to the project’s risk, agreement and cross-team dependencies.
For fixed-price work, record the exchange or variation under the actual agreement. For time-and-materials work, record the spending ceiling and release tradeoff. Reprioritization within delegated authority need not mean an amendment; tracker approval does not automatically amend a contract. Confirm changed commitments through the agreed route.
In Scrum, the Product Owner orders backlog work and Developers size it. Renegotiate without endangering the Sprint Goal or reducing the Definition of Done, the agreed quality requirements. Product Owner status alone does not confer spending authority. AI-generated code faces the same review and acceptance standard.
For an active incident, use an expedited route: log the incident and change, notify the incident and business owners, assess minimal containment and recovery, obtain authorized approval, test critical paths, then release with monitoring. Reconcile the baseline and decisions after containment. If no safe fix is established, the incident owner can choose documented containment, such as disabling exposed entry, while investigation continues. Waiting for the weekly review is not the purpose of control.

Take the agreed video change into an integration discussion
For a calling change, the completed record is already an integration brief: it explains who may enter, which booking conditions matter, what must be refused and which release constraints survive. Bring that brief to the delivery discussion before choosing a calling approach.
Request an impact assessment against the current calling approach and an estimate tied to the same tests and capacity limits. Seek a comparable proposal identifying any dependency requiring investigation. Without video calling, take one pending request through classification and a buyer/vendor decision in the register.

Bring an access requirement to the calling discussion
Website Video Calling compares simple embeds with API/SDK integration and describes Scrile Stream’s custom development service for tailored calling workflows. Open the guide, compare its approaches against your booking-linked access requirement, and bring the completed change record to an impact-assessment discussion with the service. The result to seek is a specific integration proposal assessed against your approved constraints.
Frequently asked questions
What counts as a custom software change request?
A proposed change to agreed behavior or delivery commitments belongs in assessment. Compare it with the baseline first: failure against an agreed test is a defect candidate, while unchanged behavior may need only clarification; neither classification settles payment.
What steps should the buyer and development team follow?
Capture, classify, assess, decide, revise the baseline, implement, verify and close. Name the business approver, delivery coordinator, technical reviewer and acceptance owner; a small team can combine roles.
What belongs in a usable change-control register?
Keep request and rationale, baseline and acceptance, impact and estimate, decision and authority, approved tradeoff and revised baseline, and verification and closure. Link supporting evidence and retain superseded decisions.
How do we assess dependencies without overlooking architectural impact?
Trace the requested behavior through identity, data, shared components, external services and affected tests. When a material dependency is unknown, authorize bounded investigation with defined findings before approving implementation.
Should we add budget, exchange scope, defer or reject?
Add only with accepted cost and timing changes and confirmed capacity. Exchange dispensable remaining work that frees the right roles at the right time; otherwise defer or reject according to the product goal and constraints.
Who approves changes in fixed-price, iterative or urgent work?
The authorized buyer approves priorities and spending, while technical and delivery leads establish feasibility and commitments. Follow the actual agreement for commercial changes; protect the Sprint Goal in Scrum and use expedited authorized containment for incidents.
What proves the change is complete, and what happens when testing fails?
Retain review, functional and regression results, acceptance and release evidence for the implemented version. Failed tests keep the request open; correction beyond approved boundaries requires another decision.
What is the next action for a change involving website video calls?
Use the completed record to compare calling approaches and request an impact assessment. Bring access rules, booking dependencies, acceptance tests and delivery constraints so the proposal answers a defined change.
Builds SaaS platforms for content creators, agencies, and entrepreneurs. Writes about the business mechanics behind creator-economy products and how custom software actually ships.
