Planning
Structure agreed work and dates at every delivery level.
- Agreed projects, epics, stories and tasks
- Planned start and due dates at each level
Features
Nelogi™ turns framework controls, regulatory mandates and SoWs into structured workstreams — with clear owners, reusable evidence, document reviews, approvals and training.
Turn requirements into owned work, agreed dates and connected dependencies.
Structure agreed work and dates at every delivery level.
Make responsibility and review ownership explicit.
Read live delivery state without rebuilding status reports.
Bring delivery risks and missed commitments into view.
Show how activities affect one another before delays land.
Choose a project type when creating a project — ISO/IEC 27001, CMMC, SMLDI, PCI DSS v4.0.1, SOC 1, AI governance or risk assessment — and start from a reusable template tailored to your scope. PCI DSS v4.0.1 templates support merchant and service provider readiness. Templates do not guarantee conformity or certification.
Propose dates, the customer confirms, and every later change is a recorded change request.
Work can't be marked done, submitted or approved until the items it depends on are completed. Starting work is never blocked.
Start with a framework, a SoW or your meeting notes. Choose a built-in readiness or regulatory programme template, or provide Statements of Work (SoWs) and your scope to draft structured workstreams and action items.
Assign owners, dates and dependencies across the whole plan in one place.
A gentle check when work is closed before its earlier steps — proceed with a recorded note.
Keep implementation tasks from templates, risk treatment tasks, remediation of findings and recurring control rounds in one place, each with owners, dates, approvals and evidence.
Keep each client's assets, risks and control gaps connected to the work that addresses them.
Each client's assets with owner, type and confidentiality, integrity and availability ratings. Import from CSV, link to risks, and get AI-suggested risk scenarios for review.
Add risks directly, import an existing register from CSV, or raise risks from projects and control gaps — one risk register per customer. Use risk analysis with likelihood and impact scoring based on that client's own method, record threat, vulnerability and impact, link affected assets and treatment tasks, and record acceptance only through an approval.

Completing treatment work does not automatically close a risk. Reassess residual risk and obtain appropriate acceptance.
Mark each control Met, Partly met, Not met or Not applicable, with a gap note and a required justification for Not applicable. Update many controls at once in a gap-assessment table.
See each framework's progress per client — counts by status and % met — and open the controls behind each number. Export a starting point for your Statement of Applicability.
Providers switch every page to one client in a click; customer users only ever see their own organisation.
Run controls in monthly, quarterly, half-yearly or annual rounds, suggested from the template. Each round keeps the same owner and approver, so evidence builds up all year.
Accept a risk only through an approved decision with a reason, an expiry date and the right approver for the level of risk, plus a note on framework impact. Accepted risks reopen on expiry.
Choose Reduce, Transfer, Avoid or Accept per risk. Transfer and Avoid record who carries the risk and the supporting documents. Suggested controls and AI-drafted treatment tasks are reviewed by your team. Completing treatment does not close a risk; reassess residual risk.
Keep customers and other participants involved through the work shared with them.
Keep delivery context and decisions connected to the work.
Each person gets a short daily or weekly summary of what needs them, with review-and-approve links.
A clear weekly update in seconds. Customer versions use shared items only.
See what's waiting on others and send a reminder with a personal note.
Your progress, responses received and what's waiting on others — summarised in seconds.
Connect evidence to requirements and record review decisions. Evidence is not independently verified by being stored or shared.
Maintain a clear record of review and sign-off.
Attach evidence to the work it supports — as links to your own repositories or as uploaded PDF/DOCX files.
Reuse approved evidence across tasks where permitted; each link records the version used, while retaining review for each control. Reuse does not prove effectiveness or close risks.
Going on leave? Name a backup approver for a period. Decisions record who approved, on whose behalf.
Evidence upload links let build pipelines send reports straight to the right control; they arrive internal until reviewed; links expire and can be revoked.
See who has access to which project and at what level. Flags inactive or expired accounts still holding access, people not signed in for 90 days and access on the wrong customer's project. Change or remove access with a recorded reason, and export a CSV for periodic access reviews. Customer sponsors can review their own people.
Supports access reviews; it does not replace your own review process.
Keep document versions, reviews and approval records connected to governed work. Link controlled documents or upload PDF/DOCX evidence for review.
One register for each customer's documents and evidence. Upload policies and procedures once, keep versions, send them for approval and set review dates. Link documents to projects, controls, risks and tasks, and reuse approved evidence across tasks — each link records the version used. The policy library adds templates and packs as document items.
Coordinate evidence requests, findings and remediation through existing work items, owners and review records. Independent assessors review evidence and findings; management owns implementation and remediation. Advisory work is distinct from an independent certification audit.
Translate compliance requirements into control work and security findings into assessment, testing and remediation activities. Treatments have owners, dates and verification. One corrective action can support multiple controls and risks; its outcome still needs validation.
Link assets to the risks that affect them, and risks to the tasks that treat them. Each control records its gap status.
Assign learning alongside the programme and track completion. Certificates record course completion, not compliance or certification status.
Assign short video courses with quizzes to your team and your clients' people, and track who has completed them.
Coming soon
Planned controlled sharing of selected approved assurance information with customers and auditors. Sharing supports review; it does not prove compliance or independently verify evidence.
Planned: chat alerts and connections to monitoring and security-testing tools. Pipeline evidence is available now — automated evidence uploads let build pipelines send reports straight to the right control; they arrive internal until reviewed; links expire and can be revoked.
Import epics, stories and tasks from a spreadsheet using our template, or work with our team during onboarding. Owners can export projects, work items, comments, approvals and people as CSV records. This does not include a full attachment export.