Why your request was refused

LEAT refuses budget requests for about a dozen different reasons, and
they send you to completely different places. This page is a list of
what each one means and who can unblock it.

The award is not active

The award is still a draft, is under review, has been signed but not yet
activated, or has been suspended.

Go to the grants team. An award that is signed but not active usually
has conditions still outstanding, and the refusal will say how many.

A condition has not been met yet

Somebody has to do something before this award can be spent against: a
bank account confirmed by phone, a safeguarding policy adopted, a
co-financing letter received.

The refusal names how many are left. Each has an owner and a due date.

No budget is in force

See "Approved is not the same as effective". The version you are looking
at has not been activated.

The award does not allow this

A clause in the agreement prohibits this cost, this place, this period
or this amount. The refusal names the clause.

Two ways forward, and they are different: ask the donor for a waiver, or
charge the cost to a different award that allows it. A waiver has to be
an executed document; nobody at LEAT can switch a restriction off.

This cannot be decided yet

Different from a refusal. It means the rules could not be evaluated at
all: the award's clauses have not been encoded, a rule contradicts
another, or your request does not say something a rule needs to know.

The commonest version of this is an award nobody has finished setting
up. An award with no clauses encoded funds nothing, deliberately, because
the alternative is a half-finished award behaving like an unrestricted
one.

Not enough is available

The line does not have the money. The refusal says how much it does
have.

A parent line has no room

Your line has room and the line above it does not. This happens when
several lines under one heading are each sized generously and together
come to more than the heading.

The refusal names the parent line. Somebody has to move budget between
lines before this can go through.

The same person cannot do both

You already did the other half of this: you raised the request and are
now trying to hold the budget for it, or you wrote the rule and are now
trying to make it live.

Using a second login does not help. LEAT identifies people by their
employee code rather than by which account they signed in with.