Civora
Guide contents

The whole guide on one page. Print it, or choose “Save as PDF” in the print window, to give new staff a handbook.

Civora: the guide

Setting up a new organisation

  1. Describe the organisation (Administrator)

    • Fill in the organisation profile: name, PBO registration number, currency, first month of the financial year.
    • Add the locations you work in: counties, sub-counties, sites.
  2. Set up your departments (Administrator)

    • Build your structure under Administration → Departments, with a lead for each.
    • Link each department to the workspace it runs (Programmes, Finance & Accounting, Grants & Funding, Human Resources, MEL, Procurement & Logistics, Executive Office & Governance).
  3. Bring your people in (HR officer)

  4. Set the money rules (Finance manager)

  5. Record donors and grants (Grants lead)

  6. Set up projects and budgets (Programme managers with finance)

    • Create each project, link its grants and team.
    • Add budget lines by grant, project and category.
    • Plan the activities.
  7. Prepare monitoring and field reporting (M&E officer)

  8. Set HR, procurement and governance rules (Each department lead)

  9. Go live (Administrator)

    • If you tried Civora with the demo organisation, remove it before real data goes in.
    • Check the Administration overview: its set-up checklist shows what is left.
    • Send everyone their sign-in details and this Guide; ask field staff to add Civora to their phone's home screen.

Department guide

Programmes

Delivery on the ground: projects, activities, field reports, participants and implementing partners.

Who uses it: Programme managers and officers, field staff, and anyone following delivery

What it is for

Programmes is where the work the organisation exists for is planned and evidenced. A project is funded by one or more grants, has a team, locations and a budget, and is delivered through activities that someone owns and moves from planned to completed.

Field staff send field reports from their phones, even without network; supervisors review them, and M&E validates the figures that count towards the project's indicators. People served are registered once in the participants register, and local organisations delivering part of a project are managed as implementing partners with their own sub-grant.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    Active projects, how many activities are done, field evidence this month, people reached this quarter, and what needs attention.

  • ProjectsDelivery

    Every project with its lead, grants and delivery. Open one for its grants, budget, results framework, team, partners, participants and requests.

  • ActivitiesDelivery

    The workplan: filter by mine, overdue, blocked or project. Blocked activities ask for support from the project lead.

  • Field reportsDelivery

    Reports from the field: yours, those waiting for your review, those waiting for M&E validation.

  • ParticipantsParticipants & partners

    The register of people served, with consent, duplicate checks, project enrolment and attendance by session.

  • Implementing partnersParticipants & partners

    Implementing partners: capacity assessments, sub-grant agreements, their reports and disbursements.

Setting it up

1Create your first project

Programme manager

  1. Open Programmes → Projects and choose New project.
  2. Give it a name, dates, sector and locations, choose the lead, and tick the grants that fund it.
  3. Add the team: everyone on the team (and only them, for programme managers and field officers) sees the project.
  4. Ask finance for budget lines on the project, or add them yourself from the project if you manage budgets.

2Plan the activities

  1. From the project, choose Add activity.
  2. Set the owner, due date, location and the budget line it will spend from.
  3. Owners update progress themselves; a blocked activity asks the project lead for help.

3Get field reporting ready

  1. Ask M&E for the report templates your field staff will use (MEL → Report templates).
  2. Field staff open Civora on their phones and install it (browser menu → *Add to home screen*), so the report form works offline.

How to

Submit a field report (online or offline)

Field staff

  1. Choose New → Field report, or *Submit field report* on the project or activity.
  2. Pick the project, the activity and the template, then fill in the figures and attach photos or registers.
  3. Without network, the report is saved on the phone and sent automatically when the connection returns; it is never sent twice.

A supervisor can approve, ask for changes or reject. If changes are asked for, you see the comment on the report and in your attention list.

Review a field report

Supervisors and programme managers

  1. Open Field reports or your Approvals inbox.
  2. Check the figures against the evidence.
  3. Approve, ask for changes with a comment, or reject. Approved reports go to M&E for validation.

Register participants and record attendance

  1. In Participants, register a person once, with their consent; Civora warns you about likely duplicates.
  2. Enrol them in the projects they take part in.
  3. Record a session's attendance by participant code; each project then shows unique people reached by sex, age and disability.

If a person withdraws consent, their personal details are erased and only anonymous counts remain.

Bring in an implementing partner

  1. Add the partner in Implementing partners; it also becomes a contact in Finance.
  2. Record a capacity assessment (governance, finance, procurement, people, MEL, safeguarding). A weak finance or safeguarding score makes the partner high risk.
  3. Sign a sub-grant agreement on a project budget line. Its report schedule is created automatically (monthly for high-risk partners).
  4. Disbursements are paid by Finance as bills on that line.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Programme managers and field officers only see the projects they are on or lead.
  • Field reports count towards indicators only once M&E has validated them.
  • A partner cannot be activated before its capacity assessment, and Finance cannot approve the next tranche while a partner report is overdue or the partner is suspended.
  • Registering a participant needs recorded consent (Data Protection Act, 2019).

How it connects

Questions

Why can't I see a project?
Programme managers and field officers see only the projects they are on. Ask the project lead to add you to the team.
Does the field report form really work offline?
Yes, once Civora has been opened on that phone with a connection. Reports wait on the phone and sync when the network returns.

Last checked against Civora on 30 Oct 2026.

Department guide

Grants & Funding

From funding opportunity to closed grant: pipeline, awards, money in, donor rules, reporting and donor relationships.

Who uses it: Resource mobilisation, grants and finance staff, the executive director

What it is for

Grants & Funding follows the money from the first idea to the last report. Opportunities move through a pipeline (idea, concept note, proposal, submitted, negotiation); when a donor says yes, the same record becomes the grant, so nothing is typed twice.

Each grant carries its payment schedule (tranches), its donor rules (which Civora checks every time money is spent), its reporting deadlines, amendments agreed with the donor and a close-out checklist. The overview turns all of it into a funding outlook: what is secured for this year and the next two, what the pipeline is likely to add, and the gap to your fundraising target.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    The funding outlook, the gap to target, who funds you, money expected and what is due to donors.

  • PipelineFunding

    Opportunities by stage, with value and chance of success; move them forward and record the donor's decision.

  • GrantsFunding

    Every award: what it is worth, received, spent or committed, and the next report. Filter by ending soon, to close out or no budget.

  • DonorsFunding

    Funders and prospects: what they gave, what is in the pipeline, the relationship lead, last contact and next step.

  • Tranches & cashMoney

    Every instalment donors owe, cash expected by month, and what has arrived.

  • BudgetsMoney

    Budget lines by grant, project and category, with submitted, committed, actual and available amounts.

  • Donor rulesCompliance

    The donor rules on each grant and the requests they flagged.

  • AmendmentsCompliance

    No-cost extensions, top-ups and realignments in progress and decided.

  • Reporting calendarReporting

    Every report owed to a donor, month by month, with the report pack to prepare it.

  • Report packsReporting

    The donor report pack for any grant and period.

  • Funding settingsSettings

    Fundraising targets for each year, pipeline stage chances and how donor rules work.

Setting it up

1Set your fundraising targets

Executive director or grants lead

  1. Open Funding settings.
  2. Enter what the organisation needs to raise this year and the next two (usually the approved budget, less unrestricted income).
  3. The overview now shows the gap to each target.

2Record your donors and current grants

  1. Add each donor in Donors with what they fund, their funding cycle, contacts and who looks after the relationship.
  2. Choose New → Grant award for each active grant: amount, currency (with a budget exchange rate if it is not your own currency), dates, reporting frequency, indirect cost rate and co-funding.
  3. On each grant add its payment schedule, its reporting deadlines and its donor rules from the agreement.
  4. Ask finance to add the budget lines (or add them from the grant page).

How to

Track an opportunity to a decision

  1. Choose New → Opportunity: the donor, amount requested, submission deadline and who leads it.
  2. Move it along the pipeline as the work progresses; its chance of success rises with each stage (you can set your own).
  3. When the donor answers, open it and choose The donor said yes (enter the amount, dates and agreement reference) or Not funded (record the donor's reasons for next time).

Set the donor rules on a grant

  1. On the grant, open Donor rules → Add a rule.
  2. Choose the rule: an ineligible cost category, donor approval needed above an amount, budget line flexibility (%), an indirect cost cap (%), or another condition to remember.
  3. From now on every expense and purchase request charged to the grant is checked against it.

A request above a donor's approval threshold can still go ahead: the requester enters the donor's approval reference on the request.

Record money received from a donor

Finance

  1. On the grant's payment schedule, choose Record receipt next to the tranche (or New → Money received in Finance).
  2. Check the amount the bank credited, any bank charges, and the original currency amount if the donor paid in another currency.
  3. Save: the receipt posts to the ledger and the tranche shows as received on the grant.

Organisations not keeping their books in Civora can use Mark received on the tranche instead.

Prepare and submit a donor report

  1. Open the Reporting calendar and choose Prepare next to the report.
  2. The report pack shows the award, budget against actual by line and project, results against targets with variance explanations, delivery and evidence for the period.
  3. Print it or export the transactions; when it has gone to the donor, mark the deadline submitted on the grant. The pack is frozen exactly as sent.

Agree an extension or top-up

  1. On the grant, open Amendments → Prepare an amendment: the kind, the new end date or the change to the award, and why.
  2. Record it as sent to the donor; it appears under Amendments and on the overview until the donor answers.
  3. When the donor approves, choose Donor approved: the grant's end date or award changes, and the previous values stay on record.

Keep the donor relationship warm

  1. On the donor's page, choose Log a contact: the meeting, call or visit, and the next step with a date and who does it.
  2. Next steps due within a week appear on the overview and on Donors; mark them done when finished.

Close a grant

  1. From 90 days before the end date, the grant shows a Close-out checklist: final reports, audit, assets, unspent balance, open orders and advances, staff, records.
  2. Tick each item as it is done and set how long records must be kept.
  3. When everything is done and no report is outstanding, choose Close the grant. Nothing more can be charged to it.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Nothing can be charged to an opportunity that has not been awarded, or to a closed grant.
  • Spending after the grant's end date is refused; record an approved no-cost extension first.
  • Ineligible costs and spending above the donor's approval threshold without a donor approval reference are stopped when the request is submitted.
  • Overspending a budget line beyond the donor's flexibility, or overheads above the indirect cap, is shown to every approver of the request.
  • A grant cannot be closed while its checklist is incomplete or a report is still due.
  • Reversing a grant receipt in Finance reopens the tranche.

How it connects

Questions

Our grant is in euros. How are totals added up?
Each grant has a budget exchange rate (your currency per unit of the grant currency). The funding outlook and totals use it; receipts record the actual amount the bank credited.
Why does the overview say "No target"?
Set your fundraising targets under Funding settings.

Last checked against Civora on 30 Oct 2026.

Department guide

Finance & Accounting

Double-entry books with fund accounting: money in, money out, banking, reports, close and tax.

Who uses it: Finance manager and accountants; the executive director for approvals

What it is for

Finance & Accounting keeps the organisation's books. Every ledger line carries its fund (the grant, or none for unrestricted money), project, budget line, department and contact, so one chart of accounts reports per donor without an account per donor.

Everything that moves money elsewhere in Civora lands here: paid expense requests, supplier bills from procurement, payroll, grant receipts, partner disbursements. Budgets read their *actual* from the ledger, so budgets, grants and the books always agree.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    Cash and bank, restricted and unrestricted funds, surplus, money in and out by month, and what needs attention.

  • InvoicesMoney in

    Invoices to customers (for example a consultancy), sent from your own mailbox, with part payments and tax withheld.

  • Money receivedMoney in

    Money received: grant tranches and other income, with bank charges and the original foreign-currency amount.

  • BillsMoney out

    Supplier bills, usually from procurement's purchase orders, matched to goods received and approved by someone other than the preparer.

  • PaymentsMoney out

    Payment runs and direct payments, with remittance advice.

  • Staff advancesMoney out

    Staff advances and their accounting: receipts and cash returned.

  • Payroll approval (HR)Money out

    Payroll prepared by HR waits here for finance approval; the cost posts to each grant by certified time.

  • Bank & M-PesaBanking

    Bank, M-Pesa and cash accounts, transfers, statement import and reconciliation.

  • Funds & grantsAccounting

    Balance of each fund: what each grant has received, spent and has left.

  • JournalsAccounting

    Journal entries, with reversal (nothing is ever deleted).

  • Chart of accountsAccounting

    The chart of accounts.

  • Fixed assetsAccounting

    Fixed asset register: capitalised assets with depreciation, and donor-expensed items kept for custody.

  • ReportsInsight

    Income and expenditure, balance sheet, budget against actual, ageing, trial balance and general ledger.

  • Suppliers & customersInsight

    Suppliers and customers.

  • Period close & taxSettings

    Month-end checklist, lock date, withholding tax schedule for iTax and KRA remittances.

  • Accounting settingsSettings

    Tax status, approval limits and defaults.

Setting it up

1Set up accounting

Finance manager

  1. Choose New → Set up accounting. The wizard starts from a Kenyan NGO chart of accounts and KRA tax codes.
  2. Add your bank, M-Pesa and cash accounts with their opening balances.
  3. Bring forward the balance of each grant fund on the opening date.
  4. Choose whether to post requests that were already paid before Civora.

How to

Pay an approved expense request

  1. Open the request from your attention list.
  2. Choose the account it is paid from and record the payment reference.
  3. The payment posts to the ledger on the request's grant, project and budget line.

Approve and pay supplier bills

  1. Bills from procurement arrive matched to the goods received; check them in Bills.
  2. Someone other than the preparer approves; bills above the executive threshold also need the executive director.
  3. Choose New → Pay bills to pay several at once and send remittance advice.

Reconcile the bank

  1. In Bank & M-Pesa, import the statement CSV (any bank or M-Pesa; map the columns once).
  2. Civora matches lines automatically; match the rest by hand or record what nobody recorded (bank charges, interest).

Close the month

  1. Work through the checklist in Period close & tax.
  2. Set the lock date so nothing can be posted into a closed month; only the executive director can reopen.
  3. Export the withholding tax schedule for iTax and record the KRA remittance.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Nothing is deleted from the ledger: mistakes are reversed with a journal that points to the original.
  • The person who prepares a bill or payroll cannot approve it (maker-checker).
  • A supplier bill is approved only for what was actually received (three-way match with the order and the goods received note).
  • Nothing can be posted on or before the lock date.
  • Approving a request is never treated as paying it: payment is recorded separately.

How it connects

Last checked against Civora on 30 Oct 2026.

Department guide

Human Resources

Employee files, contracts, leave, timesheets, payroll, recruitment, performance, cases and policies.

Who uses it: HR officers; supervisors for leave, timesheets and reviews; finance for payroll approval

What it is for

Human Resources is built so one HR officer can run the organisation's people work. Everyone has an employee file (statutory numbers, pay details, next of kin, grade) and a contract; each salary has a funding split across grant budget lines, with a warning when a grant ends before the contract.

Leave follows the Employment Act, timesheets record hours per grant (certified by the supervisor) and payroll applies PAYE, SHIF, NSSF and the housing levy. HR prepares payroll, finance approves it, and the cost posts to the ledger on each grant by certified time. Recruitment, reviews, disciplinary and grievance cases and policies complete the cycle.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    Headcount, payroll cost, who is away, turnover, and what HR needs to act on (missing file details, contracts and probations ending, funding cliffs).

  • EmployeesPeople

    Everyone's employee file, with a check of what is missing.

  • ContractsPeople

    Contracts and their end dates.

  • Onboarding & exitPeople

    Onboarding and exit checklists that tick themselves from live data.

  • LeaveTime

    Leave requests, balances and the team calendar.

  • TimesheetsTime

    Monthly timesheets of hours per grant, certified by supervisors.

  • PayrollPay

    Monthly payroll: prepare, send for finance approval, pay, remit deductions, release payslips.

  • RecruitmentTalent

    Vacancies from an approved requisition, applicants and safer-recruitment checks, hiring.

  • PerformanceTalent

    Probation and annual reviews.

  • CasesTalent

    Confidential disciplinary and grievance cases.

  • PoliciesTalent

    Policies by version, with acknowledgements.

  • HR settingsSettings

    Working pattern, leave rules, public holidays and statutory payroll rates.

Setting it up

1Set the HR rules

  1. In HR settings, check the working week, leave types and balances, public holidays and statutory rates.

2Add your people

  1. Choose New → Employee. One step creates the person's account, role, HR file, contract and onboarding checklist.
  2. Complete the file (KRA PIN, NSSF, SHA numbers, bank or M-Pesa details) and the salary's funding split across grant budget lines.
  3. Or import many people at once from a spreadsheet in Administration → Import data.

How to

Run monthly payroll

  1. In Payroll, prepare the month: pay is calculated from files, unpaid leave and certified timesheets.
  2. Send it for approval; someone in finance (never the preparer) approves and it posts to the ledger.
  3. Record the salary transfer and the KRA, NSSF and SHA remittances; download the bank or M-Pesa file and schedules.
  4. Release payslips: staff see them in My HR.

Recruit someone

  1. Choose New → Vacancy: the post, salary range and funding are approved by the executive director first.
  2. Move applicants through the pipeline; safer-recruitment checks must be done before any offer.
  3. Hire in one step: the applicant becomes an employee with a file, contract and onboarding.

Handle leave and timesheets

Supervisors

  1. Leave requests and timesheets wait in your Approvals inbox.
  2. Approve leave (the person names their cover); certify timesheets so salaries are charged to the right grants.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Leave balances follow the Employment Act (21 days' annual leave earned monthly, sick leave, maternity and paternity, carry-over).
  • Payroll is approved by finance, never by the person who prepared it.
  • No offer can be made before the safer-recruitment checks are complete.
  • A dismissal is refused unless the Employment Act s.41 steps were followed in the case.
  • Cases are visible only to HR case handlers.

How it connects

Last checked against Civora on 30 Oct 2026.

Department guide

Monitoring, Evaluation & Learning

Results frameworks, indicators and targets, validation, data quality, evaluations, learning and community feedback.

Who uses it: M&E officers; project leads for variance explanations and feedback

What it is for

MEL holds each project's results framework (impact, outcomes, outputs) and an indicator reference sheet for every indicator. Period targets follow each indicator's reporting frequency, and each closed period is judged against validated results.

Results come only from validated field reports or sourced M&E entries such as surveys. Data quality checks, evaluations with management responses, a lessons log and one recommendations tracker close the learning loop. Community feedback and complaints are handled here too, with sensitive complaints restricted.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    Results behind or ahead of target, reports to validate, explanations due, open recommendations and feedback.

  • Results frameworksMonitoring

    Each project's logframe and its indicators.

  • Indicators & targetsMonitoring

    Indicators with targets, results and variance; the reference sheet for each.

  • Validation queueMonitoring

    Approved field reports waiting for M&E validation.

  • Data qualityMonitoring

    Spot checks that recount reported figures at source.

  • Report templatesMonitoring

    Field report templates and their versions.

  • EvaluationsEvaluation & learning

    Evaluations from terms of reference to management response.

  • Lessons learnedEvaluation & learning

    The searchable lessons log.

  • RecommendationsEvaluation & learning

    One tracker for recommendations from evaluations, data quality fixes and lessons.

  • Community feedbackAccountability

    All community feedback and complaints, with response times.

  • MEL settingsSettings

    Variance threshold and feedback response standards.

Setting it up

1Build a project's results framework

  1. Open Results frameworks and choose the project.
  2. Add the impact, outcomes and outputs, then the indicators with their reference sheets and baselines.
  3. Set the period targets; they follow each indicator's reporting frequency.

2Design report templates

  1. In Report templates, build the forms field staff fill in; tag fields with indicator codes so validated figures count towards them.

How to

Validate field reports

  1. Open the Validation queue.
  2. Check the approved report against its evidence and validate it; its tagged figures become indicator results.

Explain a variance

The person responsible for the indicator

  1. When a closed period is more than the threshold (±10% by default) off target, an explanation is asked for in your Approvals inbox.
  2. Write what happened and what will change; it goes into the donor report pack.

Handle community feedback

  1. Anyone logs feedback under *Community feedback* in the sidebar.
  2. Ordinary feedback goes to the project lead to acknowledge and answer within your standards.
  3. Staff conduct, fraud and safeguarding complaints go only to MEL and HR case handlers, must be referred within a day, and can open an HR case.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Only validated reports and sourced entries count as results.
  • A result more than the variance threshold off target needs a written explanation.
  • An evaluation cannot close until every recommendation has a management response.
  • Sensitive complaints are hidden from the person who logged them and from the project team.

How it connects

Last checked against Civora on 30 Oct 2026.

Department guide

Procurement & Logistics

Buying by the right method, purchase orders, goods received, stores, fleet and the supplier register.

Who uses it: Procurement and logistics officers, evaluation committees, drivers

What it is for

Approved purchase requests arrive in Procurement's queue and are bought by the method their value calls for under your own thresholds: direct purchase, request for quotations or open tender (donor rules can be stricter). The purchase order commits the budget, the goods received note records what actually arrived, and Finance pays only for what was received.

Logistics runs stores (bin cards, issues charged to budget lines, counts), the fleet (transport requests, trips, fuel, servicing) and the supplier register with due diligence.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    What is being bought, orders waiting, deliveries due, stock alerts, fleet and supplier compliance.

  • Purchase requestsBuying

    Approved purchase requests waiting to be bought.

  • Quotations & tendersBuying

    Requests for quotations and tenders, compared side by side, with the evaluation committee.

  • Purchase ordersBuying

    Purchase orders sent to suppliers.

  • Goods receivedBuying

    Goods received notes: what arrived and what was rejected.

  • StockStores

    Stock items, bin cards, issues and counts.

  • Transport requestsFleet

    Transport requests to assign a vehicle and driver.

  • VehiclesFleet

    Vehicles: trips, fuel economy, servicing, insurance and inspection.

  • Supplier registerSuppliers

    The supplier register: KRA PIN, CR12, tax compliance certificate, permits, sanctions check, ratings.

  • Procurement rulesSettings

    Your procurement thresholds and methods, committee size and other rules.

Setting it up

1Set your procurement rules

  1. In Procurement rules, set the value thresholds for each method and when an evaluation committee is needed.

2Register your suppliers

  1. Add each supplier in the Supplier register with their KRA PIN, tax compliance certificate and payment details.

How to

Buy what a purchase request asks for

  1. Open the request in Purchase requests; Civora proposes the method its value calls for.
  2. Send a request for quotations and record the quotes; above the committee threshold, at least three evaluators declare any conflict of interest and score them.
  3. Award and raise the purchase order; the budget commitment moves from the request to the order.

Fewer quotations or a lesser method than the value calls for needs a written justification.

Receive goods

  1. When the delivery arrives, record a goods received note against the order: quantities accepted and rejected.
  2. Stock items go into stores automatically; Finance can now approve the supplier's bill for what was received.

Assign transport

  1. Transport requests from staff arrive in Transport requests.
  2. Assign a free vehicle with enough seats and valid insurance, and a driver.
  3. The driver records odometer readings and fuel; kilometres are charged to the project's budget line.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • A suspended supplier, or one whose tax compliance certificate has expired, cannot be awarded.
  • A committee member who declares a conflict with a bidder is excluded from that evaluation.
  • A supplier bill is paid only for what was received (three-way match).
  • Stock count differences must be explained.

How it connects

Last checked against Civora on 30 Oct 2026.

Department guide

Executive Office & Governance

Board and committees, meetings and resolutions, the risk register, compliance calendar and declarations of interest.

Who uses it: The executive director, board secretary and board members

What it is for

Governance runs the board's work: board and committees with members and terms, meetings with agenda, papers, quorum, minutes and numbered resolutions, and an action log that reaches each owner's inbox.

The risk register scores risks before and after controls against the board's risk appetite; the compliance calendar tracks regulator returns, tax and statutory deadlines; and declarations of interest are collected every year. The overview also shows what is waiting in every other department.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    Meetings coming up, risks above appetite, filings due, declarations outstanding, and what waits in each department.

  • Meetings & resolutionsBoard

    Meetings with agenda, papers, attendance, minutes and resolutions.

  • Board & committeesBoard

    The board and its committees: members, positions, terms and quorum.

  • Action logBoard

    Actions arising from meetings, evaluations and reviews, with owners and dates.

  • Risk registerAssurance

    The risk register and heat map.

  • Compliance calendarAssurance

    Statutory and donor obligations with owners and due dates.

  • Declarations of interestAssurance

    This year's declarations of interest and who is outstanding.

  • Governance settingsSettings

    The board's risk appetite and who must declare interests.

Setting it up

1Record the board

  1. In Board & committees, add the board and its committees, their members (staff or external), positions, terms and quorum.

2Set the risk appetite and the compliance calendar

  1. Set the board's risk appetite in Governance settings.
  2. Add your recurring obligations (PBO returns, KRA, data protection registration, licences) in the Compliance calendar.

How to

Hold a board meeting

  1. Choose New → Meeting, set the agenda and attach the papers.
  2. Record attendance; decisions cannot be recorded without a quorum.
  3. Record resolutions with votes and the actions arising (each reaches its owner's inbox), then approve the minutes, which locks them.

Prepare the board deck from Presentations, linked to the meeting and its agenda.

Review a risk

The risk owner

  1. Reviews come due every 30–90 days depending on the score and appear in the owner's inbox.
  2. Re-score likelihood and impact after controls and update the mitigation actions.

File a statutory return

  1. Open the obligation in the Compliance calendar.
  2. Record the filing with its acknowledgement number; a recurring obligation rolls forward to the next due date.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Decisions cannot be recorded without a quorum.
  • Approved minutes are locked.
  • A filing needs its acknowledgement number.
  • Risks above the board's appetite are flagged to the executive.

How it connects

Last checked against Civora on 30 Oct 2026.

Guide

Everyday work for everyone

The overview, your Approvals inbox, expense requests, transport, community feedback, My HR, mail and search.

Who uses it: Every member of staff

What it is for

Whatever your department, a few things are the same for everyone. The Overview shows what needs you and how the organisation is doing. Your Approvals inbox collects everything waiting on your decision, from every department. Anyone can raise an expense request, ask for transport, log community feedback, and use My HR for leave, payslips, timesheets, reviews and policies.

The search at the top (Ctrl K or ⌘ K, or the / key) jumps to any page, starts common actions and finds projects, grants, donors, partners, people, departments, field reports and requests you are allowed to see.

Setting it up

1Your first sign-in

  1. Sign in with the email and temporary password you were given; you are asked to choose your own password.
  2. If your role needs it, set up two-step sign-in with an authenticator app and keep the recovery codes safe.
  3. On a phone, add Civora to your home screen from the browser menu.
  4. Optionally connect your work mailbox under Mail.

How to

Raise an expense request

  1. Choose Create → New expense request.
  2. Pick the project and the budget line; the line decides the grant. Enter the amount, purpose and payee, and attach quotations.
  3. If the donor requires approval for this amount, enter the donor's approval reference.
  4. Submit: it follows the approval chain set by your organisation (supervisor, then the roles the amount calls for).

If a donor rule stops the request, the message says why and what to do. Purchases go on to Procurement once approved; other requests are paid by Finance.

Decide what waits on you

  1. Open Approvals: requests, field reports, leave, timesheets, reviews, explanations and actions in one place.
  2. Open each item to see the full record and decide; every decision is recorded with your name and the time.

Request leave and see your payslips

  1. Open My HR. Under *Leave*, request time off and name who covers for you.
  2. Payslips, timesheets, reviews, policies to acknowledge and your documents are in the other tabs.

Ask for transport

  1. Open Transport, give the date, destination, passengers and the budget line.
  2. Logistics assigns a vehicle and driver; you see it on the same page.

Log community feedback

  1. Open Community feedback and record what the person told you, how to reach them, and the project.
  2. Complaints about staff conduct, fraud or abuse go only to the people who handle them.

File an email on a record

  1. In Mail, open the email and choose File on a record; Civora suggests the grant or project from codes in the subject.
  2. Filed emails appear under *Correspondence* on that record for everyone who can see it.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • You see only what your role and your projects allow.
  • Every change is recorded in the audit log with who, what and when.
  • Approving a request is not paying it; payment is recorded separately by Finance.

How it connects

Last checked against Civora on 30 Oct 2026.

Guide

Library

Every file in Civora, from every module, in collections, showing each person only what they may open.

Who uses it: Everyone

What it is for

Files are attached where they belong: an agreement on its grant, a receipt on its request, evidence on its field report, a contract on an employee file. The Library brings them all together in collections (organisation documents, agreements and contracts, board papers, policies, field evidence, finance records, programme files, people files, suppliers and fleet, filed email).

Each person sees only the files whose records they are allowed to open, so the Library is safe to give to everyone. It also lists records still missing their evidence or receipt.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    Files you can open, storage used, what was added recently, and records missing a file.

  • All files

    Search all files by name, description or record, and filter by area, type, uploader and date.

  • Organisation documentsCollections

    Registration certificates, the constitution, organisation-wide documents.

  • Agreements & contractsCollections

    Grant agreements, partner agreements and contracts.

  • Board & governance papersCollections

    Board papers and minutes.

  • PoliciesCollections

    HR and organisation policies.

  • Field evidenceCollections

    Field evidence attached to reports, and reports still missing it.

  • Finance recordsCollections

    Receipts and finance records, and paid requests still missing a receipt.

  • Programme filesCollections

    Project, activity, grant, evaluation and quality-check files.

  • People filesCollections

    Employee files, applicants and HR cases (HR only, or your own file).

  • Suppliers & fleetCollections

    Supplier and fleet documents.

  • Filed from emailCollections

    Attachments from emails filed on records.

How to

Upload an organisation document

  1. Open Organisation documents and use the upload form (document managers only).

Find a file

  1. Open All files and search; each result links to its record.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • A file is visible only to people who can open the record it is attached to.

Last checked against Civora on 30 Oct 2026.

Guide

Presentations

Slides for a board meeting, a donor review or a programme review, built from live records.

Who uses it: The executive director, grants and programme managers

What it is for

Presentations prepares a deck for a meeting. Choose the meeting first (a board or committee meeting, a donor review of one grant, or a programme review), then the period and the slides. Every slide states its finding as its title and names its source, and the figures are live each time the deck opens.

How to

Prepare a donor review

  1. On the grant page choose Prepare donor review, or open Presentations and choose *Donor review*.
  2. Choose the period (for example since the last report) and the slides.
  3. Present full screen, print one slide per page as a PDF, or copy the link.

Prepare a board deck

  1. Open Presentations, choose *Board or committee meeting* and link the scheduled meeting so its agenda opens the deck.

How it connects

Last checked against Civora on 30 Oct 2026.

Guide

Administration

How the organisation is set up and kept safe: profile, structure, money rules, security, imports and the audit log.

Who uses it: The system administrator; finance for budget categories and approval policies

What it is for

Administration holds the settings every department relies on: the organisation profile, locations and departments (and which workspace each department runs), budget categories and approval policies, security and sign-in, email delivery, imports and the audit log.

Its overview is a set-up checklist for a new organisation and a record of recent changes to how it runs.

Its menu

Each entry in the workspace menu and what you do there. You only see the entries your role allows.

  • Overview

    The set-up checklist, sign-in security at a glance, and recent changes to settings, roles and rules.

  • Organisation profileOrganisation

    Name, registration (PBO) number, currency, financial year and contact details.

  • LocationsOrganisation

    Counties, sub-counties and sites used by projects, activities and participants.

  • DepartmentsOrganisation

    Your department structure, each department's lead, and the workspace it runs in Civora.

  • Budget categoriesMoney rules

    The categories budget lines are coded to (and that donor rules refer to).

  • Approval policiesMoney rules

    Who approves which requests, by amount, type, grant and department.

  • SecuritySecurity & access

    Two-step sign-in by role, members' sign-in status and sessions, and what each role can do.

  • Audit logSecurity & access

    Every create, change, approval, export and deletion, with before and after values.

  • Email deliveryData

    The organisation's sending account for notification emails.

  • Import dataData

    Import budget lines, people and locations from a spreadsheet, with a preview first.

How to

Set who approves what

  1. Open Approval policies.
  2. Create a policy for each band of amount and type of request (and optionally a grant or department), with its steps: the supervisor, then roles such as finance or the executive director.

Require two-step sign-in

  1. In Security, choose the roles that must use two-step sign-in; reset a member's two-step sign-in or sessions if they lose their phone.

Rules Civora enforces

Controls built into the system, so good practice does not depend on memory.

  • Changes to settings, roles, rules and security are recorded in the audit log, which nobody can edit.

Last checked against Civora on 30 Oct 2026.