TEG Experience client instruction guide

Open the demonstration: https://teg-experience.lovable.app

The PDF shows a screenshot of the opening screen here. Open the opening screen.

Who this guide is for

Prospective clients, programme sponsors, operational leaders, participants and facilitators. Use the demo access code supplied by TEG if the entry screen appears. No live client account is required. Start with the quick start, then use the relevant chapter whenever you need help.

What you are using

TEG Experience is an interactive demonstration using two invented organisations, Northstar Engineering and Harbour Works. The guided workflows show existing foundations, planned releases and future concepts. They do not certify a deployed client system or record genuine client outcomes.

Use invented examples throughout. Do not enter names, personal information, confidential projects or operational details into the demo.

Version 1.0 | 2 October 2026 | TEG Experience

A useful first visit

Take the short tour, play Pulse, inspect your captured evidence and create a reviewed action. Then compare the operational and sponsor views. Finish with the roadmap and programme planner.

Your first successful outcome

You should be able to explain one decision, identify its source, separate a calculation from an interpretation, create an owned action and describe what must be agreed before a real deployment.

1. 1. Open https://teg-experience.lovable.app. If the access screen appears, enter the demo code supplied by TEG and select the entry button. Ask your TEG contact for a code if needed. The homepage then shows the TEG loop and three ways to start. This does not sign you into a live client system.
2. 2. Choose 3-minute highlights for a short introduction, Start guided tour for the seven-step walkthrough, or Explore demo freely to go directly to the workspace.
3. 3. In the workspace, leave Organisation as Northstar Engineering and Cohort as All cohorts for your first visit. Leave the reporting threshold at its default of 5.
4. 4. Use Next and Back in the tour panel. Use Show presenter notes for extra context. End tour closes the tour without resetting your exploration.
5. 5. Open Pulse decision from the navigation and play the three rounds. Allow about 10 to 15 minutes for the fuller exercise, depending on your discussion.
6. 6. At the end, select Review captured demo evidence. Write a short debrief, mark it reviewed and create an action with an owner and date.
7. 7. Explore the other sections using this guide. Select Reset demo before a new independent trial if you want the original examples back.

What to expect

The short tour is an orientation, not the time needed to complete every workflow. The full experience is deliberately exploratory. You can stop, revisit a chapter and use the seeded examples even if you skip Pulse.

Check: the label “Interactive demonstration · fictional data” should remain visible. The demo may request a TEG-supplied demo access code. It should never request payment or a live client password.

Existing foundation

TEG workshops and facilitated interventions, Pulse-style scenario decisions, confidence and team debrief, and Insight forms and session-reporting concepts exist. Client deployment still needs agreed configuration and acceptance. This label does not mean that every screen in this separate demo is already operating in a client environment.

Planned release

The demo implements intended behaviour for traceability, leadership views, commitment history, Academy handoff and follow-up. Treat these interactions as a working illustration of the proposed release, not a contractual statement of production availability.

Future concept

AI-assisted interpretation and coaching, approved operational feeds, governed benchmarking and richer Academy integration are future possibilities. They depend on commissioning, governance and validation. The AI coaching example is prewritten and does not call an AI service.

The fictional programme

Northstar Engineering and Harbour Works, their teams, records, dates, capacities and outcomes are invented. Your Pulse choices are genuinely captured within the demonstration, but their consequences are scenario illustrations. Seeded programme results are not evidence of effectiveness for a real client.

Buttons with important names

Publish to demo report, Approve and publish (demo) and Approve snapshot save local demonstration states. They do not email, share or distribute a report. Mark commissioned illustrates a referral status; it does not book or buy support.

The bridge is a local simulator. Its “Reconciled” status is not a health check of the live TEGpulse or TEGinsight systems.

• Organisation: changes the fictional programme and its seeded records. Choose the organisation before starting a Pulse run. Switching organisations is an illustrative filter, not proof of access control.
• Cohort: selects All cohorts or a named team for applicable measures and comparisons. Some programme commitments and interventions remain at organisation level. Always check a panel’s own scope rather than assuming every item is filtered to a team.
• View: sets an illustrative audience context. It is not a login or permission role. To open a specific leadership screen, use Operational leader or Strategic sponsor in the navigation.
• Sector: lets you adjust the fictional discussion context. Use a general sector description; it does not regenerate scenarios or connect a real organisation.
• Presentation mode: hides navigation and filters while keeping capability and fictional-data labels. Select Exit presentation to restore the workspace. On smaller screens, use Open menu to reach sections.

What is saved

Completed Pulse runs saved through Review captured demo evidence, reviewed debriefs, linked commitments, appended notes, review states, referrals, snapshots, check-ins and demo settings are held in this browser tab’s session storage. They are not a shared client workspace and do not appear automatically on another device.

Unfinished Pulse rounds, unsaved form fields, an editable sponsor-summary draft, planner inputs and practice reflections may be lost when you leave their screen or reload. Complete the relevant save action, or download a brief, before leaving.

Start again

Select Reset demo, read the confirmation and select Reset demo again. It restores the seeded examples and clears saved demo changes and settings in that tab. Cancel keeps your work. Downloaded files remain on your device after reset. Do not rely on tab closure as a secure deletion procedure.

1. 1. Check the organisation, sector, programme name and ID. For your first visit, use Northstar Engineering and All cohorts.
2. 2. Read the Priorities, Decisions required, Evidence coverage, Open commitments and Next review summary items.
3. 3. Select a priorities or decisions item to open Operational leader. Select open commitments to reach the shared register. Select next review to open the repeat-measurement section.
4. 4. Select Evidence coverage to inspect its source. Coverage describes usable fictional responses for the selected measurement; it does not measure the quality of an entire programme.
5. 5. Read the Programme timeline. Distinguish measured phases from scheduled phases and delivered interventions from missed ones. The example dates are fixed fictional records, not a live calendar.
6. 6. Under Measures at 60 days, select a value to open its evidence panel. Team values and the All column can have different sample sizes and reporting eligibility.
7. 7. Read the audience focus and decisions waiting below the measures. The View selector changes this illustrative focus. It does not change authenticated permissions or automatically navigate to a leadership page.

Questions to ask at the start

• What is the programme trying to change, and what decision needs attention?
• What evidence is already available, and what is scheduled or missing?
• Which client or TEG commitment needs the next action?

Explore a second programme

Switch Organisation to Harbour Works and compare the safe-handover story. It has different cohorts, priorities and sample sizes. Return to Northstar for the worked exercises in this guide.

Check: you can navigate from an overview item to its detailed section and return using Overview or the programme breadcrumb.

1. 1. Leave the Participant tab selected. Read the situation, constraints and stakeholders before choosing.
2. 2. Select one of the three decisions. Consider who owns the trade-off, what information is missing and when escalation is appropriate.
3. 3. Select your confidence from 1 to 5. One means not at all confident; five means very confident. Confidence describes how sure you feel, not whether your decision is correct.
4. 4. Optionally enter a short Rationale explaining why. Use an invented example. A blank rationale is recorded as absent rather than fabricated.
5. 5. Select Commit decision. A choice and confidence are both required. The controls lock and the simulated consequence appears.
6. 6. Read the consequence, stakeholder constraint and debrief prompt. Select Next round for rounds one and two.
7. 7. After committing round three, read its consequence and select See debrief. The three choices and their confidence are shown together.
8. 8. Select Review captured demo evidence to save the run and open its evidence panel. This is the step that carries your completed exercise into the next workflow.

How to read the outcome

An escalation can be sound judgement even when the fallback is not used. A faster decision is not necessarily better. Discuss the context and decision ownership rather than trying to identify a universally correct answer.

Replay and facilitator view

Replay from round 1 starts another attempt. Saving a new attempt replaces the latest captured run; it does not add your results to seeded cohort figures. Commitments already created remain in the register until reset. Facilitator view shows a script, prompts and a seeded team feed. That feed is not live multi-user activity.

1. 1. Check the run number and date. Under Evidence lineage, identify your Pulse choices and the separate event ID for each round.
2. 2. Read the captured choices, confidence and rationale. Your values should match what you entered. They are separate from programme aggregates.
3. 3. In Debrief draft, write a short explanation of what you learned. Use at least 10 characters. Describe the decision process and an appropriate next step, not a judgement about a person.
4. 4. Select Mark debrief reviewed after reading your draft. In a real delivery, this would be done by the agreed human reviewer. Here you are trying the reviewer’s interaction.
5. 5. Under Agreed action, complete Action, Owner (role) and Due. Use a role such as Programme lead, not a named person.
6. 6. Select Create linked commitment. The action is now associated with the run and its event IDs. The lineage should show the commitment ID instead of “Not created”.
7. 7. Follow the commitment link to Agreed and happened. The new record belongs to the organisation under which you played Pulse.

A worked example

Debrief: “We asked for missing information before mobilisation and brought options to the decision owner. We need an agreed route for interface decisions.”

Action: “Agree the decision owner before the next interface meeting.” Owner: “Programme lead”. Choose a demonstration due date in the date picker.

If a control is unavailable

Review requires a sufficiently long debrief. Action creation requires a reviewed debrief and all three action fields. Once the linked commitment exists, use the register to manage it. The exercise produces no diagnosis, individual ranking or new aggregate score.

The four evidence tabs

• Raw evidence: shows source activity, session date, scenario version, cohort and available fictional response rows. Rows are withheld when the reporting threshold is not met.
• Derived measure: shows the formula, sample size, coverage, missing evidence and calculation version. Select a figure to understand its origin before interpreting it.
• Interpretation: separates the proposed meaning from arithmetic, identifies a reviewer and gives an alternative explanation. A bare measure can have no reviewed interpretation yet.
• Action: shows a proposed next step and any linked commitment. For eligible findings, it also offers Mark reviewed followed by Publish to demo report.

Add context without overwriting the source

1. 1. Open a finding and select Interpretation.
2. 2. Under Challenge or add context, choose Challenge or Context.
3. 3. Enter an invented note, such as “A planned clinic was missed; consider that alongside the repeat result.” Select Add.
4. 4. Check that the appended note appears with its type and date. The original record is preserved.

Review and local publication

Read the source, formula, interpretation and alternative explanation before marking a finding reviewed. Open Action, select Mark reviewed, then Publish to demo report. Publication is local to this demonstration. It does not distribute a client report or authenticate you as a reviewer.

If the evidence is insufficient, awaiting a repeat measure or no longer supports the written narrative, the interpretation is withheld and supported-evidence review/publication is unavailable. Do not lower the threshold simply to obtain the desired conclusion.

Try it: open F-NS-01 with Northstar selected and threshold 5. Follow the source from scenario responses through calculation, interpretation and action.

Three measures shown in the demonstration

• Escalation timing met scenario rubric: qualifying non-null responses divided by usable responses, multiplied by 100. The rubric represents agreed judgement for that scenario; it is not a universal rule that earlier escalation is always better.
• Cross-functional information sought before committing: qualifying non-null responses divided by usable responses, multiplied by 100.
• Mean stated decision confidence: the average of the usable 1-to-5 confidence ratings. Missing ratings are excluded. Higher confidence alone is not evidence of better judgement.

Sample size and coverage

n is the usable response count for the particular measure. It can differ between measures because a confidence answer may be missing while a decision is present. Coverage compares usable responses with the invited cohort.

For example, seven qualifying responses out of eight usable responses give 87.5%. If eight people were invited and only seven provided a usable value, n is seven; the missing response is not replaced with a plausible score.

Two different gaps

Insufficient data means usable responses are below the chosen reporting threshold. Awaiting repeat measure means the scheduled phase has no measured result yet. Neither means zero performance or failure. Charts leave these points without a value.

Change the threshold for an illustration

Open Demo settings and adjust Group reporting threshold from its default 5 within the range 3 to 8. At 6, Northstar’s F-NS-03 is withheld because its required 60-day measures have only five usable responses. Restore 5 for the main examples.

The threshold is a governance decision, not a guarantee of anonymity. “Supported inference” means a reading supported by the example records; “Anecdotal” means contextual evidence without the same quantitative support; “Not yet measured” means the necessary evidence is unavailable. “Proven within this demo dataset” applies only to the arithmetic.

1. 1. Confirm the fictional organisation and programme in the header.
2. 2. Read Attention this week. Distinguish priorities, decisions waiting and blockers. Note the role owner and due date for each.
3. 3. Select an item to inspect its context or evidence link. If it links to a finding, check the source before accepting the recommendation.
4. 4. Read Work movement. The count describes completed example records, not a financial saving or a proven business outcome.
5. 5. Review delivered interventions, upcoming reviews and TEG commitments to you. A missed TEG intervention is part of the delivery story and should be addressed.
6. 6. In Actions, enter an invented action, a role owner and a due date. Choose Client or TEG in Side, then select Add.
7. 7. Check the action in the commitments register. Use that record to manage its status, completion evidence and history.

Questions this view should help answer

• What decision is waiting, and who is entitled to make it?
• What is blocking application at work, and what evidence supports that reading?
• What did TEG agree to deliver, and what needs recovery?
• What is the next owned action rather than another observation?

A useful second context

Switch to Harbour Works and inspect the handover priorities. The context changes to marine and port maintenance. This demonstrates a different programme story; it does not access another client’s data.

Check: a new action has a clear verb, role owner, due date and accountable side. For a real deployment, reporting and access arrangements would be agreed with the client.

1. 1. Read Agreed outcomes, Rollout readiness and risk and Next decision before looking at the chart.
2. 2. Choose a measure above Baseline vs follow-up. Use the cohort selector for the relevant comparison scope.
3. 3. Select a chart point to inspect its source. Check the sample size, phase, scenario family and calculation version.
4. 4. Read Cohort patterns. Rubric measures can show improving, declining or stagnating arithmetic movement. Confidence uses neutral wording such as “higher stated confidence”. Unavailable comparisons are identified.
5. 5. Read the Review summary draft. You can edit its text to try the review process. Keep invented evidence, caveats and alternative explanations visible.
6. 6. Regenerate from data discards your draft edits and rebuilds the text from the current demonstration figures.
7. 7. Approve and publish (demo) saves a local sponsor snapshot. It does not send the summary to colleagues or create a live production report.

When scope changes

Changing the organisation, cohort or reporting threshold rebuilds the summary for the new context. Draft wording written for the old context should not be reused without review. Unsaved edits can also be lost when leaving the page.

Read movement carefully

Changing attendance can affect a comparison. Missing answers must remain visible. An intervention followed by a change does not establish that the intervention caused it. The same caution applies to a scenario result and a workplace application record.

Use the sponsor view to decide what evidence is sufficient for the next step, what remains unknown and what should be measured next. Do not use it to rank people, diagnose traits or promise a return on investment.

Check: you can identify the source and n for a plotted value and explain the evidence gap at the scheduled 90-day phase.

1. 1. Use All, Client or TEG to inspect the relevant records. Review owner, agreed date, due date, status, evidence, variance, next review and version.
2. 2. Select a commitment ID to open its panel. A commitment created from your Pulse run also carries the run and event links.
3. 3. To change status, select Status. Choose Open, In progress, Complete, Missed or Recovering as appropriate to your fictional example.
4. 4. If choosing Complete, enter Completion evidence. A status alone is not enough. For example, use “Fictional meeting record confirms the escalation route was agreed.”
5. 5. To change Due date, enter the new date and the requested reason for the change. The previous date and reason are retained in version history.
6. 6. Record any Variance or recovery action, then select Save new version. Check that the version number and history update.

Add a commitment

Use Add a commitment below the register. Enter the action, role owner and due date; choose the accountable Side and select Add. An action should describe what will actually be done, not only a desired outcome.

Keep an approved snapshot

Select Approve snapshot to preserve the register as it stands. Make a subsequent example change and inspect Amendments since approval. The approved copy remains intact; later changes are shown rather than silently rewriting the original agreement.

Export and delivery accountability

Export register (JSON) downloads a labelled demonstration file. JSON is a structured data format, not a polished client report. The planned-versus-delivered section includes a missed TEG clinic and its recovery commitment, so accountability applies to TEG as well as the client.

Check: completion has evidence, a due-date change has a reason, and an approved snapshot has a visible amendment after a later update.

Choose an appropriate pathway

Inspect the objective, format and follow-up on each card: Digital pathway, Behaviour clinic (group), Development pod (4–6), Individual support, Manager reinforcement, Team intervention and Specialist referral. Displayed slots and availability are fictional examples, not bookings or current capacity commitments.

Try the referral workflow

1. 1. First inspect an eligible finding in Evidence explorer. Review its source, context and next action. Mark it reviewed if appropriate to your demonstration.
2. 2. Return to Academy. Under Propose a demo referral, select the relevant finding and Pathway. The selector uses reportable findings; a finding can still be a draft, so inspect its review status.
3. 3. Select Propose referral. A local record appears with status Proposed. This does not automatically assign an individual.
4. 4. Try Approve (reviewer), then Start scoping, then Mark commissioned to explore the intended stages. All are simulated local state changes; none creates a purchase or schedules delivery.

Try the constructive challenge exercise

Read the meeting situation, choose a response and read the contextual feedback. Optionally write a reflection using fictional details. That reflection is a practice field, not a submitted assessment, and may be lost when leaving the page.

The future practice coach

The displayed participant and coach conversation is scripted. There is no live AI conversation, free-text AI response or automated diagnosis. Do not treat it as wellbeing, clinical or legal advice.

Additional support would be scoped and commissioned separately in a real programme. Individual support needs agreement with the person and appropriate manager; a game score is not a basis for assigning it. Specialist needs can require a suitable provider outside TEG.

1. 1. Confirm the organisation and cohort scope. Use Baseline, 30 days, 60 days or 90 days, or move Scrub review timeline to the relevant phase.
2. 2. Check the displayed session ID, date and measured or scheduled status. These are fictional programme dates; the phases illustrate intended review checkpoints.
3. 3. Read Repeat measures vs baseline. Select a value to inspect its source. Check both n and coverage before drawing a comparison.
4. 4. Read In this period. Distinguish delivered interventions, workplace application records and commitments due. Scenario measurement and workplace evidence answer different questions.
5. 5. In Check-in note, enter an invented observation and select Add check-in. The note is associated with the selected organisation and phase.
6. 6. Select Download demo summary (text) before leaving if you want a portable record of the selected scope, phase and threshold.

What an honest gap looks like

At Northstar’s scheduled 90-day phase, the measures show Awaiting repeat measure. No performance value or completed progress interpretation is invented. Where workplace records are absent, the screen identifies the missing follow-up rather than claiming no application occurred.

A good review question

Ask “What did we agree, what was delivered, what was applied and what can we compare?” Then identify the next measurement or action needed. A self-reported application record is useful context but is not by itself proof that TEG caused an outcome.

The downloadable summary is a fictional-data demonstration export. The progress-summary panel explains the need for human review; it does not mean that a live client approval workflow has been completed.

Check: you can tell the difference between a completed measure, insufficient responses, a scheduled phase and missing application evidence.

Read the intended handling requirements

The cards cover canonical client and cohort identity, agreed access, separation of raw and reviewed evidence, challenge, logging, controlled environments, backup and recovery, retention, export and offboarding. They are requirements to agree and implement, not a security certification.

Run the six fictional events

1. 1. Select Simulate normal run. Observe the progression to Reconciled with six expected and six received events.
2. 2. Select Connection failure. The simulator drops the connection after three events and shows Partial.
3. 3. Select Retry. All six valid events are reconciled; the three already received are counted as duplicates ignored, rather than added again.
4. 4. Select Duplicate delivery. Six events are received once and the repeated six are ignored.
5. 5. Select Wrong routing. Inspect the rejection entries for the wrong organisation and a test event routed to production. The six valid events can still reconcile while rejected events are separately shown.
6. 6. Read Demo audit history and the attempt details. These explain the local actions taken in this tab.

What the statuses mean

Pending means not yet sent. Sending means an attempt is in progress. Partial means fewer valid events arrived than expected. Retry is another attempt. Reconciled means the expected valid fictional events are present. Duplicate and rejected counts must still be inspected.

Controls can be temporarily disabled while an attempt runs. Wait for it to finish before the next test. “Test” and “production” are routing labels on fake events, not connections to those environments.

No live bridge is contacted. A real deployment needs tenant-bound authentication, isolation tests, logging and operational monitoring.

1. 1. Choose Leadership cohort 13, Department rollout 60 or Phased organisation 560. These are hypothetical templates, not named client commitments.
2. 2. Enter a general Sector and an invented Business problem. Avoid confidential details.
3. 3. Set Initial cohort size and Total phased population. Total population is everyone enrolled over time; it is not simultaneous system use.
4. 4. Set Simultaneous participants, repeat measures after baseline, facilitator capacity and cadence. Consider what the delivery team could support in parallel.
5. 5. Adjust Support demand assumption. It is a planning assumption, not an assessment of how many people actually need support.
6. 6. Read the visible arithmetic and Your demonstration brief. Check the hosting, access, measures and next-step questions.
7. 7. Select Download brief (text) or Download JSON before leaving. Planner edits are screen-local and can reset when you leave or reload.

Read the arithmetic

Cohorts round total population divided by cohort size up to a whole number. Concurrent waves round population divided by simultaneous participants up. Sessions equal cohorts multiplied by baseline plus repeat measures. Sessions per facilitator are an approximate distribution, not a timetable.

For the 560 template: 20 per cohort gives 28 cohorts; 80 simultaneous participants gives seven waves; baseline plus three repeats gives 112 sessions; four facilitators gives about 28 sessions each. At a 20% support assumption, potential demand is about 112 people.

Cycle length is cadence multiplied by repeats for a cohort cycle. It does not include staggered enrolment, scheduling delays, preparation, travel or support delivery. The planner does not prove technical capacity for that load.

Check: the brief distinguishes total enrolment, simultaneous use, facilitation and separately commissioned Academy support.

1. 1. Use All, Existing foundation, Planned release or Future concept to filter the cards.
2. 2. Select a capability. Read What you get, What must be true, How it is delivered and its dependencies.
3. 3. Follow the dependencies conceptually. Improved evidence provenance and agreed metrics support leadership reporting; tenant-bound integration and agreed deployment support operational feeds and governed benchmarking.
4. 4. Close the detail panel and open What would we do first for you? Open the planner to shape a discussion brief.

Future capabilities to explore

• AI-assisted interpretation produces drafts for human review, subject to validation and consent.
• A contextual AI practice coach would support development, subject to practitioner oversight and agreed use.
• Approved operational feeds would connect relevant client evidence after integration and access are agreed.
• Governed anonymised benchmarking would require a suitable purpose, participation, permissions and methods.
• Fuller Academy integration would connect agreed support and follow-up without implying unlimited coaching.

Agree a useful first step

Start with one programme, one cohort and the decisions the evidence should inform. Agree the scenario and rubric, measure a baseline, review the first evidence together and create owned commitments. Expand scope when configuration, evidence quality, access and delivery arrangements have been accepted.

The roadmap does not give committed release dates or completion percentages. Confirm the delivery scope, responsibilities and acceptance criteria with TEG before relying on a planned or future capability.

1. 1. Play Pulse using any decisions. Choose different confidence levels so you can recognise them in the captured evidence. Save with Review captured demo evidence.
2. 2. Find your three event IDs. Write a debrief, mark it reviewed and create a linked commitment with a role owner and due date. Check the link in the lineage.
3. 3. In Evidence explorer, open F-NS-01. Explain which part is raw evidence, which is a calculation and which is an interpretation. Add a fictional context note.
4. 4. Open the sponsor view. Select a chart point and identify its sample size. Explain why higher confidence is not the same as a better decision.
5. 5. In the commitments register, approve a snapshot. Change a due date with a reason, save the new version and find the amendment. Mark an action complete only with completion evidence.
6. 6. Explore an Academy referral and the constructive-challenge practice. Explain why Mark commissioned does not book support.
7. 7. Open the 90-day review and identify the unmeasured evidence. Try connection failure and retry in Delivery and trust.
8. 8. Raise the threshold to 6 in Demo settings. Open F-NS-03 and confirm that its quantitative interpretation is withheld. Then restore 5.
9. 9. Build and download a hypothetical planner brief. Identify one existing foundation, one planned release and one future concept in the roadmap.

You are ready to explore independently when

You can find a source, understand n and missing evidence, create an owned action, preserve a change history and explain which capabilities still need agreement for deployment. You do not need to master every screen before discussing a first programme.

Select Reset demo when you want to return to the original examples. Downloads are not removed by reset.

A button is grey or unavailable

Pulse needs a decision and confidence. Debrief review needs at least 10 characters. A linked action needs a reviewed debrief, action, owner and date. Completion needs evidence; a due-date change needs a reason. Supported-evidence approval is unavailable when its source is insufficient or awaiting. Simulator controls can be disabled during an attempt.

A figure or interpretation has disappeared

Check organisation, cohort, phase and reporting threshold. A change of scope can reduce n or make a narrative unsupported. Restore the intended context, but do not lower a threshold simply to reveal a desired result. “Awaiting” is a genuine gap in the fictional programme.

The navigation has disappeared

Select Exit presentation if presentation mode is active. On a smaller screen, select Open menu. Close an evidence panel with Close before trying controls behind it. End the tour if its panel is obscuring an item.

My entries are missing

Check that you are in the same tab and organisation. Only the latest saved Pulse run is retained; unsaved screen fields can be lost. Completed local states are not synchronised with another person or device. Reset clears them. A downloaded file is independent of browser state.

A download does not appear

Check the browser’s downloads list and download permissions. Retry the labelled download control. The planner also shows the brief on screen, so you can copy the fictional text if necessary. JSON opens as structured text and is not a formatted report.

The page does not load or asks for an access code

Check the demo link on page 1 and your internet connection. Use the published demo rather than the Lovable editing link. An access-code screen is expected: enter the code supplied by TEG. If you have no code or it is rejected, contact the TEG person who supplied the link. Do not use a live client password. Reload once for a loading error; there is no in-app support desk or promised response time.

When asking for help, provide the section URL, fictional organisation/cohort, the action attempted and error wording. A screenshot can help, but remove personal or confidential information. Do not send passwords or authentication tokens.

Purpose and measurement

• The programme problem, decisions to inform, agreed outcomes, cohort definitions and scenario/rubric.
• Baseline and repeat cadence, what counts as workplace application, how missing evidence is handled and who reviews interpretations.

People and responsibilities

• Programme sponsor, operational owner, facilitator, reviewer and support contact.
• Who can see raw evidence, team aggregates, interpretations and reports; how access is granted and removed.

Data and deployment

• Canonical organisation and programme identity, hosting requirements and approved integration routes.
• Reporting threshold, retention, export, offboarding, backup and recovery arrangements.
• Privacy, security and any client governance requirements, verified against the actual deployed implementation.

Delivery and acceptance

• Client and TEG commitments, capacity, support scope, review dates and recovery responsibilities.
• Authentication and access tests, isolation checks, evidence/calculation checks, end-to-end dry run and recovery verification.
• Which capabilities are included now, which are planned and which need further commissioning.

Your next discussion with TEG

Bring the demonstration brief and your questions. Start with one agreed programme and cohort. A real deployment guide should then identify the actual client URL, login process, role permissions, named support arrangements and approved operational procedures.

This guide describes the public fictional demonstration. It should not be used as the login, security, backup or support procedure for a live client deployment.

• Action: an owned next step with a due date. Commitment: an agreed obligation whose delivery, evidence and changes are tracked.
• Baseline: the initial measure used for comparison. Repeat measure: a later comparable measurement, rather than an assumed improvement.
• Cohort: the agreed group being considered. Scope: the organisation, cohort, phase and measure relevant to a displayed result.
• Raw evidence: recorded inputs. Derived measure: a calculation from those inputs. Interpretation: a human reading of what the evidence may mean.
• Rubric: an agreed set of criteria for the particular scenario. Confidence: how sure a respondent says they are, not a correctness score.
• n: the usable response count for a measure. Coverage: usable responses relative to invited participants. Threshold: the minimum usable count chosen for reporting.
• Null: no recorded value. Proven within this demo dataset: the arithmetic can be reproduced from the fictional records, not proof of real-world impact.
• Snapshot: a preserved approved version. Amendment: a recorded change after that version. Lineage: the trail connecting a decision, event, finding and action.
• Reconciled: the expected valid simulator events are present. Idempotent delivery: repeating an event does not create an extra record.

Direct links

Home and tours | Programme overview | Pulse decision | Evidence explorer

Operational leader | Strategic sponsor | Agreed and happened

Academy | Repeat review | Delivery and trust

Planner | Roadmap | Presentation help | Demo settings

For assistance: contact the TEG person who supplied your demonstration link.