Help Centre

What is RoleCube?

RoleCube is a workplace role-play trainer. You step into a role at a fictional company, work through a realistic multi-day business problem, and get a manager-style assessment of how you handled it. There’s no lecture and no quiz. You investigate, decide and explain your reasoning, the way you would at work.

Your first hour

• Create an account at app.rolecube.com. RoleCube is invite-only for now, so you enter the access code you were given on that first page (a link that contains a code fills it in for you), then verify your email with the six-digit code we send you.
• Complete your profile. Add a few details about your current role and experience.
• Pick a scenario from Scenarios. Each one shows its role, difficulty and length before you commit.
• Read the briefing. It sets out your role, the business, and what your manager expects. Reading the briefing doesn’t start an attempt, so you can back out.
• Work Day 1. Open documents, run queries, attend the meeting, message stakeholders. Objectives guide you.
• Build your report as you go. It saves automatically as a draft.
• Submit when you’re ready, and read the evaluation properly. The per-criterion breakdown is where the learning is.

Creating an account

You need the access code you were given, an email address, a password and a date of birth. We email you a six-digit verification code. Enter it to activate your account. Codes expire after a few minutes, so if yours has, request another.

I didn’t get the verification code

• Check your spam or junk folder, and any promotions tab.
• Confirm you typed your email address correctly.
• Wait a minute, then use the resend option.
• If your employer filters email, try a personal address, or ask your IT team to allow mail from our sending domain.
• Still nothing? Email info@rolecube.com and we’ll sort it.

I forgot my password

Use “Forgot password?” on the sign-in page. We email you a code to set a new one. We can’t tell you your existing password. Passwords are stored only as an irreversible cryptographic hash, so nobody at RoleCube can read them.

Age requirement

You must be at least 18 to use RoleCube. We check this at sign-up.

Can I share my account?

No. Accounts are personal. Sharing one breaches our Terms and Conditions and makes your evaluation history meaningless.

Deleting your account

Email privacy@rolecube.com from the address on your account and we’ll delete it, with your profile, simulation history, reports and evaluations. If you want a copy of anything first, ask in the same email, because deletion can’t be undone.

You can edit all of these from Profile at any time.

The shape of it

A scenario runs over several simulated days. Each day has a theme and a set of objectives. New material (documents, meetings and stakeholder messages) unlocks as you progress, so the problem reveals itself the way a real one does.

Are the people and companies real?

No. Every company, colleague, document, dataset and meeting is fictional and authored by us. Replies from colleagues are written by AI, working from the scenario’s authored facts and instructed not to add to them.

Objectives

Daily objectives tell you what a competent person in your role would be trying to achieve. They’re guidance, not a checklist you must complete, but incomplete objectives usually mean you have missed something the evaluation will look for. Objectives you don’t finish roll over.

Hints

If you’re stuck, hints are available. Using a hint doesn’t deduct points. Your evaluation records how many you used so you can see how independently you got there. If you would rather not see them at all, turn hint mode off in Profile.

The day timer

Scenarios can run on a simulated clock to create realistic time pressure. You can turn it off, or slow it down, in Profile. Turning it off doesn’t affect your score.

Can I get it wrong?

Yes, and that’s the point. You can pick the wrong root cause, brief the wrong people or submit thin evidence. The evaluation reflects that honestly, and nothing real is at stake.

Does my progress save?

Yes. Your day, clock position, messages, meetings, queries, objectives and report draft are all saved against your active attempt. Close the tab and come back whenever.

Do I need to know SQL?

Basic SELECT statements are enough for most scenarios. The datasets are small and the schema is shown to you. If SQL is new, start with a lower-difficulty scenario, where the data questions are more forgiving.

Your report is what gets assessed. It asks you to commit to:

• a root cause: which hypothesis you think explains the problem;
• a confidence level: how sure you are, honestly;
• a narrative: your reasoning, in your own words;
• a recommendation: what should actually be done;
• a priority and owner: who does it and how urgent it is;
• evidence: the queries that support your conclusion;
• next steps and who to brief.

What makes a strong report

• Argue the causal chain. Don’t just name a cause. Show how it produces the symptoms.
• Attach real evidence. A confident narrative with no query behind it reads as a guess, and is marked as one.
• Address the alternatives. Say why the other plausible causes are not the answer.
• Be specific in your recommendation. A named owner and a concrete action beat a vague direction every time.
• Match your confidence to your evidence. Overclaiming is penalised; so is hedging when the data is clear.

Drafts

Your draft saves to your account automatically as you type, so you can close the tab or carry on from another device and pick up where you left off. Your browser also keeps a backup copy while you write. If a save doesn’t reach us (say your connection drops), the report page restores your latest text from that copy the next time you open it in the same browser. The backup belongs to that one attempt, and it’s removed when you submit or sign out.

Can I edit after submitting?

No. Submission is final for that attempt, which is what makes the assessment mean something. You can run the scenario again. See section 8.

Your evaluation has two layers, and understanding the difference explains most questions people have about their score.

The two are combined into an overall score and grade using weights authored into the scenario. RoleCube does the arithmetic, not the AI. The AI scores individual criteria, and RoleCube combines them using fixed weights, so the AI can’t set your total on its own.

Reading your result

• Per-criterion breakdown. What each criterion asked for, how you scored and why.
• Rationales and quotes. The specific parts of your submission the assessment relied on. This is the most useful part, so read it before the number.
• Expected outcomes. What a strong answer would have covered, and whether you covered it.
• Hints used. This is context, not a penalty.

I think my evaluation is wrong

Ask us to look at it. Email info@rolecube.com with the scenario, the attempt, and what you think was misjudged. A person will review it. You have this right under our Privacy Notice, and we would rather know when the assessment gets something wrong.

Is my score a qualification?

No. A RoleCube score is training feedback. It isn’t a certification, it isn’t recognised by any professional body, and it isn’t a prediction of job performance.

• Running a scenario again. Once you have submitted, use “Do it again” on the scenario in Scenarios. Earlier attempts and their results are kept.
• No restarts part-way through. You can’t restart an attempt that is still in progress. That is deliberate, so every review is a fair read of how you handled the week. Your progress is saved, so you can leave and come back.
• Multiple attempts. Encouraged. Repeating a scenario after reading your feedback is where most of the improvement happens. Some plans limit how many attempts you can start (see the next point).
• Plan limits. If your plan limits what you can start, a scenario you can’t start is marked as locked, with the reason and, where the limit resets, the date. A limit never stops you continuing an attempt you have already started, and every result you already have stays available. If you have no active plan, you can still sign in and read your results, but you can’t start new scenarios.
• Results. Every submitted attempt is available from Results, permanently, at its own address.
• Historical attempts. Opening an old result shows it as it was. It doesn’t inherit the state of a simulation you’re running now.

The full detail is in the Privacy Notice and the AI transparency statement.

RoleCube is currently free. We don’t ask for payment details, and you can’t be charged. If we introduce paid plans, we’ll publish their prices and terms first, and you’ll only ever pay if you choose a plan.

Plans

Every account is on a plan. While RoleCube is invite-only, it’s the plan your access code gives you, and if that plan ends you can still sign in and see your results, but you can’t start new scenarios until you’re on a plan again. A plan can limit how many scenarios or attempts you can start, altogether or within a repeating period, and the product tells you when a limit stops you and when it resets.

Access codes

Creating an account needs a code, and you enter it on the first sign-up page, next to your email, before anything is created. It puts your account on the plan the code names. A code is personal, so please don’t share it, and it can expire, run out of uses or be withdrawn. A code that’s wrong, expired or used up is rejected with a message. Each attempt locks the form for a while (a minute after the first, then longer after each further one), so check the code before retyping it. Many wrong codes from one network in a short time also pause code entry for everyone on it for up to fifteen minutes, or up to an hour if it keeps happening; a correct code never counts towards that. Codes can currently be entered only at sign-up. The full terms are in section 5 of the Terms and Conditions.

Full detail is in the Privacy Notice, the Cookie Policy and the Sub-processors list. Data questions go to privacy@rolecube.com.

• Browser: a current version of Chrome, Edge, Firefox or Safari. Keep it updated.
• JavaScript and cookies: both must be enabled. Blocking our session cookie will prevent sign-in.
• Screen: a desktop or laptop is strongly recommended. The data workspace and report editor are cramped on a phone.
• Audio: needed for meeting playback. Transcripts are always available if you would rather read, or if you turn voice off.
• Network: a normal broadband connection. Corporate firewalls occasionally block our domains, so ask your IT team to allow rolecube.com and app.rolecube.com.

We build for keyboard navigation, screen readers, reduced motion and reflowing layouts, and every meeting has a full transcript so audio is never the only route to the content. The current status, known gaps and how to report a barrier are in our accessibility statement.

If something is hard or impossible for you to use, tell us at info@rolecube.com. Describe what you were trying to do and what stopped you. That’s far more useful to us than a general report.

Support hours: Monday to Friday, 9:00 to 17:00 Gulf Standard Time (UTC+4).