Module · Delivery

Project Initiation

The governed artefact chain that takes an idea from demand to an approved, initiated project.

Delivery and up Stage 01–02 · Demand → Govern
Book a demo

Get it approved and ready to start

The problem it solves

Initiation lives in disconnected documents; approvals are chased over email and there is no single record of how a project got sanctioned.

What it does

A
Demand FormCapture and triage new demand into the pipeline.
B
Project CharterBusiness case, scope, milestones and roles; submitted for approval.
C
GCR — Governance/Commercial RequirementWork packages carrying procurement, IT-security and service-transition data; template-driven; work packages feed the SORs.
D
SOR — Statement of RequirementGenerated from the GCR’s work packages, grouped by the suppliers competing for each package.
E
PID — Project Initiation DocumentWith a free-type approver search (presence / Skype).
F
Approvals & review queueSubmit any artefact for approval; approvers act from one shared queue; decisions and rejection reasons are recorded.
G
Artefact status / checklistA live picture of which initiation artefacts are done.

How it works

  1. Raise a Demand Form
  2. Build the Project Charter
  3. Define the GCR work packages
  4. Generate the SORs from the GCR
  5. Complete and approve the PID
  6. Track every gate through the approvals queue

See it in context

Screenshot
GCR work packages / SOR recommendation

Idea → Delivery → Live service, on a single thread

See where A-Line fits your delivery. We will map the modules to how your teams actually work.

Book a demo View pricing