Know what you are committing to. Before you submit.

Tender / bid reference

DEMO-MIG-014 | Fictional IAM migration tender

Consultancy / customer

Example IAM Consultancy / Example Services Group (both fictional)

Bid lead and technical reviewer

Demo Bid Lead / Demo Solution Architect (fictional roles)

Document version and review date

Example v1.0 | Review: 13 Nov 2026 | Submission: 20 Nov 2026

In-scope IAM services and environments

2,000 workforce identities; 20 applications; one test and one production environment. Discovery, staged migration, rollback rehearsal and handover. Pilot: 2 applications; remaining 18 in 3 waves of 6.

Requirement ID and source clause / page

MIG-014 | Fictional RFP section 4.2, page 12

Exact requirement or controlled summary

Describe a staged IAM migration with agreed entry/exit criteria, a rehearsed rollback approach and operational handover. Confirm that each application can meet a maximum four-hour cutover window.

Supporting evidence: title, version, location and date

Fictional Migration Method v2, sections 3-6; demo/migration-method-v2.pdf; 10 Nov 2026. Illustrative source covers waves, rollback and handover. No application-level cutover timing evidence supplied.

Coverage decision and rationale

Partial. The fictional method covers staged delivery and rollback. It does not substantiate the four-hour cutover limit for all 20 applications. No unconditional compliance statement is justified.

Evidence gap, owner and due date

Demo Solution Architect: obtain dependency inventory and pilot timing results by 17 Nov. Demo Bid Lead: submit clarification on the four-hour limit by 16 Nov. Keep the response on hold until resolved.

Work package / linked requirement IDs

WP-03 | Staged IAM migration | Linked requirement: MIG-014

Sizing basis and technical assumptions

Assume 20 supported standard connectors, clean identity data and customer-approved mappings. Two pilot applications, then three waves of six. Estimate assumes no custom connector development.

Customer responsibilities and third-party dependencies

Customer IAM Owner: app inventory and test accounts by 16 Nov. App Owners: approve mappings and test results before each wave. Missing inputs delay planning and require re-estimation.

Exclusions and unresolved scope questions

Custom connectors, licence fees, source-data remediation and 24/7 support excluded. Four-hour cutover remains unverified. Any exclusion that conflicts with mandatory scope needs explicit resolution.

Effort, rates, currency and change trigger

Illustrative only: 46 person-days + 15% contingency = 52.9 days at CHF 1,200/day = CHF 63,480, excluding tax. Re-estimate for extra apps, custom connectors or tighter cutover requirements.

Decision: Ready / Conditional / Hold

HOLD | Internal example review only; not approved for submission

Conditions that must be resolved before submission

Resolve cutover clarification; obtain pilot timing evidence; confirm inventory and connector assumptions; agree exclusions. If the mandatory window cannot be met, escalate bid/no-bid instead of claiming compliance.

Technical and commercial reviewers / review dates

Demo Solution Architect: technical review, 13 Nov. Demo Commercial Lead: estimate review, 13 Nov. Both are fictional roles; reviews are illustrative and approval is withheld.

Approved response version and scope baseline

None. Response draft v1.0 and scope baseline v0.3 remain unapproved. Update both after clarification and evidence review, then request technical and commercial approval.

Next action and accountable owner

Demo Bid Lead schedules the gap review for 18 Nov, with the architect and commercial lead. Record evidence, decision and owners before the 20 Nov submission.

Effort breakdown: discovery 6, design 8, configuration 14, testing 10, handover 4 and management 4 person-days. Total 46 plus 6.9 contingency. Effort is not elapsed delivery duration.