De Novo Dental Office IT: The Technology Plan for Your Next Location
The first office took two years to feel settled. Now the lease on the next one is on your desk, and the question is not whether the new office needs computers and a network. It is whether the second office is going to copy the first one, with its mapped drives, its three people who know the Wi-Fi password and the server in the closet behind the sterilization room, or whether it is going to be built the way you wish the first one had been.
This guide is for the owner of one to three offices, or the person running operations for a small group, in the months between the lease and the first patient at the new site. The construction mechanics of any new office, from the carrier order to the handover pack, live in our new dental office IT setup guide and are linked rather than repeated; this page covers the decisions that exist only because an office already does.
A de novo dental office is a location built from the ground up as the next office of an existing practice or group. Its IT is planned differently from a first startup: write the group standard first, decide what the new office shares with office one, and extend identity, software, phones and network to the new address from that standard.
- Write the group standard before the architect draws anything, and run every layer of office one through replicate, upgrade or retire.
- Decide one database or two from your practice software vendor's own documentation before the network is designed, because the network is built around it.
- Add the new office's people and devices to the tenant you already have, with site groups and multi-factor sign-in from day one.
- Keep the main number, give the new office a local number, write the call flow between offices and put the new address in the 911 records before opening.
- Plan what changes at office one when office two opens: its server, internet and backup become shared systems and its staff become the first help desk.
In this guide
- How does a de novo dental office differ from a first-time startup for IT?
- What should you decide before the architect draws the new office?
- How does the new location join your identity, domain and email?
- How does your practice management software extend to a second location?
- One imaging standard or two?
- How should phones and numbers work across two offices?
- What does the network template for the new office look like?
- What is the timeline from lease to opening for a de novo?
- Which budget categories does a de novo carry that office one never had?
- What changes at office one when office two opens?
- How do you staff and run the go-live at the new office?
- The IT side: what your provider builds that you never see
- What to ask your IT provider before the next location
- What to verify before you sign the lease and the provider agreement
- What does a real expansion build look like?
- Frequently asked questions
- The bottom line
How does a de novo dental office differ from a first-time startup for IT?
A first startup makes every technology decision for the first time. A de novo inherits the decisions one office already made: the practice software, the imaging family, the phone platform, the email tenant and the staff's habits. The IT job is to decide which of those to replicate, which to upgrade and which to retire before they are copied.
The word comes from group dentistry. The ADA Health Policy Institute's 2025 data file on practice size puts 7.8 percent of US dentists in practices with two to four locations, 1.9 percent in five to nine, and 17.0 percent affiliated with a dental support organization; among dentists up to ten years out of school, the DSO share is 27.1 percent. Groups call a location they build from scratch a de novo, to separate it from an acquisition, and the technology plan for one is different from both.
| Decision | First-time startup | De novo (your next location) |
|---|---|---|
| Practice software | Chosen from a blank page, usually in month one | Already chosen; the question is how a second site joins it, or whether office two is the moment to change |
| Identity and email | A new tenant and a new domain | Users added to the existing tenant under the existing naming rule; the domain question is "one or two" |
| Phones | A new number and a new platform | The main number stays; the new site gets a local number and a call flow between offices |
| Imaging | Pick a sensor family and a viewer | Match office one, or decide that office two sets the new family and office one follows |
| Network | Designed once for this building | Built from a template, with a link between offices if anything is shared |
| Server | Cloud or closet, decided fresh | If office one has a server, decide whether it becomes shared, duplicated or retired |
| Staff accounts | Everyone is new | Some staff float; the account model has to work in both buildings |
| Backup | Set up once | Per location, with office one's backup re-sized for whatever it now serves |
| Support model | Chosen at opening | Office two joins office one's plan, or the group moves to a group plan |
| Risk | Opening late | Opening late at office two, and breaking office one while you do it |
The last row is the one owners underestimate. A first startup can only hurt itself. A de novo can slow down the office that is paying for it.
What should you decide before the architect draws the new office?
Before the drawings start, write the group standard: one short document that names the practice software and how a site joins it, the imaging family, the phone platform, the email tenant and naming rule, the device list, the closet design, the network template and the backup rule. Every later decision is a yes or a no against it.
A standard does not have to be long. For a two-office practice it is two pages. What matters is that it exists before the architect, the equipment dealer and the low-voltage contractor start making the decisions for you, which is how many first offices end up designed. Our DSO IT support page describes how a group standard is applied across offices once it exists; the table below is how you write it when office two is the first time anyone has asked.
For each layer, decide one of three things: replicate office one, upgrade (office two sets the new standard and office one follows later), or retire (office one's way ends with office one).
| Layer | Replicate when… | Upgrade when… | Retire when… |
|---|---|---|---|
| Practice software | Office one's platform is current, supported and the vendor documents multi-location use | The contract is ending or the platform has no clean multi-site model | A conversion is already planned; do it before office two opens, not during |
| Imaging | The sensor and viewer family is current and the bridge to the software is stable | Office one has mixed sensor brands or an unsupported viewer | A sensor line is discontinued |
| Email and identity | Office one runs on a business tenant with one named account per person | Staff share logins or use personal email for work | Consumer email accounts |
| Phones | The platform supports several sites, local numbers and call flows between offices | A single-site system with no multi-site option | Analog lines kept "for the fax" |
| Network and firewall | The firewall model is current and configuration is documented | Consumer-grade equipment, or nobody can produce the configuration | Equipment that no longer receives security updates |
| Server | A current server with a tested backup, if the software needs one | Server is near end of life; consider hosting or cloud before site two depends on it | The software moved to the cloud and the server only holds old images |
| Workstations | Current operating system, standard build | Mixed builds; any machine on Windows 10, which Microsoft's lifecycle page says reached end of support on October 14, 2025 | Machines that cannot run the current imaging software |
| Backup | Per-device and per-server backup with a restore tested in the last quarter | Backup exists but nobody has restored from it | A single external drive |
| Documentation | A current network diagram, device list and account register | Partial or in one person's head | Never retire; start it |
Two rules keep the table honest. First, anything marked "upgrade" at office two goes into a dated plan for office one, with a budget line, or the group now runs two standards. Second, "retire" is executed before office two opens, because the week of an opening is the worst time to convert anything at office one.
Which office is the template?
If office one was built deliberately, on a current platform with documentation, the new office copies it. If it grew up ad hoc, let the de novo set the standard and schedule office one to catch up, with a date for closing the gap. The test is whether your IT provider can hand you, today, a one-page diagram of office one, a device list with operating system versions, and a list of who can administer each account. If they can, you have a template. If they cannot, you do not have a standard yet; you have an office that works.
| If office one… | Then… | And the office-one task is… |
|---|---|---|
| Runs current software, documented network, named accounts, tested backup | Replicate it at office two | Nothing beyond adding the new site |
| Is current but undocumented | Document it first, then replicate | Documentation pack from the provider |
| Has mixed hardware ages and one or two legacy habits | Office two sets the standard for those layers; office one adopts them within two quarters | A dated upgrade list with a budget line |
| Has a server near end of life and software that could be hosted or cloud | Decide the platform question for both offices before the de novo, so office two is built once | Platform decision, then migration before or well after opening |
| Is on consumer email, shared logins, no firewall configuration anyone can show | Office two is the standard; office one is a remediation project that starts now | Identity and security clean-up, in parallel with the build |
The last row is nothing to be embarrassed about. Office one was built to see patients. Office two is the first time the practice is building infrastructure for a group, and the group includes office one.
How does the new location join your identity, domain and email?
Add the new office's people to the tenant you already have, under the naming rule you already use, with one named account per person and groups for each site. Decide whether the new office uses the same email domain or a second one, and record every new account in the group's account register on the day it is created.
If office one runs on Microsoft 365, the new office is users, groups and devices inside the same tenant, not a second tenant. Microsoft's own guidance for adding a custom domain says it "recommends using a custom domain name for your organization" and notes that "many organizations also add multiple domains to support alternate company names or common variations"; to add or change domains you "must be a Domain Name Administrator", and Microsoft tells you to add users and set up mailboxes before adding the mail (MX) record for a new domain. In practice, a second office that trades under the same name keeps one domain, and a second office that trades under a different name adds that name as a second domain on the same tenant, so one directory still serves both.
The device side follows the same logic. Microsoft's documentation says "any organization can deploy Microsoft Entra joined devices no matter the size or industry". For a two-office practice, joining the new workstations to the same directory as office one means a floater signs in at either office with the same account, and a leaver is removed once.
Identity checklist for the new office
| Item | Decision | Who records it |
|---|---|---|
| Tenant | Same tenant as office one | IT provider in the group documentation |
| Domain | Same domain, or a second domain on the same tenant | Owner; registrar access in the practice's name |
| Naming rule | Same as office one (first.last or the existing rule) | IT provider |
| Site groups | A group per office for mailing lists, shared calendars and permissions | IT provider |
| Floaters | One account, membership of both site groups, a home site for reporting | Office manager and IT provider |
| Shared mailboxes | One per office for the front desk, plus any the group shares (billing, referrals) | Office manager |
| Multi-factor sign-in | Required for every account from day one at the new office, and at office one if it is not already | IT provider; owner for the exceptions list |
| Device join | New workstations joined to the directory, not a workgroup | IT provider |
| Account register | Every new vendor, carrier and software account in the practice entity's name, with the IT provider as delegated administrator | Owner |
The account-ownership register template, and the handover pack it belongs to, are in the startup guide and apply here unchanged. Our guide to Microsoft 365 for dental offices covers licence choices and mailbox setup for a practice of this size; when the new office hires, the joiner and leaver process in our dental employee IT onboarding and offboarding guide is the one both sites should follow.
How does your practice management software extend to a second location?
It depends on the platform. Cloud systems add a location in the vendor's console; server systems need a decision between one shared database and separate databases, and a way for the second office to reach it. Make that decision from the vendor's own documentation, before the network is designed, because the network is built around it.
The rule that most groups learn late is that the software decision shapes the network, not the other way round. If office two will work in a database that lives at office one, the link between the offices and office one's internet connection are now clinical systems. If each office has its own database, you have two systems to back up and a reporting problem. If the software is cloud-hosted, the link question disappears and the internet question doubles.
| Platform | What the vendor publishes about several locations (read 18 November 2026) | What the de novo needs | What to confirm in writing |
|---|---|---|---|
| Open Dental | The manual's Multiple Locations page says "Open Dental can be successfully used when multiple locations are involved" and that the practice must first decide "separate databases for each location or a single central database". It lists twelve options, from separate databases per office to a single database over a VPN, Middle Tier, terminal server, Open Dental Cloud and replication. The Clinics feature "allows multiple locations to be run from one database while keeping locations separate for reporting". | A choice of option before the network design. For a single database over a VPN the manual's "best when" list includes high-speed internet at each location and "fewer than 5 locations", with a note that the number may vary; Middle Tier "isolates the database … by preventing client workstations from directly accessing the database". | Which option your IT provider is designing to; whether eServices are in use (the manual says to contact Open Dental support before enabling Clinics in that case) |
| Dentrix Ascend | Henry Schein One's product page describes "multi-location dashboards" and tools to "simplify multi-location workflows". | Internet at the new site sized for a cloud system, a second path, and the imaging plan for where images live. | How a new location is added to your account, and what it changes on the subscription |
| Dentrix (server) and Dentrix Enterprise | Henry Schein One's Dentrix Enterprise pages could not be read by our tools on 18 November 2026, so no fact is stated here. Dentrix Enterprise is the product Henry Schein One positions for groups. | The single-database or per-site decision, in writing from the vendor. | Whether your edition supports several sites in one database, and across what kind of link |
| Eaglesoft | Patterson's pages could not be read by our tools, so no fact is stated here. | The same decision, in writing. | Whether a single Eaglesoft database can serve two offices over a wide-area link, and what Patterson recommends instead if not |
| Curve | Curve's multi-location page describes a cloud platform for "multi-location dental practices … all in one unified platform". | Internet and a second path at the new site; imaging placement. | How locations, providers and reporting are set up for a second office |
| Denticon | Planet DDS says its implementation approach "is designed for DSOs and groups, guided by experts who understand multi-location needs". | Internet and a second path; the data model for a new office. | Onboarding steps for adding a location |
The table reports what each vendor publishes; it is not a recommendation, and the vendor's page is the authority on its own product. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, which in practice means the server, network, workstations and connectivity each one needs at both offices.
If office two is the moment to change platforms, change before the build gets busy, with its own runbook: our dental PMS migration cutover plan covers the weekend itself, and our comparison of cloud-based dental practice management software covers the hosted options. A practice whose software has gone to the cloud but whose imaging has not should read why a dental office still has a server with cloud software before it plans the new closet.
One imaging standard or two?
Use one imaging family across both offices wherever the current family is supported: the same sensor line, the same viewer, the same bridge to the practice software. Decide where images are stored, how an image taken at office two is seen at office one, and who configures the bridge on each new workstation, before the first sensor is ordered.
The group-wide imaging rule (approved software, a storage rule, a device policy) is set out in our guide to DSO technology strategy; the questions below are the ones a new site adds. Legend supports the IT environment for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, and the same question comes up for all of them at a second office: where does the image database live, and how does each workstation reach it?
| Imaging question | Why it is a de novo question | Decide |
|---|---|---|
| Where the image database lives | If it lives at office one, office two's images travel over the link; if it lives in the cloud, both offices depend on internet | Same place as the practice software database, unless the vendor says otherwise |
| Which workstations get the bridge | Every operatory and consult workstation at office two, configured the same way as office one | A configuration note in the standard, per user and per machine where the bridge needs it |
| CBCT | Large files, a dedicated acquisition workstation, and the question of whether scans are viewed at the other office | Storage and viewing plan from the vendor; see our guide to CBCT computer and network requirements |
| Intraoral scanners | Cloud accounts tied to a person or a site | Account in the practice's name; site assignment agreed with the lab workflow |
| Referrals between offices | If a specialist at office one reads scans from office two | The viewing path, tested before opening |
The test before opening is simple: a sensor fired in each operatory at office two, the image visible in the practice software at office two, and, if the group shares images, visible at office one.
How should phones and numbers work across two offices?
Keep the main number, give the new office its own local number, run both on one phone platform, and write the call flow between the offices before the system is configured. Order the new numbers early, register them in the practice's name, and plan the 911 address information for the new site with the phone provider.
Phones are the system patients notice first, and a two-office practice has questions a single office never had: who answers office two's line when its front desk is at lunch, whether a call to the main number can be booked into either schedule, whether the practice software's call pop-up works at both sites, and what happens to office one's number if the system is replaced to make room for office two. Owners adding a location tend to want more lines and simpler handling rather than anything automated, and the plan should deliver that.
Numbers. New numbers for a new site are usually created by the phone provider; porting comes into it when the practice wants to move an existing number, for example one used on a temporary line during construction, or when office one's numbers move to the new group platform. The FCC's porting-interval rule at 47 CFR 52.35 requires carriers to "complete a simple wireline-to-wireline or simple intermodal port request within one business day unless a longer period is requested by the new provider or by the customer", and the rule counts from an "accurate and complete" port request, so collect a current bill and the account holder's details before the request goes in.
911 at the new address. The FCC's rules for multi-line telephone systems are at 47 CFR 9.16. In the rule's own words, a system has to be configured so that a user may "directly initiate a call to 911 from any station equipped with dialing facilities, without dialing any additional digit, code, prefix, or post-fix, including any trunk-access code such as the digit 9"; the rule also covers notification of a 911 call to "a central location at the facility" where the system can be configured to provide it, and conveying the caller's "dispatchable location" with the call. The rule sets conditions and dates for each of these. This guide describes the rule and does not interpret it: ask the phone provider to show you how the system at the new site is configured for each part, and ask counsel if you need a reading of the rule itself.
| Phone decision | Office one today | Office two plan |
|---|---|---|
| Platform | Whatever office one runs | Same platform if it supports several sites; otherwise the move to one platform happens before office two opens |
| Call flow | Ring the front desk | Written flow: which desk rings first, overflow to the other office, after-hours routing |
| Fax | Often an analog line | Fax over the platform or a fax service; see our guide to replacing POTS lines in a dental office |
| Software integration | Perhaps | Set up once at the group level and tested at both sites |
| 911 | Configured by the provider | The provider shows how the new site's system handles direct dialing, notification and location, using its own test procedure |
Our guide to dental phone systems covers platform choice, call recording and the integration with practice software; the second-office version adds only the call flow and the second address.
What does the network template for the new office look like?
The network template is the one-page standard the new office is built from: firewall model and configuration, switch and access-point models, network segments, drop count per room type, closet layout, internet order with a second path, and the link to office one if anything is shared. The new office gets the template, adjusted for the building, not a fresh design.
If office one has never had one, write it from office one's as-built state, correct the parts you would not repeat, and that becomes the template for office two.
| Layer | Template content | What the de novo inherits | Acceptance test before opening |
|---|---|---|---|
| Firewall | One model, a saved configuration, management access only from the provider's addresses | The same model, the configuration applied, the office added to monitoring | Configuration exported and stored; remote management reachable only from the allowed addresses |
| Segments | Clinical, imaging, guest, phones, building systems (cameras, TVs, door controls) kept apart | The same segment names and rules | A guest device cannot reach a clinical workstation or the imaging store |
| Wi-Fi | Business access points, a staff network and a guest network, coverage per room type | The same names, so staff devices connect at either office | A walk test in every room with the doors closed |
| Internet | A primary circuit ordered as soon as the suite address exists, and a second path from a different carrier or a cellular backup | The same two-path rule; the order date in the project plan | Failover tested by pulling the primary while a workstation is in the practice software |
| Link to office one | Only if a database, image store or phone controller is shared; a site-to-site connection on the firewalls, with the shared service's needs in writing | Exists only when the software decision requires it | Office two reaches the shared service with the primary path down at either site, if the design says it should |
| Remote access | Named accounts, multi-factor sign-in, no exposed remote desktop, access reviewed when staff leave | The same rule from day one | A scan of the office's public address shows no open remote-desktop service |
Two of those rows deserve a sentence each. The link row says "only if"; many two-office practices on cloud software need no link at all, and a link that nothing uses is a thing to maintain and a path to secure. The remote-access row is the one that has hurt dental groups most in recent years; a second office doubles the number of places a weak remote path can exist, so the rule is applied at both from the start, and our guide to dental office remote access security explains the controls behind it.
Drop counts per room, switching and the closet specification for any new office are in our guide to dental office network setup, including what changes when a group opens a new office; the table above adds the acceptance tests a second site needs.
What is the timeline from lease to opening for a de novo?
A de novo runs on the same construction milestones as a first office, but the first milestones are spent on the group's decisions rather than on vendor selection, and the last ones include work at office one. Start the standard, the software decision and the internet order in the first fortnight after the lease is signed.
The startup guide holds the eleven construction milestones, the carrier planner and the mock patient day for any new office; use them as written. The table below is what a de novo adds or changes at each stage.
| Stage | What any new office does (see the startup guide) | What a de novo adds |
|---|---|---|
| Lease signed | Technology questions answered before signing; architect engaged | Write or confirm the group standard; run the replicate / upgrade / retire table; decide one database or two with the software vendor; decide whether office one needs work first |
| Drawings | Technology on the drawings; drop counts; closet location | Apply the network template to the drawings; confirm the imaging placement with the vendor; order the internet circuit as soon as the suite address exists |
| Permits and long-lead orders | Long-lead items ordered; carrier site survey | Add the new site to the phone platform; order local numbers; add the new address to the 911 records plan; book any office-one upgrade that must finish before opening |
| Rough-in | Rough-in checked against the drawings | Create the site group, shared mailboxes and user accounts in the tenant for staff already hired; confirm the software vendor's steps for adding a location |
| Cabling and closet | Cable pulled, tested and labelled; closet finished | Firewall configured from the template and the site-to-site link built if the design needs it; monitoring and backup set up for the new site; office-one changes that touch shared systems finished and tested |
| Install and staging | Equipment received against site-prep sheets; systems installed and staged | Workstations joined to the directory; imaging bridges configured per the standard; phones registered with the new address; a floater signs in at office two with their office-one account |
| Final weeks: testing | Mock patient day; go/no-go rules | Cross-site tests: a patient booked at office one seen at office two; an image from office two viewed at office one; a call to the main number routed to office two; failover tested at both sites |
| Opening week | Daily issues log; hand-over | Provider on site at office two for the first days; a named person at office one watching for anything the opening changed there; one helpdesk number for both teams |
| First 90 days | Review; replacement cycle set | Close the office-one upgrade list; first monthly report covering both sites; the standard updated with anything office two taught you |
If the new office is in Greater Houston or Dallas–Fort Worth, the market-specific version of this timeline is in our second dental office IT plan for Greater Houston and our guide to practice expansion IT in Dallas–Fort Worth. For other markets, the engineers who do this work are listed under dental IT by city.
Which budget categories does a de novo carry that office one never had?
A de novo has every category a first office has, plus four that only exist because an office already does: the link and redundancy between sites, the per-seat and per-location increments on software and licences, the retrofit of office one to the standard, and the group-level tools for monitoring, backup and reporting. Budget them as lines, not as a contingency.
This guide gives no dollar figures. The one-time, monthly and replacement-cycle categories for any new office, and how to read quotes from the contractor, dealer, carrier and IT provider, are in our guide to the dental startup IT budget; the wider startup cost picture is in our guide to dental practice startup costs. The categories below are the ones to add when the office is your second or later. Our dental startup IT page sets out how Legend plans a new office, from the floor plan to the first patient.
| Category | What it contains | Where owners miss it |
|---|---|---|
| Cross-site connectivity | A second internet path at the new office; a site-to-site link if a database or image store is shared; upgrade to office one's circuit if it now hosts for two | Office one's internet was sized for one office |
| Software and licence increments | Added location or site fees, added users, added imaging licences, added phone seats and numbers | The per-seat lines multiply; the vendor's quote for "adding a location" is the number to ask for |
| Office-one retrofit | Every layer marked "upgrade" in the standard, with its own date | Treated as "later" and then paid for in a crisis |
| Group tooling | Monitoring, backup and reporting for two sites; a shared password vault; documentation for both | Assumed to be included; ask the provider which of these the plan covers |
| Spares | One of each critical device model, because both offices now share them | Bought twice, or not at all |
| Go-live staffing | Provider time on site at office two for the opening days; cover at office one | Priced as a day, consumed as a week |
| Support plan change | Moving from a single-office plan to a group plan or adding the second office to the current one | Not asked until the first invoice |
The last row is the buying moment. Decide before opening how the second office is supported: added to office one's plan, or the practice moves to a group arrangement. Our page on managed IT services for dental practices describes what a monthly plan covers; our guide to hidden IT costs in dental groups lists the lines that appear only after office two exists. A group that already employs an IT manager and wants a dental provider beside them should read our guide to co-managed IT for dental groups before it chooses. If you are comparing providers for the group rather than extending office one's, our list of the best dental IT companies is where that comparison starts.
What changes at office one when office two opens?
Office one stops being a practice and becomes part of a group's infrastructure. If it hosts the database or the images, its server and internet become shared systems; its backup now protects two offices' data; its staff become the people who answer office two's questions. Plan those changes as part of the de novo, not as surprises.
This is the section no first-office guide contains, because a first office has no office one. The changes are predictable.
- The server becomes shared. If the database stays at office one, every outage there now closes two offices. The decision is between hardening office one (a second internet path, power protection, a server with a current operating system and a tested restore) and moving the shared service to hosting or the cloud before office two depends on it. Either is reasonable; neither should be decided by default.
- Office one's internet becomes clinical for office two. A connection that was "fine" for one office is now the path office two's workstations use to reach the database. Size it, add a second path and test the failover with office two's workstations, not office one's.
- The backup grows and changes shape. Per-location backups, with the shared database backed up where it lives and the restore tested after office two's data starts arriving. Our guide to dental data backup sets out what a dental backup should cover and how often a restore is proved.
- Office one's staff become a help desk. For the first weeks, office two's team will call office one before they call the provider. Give them a named person at office one, a shared issues log and one helpdesk number, so the questions reach the people who can fix them.
- Office one's exceptions become the group's exceptions. The mapped drive everyone tolerates, the shared login on the sterilization workstation, the imaging viewer two versions behind: at office two they are either copied or ended. Ending them at office one is the retrofit list.
How do you staff and run the go-live at the new office?
Staff the opening with three named people: a super-user from office one who knows the practice software, a named contact at office one who fields questions in the first weeks, and the IT provider on site at office two for the first days. Train the new team on the real system, in the real building, before the first patient.
The mock patient day in the startup guide is the rehearsal for any new office; for a de novo, run it with the cross-site steps included, because those are the ones nobody has done before. Then run opening week against a plan.
| Role | Who | Before opening | Opening week |
|---|---|---|---|
| Super-user | An office-one team member who knows the software as the group uses it | Trains the new team on the real system; writes the one-page "how we do it here" notes | On site at office two for the first two or three days |
| Office-one contact | Office manager or lead at office one | Knows what changed at office one for the opening | Watches office one for anything the opening changed; answers office two's first questions |
| Floaters | Staff who will work at both sites | Accounts in both site groups; sign-in tested at both offices | Work the first days at office two if possible |
| IT provider | The engineer who built the site | Acceptance tests signed; the issues log opened | On site at office two for the opening days; remote the rest of the week |
| Owner | You | Signs the go / no-go | Reads the issues log every evening and decides what waits |
The issues log is one shared document, dated, with every problem, who owns it, and when it closed. Expect the first days at a second office to produce the same kinds of issues the first office produced, plus a short list of cross-site items (a call that did not route, an image that did not appear at the other office, a floater whose account worked in one building and not the other). Those cross-site items are the ones that go back into the standard.
The IT side: what your provider builds that you never see
Behind a de novo opening that feels uneventful, the provider has written the configuration templates, enrolled the new site in monitoring and backup before the first patient, documented both offices as one system, set up access so a leaver is removed once, and updated the practice's security risk analysis to include a second facility.
The visible work is cabling, workstations and phones. The work that makes the second office cheap to run is invisible:
- Configuration as a template. The firewall, switch and access-point configurations are saved and versioned, so office three is a copy, not a project.
- Monitoring from day one. Servers, workstations, switches, backups and the internet paths at both offices in one monitoring view, with alerts routed to people who can act. Legend runs 24/7 monitoring, and every office in a group calls the same helpdesk, staffed 24/7 at 1-800-794-1588.
- Documentation for two. One network diagram showing both sites and every shared service, one device list with operating system versions, one account register, one vendor contact sheet with account numbers for both offices.
- The security risk analysis, updated. The HIPAA Security Rule's administrative safeguards at 45 CFR 164.308 require a covered entity to "conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information", and the physical safeguards at 45 CFR 164.310 require "policies and procedures to limit physical access to its electronic information systems and the facility or facilities in which they are housed". A second facility, a link between facilities and a shared database are changes those documents have to reflect; this guide describes the safeguards and does not interpret the rule, which is a question for your compliance adviser.
- Vendor access, written down. Which vendor can reach which system at which office, through what path, recorded and reviewed, so a sensor vendor's remote tool at office two does not become an unmonitored door into office one.
If the opening is handled by in-house engineers who have done it before, most of this is routine. Legend's engineers are in-house, with no outsourced first-level triage, and onsite dispatch is by appointment across served dental markets, remote-first nationwide.
What to ask your IT provider before the next location
About the standard
- Can you hand me a one-page diagram of office one, a device list with operating system versions and the account register today?
- Which layers of office one would you replicate at office two, which would you upgrade, and which would you retire first?
- If office two sets a new standard for any layer, what is the dated plan and the budget line for office one?
About the software and imaging
- Which multi-location option in our practice software's own documentation are you designing to, and have you confirmed it with the vendor in writing?
- Where will the image database live, and how will an image taken at office two be seen at office one?
- Which workstations at office two need the imaging bridge configured, and is that written in the standard?
About identity, phones and the network
- Will the new office's users, devices and mailboxes be in the same tenant, with site groups and multi-factor sign-in from day one?
- How will the main number, the new local number and the call flow between offices work, and how will each phone at the new site carry the new address for 911?
- Does the design need a link between the offices at all, and if so what happens at each office when the other's internet fails?
About office one and the opening
- What changes at office one because office two exists, and when will each change be made and tested?
- When is the first witnessed restore that includes office two's data?
- Who from your team is on site for the opening days, and who at your company owns the issues log?
What to verify before you sign the lease and the provider agreement
Verify four things before the lease: that the suite can be served by at least one business internet carrier and that a second path exists, that the closet location on the drawings is real and lockable, that the landlord allows the low-voltage work your template needs, and that the opening date leaves time for the group's decisions. Verify four more before signing with a provider.
Before the lease
- A serviceability answer from a carrier for the exact suite, with any construction cost, and a second carrier's or cellular answer for the second path.
- A closet on the drawings with power, cooling and a lockable door, not a corner of a storage room.
- The landlord's rules on cabling, roof or riser access and after-hours work, in writing.
- A calendar from today to the opening date with the standard, the software decision and the internet order in the first fortnight.
Before the provider agreement
- The agreement names both offices, says what is included for the new site and how office one's plan changes, and says what the opening days cost.
- The provider will produce the standard, the network diagram for both offices, the acceptance tests and the handover pack as deliverables, with dates.
- Backups are per location, restores are tested on a schedule the agreement states, and the monthly report covers both sites.
- Every account the provider opens for the new office is in the practice entity's name with the provider as delegated administrator, and that is written down.
What does a real expansion build look like?
Legend Networking is a Dallas-based dental IT company that has served over 3,500 practices since 2004, with 22+ years in dental IT and 1,500+ dental startup buildouts. The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews.
Two project pages show the shape of the work. One records the IT infrastructure Legend installed for an oral surgery practice's expansion location in Texas, with workstations, networking and Wi-Fi, backups, phone integration, treatment-room technology and imaging stations. The other lists the network, Wi-Fi, backup and disaster recovery, and dental software integration work for a practice's second location in Florida. Each scope is the de novo plan above, applied to one more office: the same layers, built to the practice's standard.
Groups that are growing by purchase as well as by building should read the companion pieces: our IT integration checklist for an acquired dental office covers the 90 days after closing, and our dental practice acquisition IT due diligence checklist covers what to check before you sign. For how a growing group keeps every office on its standard once it exists, see the DSO IT support services guide; for the shared-login problem that multiplies with each office, see payer portal logins and MFA for dental groups. Any workstation still on Windows 10 at either office belongs on the retrofit list; our guide to Windows 10 end of life for dental practices explains why. Our national dental IT support page describes what a practice on a Legend plan receives, at one office or several.
Frequently asked questions
What is a de novo dental office?
A de novo dental office is a location a practice or group builds from the ground up as an additional office, as opposed to one it acquires. The term comes from group dentistry. For IT, a de novo is the one time a group can build a location that matches its standard from day one, because there is no previous owner's equipment or habits to unwind.
How is de novo dental office IT different from startup IT?
The construction work is the same: cabling, closet, internet, workstations, phones, software, imaging and testing. The difference is the decisions. A startup chooses everything for the first time; a de novo decides what to replicate from the existing office, what to upgrade and what to retire, and it has to protect the existing office while the new one is built and opened.
Should a second dental office share one practice management database with the first?
Share one database when patients and providers move between offices, the front desks book for each other and you want one set of reports; keep separate databases when the offices are separate in all but ownership. Follow your software vendor's own documentation on the options, because the choice decides whether a link between offices and the hosting site's internet become clinical dependencies.
Does the new office need its own server?
Only if the practice software or imaging requires one at that site. If the database stays at office one, the new office reaches it over a link and needs no database server, though it may still need a local imaging store or a small appliance. If the software is cloud-hosted, the new office needs two internet paths and a closet for the network, not a server.
How far ahead should IT planning start for a second dental location?
Start in the first two weeks after the lease, or before signing it: the group standard, the one-database-or-two decision with the software vendor, and the internet order need the longest lead time and shape everything else. The construction milestones are the same as for any new office; the difference is that the first ones are spent on the group's decisions rather than on choosing vendors.
Can staff work at both offices with one login?
Yes, if both offices are in the same directory. Each person has one account, belongs to the site groups for the offices they work at and has a home site for reporting. Workstations at the new office are joined to the same directory as office one, so a floater signs in at either building with the same credentials and a leaver's access is removed once.
How do phones work across two dental offices?
Both offices run on one phone platform. The practice keeps its main number, the new office gets a local number, and a written call flow says which desk rings first, where calls overflow and how after-hours calls route. Before opening, ask the phone provider to demonstrate how the new site's system handles 911 calls under the FCC's multi-line telephone system rules.
Can we move our existing phone numbers to the new office's platform?
Usually yes, by porting. The FCC's porting-interval rule requires carriers to complete a simple port request within one business day unless the customer or the new provider asks for longer, and it counts from an accurate and complete request. Gather a current bill and the account holder's details before the request goes in, so the request is right first time.
What changes at the first office when the second one opens?
If the first office hosts the database or the images, its server and internet become shared systems and need a second path, power protection and a tested restore. Its backup now covers two offices' data. Its staff field the new team's questions for the first weeks. Any exception tolerated at office one is either copied to office two or ended, and ending it is the retrofit list.
What should be tested before a second dental office opens?
Everything a first office tests, plus the cross-site items: a patient booked at office one seen at office two, an image taken at office two viewed at office one if images are shared, a call to the main number reaching office two, a floater signing in at both sites with one account, failover with the primary internet down at each site, and a 911 address check with the phone provider.
The bottom line
If the lease on your next office is signed or close to it, ask Legend for a planning call about dental startup IT for the new location: bring the floor plan, office one's device list and your practice software, and leave with the replicate / upgrade / retire table filled in and the first-fortnight tasks dated. If you want to see how a single practice is supported first, our national dental IT support page describes what a practice on a Legend plan receives.

