Appearance
Revisions & Feedback
The Revisions tab manages deliverable submissions, client feedback, and scope change requests for a project. It is your record of what was delivered, what feedback came back, and how scope was managed throughout the project.
Revision Policy
Every project has a revision policy set during proposal creation:
| Policy | What it means |
|---|---|
| Fixed rounds | A specific number of revision rounds (e.g. 2 rounds) |
| Unlimited | No cap on revisions |
| By scope | Revisions are defined case-by-case in the project scope |
The policy is shown at the top of the Revisions tab as a reference. Omako tracks revision rounds but does not block you from logging feedback when rounds are exhausted — it gives you the data you need for a billing conversation if one arises.
Submitting a Deliverable
When you send work to the client, click Submit deliverable on the Revisions tab.
Fill in:
| Field | Notes |
|---|---|
| Title | A clear label for this submission (e.g. Homepage design v2) |
| Description | Optional context for the client |
| Files / links | One or more links — Figma, Google Drive, Loom, staging URL, etc. |
| Linked milestone | Optionally tie this submission to a project milestone |
Getting Client Approval via Link
Every submission has a unique client approval link. After submitting, click the copy link icon next to the submission and send the link to your client — by email, WhatsApp, or any channel you normally use.
When the client opens the link:
- They see the submission title, description, and file links
- They write an optional note
- They click Approve or Request Changes
No login required. Their response is recorded on the submission and the round count updates automatically.
TIP
The approval link never expires. You can re-share it at any time if the client loses track of it.
Logging Client Feedback
When a client sends feedback through any external channel — email, WhatsApp, a call, or a Figma comment — log it in Omako so it is part of the project record.
Click Log feedback and fill in:
| Field | Notes |
|---|---|
| Source | Where the feedback came from (Email, WhatsApp, Call, etc.) |
| Content | Paste or summarise the client's feedback |
| Date received | When you received it (can be backdated) |
| Linked milestone | Optionally tie the feedback to a specific milestone |
Logging feedback does not consume a revision round. Rounds increment only when a client requests changes on a deliverable submission.
Scope Creep Detection
Omako scans feedback text against a keyword list you configure in Settings → Workspace → SCR Keywords. When a match is found, an alert appears on the Revisions tab.
Reading an SCR Alert
Each alert shows:
- The feedback text that triggered it
- The matched keywords
- A short excerpt from the feedback around the match
Acting on an Alert
You have two options:
- Dismiss — the request is within scope or you've decided to absorb it. The alert is marked as reviewed.
- Draft SCR — opens the Scope Change Request editor, pre-linked to this detection, so you can turn the alert into a formal request to the client.
INFO
Even dismissed alerts are saved in the project record. The history is always available if a billing conversation arises later.
Scope Change Requests (SCR)
A Scope Change Request is a formal, signed-off record of agreed scope changes. It is separate from the detection alert — detection is automatic, the formal SCR is always initiated by you.
Drafting an SCR
Click Draft SCR from a detection alert, or click New SCR at the top of the Revisions tab. Fill in:
| Field | Notes |
|---|---|
| Title | Short description of the change |
| Description | Full explanation of what is changing and why |
| Budget impact | None / Increase / Decrease |
| Amount | In ₹, if there is a budget change |
| Billing option | Add to next invoice, or raise a separate SCR invoice |
| Timeline impact | None, or the number of days being added |
Sending to the Client
When you're ready, click Send SCR. This generates a unique client link (similar to the deliverable approval link). Share the link with your client — they can review the impact summary and click Accept or Decline with an optional note. No login required.
After the Client Responds
| Response | What happens |
|---|---|
| Accepted | The SCR is locked as an accepted record. If it adds time, also raise a Timeline Amendment (see Delays & Amendments). |
| Declined | The original scope stands. The rejection is logged with the client's note. |
You can also Cancel a drafted or sent SCR at any time before the client responds.