Project change portals: what did the client approve?

Approval to move the reception desk

Suppose a team is designing an office interior. At the client's request, the designer moves the reception desk and sends revision B of the drawing. The client approves it. Later, the designer produces revision C, which also relocates a storage cabinet. The client's response still concerns revision B and the reception desk. The cabinet change needs to be presented separately.

The proposed portal shows the client a drawing with a short description of what they are being asked to review. Their response stays with that revision. The project manager sees the approved reception change alongside the later proposal awaiting a response. They can follow the conversation without comparing email dates with file timestamps.

Before sending revision C, the designer describes the additional change and identifies the new drawing. The client can revisit the earlier agreement, see what has been added, and respond to the new proposal. The earlier approval remains in the history. The project manager assigns the resulting work according to the company's agreed authorization process. From the task, the team opens the drawing covered by that agreement, even if a newer draft is already in the folder.

Check your existing approval workflow first

A standard tool may handle much of this work. Jira Service Management supports approval steps in request workflows. Designated approvers receive notifications and can approve or decline through channels including the help center and email (Jira Service Management approvals).

If you already use a similar system, establish whether the client's response stays connected to the drawing and scope presented for approval when a new attachment arrives. An “approved” field can be too broad when a request contains several revisions. Ask the administrator how the earlier agreement is preserved and a new proposal presented. Configuration and better organization of attachments may be sufficient.

When a dedicated client view helps

An extension may be enough if the internal workflow works well but clients struggle to find the proposal among comments and attachments. A focused view could show the drawing, the description of the change, and a place to respond. The team would continue receiving the request in its current task system. The connection also needs to carry the reference to the revision the response concerns.

Consider a custom portal when the project manager repeatedly pieces agreements together from email, a drawing library, and a planning tool. The initial scope can cover one type of change presented to clients. Design software and broader project management can remain in place. The useful improvement is letting the manager hand off agreed work without reconstructing the context again.

Your team needs to identify who responds for the client and who authorizes work within the firm. Clients should see materials for their own project, while designers' internal notes stay in their working environment. That gives clients a clear place to review proposals without exposing the team's entire workspace.

Conventional software can handle this core process. AI assistance with summarizing long correspondence can be evaluated separately if it is useful.

If the difficulty comes after completed work has been accepted, when a signed document needs to reach the person preparing billing, our article on acceptance certificate workflows covers that handoff.

Keeping agreements when you change tools

When migrating open requests, keep the proposal, drawing, and client response together. A list of requests with their final statuses will not let the manager explain what was agreed. Older projects can remain in an accessible archive if those connections are still available. Also establish how you could later export them from the new portal.

After launch, someone needs to manage client access and changes in how the firm works. Agree with the provider who investigates a response that reaches the portal but never appears with the team's task. Maintaining connections, code and data ownership, and access for a replacement provider belong in the comparison with a standard product.

Connect client responses to the team's work

Through its custom application service, Syntalith can build a portal connecting a proposed change, drawing revision, and client response to a task in your existing system. The project manager gets the context needed to assign agreed work, and the client gets one place to review and respond. An approval workflow that already works can remain part of the solution.

Tell us about the last change where someone had to establish what the client had actually approved. Explain where you keep drawings and where the manager assigns tasks. That conversation helps determine whether the project needs a connection between those tools or a dedicated client view as well. See Syntalith pricing for information about billing.