What is Boxcurve Unity?

Boxcurve Unity is an application for mapping accountability across your projects and operations: a single, shared place where every item of work is connected to the person or role answerable for it, and where every change to that picture is recorded. It is built on the Microsoft Power Platform (an app backed by Microsoft Dataverse and a set of automated cloud flows) and it runs entirely inside your own Microsoft 365 tenant.

Its core is the Accountability Map: a grid of tasks set against the people or roles responsible for them, scoped to a project, recorded in your chosen responsibility format: RACI, RASCI, RATSI, DACI, DCI or MOCHA. Around that map, Boxcurve Unity adds the things that make accountability usable in practice: the ability to assign and reassign responsibility, to discuss work in context, to compare one programme against another, and to see a complete, automatically maintained history of who changed what and when.

Privacy-first by design. Boxcurve Unity runs inside your tenant and reads and writes your business information only in your own Dataverse environment. Boxcurve receives no business or personal data, only the install and licensing metadata needed to run your subscription. The application contains no custom code and runs no artificial-intelligence process against your data.

The idea: map responsibility from source to destination, collaboratively and auditably

Boxcurve Unity exists to answer one question reliably, at scale: for any piece of work, who is accountable, and how do we know? It does this by mapping each item of work from its source (a process, a task, an obligation) to its destination (the person or role accountable for it), and then keeping that mapping honest over time.

Three properties hold that together:

• It is explicit. Responsibility is recorded as an assignment that links a task to a named person or role, in your chosen RACI, RASCI, RATSI, DACI, DCI or MOCHA format. Nothing is left implied.
• It is collaborative. The map is shared. People assign and accept responsibility, comment on tasks in context, work a personalised view of their own and their department's tasks, and compare the accountability maps of different projects side by side.
• It is auditable. Boxcurve Unity automatically maintains a change log for tasks and assignments, recording the field that changed, its old and new values, who made the change and when. Comments capture the identity of the person who wrote them. The result is a defensible record of how accountability moved from one state to the next.

This same source-to-destination pattern extends beyond people: work can be brought in from, and pushed out to, the tools your teams already use (for example importing task lists, or creating work items and plans in Microsoft services), so that the accountable picture in Boxcurve Unity stays connected to where the work is actually done.

Who Boxcurve Unity is for

Boxcurve Unity is for organisations that need to establish, share and prove accountability for work that spans many people, teams and projects, and for the functions that have to stand behind that work: operational leadership, programme and project management, and the risk, compliance and governance teams who need evidence that responsibilities are defined and being met.

Within the application, what each person can see and do is governed by five roles:

Role	Intended for
Administrator	Application administrators who configure and operate Boxcurve Unity.
Operations Manager	Operations managers overseeing projects and assignments.
Project Manager	Managers responsible for an individual project.
Team Manager	Managers responsible for a team within a project.
User	Team members who view and work their own assigned tasks.

Access is established first by organisational sign-in (Microsoft Entra ID) and then by membership of the project's stakeholder list, so people only ever see the projects and tasks they participate in. The role model is described in full in the Identity & Access Control document, and the complete capability set in Capabilities & Data Access.

What you can use Boxcurve Unity for

Boxcurve Unity is one application with one model, the Accountability Map, applied to several high-value problems. The use cases below all draw on the same capabilities; what changes is the question you are answering.

Accountability mapping

This is the foundation. Build an Accountability Map for a project, record who is Responsible, Accountable, Consulted and Informed, or your RASCI, RATSI, DACI, DCI or MOCHA equivalent, for each task, and keep it current as work and people change.

• Group, search and filter tasks by department, type, tag, responsibility assignment, or to show only what has changed since you last signed in.
• Assign and reassign responsibility to specific people or roles drawn from the project's stakeholder records.
• Give each person a personalised view of their own and their department's tasks.
• Compare projects side by side to review how responsibilities differ across programmes.
• Rely on the automatic change log as the audit trail for every assignment and edit.

The outcome is a living, shared map of who owns what, with the evidence to prove it.

Risk management

Boxcurve Unity makes accountability risk-aware, so that the work most likely to hurt you has a clearly named owner and a defensible trail. Risk is treated as an attribute of the work and of the people in the map, not as a disconnected register:

• Each task can carry risk indicators and compliance references alongside its owner, priority and status, so risk-bearing obligations are visible in the same place as their accountability.
• Stakeholder records capture governance attributes such as risk tolerance, impact and influence, helping you weigh who should own sensitive work.
• The change log gives you a continuous record of how responsibility for risk-bearing tasks has moved over time, which is exactly the evidence audit and assurance teams ask for.

Use Boxcurve Unity to ensure that controls, obligations and high-priority tasks are owned, watched and auditable, rather than assumed.

M&A integration and operational transformation

Mergers, acquisitions, restructures and operating-model changes are, at heart, large exercises in moving accountability from one state to another, which is precisely what Boxcurve Unity is built to track. It supports this work through capabilities you already have:

• Task packs (reusable, pre-defined sets of tasks) let you stand up an integration or transformation playbook quickly and apply it consistently across entities or workstreams.
• Compare projects lets you set a current-state operating model against a target-state model and see exactly where responsibilities differ, overlap or fall through the gaps.
• Project lifecycle operations (copy, back up, restore, reset, and promote a development copy of a project) let you model "to-be" scenarios safely before you commit them.
• Import and export let you bring existing task lists in and push agreed work out into the tools delivery teams use.

Throughout, the change log records the transition from source organisation to destination organisation, giving programme leadership and assurance teams an auditable account of how the new operating model was assembled and who became accountable for each part of it.

AI-agent governance and grounding ("agentic" transformation)

As organisations introduce AI agents into their operations, those agents take on real work, and so they need real accountability. Boxcurve Unity supports an "agentic" transformation in two complementary ways, both of which keep the human accountability model intact and add no AI of its own.

1. It governs the AI agents you deploy. Boxcurve Unity lets you treat an AI agent as a stakeholder in the Accountability Map and record a full governance profile against it, so that AI-driven work is mapped, owned and auditable alongside human responsibility. The governance attributes it can hold for an agent include:

• its model and provider identification, version and effective dates;
• its intended use and stated limitations, with links to a model card or evaluation reference;
• its model owner and audit owner, audit criticality, last-audited date and next-audit-due date;
• its logging configuration and log-retention period;
• whether it is flagged as a high-risk AI or high-risk model.

2. It grounds your Microsoft 365 Copilot. Because Boxcurve Unity holds your accountability information as structured data in your own Dataverse, that information can become an authoritative source for natural-language questions asked through Microsoft 365 Copilot, should your organisation choose to enable it. By default Copilot infers answers from unstructured content (mail, documents, chats), which has no definitive record of who is accountable for what. Unity fills that gap: when your Dataverse data is made available to Copilot in your tenant, a team member can ask in plain language "Who is accountable for X?" or "What is my accountability on this team?" and receive an answer grounded on authoritative Unity data rather than inferred from documents.

Important. Boxcurve Unity runs no AI of its own and makes no call to any AI service. The agent records above document AI agents that exist elsewhere; completing them runs nothing. The Copilot grounding is a Microsoft platform capability that you enable in your own Microsoft 365 environment: it requires Microsoft 365 Copilot licensing, is read-only (Copilot can answer and summarise but cannot create, change or delete Unity data), respects each user's existing permissions, and needs nothing configured in Unity. Unity's role is simply to hold your accountability data in a structured, governed form that Copilot can be grounded on. The full conditions, prerequisites and Microsoft references are in Capabilities & Data Access.

The result is that an emerging AI workforce is brought under the same explicit, collaborative, auditable accountability model as everyone else, and the authoritative record of that accountability is available to ground the AI tools your people already use.

Where your information lives

All business information in Boxcurve Unity, the tasks, assignments, stakeholders, projects, comments and change history, is stored in your organisation's own Microsoft Dataverse environment, within your Microsoft 365 tenant. Boxcurve Unity reads from and writes to that Dataverse; it does not keep a separate, vendor-hosted copy of your data. How this is isolated and protected is covered in Data Residency & Tenant Isolation and Data Held & Handling.

Where to go next

• Licensing & Prerequisites — what you need in place before you begin.
• Installation & Initial Setup — getting Boxcurve Unity running in your tenant.
• Capabilities & Data Access — the full list of what people can do and what each capability reads or updates.
• User Guide — day-to-day use of the Accountability Map.