CONTROL AND MANDATE

The boundaries are yours.
Throughout.

A proposal needs evidence. An action needs a mandate. A decision needs to be traceable.

FOUR CONTROL POINTS

What you need to see.

Source and quality

Which data supports the proposal, when was it refreshed and what is missing? Agree thresholds for pausing proposals.

Rule and mandate

Which actions are allowed, for which projects and within what financial or time limits? Reading, proposing and execution are governed separately.

Approval

Which role can approve and what decisions require specialist review? Exceptions need a clear path forward.

Log and follow-up

What was proposed, approved and executed? Follow ownership, timestamps and outcomes. Agree how errors are detected and handled.

TRY THE CONTROL

Outdated evidence?
Pause the proposal.

MantaILLUSTRATIVE DEMO · EXAMPLE DATA

01 / SIGNAL

Where are sales falling behind?

See the gap across the portfolio. Then look at project A to investigate what may explain it.

Show the source data

Project status: 18 unsold homes in A.
CRM: 36 prospects with permission to contact.
12 have had no follow-up scheduled for over 7 days.
8 of these have a documented match to available homes.
Fictional data. No estimated purchase probability.

Try outdated CRM data

The portfolioSales · last 30 days

Project	Plan	Sold	Gap
AProject A	20	12	-8
BProject B	20	19	-1
CProject C	10	12	+2

Project A has the largest gap. The cause needs investigation.

18unsold homes

12without a follow-up

8with a documented match

Step 1 of 4

DATA PROCESSING

Agree the setup before sharing data.

Storage, processing location, access controls, subprocessors, deletion and incident handling need documentation for the specific engagement. Include your IT and privacy owners in scoping.

Read the privacy information

EXPLORE FOUR MANDATE LEVELS

More access.
The same clear ownership.

Change the level to see how an illustrative mandate affects three actions. This is a scoping draft and grants no actual access.

ILLUSTRATIVE EXAMPLE · PROJECT A

Propose

Manta prepares decision evidence. A person chooses the next step. No changes are sent to external systems.

Try missing contact permissions

Example, not an active delegation.

FROM RULE TO USE

A mandate should
be changeable and stoppable.

Document the rule

Specify source, action, project, financial limit, validity period and responsible approver.

Test exceptions

Try missing evidence, exceeded limits, duplicate requests and unavailable destination systems before enabling access.

Follow the log

Keep the rule version, evidence, proposal, approval and destination response. Distinguish an attempt from confirmed completion.

Stop and review

Revoke access when needed. Review actions already completed separately and determine what can be reversed.

12YOUR PORTFOLIO

Which work do you
want to move forward?

Bring a land review, sales challenge or cost workflow. We review what Manta can prepare, execute and follow up in your setup.

Book a demo Explore the first deliverable