Frequently asked questions

NkiruFlow is a workflow and document management platform. It helps organisations build, route, approve and record their business processes in one place.

It’s for private companies, SMEs, enterprises, public institutions and government agencies whose work involves requests and approvals across several people or departments.

Yes. You can create forms and workflows with the form builder, or start from a reusable workflow template. Your Admin reviews and approves new forms and workflows before staff can use them.

No. You can build as many forms as your processes need.

You organise people into internal or external Groups, with Heads of Group and Approvers, and set multi-level approval paths. Each task is numbered and assigned automatically to the right person or Group.

Yes. You can set an SLA for how long each task should take, and the maximum time a workflow can run from start to finish.

It goes back to the person named on the rejection, who can correct and resubmit it. Everyone else sees it as read-only, and the history is kept.

Yes. You can share a secure submission link with outside applicants, and regenerate or deactivate it at any time.

No. Everything happens in your web browser at www.nkiruflow.com, so there is nothing to install. It also works on a phone or any other device, where the menu sits behind the icon at the top left.

You collect applications through internal forms for staff or external forms for outside applicants. Weighted scoring calculates each application’s score automatically, and score band forms place the result in a defined band. Eligibility rules can then route each application to the next step.

All modules run on the same workflow foundation, using the same Groups, approvals, signatures and audit trail.

1. Click New Request on your dashboard and choose a process. You can search or filter by Group.
2. Fill in the request details: title, description, urgency and, if the process asks for it, a due date and time.
3. Complete the form.
4. Review everything and click Submit Request.

Every request starts from a process your organisation has already defined, so you cannot start from a blank form.

Yes. Save as draft is available at every step, and only the title is required to save. Drafts are private to you and appear in My Tasks with the status Draft.

Yes. Tag them as observers when you raise the request, or later from the task. Observers can read the request and comment on it, but cannot approve it. Observers from outside the task’s Group can follow it and comment.

Yes. Use + Add Link to connect a request to another as Related, Predecessor, Parent or Child. You can add links when you raise the request or later.

The Task Pool is your Group’s shared queue, laid out in four columns: New, In-Progress, In-Review and Completed. To take on a task, drag its card from New to In-Progress, or open it and click Pick Task.

When the work is done, click Submit for Review. If you can’t finish it, Drop Task returns it to the pool for someone else.

No. Requests are never deleted: they end as Closed and stay in History. Only unsubmitted drafts can be deleted, by the person who created them.

• Approve, with an optional comment.
• Reject, with a reason. Mandate approvers choose whether it goes back to the requester or to the person who did the work.
• Request Revision, choosing a category (Missing Information, Incorrect Details, Policy Violation or Other) and describing what needs to change.

Where a request has several approvers, they act in order, and only the approver whose turn it is can approve, reject or roll back. Everyone else sees a waiting message and is notified when it reaches them. Application review stages work the same way.

No. If you were also the person who did the work, you are skipped as an approver on that request.

A process is a form design plus its approval route and, optionally, time limits for each step. Requests use processes to collect exactly the information your organisation needs.

Yes. Dropdown and checkbox fields can reveal further questions depending on the option chosen, nested up to five levels deep.

A workflow chains processes together, so finishing one starts another in your Group or a different one. Each follow-on step can run in sequence or in parallel, start automatically or manually, and carry answers forward from the first form through data mapping, so nobody has to retype them.

Yes. Hide it from task creation. Existing requests stay intact, but the process no longer appears when people raise a new request. Workflows can be hidden and unhidden in the same way.

Application processes collect submissions from internal staff, external applicants or both, such as loan candidates, vendors, grant applicants or tenders. They can be scored automatically and routed to reviewers in stages. They are part of the Application / Scoring module.

You set a maximum score and a pass mark. Each field can be scored (weighted or unweighted), act as an eligibility gate, or be informational only.

Score bands then decide the outcome automatically. By default, 90 to 100 is auto-approved, 70 to 89 goes for manual review, 50 to 69 is flagged for review, and below 50 is auto-rejected.

Yes. Outcome triggers and application chains open another form or start a workflow when an application is finally approved or reaches a particular score band. Applicants see the next form as Locked until they earn it, and they are emailed when it opens.

Through the comment box on the submission. Tick Internal note to keep a comment between colleagues; leave it unticked and the applicant sees it on their tracking page and can reply.

An SLA is a time limit on a step of a process, such as line manager approval within 4 hours or execution within 2 days. NkiruFlow then:

• shows a live countdown to whoever holds the step
• sends reminders before the deadline
• escalates to the Head of Group when the step runs late
• records a compliance breach if the step passes its final escalation point
• measures on-time performance

All steps can be timed. Each step has its own clock, with a minimum of 15 minutes. Steps you don’t time are not tracked at all.

That depends on the step. Calendar hours count around the clock. Business hours count only your organisation’s working days and hours and skip holidays. Admins set the working days, hours, time zone and holidays in Organization Settings.

Breach records are permanent, and finishing the work later doesn’t remove them. An Admin, or someone granted the waive permission, can waive a breach with a written justification of at least 20 characters. A waiver excludes the breach from efficiency figures, but the record stays.

Yes, when the delay is genuinely outside your control, for example while you wait on external input. The person holding the step, their Head of Group, Admins and anyone with SLA oversight can pause it with a reason. Paused time is taken off any overdue calculation, and every pause is recorded.

• My Performance: everyone sees their own on-time record.
• Team Performance: Heads of Group see their Group, with reminders for overdue work.
• Organisation SLA: Admins see the whole organisation, including bottlenecks and department comparisons.

Each dashboard exports as PDF or CSV.

Yes. Admins can schedule weekly or monthly reports for the whole organisation, a Group or an individual user.

Each approver saves a drawn or uploaded signature, which is applied when they approve. Changing a signature needs Admin approval.

Documents are attached to the requests they support. You can download a request’s documents and letters together as one package.

Yes. Download PDF on any task packages the request with its documents and letters. It arrives as a ZIP folder.

Yes. Audit Logs record every action taken in your organisation: tasks, processes, admin changes, sign-ins, signatures, SLA events and more. Each entry shows who acted, when, and what action was taken.

Group-level permissions control who can create, view, initiate and approve each workflow. Sessions time out automatically, every action is recorded in the audit trail, and Admins control signatures and new processes.

Yes. Each organisation’s processes are fully encrypted to protect its tasks and information from unauthorised access by other organisations.

The Workflow plan includes Workflow and Task Management:

• the form builder, unlimited forms and workflow templates
• multi-level and mandate routing
• score band applications
• audit trails
• automated task assignment and task numbering
• SLAs, analytics and chat

Pricing is per user, for each team or organisation. Every new team or organisation gets its first month free. After that, Workflow, the basic plan, costs ₦7,000 per user per month. Application Scoring costs an additional ₦4,000 per user per month.

Yes. When your team or organisation signs up, you get one month free. The free month includes the Workflow plan and all the other modules, so you can try everything before you pay.

Yes. All modules run on the Workflow plan, so it is required before you add any other module.

Only Organisation Admins. They see billing in the Billing & subscription section.

Your organisation or team can sign up and use NkiruFlow free for the first month, with access to all modules. If you’d like to see it first, book a demo and we’ll walk through one of your processes with you.

1. Click Get Started on www.nkiruflow.com.
2. Fill in the Business Details form: organisation name, your full name, work email, phone number, address, RC number and a password.
3. Accept the Terms of Service and Privacy Policy, then click Create Account Now.

The first person to register becomes the organisation’s Admin and adds everyone else from inside the platform. New organisations start with their free month.

Yes. NkiruFlow includes chat, so colleagues can message each other inside the platform while work is in progress.

Your invitation email lists your sign-in email, role, position and a temporary password. Click Join in the email to sign in.

On your first login you complete a short setup: your photo, name, phone number and digital signature, then a password of your own to replace the temporary one. The signature is required before you can continue.