Find your way around Workplace Codex.

Workplace Codex, powered by Workplaced, brings together knowledge about workplace strategy and change. You can explore either subject independently and follow their connections. Support helps you use the Codex: navigate, understand your role and find relevant guidance. Through /support or /nl/support, you can reach ten role pages with manuals and presentations. Method articles, workshops and approved strategy activity materials belong in the knowledge library and on method pages. Reading public guidance does not grant access to a client project; that requires an invitation.

• /

Choose Explore Workplace for guidance about the work environment, research or workplace decisions. Choose Explore Change when your question concerns how new ways of working become usable and sustained. Change also applies beyond relocation, including HR, technology and organisational work. Both entrances connect to the shared library. If your project changes both space and work practices, you may need both perspectives. Start with your actual question, then check each page’s purpose and intended use. Neither entrance is a mandatory course.

• /workplace
• /change-management

Open search from the magnifying glass or Library → Search. Enter a recognisable term, wait for the results and choose a content type such as Method, Workshop, Source or Glossary term. Check that your search term remains after changing a filter. If nothing useful appears, remove filters or try a shorter, more general term. Search matches words; it is not a conversational assistant that understands your project. Open a result and read its purpose before deciding whether it answers your question.

• /search

Open Methods in the library. The index contains 45 workplace methods across six phases: Discover, Define, Design, Deliver, Embed and Recalibrate. Start with a phase or search term, then use available filters such as type, stakeholder or output. Read the purpose and application before choosing material. Clear all removes filters when the selection becomes too narrow. Activity kits support existing methods; a presentation or worksheet does not create another method. Support helps you navigate; the method page remains the substantive starting point.

• /methods

Open Workshops and choose a session by its purpose and required decision. The Change collection contains sixteen sessions, W01 to W16. Search and filter by workplace phase, Change activity, language or duration. These sessions are separate from the 45 methods; some original methods also have Workshop in their title. Check both the workshop ID and title. Read preparation, exercises, follow-up and limitations on the workshop page. Its substantive files belong with that page or Resources, not in general Support downloads.

• /workshops
• /resources

Choose the Support role matching your task: knowledge user, employee, champion, consultant, sponsor, client administrator, editor, partner administrator, educator or platform administrator. On the role page, download the PDF manual and PowerPoint presentation in Dutch or English without logging in. The Dutch consultant manual is not yet available. Each button shows format, language and file size. The material is dated 4 October 2026. You can use several guides; reading them grants no project role or access rights.

In Deploy, you can view My workplace, Programme and Portfolio with fictional projects. Explore project context and phases, and view example news, documents, pulse, worksheets, actions and events. Nothing is actually saved or approved. One login through /login with email and password or Google works for the Codex and Deploy, but does not turn the examples into real client workflows. Use fictional information when trying the demo.

• /experience

It means the function is not yet available. Opening the page does not enable the menu action. On 4 October 2026, fourteen of seventeen main Deploy modules had this label. That historical count is not a completion percentage. Use the demo screens to discuss the intended result. For real work, keep using your organisation’s agreed tools until the function is available. Repeatedly clicking a reserved page will not activate it.

Check the project name and demo label before reading an action or deadline. Where the project selector is available, change the selection and check that the context changes. Examples include relocation and hybrid working, with different practical information. Selecting a demo project is not an invitation to a real client project, and an example deadline does not apply to you. Access to a client project requires an invitation; logging in or choosing an example is not enough.

• /experience/app/medewerker

No. In the demo, selecting a phase only changes the information you view. It does not advance a real project or record sponsor approval. The six workplace phases are Discover, Define, Design, Deliver, Embed and Recalibrate; phases in Deploy remain examples. Read them in their displayed context. A real programme must identify its playbook, version and who may approve a transition. That operational approval is not yet available in the demo.

No. The News page uses fictional examples to show decisions, construction progress and practical arrangements. Read the demo labels. A document marked “Demo: no file” is a placeholder, not a downloadable client document. The certificate example is also fictional and awards no qualification. Use these screens to discuss whether information is clear: what changed, whom it affects and what action is needed. For actual dates, documents and arrangements, use the confirmed channel for your own project.

• /experience/app/nieuws

No. Reading a public role page or guide grants no project role or extra permissions. Role manuals and presentations are available without login, except the Dutch consultant PDF, which is not yet available. Client projects require an invitation. Workshop files also require login and download permission; an administrator grants that permission at /manage/users. A job title, selected role screen or Codex account does not replace those access requirements.

Start on the consultant role page in Support. The English PDF manual and Dutch and English PowerPoint presentations are available without login; the Dutch PDF manual is not yet available. The material is dated 4 October 2026. Then view the Programme demo to explore project context, phase and next decision. Projects are fictional and nothing is actually saved or approved. Find substantive session material through Methods and Workshops, and use the agreed record for real project decisions.

• /experience/app/consultant

First identify the decision or outcome your session must support. On the method or workshop page, check purpose, participants, preparation, duration, exercises and follow-up. Then check the file’s ID, language, version and page references. Strategy activity materials are approved and belong on method pages. W01 to W16 require login and download permission, granted by an administrator at /manage/users. Presentations in Support explain how to use the Codex and do not replace substantive session material.

• /methods
• /workshops

No. The example worksheet in Deploy is not a shared project record: nothing is actually saved or approved. Use fictional information to explore the format. Completing a field does not share a decision with colleagues or send a message to a consultant. Keep real decisions, owners and follow-up dates in the agreed project record. Operational storage, sharing and approval are not yet available in this demo.

• /experience/app/werkblad

The complete project workflow is not yet available. The intended sequence is Question → Decision → Update → Action → Evaluation. A question receives an owner, an authorised person makes the required decision, and current guidance reaches the right audience before people act. Evaluation determines whether follow-up is needed. Publishing already has draft, review, approval and publication stages, but Deploy only shows fictional examples without real storage or approval. For actual project work, agree who handles questions, who decides and where follow-up is recorded.

Portfolio shows fictional projects, decisions and issues needing attention. Editing partner playbooks, assigning consultants and managing licences are not yet available. Download the partner guide and role presentation without logging in from the partner role page in Support, in Dutch or English. The material is dated 4 October 2026. Use it to prepare ownership, permitted uses, languages and version choices. The playbook cards illustrate the intended model. Example partners and figures are not client references or evidence of a commercial agreement.

• /experience/app/partner

No, enrolling learners and assessing work through Academy are not yet available. There is no Academy integration through SCORM, LTI, API or SSO. Prepare learning objectives and assignments, and keep real learning evidence in an agreed secure environment. Distinguish lesson completion, practical submission, assessment and external verification: they mean different things. A fictional certificate in the Deploy demo does not award an IFMEC or other qualification. Discuss the intended workflow and permissions with the learning provider.

Start on the employee role page in Support. Download the guide and presentation without logging in, in Dutch or English; they are dated 4 October 2026. Then explore My workplace in Deploy and check the project name and demo label. Read what is changing, what it means for daily work and which example action is described. The projects are fictional; nothing is actually saved or approved. A client project requires an invitation. A demo action is not a personal instruction or registration.

• /experience/app/medewerker

No, you cannot complete a real action or book an event in the Deploy demo. Actions and events are fictional examples; nothing is actually saved or approved. Reading a deadline, selecting a phase or entering worksheet text is not a booking confirmation. For a real session, follow your organisation's confirmed registration process. A future working process must clearly confirm the result of your action, including errors or unavailable options. The demo does not send a real request or reserve a place.

Ask through your Workplaced contact person or the agreed contact within your project. Submitting and following up questions in Deploy is not yet available. There is no support contact form, email address or ticket system. A fictional demo answer does not address your circumstances. Include the project context and practical question, but share personal or confidential information only through the agreed secure route. The intended connection between a question, owner, answer and follow-up is not yet a working process.

Your text is not actually saved or approved in the Deploy demo. The worksheet is a fictional exercise, not a project record. Any visible input or responding timeline does not establish shared storage, account backup or availability on another device. A completed field also does not mean someone approved your answer. Use only fictional information and do not rely on the demo for real work. Ask your project team which secure environment to use for actual outcomes.

• /experience/app/werkblad

A champion helps colleagues discuss change, prepare sessions and follow up actions. Download the champion guide and presentation without logging in through Support, in Dutch or English, dated 4 October 2026. Strategy materials belong on method pages. Workshop downloads require login and download permission. Agree what the group may decide, who approves and who records outcomes. Being a champion grants no automatic access to personal cases or authority to change policy. The Deploy worksheet is fictional and records no real decisions.

Discuss the unresolved issue through your Workplaced contact person or the agreed project review. Describe the situation, practical effect and what still needs attention. Distinguish a proposal, an approved agreement and an achieved result. Reopening and following up questions in Deploy is not yet available; a completed demo worksheet does not close your real concern. A champion can organise feedback. Decisions outside the team's authority belong with the person responsible for the project or policy.

Start with the sponsor guide and presentation on the sponsor role page in Support, available without login in Dutch and English, dated 4 October 2026. Then explore the Programme demo: identify the outcome, next decision, open questions and accountable person. Phases and milestones do not prove readiness or approval; decisions and charts are fictional. For a real programme, request evidence, uncertainties, consequences and a decision deadline in the agreed project record. The sponsor makes an authorised decision and ensures follow-up; viewing the demo records no decision.

• /experience/app/consultant

No, the Deploy demo does not save real decisions or approve anything. A displayed decision or completed worksheet does not replace authorised approval. Use your project's agreed decision record for real work. A future process must preserve the proposal, evidence, decision-maker, reasoning, conditions and effective date, and connect the decision to reviewed information for its audience. Before use, test approval permissions, corrections and publication with separate roles. Keep drafts visibly distinct from approved decisions.

No, the demo pulse is an illustration, not a readiness score or evidence of project results. The example described provides no response counts, coverage or scale definition. A meaningful report needs a clear question, period, population, response count, scale and relevant comparison before you interpret change. Sponsors should receive appropriate project results and protected aggregates, not unrestricted personal responses. Reporting in Deploy is fictional. Ask the measurement owner to explain the actual data and its limits before using it for a decision.

Prepare the purpose, intended outcomes, locations, groups, languages and responsible people. Identify the sponsor, editor and question owner, and distinguish fixed decisions from open ones. Record the partner, playbook, version and permitted uses. The operational client-project setup process is not yet available; project selection in Deploy is fictional and does not invite employees. Before activation, arrange tested configuration and permissions, clear content ownership and an agreed route for corrections or access problems.

Management of partner assignments and consultant allocations is not yet available. Prepare a bounded assignment granted by an authorised client role, within which the partner assigns consultants. Keep individual project roles and content licences separate. Working for a partner gives no general right to client data or personal cases. Have the administrator record the organisation, project, task and duration. Before operational use, test that an unrelated user and someone whose assignment has ended cannot access information beyond their authority.

Agree how the assignment ends, access is withdrawn and authorised client outputs remain usable. An operational departure and export workflow is not yet available. Keep client decisions and project history separate from partner playbooks and paid learning content. Retaining project results does not automatically grant access to the full partner library; ending an assignment should not erase the agreed client record. Have the administrator confirm your contract's retention, reading and export arrangements before relying on automatic handling.

Yes, publishing in Codex follows draft, review, approval and publication. Administrators add or replace handouts at /manage/handouts: one file at a time, up to 20 MB. They manage sessions at /manage/sessions and view operational status at /manage/operations. This does not make the fictional Deploy news page a working project publication process: nothing is actually saved or approved there. Keep the source, owner, audience, language and effective date with real content. Do not place confidential client information in the demo.

• /experience/app/nieuws

Gather what changed, who is affected, what it means and what action is needed. Check the source and whether information is planned, in progress or confirmed. Record the location or audience, owner, effective date and review date. A photograph or layout cannot replace those facts. Identify open decisions. Codex publication follows draft, review, approval and publication. Deploy project news remains fictional and is not actually saved or approved. Prepare real project information in the agreed secure environment.

Each translation is linked to one source version. After a source change, the translation must be reviewed again. Publishing follows draft, review, approval and publication. During review, check both languages, instructions, links and associated files. The language control changes only the website and does not prove that a file is an up-to-date translation. The role materials are dated 4 October 2026.

No. Support contains guidance on using the Codex, including role manuals, role presentations and practical help. Role files are publicly downloadable, except the Dutch consultant manual, which is not yet available. Workshop files W01 through W16 require sign-in and download permission. Approved strategy activity materials belong with method pages. Internal audit documents and source files are never public. One library therefore does not mean that all content shares the same destination or access rules.

After approval and publication. Role manuals and presentations are already available without signing in through the role pages. The Dutch consultant manual is not yet available. Each download button shows format, language and file size. The materials are dated 4 October 2026 and were released by the owner without a virus scan. Automatic virus scanning is not yet available. Publication therefore does not mean that a file has been automatically scanned for viruses.

Administrators replace a handout at /manage/handouts, one file at a time, with a maximum of 20 MB. Publishing follows draft, review, approval and publication. Check the other language too: a changed source requires another review of its linked translation. Report a FAQ correction through your Workplaced contact, including the page, language and incorrect text. There are no email notifications for new or changed content.

Support offers role manuals as PDFs, role presentations as PowerPoints and practical guidance on using the Codex. The ten role pages offer Dutch and English. You can download role files without signing in; the Dutch consultant manual is not yet available. Buttons show format, language and file size. The materials are dated 4 October 2026. Workshop files and strategy activity materials belong with their subject pages. Internal audit documents and source files are never public.

Look for workshop files with the relevant workshop or through Resources. W01 through W16 require sign-in and download permission, which an administrator grants at /manage/users. Strategy activity materials are approved and belong with method pages, not in Support. This does not confirm that every strategy file is already online. For a missing file, ask your Workplaced contact about availability and include the method or workshop and preferred language.

• /methods
• /workshops
• /resources

The NL/EN control changes only the website. Each file has its own language, shown on its download button. Check that language before opening the file. Role manuals and presentations are publicly available in Dutch and English, except the Dutch consultant manual, which is not yet available. The role materials are dated 4 October 2026. Changing the website language does not translate a downloaded file.

Workshop files W01 through W16 require sign-in and download permission; an administrator grants that permission at /manage/users. Role manuals and presentations can be downloaded without signing in. The Dutch consultant manual is not yet available. Documents in Deploy are fictional examples. Check which type of file you are viewing. If an expected download fails, report the page, title, language and error message through your Workplaced contact. Do not use someone else’s account.

• /resources
• /login

A PDF manual gives practical guidance on using the Codex in your role. A PowerPoint presentation explains that role and its functionality visually. Download either from the role page without signing in, in Dutch or English. The Dutch consultant manual is not yet available. Check the format and language on the button. The materials are dated 4 October 2026 and may describe demo or planned workflows. Internal source files are never public.

Check format, language and file size on the download button, then compare the title, role, version and date in the file. Public role materials are dated 4 October 2026; the Dutch consultant manual is not yet available. A bundle can contain several activities. A page reference then points to part of the same file. Pages 31 through 33 include three pages. If a file differs from an agreed project version, ask your Workplaced contact which version applies.

No. A Codex account does not automatically provide access to a client project; an invitation is required. One login covers the Codex and /experience, using email and password or Google at /login. Role manuals and presentations can be downloaded without signing in, except the Dutch consultant manual, which is not yet available. Workshop files require sign-in and separate download permission. A working login therefore does not mean you can open every project or file.

• /login

Use /login with email and password or Google. If sign-in works but a project does not open, check whether you have an invitation. Workshop downloads require separate permission, granted by an administrator at /manage/users. Record the page, time and error message and ask for help through your Workplaced contact. A support form, support email address and ticket system are not yet available. Do not share a password, recovery code or session link.

• /login

No. Use only fictional information when trying /experience. News, documents, pulse, worksheets, actions, events and phases are examples there; nothing is actually saved or approved. Do not enter employee cases, personal learning evidence or confidential project documents. For real work, use the procedure agreed by your organisation. If you are unsure about appropriate use, speak to your Workplaced contact before sharing confidential information.

No, do not assume anonymity. The pulse in Deploy is a fictional example; no real responses are saved or approved. The "Was this helpful?" button and feedback storage are not yet available. There is therefore no working feedback process from which you can infer anonymity. Before taking part in a real questionnaire, check its privacy information and who may view the answers. Discuss any uncertainty through your Workplaced contact.

• /legal/privacy

No. Technical support does not automatically have access to private project content. Access is only possible through a temporary, recorded authorisation. Arrange the help you need through your Workplaced contact before sharing project content. Share only necessary information, without passwords, tokens or unrelated personal data.

Report it through your Workplaced contact. Record the page address, title, language, time and expected outcome, together with the exact error message or incorrect sentence. Include the file version if relevant. A contact form, support email address and ticket system are not yet available. Remove confidential information from any screenshots and do not share passwords or session links. If the report concerns a real project decision, involve its responsible owner.