How a job actually runs — every template, every phase
12 seeded templates power every kind of work an Oman audit firm does — from a clean Annual Audit (TPL-AA) to monthly Bookkeeping (TPL-BK) to quarterly VAT filing (TPL-VAT). This manual walks the lifecycle of creating, executing, billing, and closing a job — with a deep dive on each template.
The end-to-end engagement flow — sketch
The 12 seeded templates
Every template ships with: full task structure (5-phase), tickable checklist items with ISA / IFRS / Oman regulatory references, deliverable list, skills required, folder-structure JSON blueprint, and quality criteria. Click any card below to jump into its dedicated walkthrough.
The 8-step workflow (applies to every template)
Every job — Annual Audit or Bookkeeping or VAT — runs the same 8-step lifecycle. The content of the work changes per template; the mechanics don't. Walk these in order:
Template anatomy
What's inside a template — tasks, checklist items, references, folder structure, deliverables. Understand this once and the rest makes sense.
Create the job
From wizard to dashboard — pick template, set FY, allocate team, watch tasks materialise + folder skeleton appear in
storage/jobs/{id}/.Walk the task board
5 phases · 8+ tasks · status lifecycle — Planning → Fieldwork → Reporting → Review → Admin. Drag-drop kanban, filter by phase + assignee + status.
Checklist cascade
The bidirectional sync — first tick auto-promotes task to in_progress; full clear demotes back. ISA / IFRS references on every item.
Files + comments
Polymorphic attachments + threaded discussions — 25 MB cap, MIME validation, internal-vs-client visibility flag, comment edit/delete by author only.
Status lifecycle
not_started → in_progress → completed → archived — validated transitions, post-commit hooks (notifications, auto-invoice, EOSB-style triggers).
Billing the job
Auto-draft invoice on completion — inherits client + fee + T&Cs, partner approves + sends, advance balance auto-applies, M11 state machine drives.
Close + archive
7-year retention pack — workpapers + AJEs + FS + report + audit trail → SHA-256 ZIP → off-site sync.
Job number is auto-issued: JOB{YYYY}/{NNNN}. Folder under storage/jobs/{id}/ is auto-materialised at create time using template tokens ({CLIENT}, {FY}, {PROJECT}). Don't rename — the system tracks state by id, the path is just for human navigation.
If you're new to AuditPro: read Template anatomy → Create the job → TPL-AA deep dive. That trio gives you the mental model for everything else.