Separate a UK registered office from an operating site before outreach

Separate the registered-office address from the operating-site field, preserving both with their evidence and purpose. If a record has already treated the registered office as the site for a proposed visit or site-specific discussion, correct that particular use only after the operating location has been established.

Identify the practical consequence of the address conflict

Start with the record that caused the problem. Perhaps a visit brief names the registered office as the installation location, or a territory allocation uses it as the factory postcode. Write down the specific use before researching another address. The correction is not simply to make the account more complete. It must prevent an evidenced address from being used for a purpose it does not support, while keeping legitimate registration information available for its original role.

Preserve the source record exactly as received, including the field heading and the source date. An export headed company address may have lost a distinction that existed in the original source. Check that source before describing the address itself as false. Record the live account identifier, the field carrying the value and the downstream document or decision affected. Do not change the address in several places independently, because that makes it difficult to establish what was actually corrected.

GOV.UK allows a registered office to use a qualifying service-provider address, such as an accountant or solicitor. That is a reason not to infer operations from registration alone. It does not prove that any particular address belongs to an accountant or that no business activity occurs there. The narrow operational conclusion is that you need separate evidence for the location required by your task. A familiar street name or map category is not a substitute for that evidence.

Find evidence for the address function

Collect the source statement that describes what each address does. A company may publish a registered-office notice separately from a named works, showroom or service depot. Capture the relevant wording, URL and check date, and identify which legal entity the statement concerns. A location on a group website may serve another subsidiary. Keep that distinction open until you can link the operating location to the account and the actual purpose of the proposed interaction.

Look for an explicit description rather than counting repeated directory listings. Ten websites copying the same registered address do not create ten independent confirmations of a factory. If the only operating-site information comes from an old document, note its date and the uncertainty. A company reply can help establish the relevant location through an already appropriate contact route, but do not disclose unrelated personal information or infer a private address to obtain that reply. The evidence should be proportionate to the correction.

Separate the company identity check from the site-function check. A matching registered number can help tie a statement to the right entity, while the wording about a works or office supports its function. Neither answers every logistical question. The visitor entrance, delivery point and technical installation location may still differ. Record only the address purpose actually established and leave the remaining distinctions for the person responsible for the visit or delivery. This guide is not a site-access or travel authorisation.

Build a populated fictional correction case

The following case is entirely fictional. An imported account has put Address A into the field operating site because the source column was labelled registered office. A draft visit brief now repeats Address A as the place where equipment is used. An unchanged source extract confirms that Address A was supplied for registration only. A current fictional company site statement identifies Address B as the named works associated with the same illustrative account identity. No real address or customer is represented.

The correction case records the original source heading, Address A, the affected visit brief and the separate evidence for Address B. The decision is to retain Address A in the registered-office field and put Address B into the evidenced works-location field. The visit brief is withdrawn for correction rather than silently replaced. Its owner must confirm the intended meeting point separately, because a published works address is not itself permission to visit or proof of the correct entrance.

In the contrasting fictional case, a directory lists Address C but provides no current statement of function or entity. The account retains its verified registered-office information, while the operating-site field stays unknown and the visit task is held. No address is promoted merely because it appears more industrial. These are constructed accepted and unresolved decisions, not observed outcomes. A real case requires its own source captures, account match and confirmation of whatever operational detail the next task actually needs.

Preview which histories and decisions would change

Before editing, identify the records that consume the address. A site-specific opportunity, a general account record and a historic conversation may all display it for different reasons. The correction should not rewrite the context in which an earlier message was sent. Keep the historical address as an observation with its original date, while making the current field function clear. If the system offers only one address field, establish a reviewed way to preserve the distinction rather than overwriting without explanation.

Check whether territory ownership, travel arrangements or another document was derived from the wrong field. Those consequences need separate owners. Updating the account address does not necessarily recalculate a territory or recall a document. Mark the affected outputs and record their observed correction status. Do not claim that every downstream use has been fixed because the account screen now looks right. The task is complete only within the scope you have actually inspected and corrected.

Keep objections and contact restrictions intact. A new operating-site address is not a new company identity and does not reset the record of a previous conversation. Nor does it create permission to contact a different person. The repair concerns address function and a specific erroneous use. Any new outreach, visit or disclosure follows the independently applicable approval and contact rules. This guide does not assume a particular LDM address model or an automatic relationship between site fields and account ownership.

Apply the smallest evidenced change and check its reversibility

Use a correction preview or controlled copy appropriate to your system to establish what the edit will affect. Target the known account identifier and the specific address-purpose fields. Confirm that the operation updates an existing account rather than creating another company with the works address as its name. If the tool cannot preserve the old value and the correction explanation, save a controlled correction record through the approved process before proceeding. Do not invent a system capability that has not been checked.

After the authorised edit, export or reopen the affected fields and compare them against the reviewed decision. The registered office should remain available in its own role, the operating site should show only the established location and unresolved purposes should remain unresolved. Check the affected task or document separately. A successful field edit is not proof that its copied address changed elsewhere. Record the actual result and any remaining downstream exceptions in the correction case.

Write an undo instruction that names the prior value, destination field and stable account key. Test that instruction in the controlled copy where practical, including what happens to the correction note. Reversibility does not mean restoring an address blindly after other legitimate changes have occurred. It means preserving enough context for a responsible person to decide how to reverse this specific edit. If new evidence contradicts the site statement, reopen the case instead of layering another unexplained overwrite onto the account.

Hand over an address decision rather than a research list

The completed case tells the next person which address serves registration, which serves the identified operational purpose and which use remains unconfirmed. Include the source record, conflicting field, identity link, affected outputs, correction decision and observed check. An unresolved case names the missing evidence and its owner. This is useful even when no operating site can yet be released: it prevents an already known registration address from continuing to masquerade as a verified destination for a different task.

The distinction from general data cleansing is the reversible correction of one specific address-function error and its consequences. A general normalisation rule can make postcodes consistent, but cannot establish what takes place at an address or repair a visit brief based on the wrong purpose. Keep the scope bounded to the actual conflict. There is no need to gather every site the group owns or to suggest a company is unreliable because its registered office and factory are different.

Source, checked 18 October 2026: GOV.UK, Check the rules for registered office addresses and email addresses, https://www.gov.uk/limited-company-formation/company-address . The source supports the distinction that a qualifying service-provider address may be used for registration. Address-purpose evidence, correction workflow and all cases here are editorial recommendations or explicitly fictional; no real operating location or right of access is asserted.

You can test this in practice with open email infrastructure statistics for domains on check.live-direct-marketing.online.

FAQ