...

Phone Case Sample Feedback: Replace Vague Notes With Actionable Revisions

Share:

Table of Contents
    Add a header to begin generating the table of contents
    Scroll to Top

    Useful phone case sample feedback does four things. It says what you observed, shows exactly where it is on the sample, states the change you want against an agreed reference, and defines how you’ll check the next sample. A note like “the logo looks off” gives a supplier nothing to measure. “Move the back logo inside the boundary in approved artwork rev B” gives them a clear target.

    A reviewer compares a phone case sample with its artwork proof at a worktable

    The format below is a practical approach we suggest for reviewing custom case samples. It isn’t an industry standard or a required supplier form. Adapt it to the references you and your supplier have actually agreed on.

    Turn a vague note into a checkable revision request

    Start by keeping three things apart: what you saw, what you want changed, and how you’ll know it worked. When reviewers mix these together, they end up with notes like “fix the corner,” and the supplier has to guess. Write each request in this order:

    1. Identify the sample and round. Use the supplier’s sample ID or another label you both recognize, plus the review round (for example, “Round 2”).
    2. Name the governing reference. Point to the approved art file, drawing, or specification, including its revision. If no reference covers the issue, say so and agree on one before asking for a change.
    3. Describe the observation and its location. Name the feature (logo, camera cutout, button cover, lower-edge opening) and where it sits on the case. Describe what you see without jumping ahead to a fix.
    4. State the requested change. Say what the result should be compared with the reference, such as “match the outline in drawing rev C,” not “make it better.”
    5. Define the check. Explain how you’ll confirm the fix on the next proof or physical sample, for example “compare the next proof against the same file” or “inspect the same opening against the drawing.”
    6. Keep it open until the check passes. If the next sample doesn’t meet the check, don’t mark the request resolved. Write down what still doesn’t match and what should change next.
    Flow diagram turning a sample observation into a revision request and checking it on the next proof

    Step 5 matters most. If you can’t describe how you’ll check a request, the request usually isn’t specific enough yet.

    Use different checks for visual and physical issues

    Visual issues and physical issues need different references and different checks. Artwork problems are usually judged against an approved art file, and you can often check them on a digital proof. Fit and openings have to be checked on the physical case against the agreed drawing. The examples below are hypothetical. Replace the bracketed items with your real sample ID, round, and reference.

    Artwork placement or print appearance

    Vague: “The logo looks off. Move it.”

    Actionable: “On sample [ID], round [#], the back-panel logo sits outside the boundary shown in approved artwork [file/revision]. Move it inside that boundary. We’ll check the next proof against the same file.”

    This version only works if the approved file actually defines that boundary. If it doesn’t, the first job is to agree on the intended placement and update the file. Don’t invent a margin or print tolerance in your note. Print appearance works the same way. Tie “the color looks dull” to the approved color or artwork reference, and judge the next proof against that same reference rather than against your memory.

    If your team already reviews artwork in Figma, comments there are pinned to the point or region of the canvas you select. Collaborators can reply, and the comment can be resolved once the feedback has been addressed. This helps you pin down notes on the design file. It doesn’t track what happened on the physical sample, so keep the sample record separate.

    A physical opening or fit-related observation

    Vague: “The port opening is wrong.”

    Actionable: “On sample [ID], round [#], the lower-edge opening does not match the outline in drawing [number/revision]. Revise it to match that outline. We’ll inspect the same opening on the next physical sample against the drawing.”

    Name the specific opening (charging port, speaker grille, camera cutout, side button) instead of saying “the openings.” Test the sample on the exact device model it was built for, not a similar phone in the same family. Leave dimensions and tolerances to the agreed drawing. If the drawing seems wrong, for example the opening matches the drawing but still blocks the port, say that directly. The change then belongs in the drawing first, followed by a new sample.

    Tie feedback to the sample, reference, and revision round

    Every request should stay linked to three things: which sample it came from, which reference governs it, and which round it belongs to. Without those links, a note from Round 1 can get applied to the wrong version, or quietly dropped. The tracking approach below is our practical suggestion, not a verified supplier process.

    Identify the sample and applicable reference

    Record the sample identifier, the governing reference and its revision, and the round label together at the top of each set of notes. Use the supplier’s own sample ID when there is one, so both sides mean the same physical piece. If you aren’t sure which sample you’re holding, or which file revision it was built from, ask your supplier to confirm before you send feedback. Don’t assume.

    Other industries do this formally. The Sellafield Volume Products Supplier Manual requires inspection reports to reference the revision levels of drawings and specifications. It also requires an action plan that assigns an owner and an agreed timescale to each deviation. That manual comes from a very different manufacturing setting and isn’t phone case guidance. It does show why linking a finding to a specific revision makes follow-up dependable.

    Revisions also affect approvals you’ve already given. If a spec change touches a fit-critical feature or an approved appearance, check whether the earlier sample still represents the new version before you rely on it.

    Keep the round and follow-up connected

    Keep each request with the supplier’s response and the returned sample. Then the next round starts from your open list, not a blank page. When the new sample arrives, go back to the same feature and compare it with the result you asked for, using the same reference. A feature that has visibly changed hasn’t necessarily been fixed. Run the check you defined.

    Then give each request a clear status:

    Outcome on next sample What to record
    Check met Resolved, with the round it closed in
    Partly met Open, plus the remaining mismatch
    Not met or new issue Open, plus the next requested change

    Carry the open items into your next set of notes using the same sample ID and reference format. Once every item tied to the approval is resolved, you’ll have a clear record to support moving to the next step.

    FAQs

    What should I do if no drawing or art file covers my concern?

    Agree on a reference before you request the change. Describe the observation and its location, explain the result you want, and ask your supplier to update or confirm the file or drawing. Your check is only as clear as the reference behind it.

    Can I approve artwork from a digital proof instead of a physical sample?

    For appearance, a proof checked against the approved art file can often confirm placement. Fit and openings are different. Those need checking on the physical case, on the exact device model, against the agreed drawing.

    How many issues should I put in one note?

    Give each issue its own numbered request with its own location, change, and check. This lets the supplier respond item by item. It also means one unresolved item stays open without holding the others hostage.

    When is a revision request actually resolved?

    It’s resolved when the next sample meets the check you defined against the same reference. If it only partly matches, keep it open and record what’s still different.

    If you’re preparing notes on a custom case sample with us, send them in this format through our official store. We’ll work through each open item with you round by round.

    CONTACT US