Get an internal check
before sending work to your client.
Work is ready to go to the client, but you want a teammate to look first, without the client seeing the check or it counting as their approval.
By the end, you’ll have asked a teammate for an internal check, seen them approve one asset and send another back with a reason, and prepared the client review for the approved one.
Before you start
- A project deliverable with an asset attached.
- To request a check: you can edit the project, or the deliverable is assigned to you.
- A teammate who can see the project and the asset, to be the reviewer.
Watch the walkthrough
Get an internal check before sending work to your client.
Alex Morgan produces the Harbor and Pine winter launch. Open the campaign key visual.
It could go to the client right now: Prepare client review is right here. But Alex wants a teammate to look first. An internal check is optional, and this is where you ask for one.
Under Internal review, click Request internal review.
Pick the reviewer. Any teammate who can see this project and the asset can check it. Here, it's Jordan Reyes.
Set a due date, if you need one.
The check covers the version attached right now. It doesn't open a client review, and it doesn't use a client revision round.
Click Request and notify reviewer.
The panel now says Awaiting internal review, with Jordan's name.
Jordan gets a notification: an internal check is assigned on this project.
Open the project. Needs attention lists every check waiting for Jordan. The front label is there too: Alex asked for that one earlier.
Start with the key visual. Click Open check.
Jordan has two choices: Request changes, or Approve internal check.
The key visual is good. Click Approve internal check.
The dialog says it plainly: this records the studio's check. Client approval remains a separate step. Confirm.
The key visual is ready for client review. Sending it is up to someone whose role includes client reviews, and Jordan's doesn't.
Now the front label. Click Open check.
This one needs work. Click Request changes, and say what has to change. A reason is required.
It stays internal: the client isn't notified, and their revision allowance doesn't change. Click Request changes and notify owner.
The front label goes back to Alex, with Jordan's reason.
Back with Alex. The notifications show the approval: the key visual is ready for client review. Open the project.
Needs attention shows the change request on the front label, with Jordan's reason. Click View feedback.
The panel keeps the request next to the version Jordan checked. Alex fixes the label and asks for another check.
The Reviews tab lists internal checks on their own, apart from client reviews. An internal approval never counts as your client's.
Open the check on the key visual.
It's internally approved and ready for client review. Click Prepare client review.
The key visual is selected. Sending it is covered in the guide on sending work to your client for approval.
In short: request an internal review on a deliverable, and let your teammate approve it or ask for changes. Then prepare the client review. Your client never sees the internal check.
Search across all videos and guides.
A teammate’s check first, the client’s answer after.
Alex Morgan produces the “Harbor & Pine winter launch” project. Before the client sees anything, Alex asks Jordan Reyes, a teammate, to check the campaign key visual. Jordan approves it, and sends the front label back with a change.
An internal check is optional, and it’s hidden from the client. Its decision records your studio’s check; it’s never your client’s approval, and the two are kept apart everywhere. Sign in to YetOnePro and open a project to follow along.
- 01
Open the deliverable
On the project’s Overview, open the deliverable, here the campaign key visual. It could go to the client right now: Prepare client review is right there. The internal check is the step you can add before it.
- 02
Request an internal review
Under Internal review, marked “Hidden from the client.”, click Request internal review. You can request one if you can edit the project, or if the deliverable is assigned to you.
Pick the reviewer: any teammate who can see this project and the asset, here Jordan Reyes. Set a due date if you need one, then click Request & notify reviewer. The deliverable now shows Awaiting internal review with the reviewer’s name.
The check covers the version attached right now. It doesn’t open a client review, and it doesn’t use a client revision round. - 03
The reviewer is notified
Jordan gets a notification that an internal check is assigned on this project. In the project, Needs attention lists every check waiting for them, each with Open check.
- 04
Approve the check
The reviewer has two choices: Request changes, or Approve internal check. For the key visual, Jordan clicks Approve internal check. The confirmation says it plainly: this records your studio check, and client approval remains a separate step.
The key visual is now ready for client review. Sending it needs a role that includes client reviews, Owner or Project Manager by default; Jordan’s role doesn’t.
- 05
Request changes with a reason
For the front label, Jordan clicks Request changes and says what has to change; a reason is required. Then Request changes & notify owner.
It stays internal: the client isn’t notified, and their revision allowance doesn’t change. The front label goes back to Alex with Jordan’s reason.
- 06
Needs attention and View feedback
Back with Alex, the notifications show the approval: the key visual is ready for client review.
The change request is on the project’s Overview: under Needs attention, the front label shows Jordan’s request. Click View feedback to see it next to the version Jordan checked. Fix the label, then ask for another check.
- 07
Reviews tab: Internal checks
The project’s Reviews tab lists Internal checks on their own, approved or with changes requested and the reason, apart from client reviews. An internal approval never counts as your client’s.
- 08
Prepare the client review
Open the check on the key visual. It’s internally approved and ready for client review. Click Prepare client review: the key visual is selected under Files to include.
Sending it is covered in Send work to your client for approval. If your client later answers by email or on a call, see Record an approval your client gave by email.
In short: request an internal review on a deliverable, and let your teammate approve it or ask for changes. Then prepare the client review. Your client never sees the internal check. To pass a deliverable on instead, see Hand a deliverable over to a teammate; for notes only your team reads, Keep internal comments separate from client feedback.
Check the result
- You requested an internal review on the deliverable, with a reviewer and a due date if needed.
- The reviewer approved the check, or requested changes with a reason.
- You found a change request under Needs attention, with View feedback, and on the Reviews tab.
- For approved work, you prepared the client review as a separate step.
If it didn’t work
Does an internal approval count as the client’s approval?
No. It records your studio’s check. Client approval remains a separate step, and the Reviews tab lists internal checks apart from client reviews.
Does my client see the check or the reason for changes?
No. The check is hidden from the client. Requesting changes doesn’t notify them and doesn’t use their revision allowance.
Which version does the check cover?
The version attached when you request it. After a fix, request another check.
The reviewer approved, but they can’t send the work to the client.
Sending a client review needs a role that includes client reviews (Owner or Project Manager by default). Someone with that role prepares and sends it.
Where do I see that my teammate requested changes?
On the project’s Overview under Needs attention, where View feedback shows the reason next to the version they checked, and on the Reviews tab under Internal checks.