UK-based support

Pre-Port Validation: How to Reduce Number-Porting Delays

Pre-port validation checks the number, range, provider and account evidence before submission, reducing avoidable delays and rejected orders.

Telephone-number port order being validated against provider and account records

Pre-port validation is the work completed before a number-port order is submitted. It checks that the requested numbers, losing provider, account details and associated services are understood. This does not guarantee a port date, but it reduces predictable rejection and prevents incomplete orders entering the process.

Confirm the complete number scope

Start with every number on the account, not only the one printed on the website. Identify main billing numbers, DDIs, ranges and services using numbers indirectly. Check whether a requested number is part of a contiguous block.

Identify the true losing-provider route

The billing supplier may use a wholesale carrier that holds the range. Establish the provider path and use the correct industry process. Guessing from an invoice logo can send an otherwise accurate order to the wrong destination.

Match account evidence

Compare legal name, trading name, account reference, installation address and postcode with the losing provider’s records. Historic addresses are common. A recent bill is useful, but request additional confirmation when it does not show the full number range.

Check service dependencies

Determine whether the number is linked to broadband, ISDN, SIP, alarm or other services. Record what may cease and whether the order needs a particular sequence. Do not use number porting as an accidental service cancellation mechanism.

Validate the gaining destination

The new platform should have users, queues, schedules and failure routing configured. Test with temporary numbers where possible. A managed number-porting service should connect order validation with technical readiness.

Check authority and dates

Confirm that the requester is authorised and that company details are consistent across forms. Identify blackout dates, key contacts and an escalation route. A target date should follow acceptance, not precede validation.

Record the result

Produce a concise validation record: number list, range status, losing path, matched account data, dependencies, evidence gaps and next action. This gives the gaining provider, reseller and customer one controlled source.

For providers managing ports on behalf of customers, the I.T Communications wholesale programme can support structured ordering and escalation without inventing customer records.

Validation checklist

  • Complete numbers and range structure.
  • Losing provider and underlying range holder.
  • Account name, reference, address and postcode.
  • Recent bill and supporting evidence.
  • Associated-service impact.
  • Ready and tested destination.
  • Authorised contact and workable dates.

Pre-port validation replaces assumptions with evidence before time-sensitive work begins. Ask our team to validate a business number range before submitting the port.