Formal intake

Start formal intake with the scope, timing, and files in one place.

Use this form when the request is clear enough for a real first review. Attach the documents already shaping the decision so the review thread does not restart later.

Start submission Check status

What to have ready

These details make the first review useful.

State the problem, target outcome, users, and operating context.
Name the timing pressure, milestones, stakeholders, and value range if known.
Attach the documents already shaping the decision, even if the pack is not complete.

What happens after submission

The reference number keeps review and status tied to one request.

New

The request has been logged and is waiting for structured review.

Under review

The submission is being reviewed for fit, scope, and any follow-up needed.

Requested information

The team needs more detail or supporting material before continuing.

Check status Review process

Selected capability

The selected capability stays attached to this submission.

Platform modernization and integration

The first review starts with the intended capability already attached.

Organization and contact

Organization name *Contact person *Email *Phone

Program type and value

Program type *Estimated contract valueUse a range if the program is staged or still being finalized.

Scope and timeline

Timeline *Include any review window, procurement deadline, or target implementation start date.Project scope *A strong scope explains users, operating pressure, integrations, constraints, and what has to be true at handoff.

Documents and confirmation

Upload documents

Accepted types: PDF, DOCX, XLSX, PPTX, TXT, CSV, JPG, PNG, WEBP, ZIP

Up to 10 files, 20MB each.

Drag files here or browseScope packs, technical notes, pricing sheets, governance papers, or related files.

No documents selected yet.