The project is labelled mandatory, so nobody challenges its scope or timing. Before prioritising it, establish what obligation has been confirmed, who is qualified to interpret it and which outcome the business must achieve. A genuine requirement does not automatically justify every feature attached to the proposed project.
APM's governance commentary emphasises clear authority for project decisions. This article provides an internal management record, not an interpretation of law, regulation or contract. Obtain current advice from the relevant qualified owner about the actual obligation.
Photo by Sarah Elizabeth on Unsplash.
Ask what makes the work mandatory
Locate the source and responsible owner. It might concern an applicable legal duty, a contractual commitment, an internal control decision or another requirement. Keep those categories visible rather than treating a sponsor preference as equivalent to an externally imposed obligation.
Ask the appropriate owner to confirm applicability, required outcome, deadline and any conditions. Record uncertainty as a question to resolve, not a confident statement copied from a sales presentation or informal message.
Build an obligation-to-scope record
Capture:
Requirement source and current interpretation owner.
Confirmed applicability and relevant deadline.
Outcome or evidence required.
Proposed work directly needed to achieve it.
Additional improvements that are discretionary.
Consequence and escalation route for a gap.
Person authorising the delivery approach and resources.
Do not use this record to determine that a cheaper scope is compliant. That judgement remains with the appropriate specialist and business authorities.
A hypothetical mixed project
A business needs to replace a service arrangement by a confirmed end date. The proposed project includes the necessary replacement plus a redesigned dashboard and additional reporting features.
The sponsor asks which work is essential for continuity and which can follow separately. The authorised owners confirm the requirements and the practical dependencies. If the extras are independent, the business can compare them as discretionary scope rather than presenting the whole bundle as unavoidable.
If the extra feature is genuinely needed for the required operating outcome, retain it and explain the evidence. Scope discipline is not an excuse to remove an essential control.
Prioritise the feasible response
Compare possible delivery approaches against confirmed obligations, available people and acceptance conditions. Identify the latest useful decisions and any specialist lead times. A mandatory label does not create resource availability or remove delivery uncertainty.
When the obligation cannot be met under the current plan, escalate to the right authority promptly. Do not invent a workaround, waiver or extension. Present the evidence and available options for qualified assessment.
Keep the classification current
Review changes in the requirement, interpretation or business context. Preserve the source and date behind important decisions. Distinguish the mandatory result from the preferred project method so the team can respond intelligently when conditions change.
The small-team project planning guide connects scope with a realistic sequence. For the connected task, read What Should a Project Sponsor Actually Decide?. If mandatory projects arrive as unquestionable bundles of work, discuss your project requirements.
