A scope comparison should begin with separately identified proposals. Record what each current source represents before placing them beside one another. An assembly, an optional member and a service item may have different boundaries even when grouped under a similar catalogue name. The comparison should preserve those differences rather than filling every row with an assumed equivalent.
Ask the provider to identify the proposed included items and the references supporting that scope. If an alternative changes one component, retain the previous assembly issue and name the affected relationship. A picture or a locally selected record does not prove a supplied set, quantity or commercial inclusion. Keep technical and commercial questions with their responsible parties.
Use configuration issue when a proposal changes. The demonstration’s ordered list represents reading order only and contains fictional identifiers. Carry actual proposal identifiers and open differences into document review. A useful comparison is traceable to current sources; it is not a compatibility decision or a replacement recommendation.
Keep these fields together
- Proposal identity
- Included scope source
- Alternative identity
- Proposed difference
- Responsible response
Use the blank source worksheet to record actual information from the responsible provider. Fields are intentionally empty; the fictional collection does not supply a decision, current document or real project record.
Download a blank source register (CSV)