Sign inNothing is filed without sign-off
Jobs move to In review on the board, the named reviewer approves or returns them with per-task notes, and only approved work reaches Ready to file. Every decision is logged on the job it explains.
Oblix's reviews-and-compliance workflow is a built-in sign-off step for accountancy jobs: a job moves to "In review", only the named reviewer can act, and they either approve it or return it for amendments with per-task and overall notes. Approval moves the job to "Ready to file" rather than closing it, so nothing reaches Companies House or HMRC without a reviewer having signed it off. Every decision is written to an audit trail and the assignee is notified in-app and by email.
- Forces every job through a reviewer sign-off before it can reach Ready to file
- Blocks a job from entering In review unless a reviewer is named
- Lets the reviewer approve or return work with per-task and overall notes
- Notifies the person who did the work, in-app and by email, of the decision
- Records each review decision and status change as audit evidence on the job
Work gets filed that you never actually checked
As the principal, your name is on the file. But review happens over someone's shoulder, in a reply to an email, or not at all when the deadline is tight. There is no record of who looked at a set of accounts, what they queried, or whether the queries were ever cleared. When a client or a regulator asks how a return was checked, the answer lives in someone's memory. You want a review step that is part of the work, not a favour someone does at the end and immediately forgets.
A review step the work cannot skip
In Oblix a job cannot reach Ready to file until the assigned reviewer has signed it off. A job can only enter In review when a reviewer is named, the reviewer is not the person who did the work, and approval moves the job to Ready to file rather than straight to Complete, so there is still a deliberate filing step. The reviewer's queries are attached task by task, the person who did the work is told what to fix, and every decision is recorded against the job. The evidence sits next to the work it explains, not in a separate spreadsheet.
How the review workflow works
The whole loop lives on the job and the Kanban board, so there is nothing extra to learn.
Move to In review
When work is done, the job moves into the In review column. Oblix blocks the move unless a reviewer is named, so a job can never sit waiting for a review nobody owns.
Reviewer opens the review panel
Only the assigned reviewer can act on the job. They see each task with an OK or amendment-needed flag, a note box per task, and a message box for the person who did the work.
Approve or return
Approve moves the job to Ready to file — signed off but still to be submitted. Return for amendments sends it back to the assignee and needs at least one task flagged, so the reasons are always specific.
The assignee is told what happened
Either way the person who did the work is notified in-app and by email, carrying the reviewer's message and the per-task notes, so nothing stalls silently waiting for someone to notice.
Every decision is logged
Each review writes an audit entry recording who reviewed, the decision, and how many amendments were raised, plus a status-change record on the job's history.
Compliance evidence kept next to the work
Review notes, status changes and sign-off decisions are stored on the job itself, not in a separate tracker. Sensitive actions across Oblix are written to an audit trail that records who did what, to what, and when. Reviewers also get their own queue of jobs waiting on them, and managers can see the consolidated view, so the principal can answer how a piece of work was checked without reconstructing it from memory or email.
What it gives the practice.
A job cannot enter In review without a named reviewer, and approval moves it to Ready to file rather than closing it
Nothing reaches Companies House or HMRC without a reviewer having signed it off first
Per-task OK or amendment-needed flags with notes, plus an overall message to the assignee
Queries are specific and traceable, not a vague 'have another look'
The reviewer can approve or return for amendments, and a return requires at least one task flagged
Work only comes back with concrete reasons, so it gets fixed once
Every review decision writes an audit entry and a status-change record on the job
You can show how any piece of work was checked, and by whom, on demand
The assignee is notified in-app and by email on approve or return
Jobs don't stall silently waiting for someone to spot the outcome
Questions practices ask
Can a job be filed without being reviewed?
No. A job cannot reach Ready to file until the assigned reviewer has approved it, and it cannot even enter In review without a reviewer named. Approval moves the job to Ready to file rather than straight to Complete, so there is always a deliberate sign-off before anything is submitted.
Can someone review their own work?
No. Only the job's assigned reviewer can act on a review, and the person who did the work is excluded from the reviewer picker, so they cannot sign off their own job. This keeps a genuine second pair of eyes on every piece of work before it is filed.
What does the reviewer actually see when they open a job?
The reviewer sees each task on the job with an OK or amendment-needed flag and a note box, plus a message box for the person who did the work. They then either approve the job, which moves it to Ready to file, or return it for amendments, which requires at least one task to be flagged. The assignee is notified of the decision in-app and by email with the reviewer's notes.
Is there a record of who reviewed what?
Yes. Each review writes an audit entry capturing the reviewer, the decision and the number of amendments raised, and the status change is recorded on the job's own history. That evidence is kept on the job it relates to, so you can show how a piece of work was checked without rebuilding it from email or a spreadsheet.
What happens when a reviewer returns a job for amendments?
The job moves to Amendments needed and goes back to the person who did the work, who is notified in-app and by email with the reviewer's per-task notes and overall message. A return requires at least one task to be flagged, so the assignee always knows exactly what to fix. Once corrected, the job can go back into review.
Give the practice one place to see the work.
Bring every client, job, deadline, document, chargeable hour and client conversation into a single operating view for the whole firm.