---
title: "Implementation"
url: https://doorjames.com/implementation/
language: en
updated: 2026-09-22
type: info
section: company
description: "Around four weeks per first location, 15 steps from kick-off to go-live, clearly assigned tasks – and no implementation fee for the standard rollout."
translations: de=https://doorjames.com/de/einfuehrung/
formats: https://doorjames.com/implementation/index.md https://doorjames.com/implementation/index.json https://doorjames.com/implementation/index.jsonld
bookDemo: https://meet.doorjames.app/public-schedule/99469a6d66d20f7fdd5ee19182a8f8bd (30 min, Microsoft Teams)
---

# From decision to go-live

> The standard Door James rollout is built for speed: as a planning assumption around four weeks per first location, with further locations running in parallel. The sequence covers 15 steps from kick-off through SSO setup, capture of floor plans and assets, configuration and approval to training and go-live. There is no implementation fee for the standard rollout.

Not an implementation project but a structured sequence with clearly assigned tasks.

## Key facts

- **Timeline:** around four weeks per first location
- **Parallel:** further locations at the same time
- **Cost:** no implementation fee
- **Afterwards:** self-administration in the Admin Panel

## Why it is not a classic implementation project

Door James is a standardized product. The rollout therefore consists not of development but of data capture and configuration. That shifts the critical path: the pace is set not by the software but by the availability of your location data.

## What you can prepare before the start

Three things noticeably shorten every rollout. First, current floor plans in a usable format. Second, a complete list of bookable resources with numbering, type and equipment. Third, an appointment with whoever approves Entra ID registrations in your organization. Clarifying those three before the kick-off usually saves one to two weeks.

## After go-live

We stay close in the first weeks, because that is when the typical adjustments come up: sharpening rules, renaming areas, tuning quotas. After that, responsibility moves to your administrators as planned – and the only recurring task is to look at the reports.

## How it works

1. **Kick-off and demo** – Shared understanding of goals, locations and scope; demonstration of the platform for everyone involved.
2. **Align stakeholders** – Involve project owners, location owners, IT, data protection and employee representatives early.
3. **Define module scope** – Which modules are activated, organization-wide and per location?
4. **Set up identity** – OIDC connection to Entra ID or another provider, groups and permitted domains.
5. **Capture floor plans and office data** – Floor plans, addresses, opening hours, reception details, banner images.
6. **Provide the asset list** – Bookable resources in an agreed spreadsheet – numbering, type, equipment, restrictions.
7. **Build the location** – Areas, zones and assets are created and placed on the floor plan.
8. **Configure privacy and visitors** – Deletion periods, anonymization, location-specific notices, visitor workflows and questionnaires.
9. **Enable integrations** – Outlook room calendars, Teams app and further connections, where in scope.
10. **Approve the location** – Location owners review the configuration and approve it.
11. **Order stickers** – QR code stickers for check-in, if used, and placement on site.
12. **Admin training** – Training for administration and reception roles, handover of manuals.
13. **Inform users** – Communication to the workforce with templates, videos and notes on the rules.
14. **Go-live** – Release for all users at the location.
15. **Follow-up** – Support and customer success for the first weeks, then self-administration.

## Frequently asked questions

### What typically delays a rollout?

Almost always the same three things: missing or outdated floor plans, an incomplete asset list, and scheduling with IT for the identity connection. All three can be prepared before the project starts.

### Can we roll out several locations at once?

Yes. After the first location the sequence is established; further sites run in parallel, depending on how quickly location data arrives.

### Who maintains the locations afterwards?

Your location and organization administrators in the Admin Panel. That is exactly what the role model is designed for.

### Do we need a project team?

One project owner plus one responsible person per location is usually enough. A larger team is not necessary; clear ownership is.

## Related pages

- [Support & help](https://doorjames.com/support/)
- [For IT](https://doorjames.com/solutions/it/)
- [Contact](https://doorjames.com/contact/)

---
Door James by CGI · https://doorjames.com · doorjames.support@cgi.com