AWRA Help Center
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
What is new, release notes, changelog history, status updates, and product change tracking.
Human Resources — employee records, leave, attendance and time, payroll and payslips, and employee self-service.
Delivery management — projects and tasks, Kanban board and my tasks, planning and Gantt, agile sprints, time and budget tracking, and flexibility (labels, checklists, templates).
Support desk — tickets, department queues, categories and assignment, SLA timers and escalation, the public intake portal, and staff self-service (My Tickets).
Android, iOS, mobile workflows, barcode scanning, scanner bridge, and field operations.
APIs, webhooks, sync patterns, QuickBooks, connectors, and external system implementation.
Trust, security, privacy, compliance, uptime, access controls, and procurement review resources.
Pricing, plans, subscriptions, ROI estimates, billing conversations, and commercial review.
AWRA Academy courses, lessons, assessments, and verifiable certificates — learn the platform module by module.
Implementation, onboarding, migration, demos, training, rollout, and customer success guidance.
Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
Buying — requisitions and approvals, RFQs and quotation comparison, purchase orders and receiving, three-way matching, supplier prequalification, and landed cost.
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Money — chart of accounts and journals, expenses, budgets and controls, vendor payments, the payments register, aging reports, and period close.
Asset register — tagging and custody, assignment and location history, condition and verification, maintenance, depreciation schedules, and disposal.
The supply base — supplier records and documents, performance scoring, the vendor portal and collaboration, and vendor-side self-service.
Seeing the business — the report catalog, BI Studio and custom report builder, saved filters and scheduled reports, dashboards, and predictive insights.
Making the system act — approval workflows, rules and triggers, the unified action queue, exception handling, alerts and notifications, and scheduled jobs.
Core product documentation, module explainers, operating concepts, and platform overviews.
Browse Help Sections
Each article is backed by approved public knowledge and links back to the authoritative AWRA resource for deeper context. Tap a section to expand it.
Delivery management — projects and tasks, Kanban board and my tasks, planning and Gantt, agile sprints, time and budget tracking, and flexibility (labels, checklists, templates).
AWRA Blog
Rwanda holds public and donor-funded spending to a high bar, and the audit trail is where that bar is met or missed. What procurement software must enforce — competition, approvals, three-way matching, grant-tagged spend — and where the honest limits are.
AWRA Blog
Addis is one of Africa's great hubs for NGOs and development agencies — and donor-funded procurement is judged twice: by your finance team, and by an auditor who was not in the room. The controls that make both pass, across currencies.
AWRA Blog
Donor-funded procurement lives or dies on the audit trail. What procurement software must enforce for a Kampala head office running field projects — competition, approval chains, three-way matching, grant-tagged spend — and where the honest limits are.
AWRA Blog
An overrun is not an event, it is a trend that becomes an event. The reporting rhythm and the three numbers — budget, committed, actual — that let you see one forming in time to do something.
AWRA Blog
Most organizations can tell you what a project was supposed to cost and what it eventually cost. The expensive gap is the middle — the months where an overrun was forming and nobody could see it yet.
AWRA Blog
Forty-one tasks in a flat list gets abandoned by week three. Nine deliverables with steps beneath them does not. The structure that makes a plan readable — and the one number on the project page you should not take at face value.
AWRA Blog
Agile metrics are genuinely useful to a small number of teams and pure theatre for everyone else. How to tell which you are, what the burndown actually computes, and the one setting that makes it read zero forever.
AWRA Blog
The largest cost category on most projects has the weakest evidence behind it. Valuing work instead of processing a claim, comparing issued materials against valued progress, and mirroring retention on both sides of the chain.
AWRA Blog
Tasks here can have subtasks, and subtasks can have their own. The tree is real, it survives cloning, and it orders work. Rollup arithmetic — hours, points and cost summing from children to parent — is the natural next layer, and one we can build for you.
AWRA Blog
Tickets received and closed are the two most reported and least useful numbers in support. The four measures that show whether a desk is coping, why reopens beat resolutions, and how to read satisfaction honestly.
AWRA Blog
Victoria caps what a builder may hold at each stage as a percentage of the contract price, with the stages defined by what is physically built. Our projects module holds the stages in order and holds no contract price at all.
AWRA Blog
Manufacturers barcode the tinned tomatoes. Nobody barcodes the rice you repack, the uniform you assemble, or the part whose label rubbed off — and those are usually the high-margin, high-shrinkage half of the catalogue. Trade numbers versus internal codes, and what to check before you print five hundred labels.
AWRA Blog
A budget is a department, a category and a window. Purchase-order spend against it is department-scoped; expense spend is not, because an expense carries a project instead. One column of the report is departmental and the one beside it is organisation-wide — and it says so.
AWRA Blog
Six activities are behind and everybody has a reason. Two of them probably have three weeks of float and nobody in the room knows which two. The arithmetic that answers it, and the five things it does not account for — including the undated task that silently counts as one day.
AWRA Blog
Japan makes the main contractor keep a register of everyone working below it, on site — and makes each tier tell the tier above who it engaged. The party who keeps the register is not the party who fills it in, and our supplier portal is already the right channel.
AWRA Blog
A British contractor files monthly, naming each subcontractor, what they were paid, and how much of it was materials. That third figure is defined as what the contractor is satisfied the subcontractor's own materials cost — not a number on any document you hold.
AWRA Blog
The second identical warehouse is planned from memory, the third from the second, badly, by whoever still has the file — and every retyping loses the task that was added because something went wrong. What a template carries, and the hour of dating you must do before trusting the programme.
AWRA Blog
A weekly scaffold check runs for four months and then stops, because recurrence happens on completion rather than on a date. Nothing is overdue and nothing is flagged — the series is absent rather than late. Why that is the right default for a site, and what it costs you.
AWRA Blog
Rollouts stall on small ambiguous decisions nobody has authority to settle. What the owner actually decides, the twelve to fifteen days it costs, why it should not be the IT person, and the six things to hand them in writing.
AWRA Blog
A count plan asks how often you intend to count, requires an answer and stores it. Until 1 October 2026 nothing happened on that rhythm — no session was ever raised, and a plan reading "monthly" looked exactly like a control that was running. Now a daily job opens the count when it is due and tells the assignee. What the inert field taught us, and what is still left to build.
AWRA Blog
The timeline here draws your current dates against a snapshot of the dates you agreed to, and shows the variance per task. It is one of the better-built things in this product — and it has exactly one snapshot, with no record of when it was taken.
AWRA Blog
A project can be attached to any other record in the system — the machine being overhauled, the building being fitted out, the contract it delivers. The attachment point exists, the way to read it exists, and nothing has ever filled it in.
AWRA Blog
Contractors buy the half that argues for money and improvise the half that spends it. A worked look at where a thin margin actually goes — a variation claim lost to a notice period, and plant hired in that the business already owned.
AWRA Blog
Peru sets a monthly valuation cycle for public works with the deadlines written into it — present within the first three days of the following month, supervisor reports within five, entity pays by month end. The binding deadline is not the payment one; it is how fast you can close a month.
Page 2 of 4 · 86 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
