UI/UX design for Hyderabad pharma artwork review

Keep a design comment attached to the carton panel and proof where it was raised. Let the next reviewer see what changed and who needs to accept it.

See a carton proof review
Light line illustration of Hyderabad’s Charminar and Qutb Shahi Tombs.

Give reviewers an accessible way to compare proofs

A side-panel change for a fictional Hyderabad packaging team

The Telangana government’s life sciences overview includes Hyderabad and describes pharmaceutical manufacturing in the region. This fictional example follows one carton proof through design review and a supplier handoff. GreyBath delivers UI/UX work remotely.

Anchor a comment to an identifiable proof location

A designer submits proof P07 of a mock carton. A reviewer notices that a fold marker crowds an internal art reference on the right side panel. The reviewer pins a comment beside the reference and gives it a short text label. The thread records the panel, proof ID and reviewer so another person can locate it from the comment list.

Carry the open issue to the next proof

In P08 the designer moves the art reference. The side panel now has enough room in the fictional layout, but the old comment remains attached to P07. P08 links to that comment and presents the changed panel for a second review. The reviewer can accept the revision for that issue and still inspect the original note.

Show which proof the supplier received

A coordinator sends the team’s accepted P08 with an artwork reference. The supplier replies with a preview marked P07. The handoff view shows the accepted proof and returned proof side by side. The coordinator requests the P08 preview and keeps the discrepancy open until the team verifies the correct file.

Make each review responsibility visible

Put the fictional proofs in front of a designer, reviewer and supplier coordinator. Ask each person to explain what changed, which version they see and what they need to do next.

Packaging designers

Respond to a specific panel comment and point the reviewer to the revised spot in the next artwork version.

Artwork reviewers

Find the original comment from a text list, compare the panel and record the handling of that issue.

Packaging coordinators

Identify exactly which version was sent and check that the returned preview refers to the same proof.

Product and design leads

Agree how the interface represents open feedback, acceptance and version mismatches across review roles.

Follow one panel comment through two proof revisions

  1. Add the P07 comment

    Using only the keyboard, open the right-side panel from the text list and add a comment in the prototype. Check that someone else can locate it without relying on the colour of the marker.

  2. Review the changed P08 panel

    Open P08 and find the link to the earlier issue. Compare the changed area and confirm that the P07 record remains available after the reviewer marks it addressed.

  3. Review a returned P07 preview

    Show the supplier’s fictional P07 return beside the P08 handoff. Check that the coordinator can find the mismatch and describe the next step without changing the proof’s prior review history.

Decide what the review interface needs to show

Prototype one carton proof workflow using mock assets. The client defines its own artwork, review responsibilities and formal approval procedures.

Discuss your project
Panel identity

Agree how the team names each panel on the unfolded artwork. Decide how an annotation stays locatable when artwork placement changes between proofs.

Comments and proof status

Decide which action closes a comment and how reopened issues are shown. Keep the status of each comment visible separately from the status of the proof.

Supplier version check

Agree which identifier staff send, where the supplier preview is displayed and who records a matching or mismatched return.

Questions about packaging proof review

Ask us something else
Can a comment be viewed without selecting a pin on the artwork?

Yes. Pair each pin with a text entry that states the panel, version and issue. Make the comment available from the list and support keyboard focus when someone opens it.

What if a panel changes between proofs?

Preserve the original annotation and link the response or follow-up to the corresponding panel in the new proof. Ask reviewers to verify the location again when the layout moves.

What happens when one comment is resolved?

Update that comment’s state and retain its history. Show the proof review status separately so staff can still see the work that remains.

Can we prototype around our existing proofing tool?

Yes. Map the current proof and reference fields first, then test the review flow with fictional files and agree where the interface should hand over to the existing tool.

What should we bring to a UI/UX discussion?

Bring two mock proofs, one panel-specific comment and an example of how your team identifies the supplier’s returned version.

Give the supplier handoff a proof reference