All Insights
ERP decisions4 min read

Choose an ERP sponsor who can make the pending decisions

Assign an ERP sponsor with clear decision rights, a usable escalation route and capacity to resolve conflicts between departments. Includes a decision card.

An ERP sponsor decision card identifies the conflict, options, affected work, authority, decision date and recorded outcome.
Original DATUM decision card. Proposed operating practice, not a vendor-mandated governance model. Open full-size diagram

Choose an ERP sponsor who can resolve decisions that cross departments and protect the time needed to implement them. A senior title helps only if the person has the authority, availability and operating context to make those decisions.

The project manager coordinates the work. Process owners know how their areas operate. The sponsor settles conflicts that those owners cannot resolve within their delegated authority. Write that division down before a disputed decision holds up several workstreams.

ERP joins records and processes across functions such as procurement, accounting and operations. That shared scope is described in Oracle's ERP overview. The sponsorship worksheet below is DATUM's proposed way to handle decisions across those boundaries, not a vendor-mandated organizational model. Oracle: What is ERP?.

Test the role with decisions, not attendance

Take three pending decisions from the actual project. Ask the proposed sponsor what information they need, whose input is required and what they can decide without another escalation. Use decisions like these:

DecisionInput neededSponsor's roleWhat remains with specialists
Two teams define job completion differentlyWork evidence, billing dependency and customer obligationResolve the shared operating definitionService-specific technical acceptance
Data cleanup competes with daily workRequired cleanup, capacity and consequence of delayAssign capacity or change the release scopeCorrect record values and financial treatment
A late requirement expands the releaseBusiness consequence, alternatives and delivery effectDecide the authorized scope tradeoffTechnical feasibility and detailed estimate
An acceptance test failsEvidence, operational impact and recovery optionsDecide whether the release conditions are met within authorityQualified judgments outside the sponsor's expertise

A sponsor should not overrule a finance or safety determination merely to hold a date. The role is to obtain the necessary decision and act on its consequence, including changing the plan.

Agree a decision route people can use

Create a short decision card with the issue, recommendation, alternatives, affected work, decision owner and date needed. Attach the underlying evidence rather than forwarding a long chat history.

For an invented example, sales wants a job visible to scheduling as soon as the quote is accepted. Operations wants it held until material availability is checked. The sponsor needs to understand whether the business wants early visibility, permission to promise a date, or permission to release work. Those are different decisions and may require different states.

A useful outcome might allow the scheduler to see accepted work while withholding release until the material check passes. That is a proposed policy, not a universal ERP rule. Record it so the implementer can turn it into a configuration and acceptance case.

If the sponsor is unavailable, name a delegate and the limits of that delegation. A deputy who can convene a meeting but cannot make the pending decision does not resolve the bottleneck.

Make the commitment visible in the plan

Agree how often the sponsor reviews unresolved decisions and how urgent exceptions reach them. Choose a cadence the person can actually keep. Do not borrow a meeting frequency from another company and call it a requirement.

Track decision age, affected work and whether a supposedly settled question has reopened. Repeated reopening may mean the earlier decision lacked the right participant or did not identify what would change it. It does not automatically mean the project needs more meetings.

Keep the sponsor's acceptance separate from the implementer's report. The delivery team can show completed configuration and tests; the authorized business owners must still accept the resulting operating process. Use the statement-of-work worksheet to place those responsibilities in the delivery agreement.

Before confirming the sponsor, walk one real disagreement through this route. If nobody can identify who has the final decision or when it will be made, revise the role assignment while the cost of doing so is small.

How we research and review these articles