1.2 — What needs approval

Three types of records in blink i go through an approval workflow before they are confirmed:

Each of these uses its own configurable workflow — you can have a two-step booking approval and a single-step expense approval running independently. Workflows are set up by workspace administrators under Settings › Approval Workflows.

1.3 — Approval request states

Every approval request (the object moving through the workflow) has a state that describes where it is in the process:

2.1 — The approval queue

Approvals › My Approvals lists every request currently waiting for your decision. The list is split by module — Bookings, Expenses, Purchase Orders — with a count badge on each tab showing how many are pending.

2.2 — Reviewing a request

Click Review on any row to open the full record. What you see depends on the record type:

• Booking — customer details, property (plot/unit, project), agreed sale value, payment plan, KYC completion status, uploaded documents, and the submitter's notes. See the Bookings guide for field definitions.
• Expense — vendor, project, category, line items, total amount, payment mode, and any supporting attachments. See the Procurement guide.
• Purchase Order — vendor, project, SKUs, quantities, unit prices, total, expected delivery date, and expense category. See the Procurement guide.

The Approval History panel at the bottom of the detail shows every previous step — who approved it, when, and any comments they left. Review this before acting if the request has passed through earlier steps.

2.3 — Approve, return for correction, reject

From the review detail (or via the inline actions on the queue list), three decisions are available:

2.4 — Bulk approval

When multiple low-value or routine requests are pending (e.g. a batch of small expenses that all look correct), you can approve several at once without opening each one:

• On the My Approvals queue, check the boxes on the left of the rows you want to approve.
• A selection bar appears at the bottom of the screen showing the count selected and an Approve Selected button.
• Click Approve Selected and confirm. All selected requests are approved in one action.
• Bulk approval is only available for the final approval step — requests that still have further steps after your approval are not eligible for bulk action.

3.1 — How to submit

Each module has its own submission trigger:

If the pre-submit check fails, blink i highlights the missing fields in red and does not submit. Fix the gaps and try again. On successful submission:

• The record's status moves to Pending.
• The first approver in the workflow is notified by in-app notification and email.
• You can no longer edit the record while it is pending — editing is locked until the approver acts.

3.2 — Tracking your submission

After submitting, open the record to see the Approval Progress panel. It shows:

• Each step in the workflow, in order.
• Which step is currently active (highlighted with a spinner).
• Completed steps showing the approver's name, their decision, and the timestamp.
• The approver assigned to the current step — so you know who to follow up with if the request is taking too long.

You can also see all your pending and recently decided submissions under Approvals › My Submissions.

3.3 — Handling a return (On Hold)

If an approver returns your request, you will receive a notification with their comment. The record moves to On Hold and becomes editable again. To fix and resubmit:

1. Read the approver's comment — it appears in the Approval History panel on the record. Understand exactly what needs to change before editing.
2. Make the corrections — edit the record. For bookings, this might mean uploading a missing document. For expenses or POs, it might mean correcting a line item amount or category.
3. Resubmit — click Submit for Approval again. The workflow restarts from step 1, even if the previous return came from step 2. All approvers are notified fresh.

4.2 — Creating a workflow

Navigate to Settings › Approval Workflows and click + New Workflow. Fill in the workflow header:

Click Save to create the workflow shell. Then add steps (see 4.3) and conditions (see 4.4) before activating.

4.3 — Steps & approvers

A workflow is made up of one or more sequential steps. Each step has one or more approvers — all must approve before the request advances to the next step.

On the workflow detail, click + Add Step to add a step. Configure each step:

4.4 — Conditions & value thresholds

Conditions let a workflow apply only to certain records — by value, by project, or by category — so routine low-value items can bypass steps that only matter for larger amounts.

On any step, click Add Condition to scope when that step fires:

A step whose conditions are not met is skipped automatically — the request advances to the next step that does match, or is approved immediately if no further steps apply.

4.5 — Escalation

Escalation automatically reassigns or chases a request if an approver has not acted within a set time. Configure it on each step:

5.1 — Booking approvals

When reviewing a booking approval request, verify the following before approving:

If everything checks out, click Approve. The booking is confirmed, the plot is marked sold, and the payment schedule activates.

5.2 — Expense approvals

When reviewing an expense, check:

• Project and category are correct — the expense will post against this project's budget item. A wrong category distorts budget reporting.
• Line items are reasonable — quantities, units, and unit prices look right for the type of spend.
• Total is within the submitter's authorisation limit — your organisation's policy may require higher approval above certain amounts.
• Supporting attachment is present — invoice, receipt, or bill attached and matches the claimed amount.
• Vendor is correct — not a personal account or an unrecognised payee.

5.3 — Purchase Order approvals

When reviewing a PO, check:

• Vendor is approved — the vendor should be in the system and an authorised supplier for the goods being ordered.
• SKUs and quantities are reasonable — the items match the project's current needs. Verify against the project's Development / Budget if in doubt.
• Unit prices are market-rate — flag significant deviations from the last purchase price for the same SKU.
• Expense category is correct — the auto-created expense will post to this category.
• Expected delivery date is realistic — check it does not conflict with site schedules.

On approval, blink i immediately creates a linked expense and lists the PO under Inward / Outward › Pending POs ready for goods receipt.

6.1 — When notifications are sent

In-app notifications appear as a badge on the bell icon in the top-right corner of blink i. Click the bell to see all recent notifications. Email notifications go to the address associated with your blink i account.