Creative review
Point at the problem. Then prove it is fixed.
Keep every version of a creative item under one proof, pin feedback to the image and record the decision.
Version 2Feedback that points at something.
A pin says where. The comment says what to change. Choose a pin on the sample to read its note, including one already resolved.
The proof
One proof. Every version. A clear decision.
Version one came back with changes requested. Version two sits under the same proof, waiting for a decision.
One proof, every version
A revision lands under the same proof, so nobody hunts for the current file.
Pins on the image
Numbered annotations point at the exact spot the comment is about.
Open and resolved, kept apart
Resolved notes stay on record without crowding the open ones.
Upload new versionA decision on the version
Approve or Request Changes, recorded against the file that was reviewed.
A clear status
Draft, In Review, Approved or Changes Requested, at a glance.
Linked to the work
Connect the proof to its project or task, then update delivery when it closes.
Review each file the way it works.
Images get pins, PDFs open in an embedded view and other media travel as file links. Video with timecoded comments needs a specialist tool, and the brief, versions and decisions stay in Flowboard around it.
- Image
Pins on the image
Place numbered annotations on the area that needs to change.
- PDF
An embedded document view
Read the PDF inside the proof alongside its versions and decisions.
- Other media
Shared as a file link
Keep the file with its proof and review history.
- Video
A specialist review tool
Timecoded comments and frame comparison belong in a dedicated video tool.
Clear about who reviews where.
What proofing does
- Keeps every version of a creative item under one proof.
- Pins numbered comments to image files.
- Records Approve or Request Changes on the version reviewed.
- Keeps open and resolved annotations apart.
What it does not do
- Appear in the client portal. Share the file on a client-visible task for client feedback.
- Annotate video frame by frame.
- Mark up a PDF. It opens in an embedded view.
- Stand in for contract acceptance. Define what a review decision means in the agreement.
Name one person who consolidates feedback and one who decides, before the second reviewer joins. See how clients give feedback ↗
The details.
Everything above, in depth. Open what you need.
Make the proof a stable review object
Create the proof around the creative item being reviewed, with a useful title and description. Connect it to the relevant project or task where appropriate. A new file version should belong to the same recognizable review context when it is a revision of that item, rather than becoming an unrelated upload that reviewers must rediscover.
Each proof keeps its versions and review activity, and team reviewers record an approve or request-changes decision on a version. Those decisions help the producer identify what needs attention. They work best when the team agrees who is reviewing, what the review covers, and whether a new version needs another explicit decision.
Use the right review behavior for the file
Image proofs support visible annotation pins on the image. This is useful for feedback about a layout, an individual element, or a specific area that would be awkward to describe only in prose. Keep the comment actionable: identify the concern and the requested change rather than leaving an unexplained marker.
Review images with annotation pins and PDFs in an embedded document view. Other media can be shared through file links. Use a specialist review tool when you need document markup or frame-accurate video comments.
An illustrative design review with a clean outcome
Imagine a studio reviewing a campaign key visual. Version one is ready for internal review. The art director places an image annotation on a low-contrast text area and records a specific change request. The designer uploads version two under the same proof so the team can identify which file addresses the feedback.
The reviewer checks the current version and records the decision. Once approved, the producer updates the delivery task and prepares the client handoff. Use the proofing workspace for your team's annotations and decisions. Proofs are not shown in the client portal, so share the file with the client on a client-visible task and collect their response in its comments.
| Review step | Useful record | Common ambiguity to remove |
|---|---|---|
| Submit a version | Named proof and current file | Which creative item is this? |
| Give feedback | Image annotation and clear comment | What needs to change? |
| Revise | New version in the same context | Which file is current? |
| Decide | Approval or requested changes | Can delivery proceed? |
Introduce a review protocol before adding more reviewers
The review tool helps organize feedback, but a simple protocol determines whether that feedback moves the work forward. Agree it at the beginning of the engagement.
Name the review owner
Identify the person who consolidates feedback and the person authorized to decide. Avoid treating every comment as an equal commercial instruction.
Prepare a clear version
Upload the relevant file with a meaningful title and description. Explain what is ready for review and what is still intentionally unfinished.
Request actionable feedback
Use image pins where supported and write comments that specify the issue. Separate mandatory changes from optional ideas when the distinction matters.
Close the review deliberately
Upload revisions as new versions, inspect the current file, and record the decision. Update the associated task so the delivery plan reflects the outcome.
Know when a specialist review tool belongs in the workflow
Use a specialist video-review tool for timecoded comments, frame comparison, and playback controls. Keep the brief, delivery plan, file versions, and review decisions in Flowboard so the team can follow the project around that specialist workflow.
Likewise, a proof approval is not automatically acceptance of every contractual milestone. Define the meaning of the review in the project agreement. An internal art-direction decision, a client task approval, and a signed commercial proposal have different purposes. Keep those distinctions clear when a decision affects scope or payment.
Questions
Before the first round of feedback.
Can reviewers point to a specific part of an image?
Yes. The image proof canvas supports annotation pins on image files. Pair the pin with a clear comment so the designer knows what to change. A marker without an explanation can identify a location without resolving the actual review question.
Does the same annotation experience work on video?
No. Use a specialist video-review tool for timecoded feedback and playback controls. Flowboard provides image annotation pins, embedded PDF viewing, and file links for other media.
Can a proof contain more than one version?
The proof model tracks file versions and related review activity. Use a new version for a revision of the same item so the team can identify the current file and understand the review context. Avoid creating unrelated proof records for every small revision.
Can clients use every proofing action through the portal?
No. Proofs are for your team: image pins and approve or request-changes decisions happen in the internal proofing workspace, which clients do not see. For client review, share the file on a client-visible task, where the client can reply in the comments, and record their decision there.
How should approval affect the project plan?
Record the review outcome, then update the delivery task and next step. If approval also confirms a commercial milestone, follow the acceptance process agreed with the client.