Autosave isn't working in this browser. The browser has refused to store your changes (its storage may be full or blocked), so they live in memory only and vanish when you close this tab. Save my data now, and again before you close; Load my data restores it.
You're using Safari. Safari clears what a website has stored - including this Studio's autosave and version history - after seven days of Safari use without a visit to the site (Apple's own rule, from WebKit's 2020 tracking-protection update). A backup file in a folder that syncs (Dropbox, OneDrive or Google Drive) is the only copy Safari can't clear.
Earlier versions can't be kept in this browser. It has refused the storage the Studio uses for them - it may be blocked in the browser's settings. The Studio can't tell whether this is a private window, where everything it stores goes when the window closes, so Save my data before you close it.
This browser's storage is filling up.
Nice first session. Save my data now so your work survives even if this browser's storage is cleared or you switch machines.
Research Studio is open in another tab or window. Two open copies save over each other's changes, and an older version left open can strip your plan. Close one of them, then reload the other so it starts from what was saved last.
This tab has stopped saving. The browser now has a different project open, and saving from here could overwrite it - so what you type in this tab is not being saved to this project. Save my data makes a backup file of what is in this tab, and Version history keeps a copy where this browser allows it. Reload this page to carry on with this project here - the other tab then stops saving instead. Use Projects to switch between projects.
To do: add your name in Settings - it's shown on every document you export for your supervisor.
Your research project plan
Weighted totals out of 100, using your criteria weights - a 100-point budget set in Settings. Score ideas from their detail view.
◔
Add a journal entry
Record decisions, changes of mind, insights and tutor feedback as they happen. This journal - with the idea histories - is the raw material for analysing your development process later. Copy your Project summary into your own project log at the end of each working session.
Prompts to reflect on. The questions programmes ask in a reflective log - answer any of them, in your own words.
Supervision meetings
A record of each meeting with your supervisor: what you planned to cover, what was decided, who does what by when, and when you meet next. Your own record - your institution's forms and rules decide what you must keep.What never goes in here: anything about a participant or anyone else - only your supervisors' names, dates and the work.
AI use log
A running record of the AI tools you use for your project: what you asked, what came back, how you used it and how you checked it. It is your own record - your institution's rules and declaration form decide what you must submit. Keep participants' personal data out of it.
By switching this on, you agree that your AI use log may hold health or other sensitive details about you, and that it is kept on the Studio's server for your account in this team, where only you can read it in the Studio; a look by the Studio's operator is written into your own records first and shown to you. Switch it on in each browser whose log you want kept there. Switching it off in any browser deletes that copy; the log in each browser stays.
Project setup
Tell the Studio about your project and the course it's for - by hand, with any AI chatbot, or both. Your plan, deadlines, checklist and User Guide follow what you save here, and nothing changes until you press Save setup.
Project templates
Set up the project for your course once - phases, tasks, deadlines, assessment and course rules - choose what students may change, then give them the template. They load it in Project setup, and every student starts from the same plan.
Template details
What students see when they load it, and on the instructions sheet that comes with it.
User Guide
Start here
This guide has a tab for each chapter, and the same guide as a formatted PDF - Download PDF, in the header. Project setup is the next chapter: everything else in the Studio follows from it.
The welcome page
The Studio opens with a welcome page: what it does for universities, programme directors, lecturers and students, each on its own tab, then every part of the Studio in one view. Open the Studio, at the top or the foot of the page, closes it; on the Students tab, Start with Guided setup closes it and opens Guided setup. Tick Don't show this again beside either button and the Studio opens straight to your work from then on - the choice is kept in this browser only, never in your saved data. The Welcome button, beside the Studio's name at the top left, opens it again at any time, and so does Show the welcome page, at the end of this chapter or in Settings.
To send the page to someone, add #welcome to the end of the Studio's address: it opens the page even for someone who has chosen not to see it. #welcome-universities, #welcome-directors, #welcome-lecturers and #welcome-students open it on that tab.
How this guide works
Chapters. The tabs along the top are the chapters. Click one, or press the left and right arrow keys once a tab has focus - Home and End go to the first and the last. When they don't all fit, the row scrolls sideways. A chapter with several headings has an On this page list beside it that jumps to each one.
Your setup shapes it. Project setup is the second chapter. While your plan follows a setup of your own, the guide adds a chapter about your project and course, and leaves out the chapters written for one particular course - unless your setup started from that course's own plan path, which keeps them. Switch back to the built-in preset and the guide goes back to how it was.
The PDF (Portable Document Format). Download PDF, in the header of this window, saves the whole guide as a formatted file: a cover with the version number, a contents page whose entries link to each chapter and heading, bookmarks, and page numbers. Open PDF to print shows the same file in a new tab, ready for your browser's print button. The Studio builds it on your computer from the chapters you see here, so it always matches your setup, and nothing is sent anywhere. The file lists the latest ten versions in Version history; the tab lists every one.
After an update. The See the version table link in the update banner opens this guide at Version history.
The sources behind the Studio. The guidelines chapter lists the national frameworks, institutional rules and good-practice codes the Studio's advice draws on, each with who issued it, its version, its date and a link to the original. Download these references (.ris) saves them for Zotero or another reference manager - .ris is the Research Information Systems format they all read.
Project setup
The Project setup tab fits the Studio to your project and your course: institution, programme, what you call the project, dates, phases, tasks, deliverables, assessment criteria, course rules and thematic areas. Your plan, deadlines, checklist and this guide follow what you save there.
Guided setup
Guided setup walks you through setting up a project in a window of its own. It opens by itself once for a project you haven't started working on - after the welcome page - and you can open it any time from the Guided setup link beside the course line on the Plan, at the top of Project setup, or in Settings. Tick Don't open this by itself on its opening screen to stop the automatic opening in this browser; the links still open it. Every route into a new project leads here too: on the welcome page, the Students tab's Start with Guided setup opens it, and in Your projects, New blank project opens it at its opening screen and New from a plan path or template opens it at its Template step - even with Don't open this by itself ticked, with no welcome page in front of it.
The steps are listed along the top, and you can jump to any of them: the opening screen; Template, where you choose the plan path closest to your project or load the project template your lecturer gave you; then five sets of questions - About you (your name, student number and email), Your course and project (institution, programme, what you call the project, its name), Your dates and deadlines (start and submission dates, and up to six deliverables with their due dates), Your supervisor (names, how often you meet, emails) and Your topic (a working title, a research question and why it interests you - which makes your first idea on the Ideate tab - and whether it is your main direction); then Your course documents; and Check and save. A box beside each step, Agreed so far, shows what you have answered.
Nothing has to be answered. Your name, student number, email, project name, supervisor emails and the first-meeting answers are saved as you type, exactly as Settings and the first-meeting checklist save them. Everything else - the plan path, institution, programme, dates and deliverables, and the documents - waits in Project setup's working copy, and nothing reaches your plan until Save my setup on the last step, which does what Save setup does in Project setup and so still waits until everything under Needs your decision is settled. A plan path chosen over a plan you haven't changed replaces it at once; over a plan you have changed, the window shows the same choice Project setup does. Change your dates while the plan is still as the Studio set it up and its phases refit to your weeks; if you have changed the plan, the window tells you to pick your template again in Project setup. Anything your lecturer's template locks is shown read-only.
Prefer to speak? Under the first box of the question steps there is a line pointing to your device's own dictation: on a Mac, press Fn (Globe) twice; on Windows, press the Windows key + H; on a phone or tablet, use the microphone on your keyboard. The Studio doesn't listen itself and never asks your browser for the microphone.
Which plan you follow
The line under the title of Project setup says which plan you follow. A new workspace follows the built-in course preset until you save a setup of your own. After that a buttonA new project starts on General research project, saved for you as a setup of your own - the line shows it as your Plan path. Change any phase, task or date, or pick another plan path, then save. The built-in course preset stays available, and a button beside the line switches between the two at once and deletes nothing - Use my project setup while the preset is in force, and a button back to the preset while your own setup is. Each keeps its own start and submission dates and its own progress, so you find each as you left it. The dates on this tab always belong to your setup; Settings changes the dates of whichever plan you follow at the time.
Start from your lecturer's template
If your lecturer gave you a project template, load it first, under From your lecturer - the .zip, or the .json inside it: what your lecturer set shows read-only, with a lock and "Set by your lecturer", and nothing else you bring in changes it. The lock is a reminder, not a rule - the Studio runs in your own browser - so if something your lecturer set needs to change, ask your lecturer.
After you load a template
The card. The From your lecturer card shows the template's name and version, your lecturer and their note, how many items they set and a Questions line with their contact. Until you save, it reads "Not saved yet - Save setup keeps it."
An update. When your lecturer sends one, choose Load a new version on the same card. What they set updates, and so does anything you haven't changed since you loaded the last version. Anything you have changed, where it now differs from your lecturer's, waits under Needs your decision, with Keep yours or Use your lecturer's; your progress stays.
Locked phases and tasks. Plan paths are off. The first load replaces your own phases and your own tasks that have no progress; until you save, Discard changes goes back to your last saved setup.
Phases and tasks that aren't locked. If you already have some of your own, the first load holds both sets under Needs your decision - Keep yours or Use your lecturer's.
Closed lists. A list your lecturer closed takes none of your own.
Or start from a plan path
Otherwise start Phases and tasks from a plan path - the Digital4Business (D4B) course plan, which also brings the course's deliverables, key dates, area choice window, areas and assessment criteria and, when you save, the progress on its tasks and tasks of your own; or a general research project, a classic academic thesis, a business consultancy report, a company process analysis, a business plan, a practitioner book or a PhD over 3 or 4 years - fitted to your dates, then change anything. The paths are kept up to date online, so one can change, or a new one appear, between versions of the Studio; a setup you've already started keeps what it took from its path. The D4B course plan is kept online too: when its phases or tasks are updated you get the update the next time you pick it, with each course task keeping the dates the course published, while its deliverables, key dates, area choice window and assessment criteria stay as built into the Studio and the D4B preset itself never changes under you.
Dates in a setup
Set your Start date and Submission date under About your course. The line under them says how long you have, and Save setup won't go through until the submission date is after the start date.
Phases count in weeks from your start date, so they move when it moves. The dates you set on tasks, deliverables and key dates stay where they are; a deliverable you leave undated is due with your submission, and a task you leave undated spans its phase and shows as an estimate.
Picking a plan path
Set your dates first. The Studio fits a path to the dates you have when you pick it, and its phases don't stretch or shrink if you change the dates later. The two PhD paths are built for about 3 and 4 years: on the Studio's default dates every stage shrinks to a week or two, and the card says "Designed for about 3 years - set your dates first". If you picked too early, set your dates, open Choose another path, pick the same path again and choose Use the plan path.
PhD review checkpoints. Each PhD path dates its checkpoints across your own dates: an agreed research and development plan, research integrity training and a second panel meeting in year 1, a meeting to prepare for the progression review about two months before it, the progression review itself (confirmation or transfer) about 20 months in, the annual reviews, examiners nominated at least three months before you submit, your supervisors reading the full draft, and a mock viva. In the Irish rules checked, full-time deadlines for the progression review fall between about 20 and 24 months - Dublin City University's window opens at 12 - and part-time ones later, so check your regulations and move any date to fit. The integrity training, the second panel meeting, the preparation meeting and the examiners are optional: delete any your regulations don't ask for. Each review that meets a panel reminds you to keep a copy of the signed form, outside the Studio. A PhD setup saved before version 3.12 keeps the checkpoints it had; pick the same path again and choose Use the plan path to bring in the new ones.
Over phases or tasks you already have. A path you pick doesn't replace them. It waits under Needs your decision, and Save setup stays off until you choose Keep yours or Use the plan path. Tasks you've changed keep your wording and dates. A task the path doesn't have comes along if you've made progress on it in the Plan - and, when your setup started from a path, if you added or changed it.
Another path. Choose another path - or Start from a plan path, if you built your phases by hand - opens the list again, and Hide plan paths closes it.
Two plans, kept apart
Every workspace starts on a built-in course preset, the Digital4Business (D4B) preset.A project made before v3.14 started on a built-in course preset, the Digital4Business (D4B) preset; a new project starts on General research project, saved as a setup of your own. When you save a setup, your plan follows your setup instead, and each keeps its own progress, tasks of your own, and start and submission dates. Only the D4B course plan path brings your preset progress and tasks of your own across when you save; on any other path, or a setup you build by hand, your preset progress stays on the preset, so the setup's plan starts fresh and only the items you added from your documents come across. Your preset work is still there.
The line at the top of Project setup says which plan you follow. Use the D4B preset switches back to the preset, and Use my project setup - it appears once you've saved a setup - switches to yours. Nothing you did on either plan is lost.
Fill in the rest - by hand or with an AI chatbot
Fill in the rest by hand, or let an AI (artificial intelligence) chatbot interview you - the Studio never calls one itself. Press Copy interview prompt (Read the prompt shows the text first), paste it into ChatGPT, Gemini, Copilot or Claude, and answer its questions. Attach or paste your brief into that chat too; Copy text, on any file you've added, gives you its text to paste. Then paste the AI's whole final reply into the box and press Check the reply: nothing reaches your form until you do. The Studio fills your gaps, keeps what agrees and lists the rest under Needs your decision.
Linking assessment criteria
Under How it's assessed, open Link the tasks that show it's met, below a criterion, and tick the tasks or deliverables that show it. Submission readiness at the foot of the Plan ticks the criterion only when every one of them is done, and a criterion you don't link stays at No task linked. Weight % is the criterion's share of the mark and shows beside it on the Plan. It doesn't have to add up to 100, and it's separate from the 100-point budget for scoring ideas in Settings.
Your course rules
Record your course rules - AI use, referencing, word limits, extensions, ethics and more - with where each one says so and when you last checked it; your plan reminds you to check them again.
Your brief or handbook
Add your brief or handbook as a PDF, a Word (.docx), .txt or Markdown (.md) file and the Studio reads it on this computer, keeping the text but never the file.
Each date it finds becomes one entry for the date and the thing it marks, named from the words around it - in a Word table, from its row; a sentence that only describes the course, from the phrase near its date.
A date for something already in your setup fills it in, and one that disagrees waits under Needs your decision.
Anything new waits at the top, under From your documents - to review: Add to plan puts it on the plan you follow now, as a task of your own on its date - a deadline for work you hand in, such as a proposal or a report, goes on marked as a deliverable - and Doesn't apply drops it; a re-read won't bring it back, but Review again, under Dates in your documents, will. Neither waits for Save, and a setup you save later takes what you added across.
When your setup has no phases, the Studio suggests the phases your documents name, with their weeks.
Some dates are only listed, with the reason beside them: the document doesn't say what the date is for, it's a version or publication date, it spans most of your project, it falls outside your project's dates, or the document gives more than one date for it. A date the Studio isn't sure of is marked Check this date. Re-read all documents does all of this again, for documents you added before.
Files, pasted text and links
Adding files. Choose files, or drop several at once on the box. The Studio reads up to 10 files - PDFs to 20 MB, Word files to 10 MB, and text and Markdown files to 2 MB - up to 300 pages of a PDF and 150,000 characters of text across all of them; a file cut short carries a first part only tag.
Files it refuses. An older Word .doc, a Rich Text Format (.rtf) file, an image, an empty file or a scanned PDF (pictures of pages, no text) is refused, with the reason under the box.
Your brief, pasted as text. If a file won't read - a password-protected PDF or Word file, say - or you don't have one, paste its text into Your brief, pasted as text (up to 50,000 characters). The Studio reads the box for dates when you click away from it, just as it reads a file.
Links to course documents. + Add a link records a title and a web link; one that doesn't start with http:// or https:// stops Save setup. While your plan follows your setup, the links and your pasted brief appear in the Your project and course chapter of this guide.
File rows. Each row has Copy text, to paste into an AI chatbot; Show the text, to check what the Studio read; and a cross button, which takes the file and its text out of your setup - until you save, Discard changes brings back a file you'd saved. Dates it already filled in, and tasks you added with Add to plan, stay; items still waiting under From your documents or Needs your decision go with the file.
Needs your decision
When something you bring in disagrees with your form - your lecturer's template, the AI's reply or a date in a document - or you pick a plan path over phases and tasks you already have, the point waits in a card called Needs your decision, above Save setup. It has a button for each choice, such as Keep yours, Use the AI's, Use your lecturer's or Use the plan path.
A question the AI left open has a Settled button and an optional note instead: it changes nothing itself, so edit the form if the answer matters. Save setup stays off until every point is settled, and each choice goes into your Journal when you save.
What reaches your plan, and when
Everything else you change in your setup reaches your plan only when you save.
What Save setup needs. A start date, a submission date after it and at least one phase, task or deliverable. Anything missing, or a row left half done - a new phase with no name, say - shows as a reason beside the button.
Empty rows. Rows you add and leave completely empty drop out when you save.
When it's greyed. Save setup stays greyed while a decision waits under Needs your decision, while the Studio's still reading your documents and, once you've saved a setup, until you change something.
After it saves. The Studio opens the Plan tab.
Drafts and Discard changes
While you work, Project setup keeps your changes in this browser as a draft, so you can close the Studio and pick up where you left off. A dot appears after the name on the Project setup tab until you save or discard them. Save my data doesn't include the draft, so save your setup before you move to another computer.
Discard changes asks first, then goes back to your saved setup and drops everything unsaved, including files you've added since. What you've already put on the plan with Add to plan, or dropped with Doesn't apply, stays as it is.
Open in Claude - this browser
The Open in Claude button beside Copy interview prompt starts Claude with the prompt typed in. The card at the foot of the right-hand column sets what it, and every other Open in Claude button, starts: The Claude app (the default, which needs the Claude app installed) or A terminal window, which runs Claude Code and shows as Open in terminal.
The same card sets the folder Claude opens in. Type the full path, starting with / or a drive letter such as C: (Windows), and press Use this folder; Clear stops using it. The app-or-terminal choice covers every project in this browser, and the folder belongs to the project you're in. If a prompt is too long for a link, the button switches off and says so - use Copy interview prompt instead.
Your project and course
Timeline and milestones
Deadlines and key dates keep their calendar dates; phases count in weeks from your start date ( - change it in Settings or Project setup).
Using the Studio
Ideas
Ideate. + New idea, at the right of the search box, creates a full idea card in any stage from Sparks to Chosen and opens it at once - only the title is needed. Your ideas move through Sparks → Exploring → Researching → Shortlist → Chosen, with Archived for ideas set aside - archiving never deletes an idea, so changes of mind are cheap and recorded (Start empty and Reset everything, in Settings, do remove ideas - see Settings, below). Drag a card into Archived (or anywhere else) to move it there directly; every move is logged in the idea's history.
Sparks column. Type an idea in the box at the top: Add spark records it as-is. The Spark generator asks for a fuller picture of a topic area - description, short name, who it's for, the itch, constraints - and how many sparks to spin (1 - 20, though you get fewer when the lenses run out of angles). The richer the entry, the more specific the angles: lenses cover scope, stakeholders, evidence, adoption, accountability, regulation, practice, time and combinations, plus lenses built from your audience, problem, constraints and the keywords in your description. It's a mechanical divergence aid, produced locally by rules, not by AI (artificial intelligence) - and your full entry is saved to the Journal with each run. Rate any spark 1 - 5 for interest and the column ranks highest first. Promote moves a keeper to Exploring; ✕ archives a spark into the Archived column.
What the Spark generator needs. It needs a short name or a description - a description fills the short name in for you. A run makes at most as many sparks as the lenses find: eight from a short name alone, nine when the board also holds an idea for it to pair with (any idea that isn't a generated spark - the Sample cards count, archived ideas don't), and up to 17 once you also fill in who it's for, the itch, the constraints and a description - even if you ask for 20.
Repeats and fit. Run the generator again with the same details and it works through the lenses in turn; once it has been all the way round, it brings back titles you already have, so archive the repeats. Two lenses assume small firms and EU (European Union) rules - archive any that don't suit your field.
Idea detail. Click a card to sharpen the research question, log research findings with links and takeaways (Download references (.ris) saves an idea's research log as a file to import into Zotero - it appears once you've logged a source; All references (.ris) in Project summary saves every idea's log), note the points For and Against, and score against your criteria. The search links - Google Scholar, Semantic Scholar, Consensus and Connected Papers - open in a new tab and search your research question, or the title until you've written one. Under them, a Deep research prompt - built from the idea - asks a deep research tool to map the literature: coverage, the main positions, gaps, recent developments, methods and a search string, citing only sources it found, each with a link or DOI (digital object identifier). Check every source before you use it.
Searching and filtering the board
Search. The search box on the Ideate tab looks for exactly what you type - a word, part of a word or a phrase with its words in that order, in any case. It looks in each card's title, The itch, Anchored in, Candidate research question and Tags. It doesn't look in For, Against, Likely artefact, Working notes, the research log or the area.
Area buttons. When your setup lists thematic areas, a button for each sits beside the search box (LiU, NOVA, NCI and UNIBO on the D4B plan). A button that's switched on (filled in) shows only that area's ideas; switch on several and the search then narrows within them. Click a button again to switch it off.
If a card seems to be missing. Search and the area buttons hide every card that doesn't match, in every column, and the number beside a column's name counts only the cards showing - a column can read "Nothing here yet" while its cards are just hidden. A new spark, typed or generated, starts as "Area not decided yet" (change it under Thematic area in the card), so no area button shows it while one is switched on; a + New idea card does the same until you choose its area, and the search has to match its words too. Clear the search box and switch off each area button - nothing is lost.
Where they apply. Both filters work on the Ideate tab only, stay on while you visit other tabs, and clear when you reload the page.
Inside an idea card
The fields. The itch says why the idea draws you, Anchored in names your own earlier work it builds on, Likely artefact says what you'd produce, and Working notes hold anything else. For and Against take one point per line. Tags are separated by commas; they feed the search box and, until you edit it, the Deep research prompt.
Saving and closing. A card has no Save button: it saves to this browser as you type. Done, Close, Escape and a click outside the card only close it. Save my data is separate - it writes your backup file.
Search links. The four search links under the research question search the question as it stood when you opened the card, or the title if it was blank. Reopen the card after you write or change the question, and they follow it.
Log a change of mind. At the foot of the card, this button jumps to the Journal with the type set to Change of mind and this idea selected, ready for you to write the entry.
The research log and the Deep research prompt
Research log. Only the Source title is needed. Paste a full APA (American Psychological Association) 7 reference into it and the .ris file picks out its year and any DOI. Type is one of Paper, Report, Article, Book, Conversation, Dataset or Thought.
Links and mistakes. A Link is optional, and it must be a web address: one starting www. or doi.org/ gets its https:// added, and a bare DOI (10.1000/xyz) becomes its doi.org link. Anything else is refused when you press Add to research log, so you can correct it. (A link saved before version 3.17 that doesn't start with http:// or https:// isn't shown as a link or put in the .ris file.) Once you press Add to research log, a source can't be edited or removed, so check it first. The idea's card on the board then shows how many sources you've logged.
Deep research prompt. Click its heading, under the search links, to open it - it starts closed, and once opened it stays open on other ideas until you reload the page. While it says Suggested, it follows the idea: the title, research question, itch, Anchored in, the first 12 tags as keywords, the thematic area once you've set one, and the titles of your last eight logged sources. Once you edit the text it says Edited by you and stops following the idea.
Reset to auto. This button is greyed out until you edit the prompt. It throws your edits away without asking and brings the suggestion back. Copy prompt copies whatever is in the box.
The personal-data check. Copy prompt runs the same check on this prompt as on the Journal, the AI use log and the other prompts - for email addresses, phone numbers and a few telling words - and asks before you go on. The fields of an idea card aren't checked, and the check can't catch a name, so keep participants' names and contact details out of both. The Your data chapter lists everything it covers.
Your leading idea
Which idea it is. The Plan's suggested prompts and the Progress report write about your leading idea - its title and research question - and say "not final yet" until it's in Chosen. That's the first idea in Chosen (the one nearest the top of the column, if two are there), otherwise your front-runner, otherwise your highest-scoring Shortlist idea (the one nearest the top, if scores tie or none is scored yet). Archived ideas never count, and with none of these the prompts carry no topic.
Front-runner. Mark as front-runner, at the foot of an idea's card, puts an amber front-runner badge on the idea you're leaning towards without moving it between stages. Only one idea holds the badge: marking another moves it, and Clear front-runner - the same button - removes it. Each change is logged in the Journal as a Decision.
Project name. Until you type a project name, the Project name box in Settings suggests your Chosen idea's title, or your front-runner's when none is in Chosen.
Moving, archiving and restoring ideas
Without dragging. You don't have to drag a card: open it and change its Stage to move it to any column, including Archived. To open a card from the keyboard, Tab to it and press Enter or Space.
Archiving. Archiving keeps everything you logged, and your earlier Journal entries stay linked to the idea. An archived idea drops out of Compare, the idea list for new Journal entries, the leading idea in your suggested prompts and the project-name suggestion.
Bringing an idea back. Open an archived card and press Restore idea to return it to the stage it left. Or pick a different Stage in the card, or drag it out of Archived into any column - each move is logged in the idea's history.
The sample cards and Start empty
Sample cards. A new project starts with four ideas marked Sample - examples of a worked-up card, not topics to choose. Archive them with the cross on each spark card; editing a sample doesn't remove its Sample label. No control deletes a single idea for good.
Start empty. Start empty (clear all ideas, keep settings), under Danger zone in Settings, clears every idea and your Journal after you confirm - one entry noting the clearing stays - and keeps your settings, dates, criteria, plan, plan baseline and snapshots, approvals, data plan, meeting log, AI use log, draft feedback record, company project safeguards, assessment terms and word counts, training record, the date you last exported a panel pack, and your team - its members, charter and task owners. Use it before you've done any work, not after. Reset everything to the original seeds, beside it, replaces all of it - ideas, Journal, name, dates, criteria, plan, project setup, plan baseline and snapshots, approvals, data plan, meeting log, AI use log, draft feedback record, company project safeguards, assessment terms and word counts, training record, the date you last exported a panel pack, and your team with its charter and task owners - and brings the samples back.
Scoring and comparing your ideas
Scores. Open an idea and give each criterion a score from 0 (weak) to 5 (strong); a dash means you haven't scored it, and choosing the dash again clears a score. A 5 earns the criterion's full weight, a 3 earns three fifths of it and a 0 earns nothing, and the total, out of 100, adds them up - so a criterion you haven't scored earns nothing. Score every criterion before you compare: a 5 on one criterion weighted 20 gives a total of 20, and a single 0 gives a total of 0.
Compare. Every idea that isn't archived is listed, with its total - a dash if it has no scores. Scored ideas come first, highest total at the top, then Unscored ideas from A to Z. Switch Include unscored ideas off to hide the unscored ones, except any in Shortlist or Chosen; it's back on when you reload.
Reading the totals. The same total shows as a badge on the idea's card and as the Weighted score in Export for supervisor, the button on an open idea. Point at a column heading in Compare to see its weight, and click an idea's name to open it. Treat the numbers as a conversation starter, not a verdict - a low score on curiosity should worry you more than a low score on anything else.
Running your plan
Plan. The plan lays out your research project as tasks in four phases - Explore and orient, Choose your track, Build your project, Submit - drawn from the course's Moodle pages, the Module Handbook and its Topic videos. The Gantt runs on to your submission date, which can fall after week 12. Switch between a Gantt timeline (bars across the weeks, the Moodle area-choice window, milestones and today's date - click a milestone diamond to jump to the task it falls on) and a Kanban board you can drag between To do, In progress and Done. Add your own tasks and sub-tasks, and move any date to fit your plan - in the Gantt, drag a bar to move a task, drag its ends to change its dates, or drag it up or down to reorder it. The view stays with the task you let go of: a phase you have not put in order by hand lists its tasks by date, so new dates can move a task to another row - the chart scrolls with it, and keeps the weeks you were looking at. Long task names wrap onto a second line, and the header row with the weeks stays under the title bar as you scroll down. Rename any task where it sits - the pencil that shows when you point at it, or F2 - and the course keeps its own name: Use the plan's name, in the task, brings it back. Open any task, from its bar or its card, to mark it as a deliverable - it then ends in a diamond with its due date and carries a Deliverable tag - or back; Use the plan's own undoes it. Dashed bars mark estimated dates - treat them as a starting point. Solid bars carry dates the course gives you - the Moodle area-choice window, the deadlines its materials state and your submission date - or dates you've set yourself. On this plan, moving your start date moves every task and milestone with it, dates you've set by hand included, except your submission date and the upload task that follows it. The area-choice window moves too, so check Moodle for the real window after any change. Open a task and Builds on lists the tasks it follows on from, each marked done or not done yet - click one to open it. Until they're done, the task's Kanban card carries a Waits on line, even in the Done column. It's a planning hint, not a lock: you can move any task, in any order. Every status change is logged in the Journal as a Task update.
Suggested prompts for Claude. Open any task to see a prompt built from your project so far - it updates as your plan changes. It opens with a line about your course and the week you're in (or, before your project starts, its start date), then names one of your ideas: your Chosen idea, else your front-runner (the Mark as front-runner button in an idea's detail view), else your best-scored Shortlist idea - with its research question and thematic area if you've filled them in, and a note that the topic isn't final unless the idea is Chosen. Archived ideas are never used, and with no idea to name, the topic lines are left out. Then come the task with its dates and status, what it involves (your own notes, for a task of your own), what it builds on, if the plan lists that, and your sub-tasks. It asks for credible academic sources as APA 7 references with their links written out, and for a .ris file to import into Zotero - open and read every source before you cite it. Edit it and your version is kept; Reset to auto brings the suggestion back. Copy prompt copies it for any AI (artificial intelligence) assistant; Open in Claude starts a new session in the Claude app on this computer with the prompt typed in, ready for you to read and send - nothing is sent until you press Enter, and it needs the Claude app installed. The "or in a terminal" link beside it starts Claude Code in a terminal window instead, and needs Claude Code installed. The Open in Claude card in Project setup chooses which of the two the main button starts - the button then reads Open in terminal - and the project folder they open in; both are kept in this browser only. With a folder set, the prompt also tells Claude to check it for your notes and drafts; with none, the session opens in your home folder. If an edited prompt grows too long for a link, that link switches off - use Copy prompt instead. Treat every source a prompt brings back as a lead: find it, open it and read it before you cite it.
Submission readiness. At the foot of the Plan, seven criteria the course states outright in Topics 1-2 and the Module Handbook, each showing Not started, Under way or Met. You don't tick them: a criterion is Under way once a task linked to it is In progress or Done, and Met when every linked task is Done. A count shows how many are met, and clicking a linked task's name opens it. The set is provisional until the course publishes its own marking criteria - Topic 6 covers evaluation-criteria theory, not the project's own rubric. Below the criteria, the Handbook's five learning outcomes show as a separate reference, never ticked off.
Your submission bundle. Below the criteria, a separate list of what usually goes in with your work, worked out from what your project holds and not counted in the criteria above: a declaration that the work is your own; an AI use declaration or a statement that you used none - ready once every entry in your AI use log is finished, under way while drafts are left, and Check yourself while the log is empty, because you may have used no AI and the statement of non-use you build isn't kept; your ethics approval reference, once you have an application in Approvals or a task that collects data from people - ready when every application is cleared; your research integrity training certificate, when your plan has that checkpoint; your word count against the limit, when your course rules give one; what happens to confidential data after you submit, once you have a data plan - ready when it has a retention period and a destruction date; and the forms and copies your course asks for. Lines the Studio can't see for itself say Check yourself. Each line with somewhere to go has a button that opens it. Nothing here is stored - it changes as your project does.
Reading your plan
Phase buttons. The buttons under the Plan title show how many tasks are done in each phase. Click one to show only that phase in both the Gantt and the Kanban board, click more to add their phases, and switch every highlighted button off to see all your tasks again. The rest are hidden, not deleted - the counts at the top and Submission readiness still include them. The filter isn't saved, so it clears when you reload the page.
Summary line and Overdue. The line under the Plan title counts your tasks done, in progress and overdue, and shows which week you're in while your project's weeks are running. Each sub-task counts as a task of its own. A task that isn't Done - even one that's In progress - shows ! Overdue on the Gantt and on its Kanban card once its Due date has passed, estimated dates included, and your Progress report lists it under Behind plan. Mark it Done or move its Due date to clear the tag; if many tasks show it at once, check your start date first.
Export plan (CSV). In the Plan's course line, Export plan (CSV) downloads your plan as a file with one row for every task, in the order the Plan shows them: its name, phase, parent task, notes, start and due dates (year-month-day), status, whether it is a deliverable and what it builds on. ClickUp and Monday.com can import a CSV file and ask you to match each column to a field of theirs, and a spreadsheet opens it directly. The Studio only writes the file: it doesn't connect to either service, and it has not been tried inside either. The privacy check runs first, as it does before any other export of your own words, and a cell that starts with = + - or @ is saved as text so a spreadsheet never runs it.
Running late. A task that isn't Done and is past its due date has a What are my options? button in its box. It shows what your course says about late work - the rule you recorded under Course rules in Project setup, with its source, or a note that none is recorded - and the deliverable the task leads to. If your course says to ask a number of days before the deadline, type that number to work out the last day to ask; the number isn't saved. It also words a short note to your supervisor or lecturer, to copy into your own email. The helper never promises an extension - asking doesn't mean you will get one - and the only thing it can keep is a Change of mind entry in your Journal, when you choose Add to Journal. It changes no task, status or date.
Marks and word counts. Mark a task as a deliverable and its box gains an Assessment section: its share of the mark, whether it is graded or pass or fail, a word limit, a tolerance and the learning outcomes it assesses - all optional, and all typed from your course's own documents; the Studio never fills in a figure. The Plan then shows each deliverable's share of the mark and whether together they account for all of it. Word counts, beside it, is where you type the words you have written so far for each deliverable, or paste text to count it there - the text is counted and then discarded, and only the number and the date are kept. A count over the limit but inside the tolerance you entered is shown as that, and one past it says so. Your submission bundle gains a word-count line from the same figures. Your own record - your institution's forms and rules decide.
Start date. Change it in Settings - or, on a setup of your own, under Start date in Project setup, then Save setup. Your submission date stays where it is, so a later start can push tasks past it without any warning on the Plan: check the end dates afterwards. Until the new start arrives, the countdown at the top of the page, beside the Studio's name, counts the days to it. On a setup of your own, the phases move with the start date, and so does any task you left without dates; a task with a date keeps it.
This week
What to do now. This week, the first link in the line under the Plan's title, opens one window for the week from Monday to Sunday: the tasks that are overdue, oldest first, and the tasks due by Sunday, then the next milestone and the days left. When you have set them up it also shows the last day to send a draft for feedback, the open actions from your last supervision meeting, and any ethics approval your tasks wait on. Each list shows 8 and says how many more are on your plan.
One click. Done marks a task done and notes it in your Journal, as it does on the Plan; Open opens the task. The actions come from your latest meeting dated today or before - an action whose task on your plan is done is left out. One that isn't on your plan yet has Add to plan, and Open meeting opens the meeting's record. Draft feedback and Open Approvals open those windows.
Nothing stored. The window is worked out from your plan each time it opens, so it keeps nothing of its own and has nothing to back up. Days are counted as calendar days, so a week when the clocks change counts right.
Planning the week. On a Monday the window suggests planning the week. Copy a planning prompt copies a prompt with this week's tasks, the next milestone and your open actions, for an AI tool you choose - after the same privacy check as the Studio's other prompts - and offers to note it in your AI use log. The Studio sends nothing itself.
Working on a task
Status. Open a task from its Gantt bar or its Kanban card and set it with the Status buttons - To do, In progress or Done - or pick it from the menu on its Kanban card; the Gantt has no status control of its own. The Done button at the foot of the task box only closes it, because changes save as you make them, so it doesn't mark the task done.
Dates. Type or pick a task's Starts and Due dates in its task box - on the Kanban board that's how you change them. If a Due date falls before the start, the Studio moves it to match the start. Under a task's title, a tag says where its dates come from, such as Estimated - move it to fit your own plan. Once you change a task's dates, by typing them, dragging its bar or using the keyboard, its bar loses its dashed outline and its Kanban card stops saying estimated; reopen it and, on a task from your course or setup, the tag reads Your own dates and Use the plan's dates puts the plan's own dates back. With the keyboard, tab to a Gantt row and press Alt (Option on a Mac) with the left or right arrow to move it a day - add Shift to change only its Due date.
Sub-tasks. Open a task and choose + Add sub-task, or pick a parent under Part of (optional) in + Add task at the top of the Plan. A sub-task stays in its parent's phase, starts with its parent's dates, can take sub-tasks of its own, and counts as a task in the plan's totals. Each keeps its own status - marking every sub-task Done doesn't mark the parent Done, or the other way round.
Remove task. On a task you added yourself, Remove task - bottom left of its box - takes it off your plan after you confirm. Its sub-tasks move up a level, and the Journal keeps a note with its name and status, not its notes. Tasks that come from your course or setup have no Remove task button: on a setup of your own, use the cross button (Remove this task) beside one in Project setup, then Save setup; on the built-in plan, start a setup from its plan path first.
Baselines and snapshots
Save a baseline. Baselines, a link in the line under the Plan's title (beside Export plan), opens a window where Save baseline keeps a dated copy of your plan as it stands - usually the plan you agreed at the start. It copies each task's name, phase, start and due dates, status, deliverable mark and parent task, and your phases and milestones. Dates are kept as calendar dates, so if you later move your start date, the tasks show as moved.
Re-baseline. Re-baseline makes the plan as it is now your new baseline. It asks you to confirm, and keeps the old baseline as a snapshot named after it, with "baseline until" and the day you replaced it, so you can still compare against it.
Take a snapshot. Give it a name (up to 60 characters) and, if you like, a note (up to 300); the date is filled in for you. Take snapshot saves a dated copy of the plan as it is now. The Studio keeps up to 30 snapshots; past that it says so, and you remove one first. Remove asks you to confirm and can't be undone in the Studio - a Save my data file or a version in Version history made before then may still have it. A plan of more than 400 tasks, 30 phases or 60 milestones can't be saved as a baseline or snapshot - the Studio says so rather than keep part of it. With 30 snapshots kept, Re-baseline asks you to remove one first, because the old baseline is kept as a snapshot.
Compare. Pick the plan as it is now, or any snapshot, and the window lists how it differs from the baseline: the last due date on the plan, then dates moved (days later or earlier), tasks made longer or shorter, deliverables whose due date moved or that were marked or unmarked, status changes, tasks moved to another phase, tasks added, removed and renamed, milestones moved, new or gone (matched by name), and phases added, removed and renamed. Copy text, Download Word (.docx) and Download PDF take the comparison as shown, after the privacy check.
On the Gantt. Once you have a baseline, a thin amber line under a task's bar shows its baseline dates wherever they differ from its dates now, and the legend says so.
Where they are kept. The baseline and snapshots are part of your project: they go into every Save my data file and every version in Version history. In a project shared with a team they stay in your own copy and are not sent to your teammates. Start empty keeps them; Reset everything clears them.
Working as a team
If your project is a team project, one of you can keep the plan in this browser for the whole team. Nothing is sent anywhere and there is no sign-in - the team is part of your project, like the rest of it.
Your team. Team, on the Plan, opens the Team window. Add each member, with a light role if they have one - plan keeper, editor - and choose the lead; the first member you add leads until you choose another. A team holds up to 10 members. At six a short note says most group work guidance recommends 4 or 5, and from seven it suggests smaller groups of 3 to 5, each with a named lead. Remove takes someone off the team. If they own or help with a task, agreed the charter or hold a meeting action, they are kept as a former member, with the day they left, so the record still reads true - Bring back puts them back.
The team charter. Team charter sets out how you agreed to work together: what you're aiming for, who does what, how often you meet, how you keep in touch, how you decide, the standard you hold each other to, what happens if someone doesn't deliver, and who you go to if you can't sort it out. Agreed today records each member's agreement with the date, which you can correct. Once anyone has agreed, the text doesn't change: Revisit the charter makes a new version for everyone to agree and keeps the old one, with its agreements, under Earlier versions. Once your project passes its half-way point, a charter made before then is flagged for a revisit. Download the charter (PDF) gives you a copy to share. The Studio keeps 12 versions.
Task owners. With a team, every task's box has an Owner - the one person accountable for it - and Helping, for anyone else working on it. The owner's name shows on the task's Gantt row and Kanban card, and the team line on the Plan counts open tasks with no owner. Tasks for, above the chart, shows only the tasks one member owns or helps with, or the tasks nobody owns yet. While it shows one member's tasks you can't reorder them, so the tasks out of sight keep their place.
My tasks. My tasks lists one member's tasks - the ones they own and the ones they help with, with what is overdue - and the meeting actions given to them that aren't on the plan yet. On a saved meeting in the meeting log, choose which team member does each action; Add to my plan then makes them the task's owner.
What it records, and where. An owner is who the team agreed is accountable - the Studio doesn't record who typed what. The team, its charter and its task owners are part of your project: they go into every Save my data file and every version in Version history, so send a teammate your file if they need a copy. Start empty keeps them; Reset everything clears them.
Working with your supervisors
Progress report. The Progress report button, next to Projects at the top of the page, builds a report for your supervisors from your plan and journal: where things stand, anything behind plan, what's coming up and your latest journal entries, plus your topic and deliverables when you have them and, once you've filled in how often you meet or how quickly you get feedback on a draft, the working agreement from your First-meeting checklist. Download Word (.docx) and Download PDF save it; Email to supervisors opens your own mail app with a message addressed to the supervisors you've added in Settings (up to three) and copied to you if you've added your own email there. The Studio can't attach files or send anything itself, so attach the two downloads before you send. Your name in Settings goes on the report and signs the email. The optional note goes into the report only and isn't saved - it's gone when you reload the page.
Export for supervisor (one idea). At the foot of an idea's card, Export for supervisor builds a one-idea report as Word, PDF or Both. It holds everything you've written on the idea, Working notes included - only the Deep research prompt stays out - so clear anything private first. It says "Prepared by" with your name from Settings (add it first, or the report says it's missing), plus your student number and email if you've entered them.
Export formats. Word downloads a .doc file. PDF opens the report in a new tab and starts the print box, where you choose Save as PDF - allow pop-ups if nothing opens. Both downloads the Word file and opens the report in another tab without printing.
First-meeting checklist. On the Plan tab, a short agreement to fill in with your supervisor - how often you meet, how quickly each of you replies, the course's AI rule and ethics route - with a one-page PDF for you both to keep. It saves as you type, and it's your own record, not your institution's form.
Draft feedback. On the Plan tab, Draft feedback opens a window for what your supervisor has agreed to read - which drafts, how many, and how many calendar days feedback takes - and up to four spells when they are away and not reading, such as August. From the days to give feedback and your submission date, the Studio works out the Last day to send a draft for feedback, skipping the days your supervisor is away, and puts it in your milestones and, when it falls inside the chart, on the Gantt. In a task's box, Sent for feedback today records the task as a draft sent; the box then says when feedback is expected by, and the task carries a Feedback by tag on the Gantt and the Kanban board until it is done. The window lists every draft sent, with when feedback is expected, and counts them against your allowance; you can add one by hand or remove one. It shows your course rule on feedback, if your setup has one, and what you agreed at your first meeting. It never holds the drafts themselves, only their names and dates. It is part of your project, so Save my data includes it, and it holds up to 40 drafts.
The panel pack. On a PhD (Doctor of Philosophy) plan path only - the three-year or the four-year PhD thesis - a Panel pack button sits beside Progress report, and Draft your panel pack appears in the task box of the review checkpoints that meet a panel: the research and development plan, the progression review, and the annual reviews in year 2 and, on the four-year path, year 3. It drafts the text of a progress review for your panel in the pattern of Part 1 of UCD's (University College Dublin's) RPDP (Research and Professional Development Plan) form - research since your last review, then your plan for the next period - but it doesn't reproduce UCD's form or any other institution's. Choose From and To dates - From starts at the date you last exported, or at your start date, and To at today - then Generate a draft. It lists the tasks you marked Done between the two dates, every task in progress, and your Journal entries between the two dates, leaving out Task updates; then your plan for the next period - the open tasks due from the To date to 90 days after it, the milestones in those days, every deliverable still to come, and any open task whose planned end date is before To. Five boxes take what the Studio has no record of yet - modules and credits, prior learning, career development, research integrity and ethics training, and anything else to raise - and Generate adds each one you fill in as a section of its own. The draft is yours to edit: a line that starts with ## and a space becomes a heading. Copy text, Download Word (.docx) and Download PDF take the draft as it stands in the box and add a fixed title, calling it a draft for your panel form, and a closing line saying your institution's form and rules govern. The privacy check runs on the whole draft first. Nothing you type in the window is saved - the draft and the five boxes go when you reload the page - and the only thing kept is the date of your last export, which becomes the next From date; Start empty keeps that date and Reset everything clears it. It is a draft for your own panel form, not the form itself. The sections follow UCD Graduate Studies' guide to the online RPDP form and UCD's Academic regulations 2026-2027 (regulation 7.35); QAA's (Quality Assurance Agency for Higher Education's) 2018 advice on research degrees says students usually provide at least a written submission for a progress review; and the research degree regulations of DCU (Dublin City University, section 8.1.2) and Maynooth University (section 8.4.2) tell you to keep a copy of the final form, so keep one outside the Studio. All five are listed in the Guidelines chapter.
Project snapshot. In the Progress report window, Download snapshot (web page) saves a read-only web page of your project as it stands today, for your supervisor to open in any browser: the summary, your topic, the whole plan with a timeline and today's date marked, deliverables and milestones, where your approvals stand, each meeting's decisions, actions and next date, your Journal's decisions, changes of mind and milestones, and the note, if you typed one. It leaves out your reflections and other Journal entries, your meeting notes, agendas and your supervisor's feedback, and the boxes you type in Approvals. It is a picture of that day and doesn't change when your plan does - make a new one when you want to share an update. The page holds no script and sends nothing, so it opens safely from an email or a shared folder. If you email it, your supervisor downloads the attachment and opens the downloaded file - an email's own preview, Gmail's for one, may show the page's code instead. The privacy check runs on what it holds first.
Training and credits. On a PhD (Doctor of Philosophy) plan path, a Training button on the Plan tab opens your training record: each course, workshop or module, who ran it, when you completed it, its certificate reference and when it needs renewing - some universities ask you to retake research integrity training every few years - and whether it is research integrity training or carries credit, with its module code and ECTS (European Credit Transfer and Accumulation System) credits. A running total shows your credits against the number your course asks for, which you enter. It holds up to 100 entries and saves as you go. It links to Vitae's Researcher Development Framework (RDF) for assessing your own development; Vitae licenses the RDF separately, so the Studio doesn't reproduce it. On any other setup, the button appears only when your course rules mention research integrity training, and the window then holds just that certificate line. Your submission bundle shows the integrity certificate as ready once its reference is recorded. Keep the certificates themselves outside the Studio.
Supervision meetings
The meeting log. On the Journal tab, switch from Journal or AI use to Meetings - or choose Open meetings on the Plan tab's Supervision meetings line. It is a record, kept apart from the Journal, of each meeting with your supervisor: the date, how you met, who was there, what you planned to cover and the material you sent beforehand, your notes, what was decided, your supervisor's feedback in brief, the actions that came out of it, when you meet next, and the day you sent your notes to your supervisor to check. + Add a meeting opens a form; a meeting saves when you press Save meeting - Cancel, Escape or a click outside drops what you've typed. It is your own record - your institution's forms and rules decide what you must keep - and some institutions ask for a record of every meeting, so check yours.
Preparing a meeting. The Plan tab shows a Supervision meetings line: when you last met and, if one is agreed, when you meet next. Prepare the next meeting, on that line or in Meetings, opens a meeting dated for your next one - or that meeting, if you have already logged it - with its agenda drafted from your plan. Draft from my plan, under the agenda box, does the same for any meeting, for the date in the form: what you have marked done since the latest meeting dated before that date (or in the four weeks before it, if there is none), what is due by that day or overdue, what is coming up in the two weeks after it, the open actions from that meeting (one whose plan task is done is left out) and your supervisor's feedback from it, with a Questions for you heading to finish. Each list shows up to six, and the draft fits the agenda box. It asks before it replaces anything you have typed, and nothing is kept until you press Save meeting.
Actions, and your plan. Each action has what needs doing, who does it (me, my supervisor or both of us) and, if one was agreed, the day it is due. Add to my plan, beside an action in a saved meeting, makes it a task of your own on the Plan, named for the action and due on its date, with "From the meeting on" and the date as its note; an action with no date runs from today for a week. The action remembers its task, so pressing the button again opens that task instead of adding a second. If you remove the task from your plan, the button offers Add to my plan again.
Copy as email. Copy as email puts the minutes on your clipboard to paste into your own mail app: the date, what was decided, your notes, each action with its owner and due date, your supervisor's feedback and the next meeting, with a line asking your supervisor to tell you if you have got anything wrong. It runs the same privacy check as the Journal first. The Studio sends nothing.
The Journal, and what never goes in. A new meeting adds one note to the Journal, such as "Supervision meeting on 6 Oct 2026 - written up in the meeting log", that holds none of the meeting's text; the note stays if you later delete the meeting. Only your supervisors' names, dates and the work go in the log - nothing about a participant or anyone else. Saving a meeting runs the same privacy check as the Journal for email addresses, phone numbers and a few telling words, and asks before it goes on.
Where the meetings are kept, and their limits. The log is part of your project: it goes into every Save my data file and every version in Version history, and stays with its project when you switch projects. It holds up to 80 meetings and about 100,000 characters in all. Who was there holds 200 characters, each of the five text boxes holds 2,000 characters, and a meeting takes up to 12 actions of 300 characters each. A save that would pass a limit is refused and says why. Start empty keeps it; Reset everything clears it.
Reflecting on your project
Reflections. In the Journal, choose Reflection as the entry type and four prompts appear: what you planned and what happened, what you would change and why, the ethical and sustainability implications of what you did, and what you have learned as a researcher. They follow what programmes ask of a reflective log or a reflective section. Add the prompts puts them in the box, after anything you have already typed. A reflection saves like any other entry, after the same privacy check, and the Reflections filter shows only them.
A reminder. Remind me to reflect, under the prompts, is off until you choose Every week or Every fortnight. Then, once that many days have passed since your last reflection - or since your start date, before your first - a reminder sits at the top of the Journal, with Write a reflection and Not now, and a short message says so when you open the Studio. Not now hides it until you next open the Studio. The choice is saved with your project.
Export. Copy reflections and Reflections (Word), beside the Journal's filter, put every reflection, oldest first and with its date, into one text or one Word file for the reflective section of your report. The privacy check runs on all of them first.
Recording your use of AI
The AI use log. On the Journal tab, switch from Journal to AI use. It is a record, kept apart from the Journal, of each time you use an AI tool for your project: the date, the tool and version, the plan you use it on (free, paid or your institution's), what it was for, the task or idea it was for, what you asked, what came back in brief, how you used or changed it, how you checked it, and a short reflection. + Add an entry starts one; open an entry to Edit or Delete it. It is your own record - your institution's rules and declaration form decide what you must submit - and it records your use without judging it.
Drafts from your prompts. After Copy prompt or Open in Claude on a task, Copy prompt on an idea's deep research prompt, or Copy prompt or Open in Claude in the Project setup interview, a note offers Add a draft to my AI use log. One click adds an entry holding the prompt (cut at 2,000 characters if it is longer), the task or idea it was for, today's date and, when the button names it, the tool - Open in Claude does, Copy prompt can't know where you pasted the prompt. An entry with nothing yet about what came back, how you used it or how you checked it shows as a draft. The Studio can't see what happens in the AI tool, so press the button only when you use one, and finish the entry once you've read the reply. The same prompt for the same task or idea on the same day is added once if it is up to 2,000 characters long; a longer prompt is added each time, as the entry keeps only its first part.
The privacy check. Before an entry is saved, by hand or as a draft, the Studio runs the same check as the Journal for email addresses, phone numbers and a few telling words, and asks before you go on. It is a nudge, not a filter: it can't catch a name, so keep participants' details out of the log as you would out of any prompt.
Build a declaration. Build a declaration turns the log into a declaration and, in most layouts, an appendix with each use in turn. Choose a layout: a generic one, which lists the fields the Higher Education Authority's principles say a declaration covers, or one that follows the TOPIC (Tools, Outputs, Prompts, Iterations and Critical Reflection) log of Dublin City University (DCU), the thesis statement of University College Dublin (UCD), the minimum acknowledgement of Trinity College Dublin (TCD) or the declaration template of University College Cork (UCC). DCU's log lists each use itself, so it has no appendix. Each names its source, with a link and the date the Studio checked it (27 September 2026). Institutions change these forms and not every course asks for one - DCU's and UCD's are written for research theses - so check your own before you submit. Where a layout asks for something the log doesn't hold, such as TCD's publisher and web address or the rest of UCD's and UCC's wording, it leaves a bracketed gap for you to fill; the generic layout also leaves one for a box you left empty in a finished entry - the tool, what you asked, what came back, how you used it or how you checked it - and for what is yours and what came from AI, if you leave that box empty. A finished entry with no purpose chosen leaves a bracketed gap in every layout, where the declaration says what you used the tool for. Ticking I did not use AI for this work builds a statement of non-use instead: DCU and UCC have their own sentence, and the other layouts use a plain one. If your log holds finished entries while it is ticked, the window says so, in case any of them are for this work. Copy text, Download Word (.docx) and Download PDF save the declaration as the preview shows it. The PDF prints the letters of most Western European languages, such as French, German, Irish and Spanish, as they are; some other accented letters, such as the Welsh w and y with a circumflex, print without their accent, and characters it has no shape for, such as Greek or Cyrillic letters and emoji, print as question marks. The Word file and the copied text keep them. Drafts stay out unless you include them. The box for what is yours and what came from AI isn't saved; the privacy check reads it before you copy or download, and a statement of non-use leaves it out. If you've recorded a course rule on AI use in Project setup, the window shows it and warns when it reads as if AI isn't allowed; the Studio only reads your words and can be wrong, so go by your course's own.
Where it is kept, and its limits. The log is part of your project. An entry saves when you press Save entry - Close, Cancel, Escape or a click outside the box drops what you've typed in it. The log goes into every Save my data file and every version in Version history, and stays with its project when you switch projects. It holds up to 300 entries and about 150,000 characters in all. Each box stops taking text at its limit: 80 characters for the tool and version, 200 for the task or idea it was for, 2,000 for the prompt and 1,000 for each other box. Past 300 entries or 150,000 characters the Studio says so and refuses the entry. A draft from a prompt longer than 2,000 characters keeps the first part and says so. Deleting an entry can't be undone in the Studio - a Save my data file, or a version in Version history, made after you added it may still have it. Start empty leaves the log alone, and Reset everything clears it.
Ethics approval and data collection
The Approvals window. On the Plan tab, the Approvals button opens a window with one card for each approval you need: a full committee review, a school or programme route, a low-risk or exempt route, a host organisation's approval, or a note that none is needed. For a committee you record its name, its next submission deadline and meeting, the months it doesn't meet, when you submitted, the turnaround in weeks your own institution gives, where the application stands (not started, drafting, with my supervisor, submitted, changes requested, approved, or approved with conditions), the approval reference and date, any conditions and amendments, and which of an information sheet, a consent form and a data protection check - a DPIA (Data Protection Impact Assessment) screening - you are preparing outside the Studio. For "no approval needed" you record why, and who confirmed it. It saves as you type, and it is your own record - your institution's forms and rules decide.
Company and client projects. On the consultancy, process-analysis and business-plan paths, the Approvals window opens with a Company or client project card: the organisation's written permission - who signed it, when, and what it covers; who signs any agreement - at some universities only the university can; whether confidential material is needed to grade the work; how the organisation will be anonymised in your write-up; when the data owner confirmed the data is anonymised; a letter of engagement, where your course asks for one; and a reminder that employees may find it hard to refuse to take part. It saves as you go, counts what you have recorded, and one button adds the organisation's approval to your applications, to track like any other. It records that each exists - never the letter, the organisation's confidential documents or its data. If confidential material is needed to grade the work, Your submission bundle adds what happens to confidential data after you submit. The tasks "Agree the brief and scope with your client" and "Confirm access to people and data" link to the card. Start empty keeps it and Reset everything clears it.
What the Studio works out. From the date you submitted and the turnaround you entered, it shows when to expect a decision, and warns when that date falls in a month your committee doesn't meet, when a meeting date you entered does, or when a submission deadline you entered has passed. When a task is marked as collecting data from people, it also shows the date to submit by to hear back before that task starts. The turnaround is yours to enter - the Studio doesn't know any committee's timings. If your course rules in Project setup include an ethics rule, the window shows it above the cards, with its source.
Collects data from people. In a task's box, Collects data from people marks a task that gathers data from people - an interview, a survey, a pilot. While any application you have recorded is not cleared, or none is recorded, a marked task that isn't done shows Waits on ethics approval on the Gantt, on the Kanban board and in its box, and the Plan shows one line saying how many tasks wait. An application is cleared when it is approved, approved with conditions, or recorded as needing no approval; one open application among several keeps the wait going. It is a reminder, never a lock: you can still start or finish the task, and when you start a marked task that is waiting, the Journal's Task update says it was started before ethics approval was recorded. Some universities say plainly that approval has to come first: University College Dublin's Office of Research Ethics gives no retrospective approval, and University College Cork's Code of research conduct requires approval before the research starts, as the Guidelines chapter lists - which is why the reminder is there; check your own.
What never goes in here. Only names, dates, references and where things stand: never the application itself, an information sheet, a consent form, a recording, a transcript or anything about a participant. Your progress report gains an Ethics approval section - each application's committee, where it stands, its dates and reference, and how many marked tasks wait - and leaves out the conditions, amendments and notes boxes.
Where the approvals are kept, and their limits. Your approvals are part of your project: they go into every Save my data file and every version in Version history, and stay with their project when you switch projects. The Studio keeps up to 10 applications; the notes box holds 2,000 characters and the conditions and amendments boxes 1,000 each. Start empty keeps them; Reset everything clears them. The Collects data from people mark is kept on the task itself.
The short data management plan
What it is. On the Plan tab, the Data plan button opens a short plan, one to two pages when printed, for how you will look after your data. It follows the six headings of Science Europe's guide to research data management - data description and collection or re-use; documentation and data quality; storage and backup during the research; legal and ethical requirements; data sharing and long-term preservation; and responsibilities and resources - with a line under each saying what it asks. It also holds a version number, the date you first wrote it and the date you last updated it (the Studio stamps both when you edit; change them if you like), where the data will be kept, how long it will be kept and why, and a destruction date. Write a few sentences under each heading; an empty one prints as "Not written yet". It is your own record - your institution's forms and rules decide - and it saves as you type.
Storage, and the destruction date. Use the storage your institution approves: the window warns that personal laptops, USB sticks and unapproved cloud accounts are not recommended. Your institution or funder usually sets how long data is kept; if your course rules in Project setup include a rule on keeping and deleting data, the window shows it above the boxes, with its source, and doesn't copy it in. The destruction date goes on your plan as a milestone: a diamond on the Gantt chart when it falls inside the chart, a line on the Plan, and an entry in the milestone list in this guide, under What it asks of you on the D4B plan, or under Your project and course on a setup of your own. A date years after you submit - which is usual - shows on the line and in the list, and nothing is added to your task list.
Copy, Word and PDF. Copy text, Download Word (.docx) and Download PDF run the same privacy check as the Journal first, and ask before they go on if the plan looks as though it has an email address, a phone number or a telling word. The Word file and the PDF carry the plan on its own, not the boxes around it, and say that it holds the plan, not the data. Copy a drafting prompt copies a prompt for an AI chat that names the six headings, includes what you have written so far, and tells the chat not to accept participant data; it runs the privacy check too, and offers to add a draft to your AI use log.
What never goes in here, and where it is kept. Participants' names, linking keys that connect a person to their data, and files never go in - this is the plan for the data, not the data. The plan is part of your project: it goes into every Save my data file and every version in Version history, and stays with its project when you switch projects. Each of the six boxes holds 1,500 characters and the storage and retention boxes 600 each. Start empty keeps it; Reset everything clears it. The Data plan window also links to your approvals, and the tasks Write your data management plan and Collect your data open it from their own boxes.
On a phone or a small screen
The page scrolls as a whole. On a phone, or on a screen that is short because it is turned sideways, the header and footer no longer stay fixed round a small window. The header scrolls away as you move down, the tab bar stays at the top so you can change view from anywhere, and the footer waits at the end of the page. Choosing another tab starts it from its top. On a larger screen with a mouse nothing changes; a touch screen of any size keeps the larger touch targets.
Windows and the Gantt. Every window - Approvals, Data plan, the meeting form, a task - fits the width of the screen down to 320 pixels, and scrolling inside one does not move the page behind it. The Gantt chart scrolls sideways inside its own box, and its header row stops under the tab bar while the tasks scroll past. Buttons in the header and the tabs are at least 40 pixels tall on a touch screen.
Settings
What it holds. The Settings button, at the top, opens one box with your details, supervisors' addresses, project name, dates, scoring criteria and the Danger zone. There's no Save button: everything saves as you type, and it all goes into your Save my data file except the lecturer tick box. Done closes the box once your weights total 100. Escape or a click outside closes it too and keeps what you've typed - but while the weights don't total 100, the first press only warns you and keeps the box open, and a second press closes it anyway.
One set per project. Each project keeps its own Settings, so a new project starts with them blank or at their defaults. "I'm a lecturer" is the exception: it stays with this browser.
About you. Your name, student number and email; the last two are optional. Your name heads the Progress report, the First-meeting checklist and Export for supervisor, and it starts your backup file names; Export for supervisor also prints your student number and email. Until you add a name, a to-do banner and an amber Settings button remind you.
Supervisors' email addresses. Up to three, one per line. They address the Progress report message and nothing else; if you've added your own email, it goes on that message's Cc (carbon copy) line. The Studio sends nothing itself.
Project name. It tells your projects and backups apart, and you can also change it in Projects. Once your name is in too, the tab bar shows "Your name - Project name" in a pill, centred between Journal and Project setup; a long title wraps onto two even lines, the whole of it is in the pill's tooltip, and on a phone or a narrow window, where there is no room, the pill is left out. The project name also goes into each Save my data file name (it reads Research Report until you set one) and onto your Progress report and First-meeting checklist. The grey example in an empty box is only a suggestion and isn't saved until you type it.
Dates. Your start date and submission date belong to the plan you're following: a project setup of your own keeps its own pair, and each pair comes back when you switch plans. Moving the start date shifts the phases, which count in weeks from it, but never your submission date, so a later start can push later milestones past it - move both if your plans change. If your lecturer's template fixes a date, its box is greyed out and says so.
The countdown line. The line beside the title follows those two dates, and it isn't a button, so change them here. Before your start date it counts the days until your first week; after that it shows the week you're in, out of your plan's total, and the date of your next milestone - the one marked NEXT under Timeline and milestones in this guide - and once your submission date has passed, it suggests updating your dates.
Scoring criteria and weights. Rename a criterion, change its weight, add one with + Add criterion (it starts at 10) or remove one with the ✕ button beside it. The Total line tells you how many points to add or remove, and Done stays greyed until it reads 100 of 100. Compare still scores out of 100, dividing by whatever your weights add up to.
Removing a criterion. The ✕ button removes a criterion at once, with no question: its column leaves Compare, its scores stop counting on every idea, and a criterion you add back later starts blank. You must keep at least two. An idea earns nothing on a criterion you haven't scored, so a new criterion pulls scored ideas down until you score it.
Not your marking criteria. These criteria are for choosing between ideas. If you follow a project setup of your own, the criteria your work is marked against go in Project setup, under How it's assessed, and feed Submission readiness. The eight starters are only a starting point, and one of them counts a fixed number of weeks, so rename, reweight, add or remove to fit your project.
Start-up panel and lecturer tick box. Show the start-up panel opens the panel Research Studio shows when it opens. Tick I'm a lecturer to add the Lecturers tab - see For lecturers, below.
Danger zone: Start empty. Start empty (clear all ideas, keep settings) removes every idea, archived ones included, with its scores, research log and notes, and every Journal entry, and leaves one new note, "Ideas cleared - starting empty." Your details, dates, criteria, project setup, plan progress, own tasks, plan baseline and snapshots, approvals, data plan, meeting log, AI use log, draft feedback record, company project safeguards, assessment terms and word counts, training record and the date you last exported a panel pack stay.
Danger zone: Reset everything. Reset everything to the original seeds puts the starter ideas back and returns everything else to how it began: your name, contact details, supervisors' addresses and project name are emptied, your dates and criteria go back to the starter ones, the Journal goes back to its opening entry, and your project setup, course documents, course rules, the template your setup came from, the document items you skipped, plan progress, your own tasks, your plan baseline and snapshots, your First-meeting checklist, your approvals, your data plan, your meeting log, your AI use log, your draft feedback record, your company project safeguards, your assessment terms and word counts, your training record and the date you last exported a panel pack are cleared. Each Danger zone button changes only the project you're in and asks you to confirm - Reset asks twice - so Save my data before you use either.
For lecturers
Lecturers. Tick "I'm a lecturer" in Settings and a Lecturers tab appears. Build a project template for your course with the same form as Project setup - from a blank page, a plan path or a setup you already have - and choose, item by item, what students may change: untick "Students can change this" on anything every student should keep, untick "Students can add their own" to close a list, and tick "Fixed deadline" to keep a task's dates fixed on every student's plan. Download gives one .zip - the template and a short PDF telling students how to load it. Templates stay in your browser, never in your backups, so keep the .zip; Open a template file brings one back. Change a template after downloading it and it becomes the next version: students load it the same way, and keep their progress.
Opening a template file. Open a template file adds one from a .zip or .json to your list, here or on another computer. If you already have that template, the Studio asks before replacing it - even when the file is the same version or an older one, so read both version numbers in the question first. The copy you replace is gone unless you downloaded it. After an older file replaces a newer one, your next saved change gets the number the newer copy already had, so two different templates can go out as the same version.
Locks are a reminder, not a rule. The Studio runs in each student's own browser, so it can't stop a student who edits the template file, and one who never loads it isn't held to your locks at all.
Keeping a record and staying current
Journal. The sequential record of decisions and changes of mind, newest entry first. Choose the entry type - Decision, Change of mind, Insight, Research note, Tutor feedback, Milestone or Reflection - and, if it's about one idea, that idea under Related idea (optional); the list holds ideas you haven't archived, and both boxes keep your last choice after you add an entry, so check them before the next one. Filter, above the list, shows one type at a time and also offers Task updates, which only the Studio writes. Click the idea or task named on an entry to open it.
Entries are permanent. You can't edit or delete a single Journal entry once you've pressed Add entry - or Continue anyway, if the privacy note appears - so read it through first. Recent entries appear in the Project summary and the Progress report, and every Save my data file carries them all. Removing entries means clearing or replacing your work: Start empty, in Settings, clears every idea as well as every entry, and Reset everything replaces the lot - so Save my data first.
Entries the Studio writes for you. A Task update when you change a task's status (it also says so when you start a task marked as collecting data before ethics approval is recorded), remove one of your own or add one from your documents; a Tutor feedback note for each new meeting you add to the meeting log; a Research note for each Spark generator run; a Decision when you mark, move or clear the front-runner (the ★ button in an idea's detail), save your Project setup or switch plans; and a Milestone when the Studio first opens and when you press Start empty. Adding a task by hand writes nothing, and moving an idea between stages is logged in that idea's own history instead.
Project summary. Project summary, at the top, shows a formatted summary of your project - your ideas by stage with their scores, interest ratings, research questions and number of sources logged, a count of archived ideas, your plan progress, your latest eight Journal entries (Task updates are counted, not listed) and your next milestone - with headings, lists and bold, as you would paste it into a report. It used to be called Session summary and showed the plain Markdown text.
Using the summary. Copy formatted puts it on your clipboard with its formatting, to paste into Word or an email; Copy Markdown and Download .md take the Markdown text, and the file name carries the date. Edit the Markdown, under the summary, lets you change the text first - the formatted view follows as you type. All three run the privacy check first. Opening Project summary again builds a fresh one, so copy or download first. All references (.ris) saves every logged source for Zotero or another reference manager.
A suggested rhythm. One 25-minute pass per week until week 5: read the coaching prompt in the strip under the tabs on the Ideate tab (Next prompt shows another), touch three cards, log one journal entry, Save my data.
Roadmap. The Roadmap button, at the top, shows the versions planned next - each with its goal and what's in it - then ideas not yet in a version, with what has shipped folded away at the bottom. It's read from the Studio's website each time you open it, so it stays up to date between versions. Its Contributors list, at the top, names everyone whose suggestion is now in the Studio, with each one and the version it came in; choose a name to see only that person's suggestions. New ideas are planned into a coming version with room, and one that builds on another is placed after it, so an idea can move to a later version as the list grows.
Send Feedback/Ideas. The button at the foot of the page opens a short form: choose Idea, Bug, Praise or Other, write your message (at least three characters), and add a name or contact only if you'd like a reply or a credit line. If your suggestion is built and you asked for a credit line, your name goes on the Roadmap's Contributors list. Add an email address, and tick the box beside it - your consent - only if you'd like the owner to reply or to tell you when your suggestion is live: he sends each email himself, never automatically, every one carries a link to stop the emails or to delete your details, and the address is kept with your suggestion only for the period in the privacy notice. Those emails go through Resend, which keeps its records and logs in the United States whatever region it sends from. It goes to the Studio's owner, named in the footer - not your supervisor or your institution - with the Studio's version number added for you. Screenshot, beside it, opens the same form with a picture of your window already attached; Attach a screenshot inside the form does the same, and Remove screenshot drops it. The picture shows whatever is in the window when it's taken, so close or scroll away from anything private first. If the Studio can't reach the owner's backlog, a Send by email instead button appears; it opens your mail app with the message ready, without the picture. After a message is sent, this browser remembers the name and address you typed and fills them in next time - they are never part of your project or sent anywhere else, and Forget my details, under the address, clears them. The tick box is never filled in for you: you tick it each time you want a reply.
Getting around
Closing a box. Press Escape, or click the dimmed area around a box, to close it. Settings, ideas and tasks save as you type, so closing them loses nothing - but New idea and Add task make nothing until you press Create idea or Add task (what you type in New idea is kept as a draft in this browser until then), and an AI use entry changes nothing until you press Save entry. While your weights don't total 100, Settings needs a second Escape or click outside to close - the first only warns you - so you can rebalance them first.
Keyboard. On the Plan tab's Gantt, press Tab to reach a task and Enter or Space to open it. F2 renames it - Enter or clicking away keeps the new name, Escape cancels. Hold Alt (Option on a Mac) and press the up or down arrow to move the task up or down among the tasks beside it in its phase, or the left or right arrow to move both its dates by a day; add Shift to move only its due date, which can't go earlier than its start. Escape during a drag puts the bar back where it was.
On a phone. The Studio fits a phone screen: the header buttons wrap onto several rows, the page doesn't scroll sideways and the Gantt chart scrolls inside its own frame. The row of tabs scrolls sideways when they don't all fit - swipe it to reach the ones at the end, such as User Guide.
Hover over a button for a one-line explanation of what it does. On a touch screen there's nothing to hover with, so the explanations usually don't show.
Your data
Read this once. It says what the Studio keeps and where, what each safety feature does and doesn't do, and what should never go in it.
Before you type anything
What never goes in here
Names, email addresses, phone numbers or other contact details of anyone who takes part in your research.
Consent forms, recordings, transcripts, survey exports you could trace to a person, and any key linking codes to people.
Special-category data (health, beliefs, and similar), a host organisation's confidential documents, and log-in details.
Fine to keep here: plans, dates, committee names, approval references, tool names and anonymous counts.
Backups travel by email and cloud folders, and the prompts here are pasted into AI tools - so anything typed in can travel. The Studio checks the Journal, the AI use log, and the prompts you copy or open in Claude - the task prompts, the deep research prompt and the Project setup interview prompt - for email addresses, phone numbers and a few telling words, and asks before you go on. It also checks a panel pack draft, a project snapshot for your supervisor, and the note in your own words in a declaration of AI use, before you copy or download them - the note only when the declaration includes it. It doesn't check text you copy from a course file, or anything you type into an idea. That check is a nudge, not a filter: it can't catch a name.
The warning and the hints. The boxes where you write notes about your work - the Journal, ideas (the itch and Working notes), tasks, the AI use log, the meeting log, Approvals, the data plan, the panel pack, your notes for your supervisors and for your AI declaration, and the feedback form - carry a short warning to keep sensitive details out, and anything that identifies another person (a window with several boxes shows it once, at the top). Boxes that hold names the Studio needs (your supervisors and your team), your project's setup, and the drafts it writes for you to send on (the late-task note, the project summary and the panel draft) don't carry it and aren't checked. As you type, and a moment after you stop, the Studio also looks for email addresses, phone numbers, Irish Personal Public Service (PPS) numbers, Eircodes, bank account numbers (International Bank Account Numbers, IBANs), dates of birth, words about health and other sensitive subjects, and signs that a note is about a research participant. What it finds is listed under the box, with Show (selects that text, so you can take it out) and Leave it (hides that hint until you change that part of the text). The hints never stop you saving and never change your text. The check runs on this computer: what it finds is not saved or sent, and it looks only at a box you have typed or edited in, so notes you saved earlier aren't checked until you change them. To check what you've already saved, use Check my saved notes in Settings. It looks through your Journal entries, ideas (the itch, Working notes and research log takeaways), your own tasks' notes, the AI use log, the meeting log, Approvals and the data plan for the same things, and lists what it finds note by note. Show opens the place and selects that text, and in a box the box's own hints then show. It runs on this computer too: nothing is sent, and what it finds isn't kept.It can't spot names - read your notes through yourself. In the feedback form the warning is there because your message is stored on the Studio's server.
When you paste a prompt into an AI tool
What the Studio does. The Studio never calls an AI (artificial intelligence) itself. Copy prompt puts the text on your clipboard, and Open in Claude hands it to the Claude app or a terminal on your computer. Once you paste or send it, it is with that AI company, under your account with it - Joe never sees it, and the company's terms and your settings decide whether it is kept, read by reviewers or used to train its models.
What the main tools said when checked on 24 October 2026. These terms change, so follow the links for the current wording.
ChatGPT on a personal account (Free, Plus, Pro): OpenAI may use your conversations to train its models unless you turn off Improve the model for everyone under Settings, Data controls; temporary chats aren't used for training. ChatGPT Business, Enterprise and Edu aren't used for training by default. OpenAI's page.
Claude on a personal account (Free, Pro, Max): Anthropic trains on your chats if you allow it under Model Improvement in your Privacy Settings, and then keeps them, de-identified, for up to five years; incognito chats aren't used. Anthropic's commercial products - Claude for Work and its API (application programming interface) - aren't used for training by default. Personal accounts, commercial products.
Gemini on a personal Google account: with Keep Activity on, Google uses your chats to improve its services, including training its models, and human reviewers read a sample, which is kept for up to three years; with it off, chats are kept for 72 hours. A work or school account can have different terms - check your university's. Google's page.
Microsoft Copilot Chat signed in with a work or school account: a green shield beside New Chat shows enterprise data protection applies, and Microsoft says prompts and responses aren't used to train the underlying models. Microsoft's page.
A thumbs up or down on a reply sends that conversation to the company as feedback: OpenAI may train on it even after you have opted out, and Anthropic keeps it for up to five years.
Owning an idea and keeping it private are different things. Pasting an idea into an AI tool doesn't hand it over: OpenAI's terms, for example, say you keep your ownership rights in what you put in (Terms of Use). Keeping it private is the harder part - a conversation that is kept, reviewed or trained on isn't only yours any more. For an unpublished method, a host organisation's confidential material or a co-author's work, switch training off, describe the idea in general terms rather than in full, or use the AI tool your university gives you through your student account, and check what your course rules and your supervisor say.
What the privacy check can't do. The check before you copy a prompt looks for email addresses, phone numbers and a few telling words. It can't recognise an original idea, so it won't warn you when one is in a prompt - that call is yours.
Where your work is kept
Everything you add to the Studio autosaves to this browser on this machine, in the browser's own storage for this site (called localStorage), about half a second after you stop. Autosave lives there; Version history is kept in the browser's built-in database (IndexedDB) for this site. Neither is a backup, and a browser that clears one clears the other.
Text you haven't added yet. What you type into the Journal box, or into New idea's title and itch, is kept as a draft in this browser about half a second after you stop, and comes back after a reload or when you open New idea again; it goes once you add it (Add entry, Create idea), and Start empty and Reset everything clear it. A draft belongs to its project and travels with it when you switch projects, but it's in no backup file and no version until you add it. Text in the other boxes that wait for a button - a new task, an AI use entry, a meeting - isn't kept until you press it.
The Studio doesn't send your work anywhere. Opening it loads its font and the list of plan paths from the Studio's own website, and asks Google for nothing (the button that shows planned changes reads its list the same way); neither request carries your work. It also loads two helper libraries from jsDelivr, a public code host, only when you need them: the PDF reader (PDF.js) when you add a PDF, and a screenshot tool when you attach a screenshot to feedback. Each is checked against a fixed fingerprint before it runs. Your work leaves this browser only when you send it - through the feedback form, by pasting a prompt into an AI tool, by opening a prompt in Claude, or by emailing a report yourself.
The Privacy button in the footer opens the privacy notice: who runs the Studio, what the feedback form keeps and for how long, who else handles it, and your rights. The Send feedback form links to it too.
Course files you add in Project setup are read on this computer, and only their text is kept - never the file. Your file is never sent anywhere.
Your Save my data file holds your name, student number, email and supervisors' addresses along with your work, and its file name carries your name and project name - treat it as personal before you send it on.
The Screenshot button in the footer, and Attach a screenshot in the feedback form, take a picture of your window and send it with your message, so it shows whatever is on screen when you press the button, such as your ideas, journal entries or project name. Scroll away from anything private first. You see a preview, and Remove screenshot drops it. Send by email instead doesn't include the picture.
Some things stay in this browser only and never go into a backup file or a version: the folder Open in Claude uses (and whether it starts the Claude app or a terminal window), "Don't show this on start-up", "I'm a lecturer" and a lecturer's templates (the .zip they download is the copy to keep), the folder Save my data and Load my data last used, drafts of text you haven't added yet, which file the automatic backup keeps up to date, the browser's answer about keeping its storage, and a Project setup draft you haven't saved yet (typed text, a pasted AI reply, decisions still to make, course-file text). That draft is autosaved in this browser, but it's in no backup and no version until you save the setup.
Keep the Studio open in one tab at a time. Two open copies of the same project take turns saving over each other. A tab notices only when it next saves - so a second copy shows no warning at first - and then it keeps what the other tab had in Version history ("Kept just before this tab saved over work from another tab"), stops writing the automatic backup file until you reload it, and tells you. The browser holds one open project at a time, so if another tab moves it to a different project (Projects, Switch to it or Copy link), the tab you left behind stops saving at once and says so. In that tab, Save my data makes a file of what's there, and Version history keeps a copy of what you type; reload it to carry on with its own project - the other tab, which has the other project open, then stops saving instead.
Backups and Save my data
Backups use JSON (JavaScript Object Notation) files - plain text, readable anywhere, openable in any editor.
In Chrome and Edge, Save my data and Load my data remember the last folder you used, so the dialog opens there next time instead of your default Downloads folder. Safari and Firefox don't support this yet - Save/Load work exactly as before, opening the normal system dialog each time.
Autosave is per browser and per web address: open the studio in a different browser, on another machine or at a different web address and it starts fresh. Each browser gives a project its own id, so the first time you load your own file on another machine the Studio asks whether it's the same project, and says the ids differ. Answer yes if it is: the Studio remembers the file's id, and later files of that project load without the question.
If you first used the Studio at its old web address, a banner there asks you to use Save my data, then open the new address it links to and use Load my data there. The banner also lists what Save and Load don't carry across. Until you do, the new address can't see your work; it stays at the old address, which keeps working in the meantime.
Checked or not. Chrome and Edge save straight into the folder you pick, so the Studio reads the file back and compares it with what it wrote, then says "Saved and checked". Other browsers download the file, and nothing can read a download back, so the Studio says "saved, not checked" - open the file from your Downloads folder if you want to be sure. A file that reads back wrong isn't counted as a backup: the Studio says so, and the backup line keeps saying it until you save a good file. If writing the file you picked doesn't finish within a minute, the Studio stops it and says so, counts nothing as a backup and downloads nothing in its place - try Save my data again, or choose a different folder.
Load my data
Load my data replaces the project you're in with what the file holds; it doesn't merge. The project keeps its place and its id in your list of projects and takes the file's name - so loading a different project's file puts that project's work where yours was. If you have other projects in this browser, switch to the one you want to fill (or start a new one) first.
Before it goes ahead the Studio asks, and shows when the file and your open work were last saved, and whether your open work is the newer. It then tries to keep your open work in Version history ("Kept just before Load my data replaced your work", with the project's name), and in one pre-import copy in this browser that no screen opens. If this browser can't keep either, it says so - before going on when it already knows, and straight afterwards when a copy fails at that moment. If you're unsure, Save my data first.
After Load my data, the automatic backup (below) is paused until your next Save my data through the file picker.
The backup line
At the foot of the page, one line says when the Studio last saved a backup file (or, after Load my data, when it loaded one) and how many autosaves have changed something since. The count is kept in this browser only, never in your backups. The line can't tell whether the file is still there, was moved, or sits in a synced folder.
Unsaved changes. When your work holds changes that no backup file has yet, the box around Save my data and Load my data turns amber and shows "Unsaved changes". Autosave in this browser doesn't clear it. Save my data does, and so does Load my data, and so does the automatic backup file in Chrome and Edge when it's on.
It turns amber when you have no backup file yet, when the last one is three days old or more and things have changed since, when a file you saved didn't read back correctly, when the automatic backup has stopped or needs your permission, and when this computer's clock makes the file's date unbelievable. After Reset everything it counts changes against the file that still holds your old work. The same information is in the Version history window; on a small or zoomed-in screen the calm line steps aside and only an amber one stays.
A reminder at the top of the page. When your last backup file is three days old or more and things have changed since - or you have no backup file yet three days after you started the project, once the first-save note has been shown - a reminder at the top of the page says how old the file is and how many changes it is missing, with Save my data now beside it. It appears only when the Studio isn't keeping a backup file up to date for you: always in Safari and Firefox, which can't do that by themselves, so there Save my data is the copy that survives a cleared browser, and in Chrome and Edge until your first Save my data or while the automatic backup has stopped, is paused or waits for your permission. Remind me tomorrow hides it for a day, in this browser, for this project; the line at the foot of the page stays amber. It waits while another notice offering Save my data is showing.
Automatic backup (Chrome and Edge only)
After you Save my data through the file picker, the Studio keeps that file up to date: about every 5 minutes while something has changed, and when you leave the page. It works only while the Studio is open in a tab, so the file can be up to 5 minutes behind. It needs a browser feature that only Chrome and Edge have today (it's checked when the page opens), so in Safari, Firefox and any browser without it, use Save my data.
Before each write it reads the file. It writes only when the file is a backup of this same project holding no work this computer hasn't seen (if it does, see Using the Studio on two computers, below), and only a complete, valid backup of the project you're in; afterwards it reads the file back. If any of that fails - the file has gone, holds something else, reads back wrong, or a write doesn't finish within a minute - the automatic backup stops, says why, and stays stopped until you Save my data and choose a file, or turn it off - reloading the page doesn't start it again. A file that couldn't be read at that moment (a cloud folder still fetching it, say) can pass by itself, so after that a reload does try the file again.
It pauses after Load my data, Restore, Start empty and Reset everything, until your next Save my data through the file picker: the file may hold work those actions replaced. A Save my data that ends in a download doesn't lift the pause, and the toast says the file you picked couldn't be written.
It doesn't protect you from an ordinary edit. If you delete a meeting or replace a setup, the file is overwritten with the new state within about 5 minutes. Version history keeps earlier states, and dated Save my data files (kept in a synced folder) are the copies to rely on.
If the browser asks for permission again, a button appears beside the backup line and the automatic backup waits until you click it. Each new Save my data through the picker makes the new file the one kept up to date; earlier files stay as they were. You can turn it off in Version history.
Using the Studio on two computers
How it works. Keep your automatic backup file in a folder that your Dropbox, OneDrive, iCloud Drive or Google Drive app keeps in step between your computers. The Studio sends nothing anywhere: your cloud app copies the file, under your own agreement with that company, and the Studio on each computer reads and writes it.
Setting it up. On the first computer, Save my data into that folder - the automatic backup then keeps the file up to date. On the second, open Version history, choose Open a synced file and pick the same file. If the project open there isn't the same one, the Studio asks before it loads the file, just as Load my data does, and keeps what was there in Version history. Choose Allow automatic backup if the browser asks, so the Studio can write to the file as well as read it. Afterwards, keep saving into that same file: Save my data suggests a new, numbered name each time, so pick your synced file and replace it. Saving to a new file makes the new one this computer's synced file, and the other computer won't see it until you open that file there too. If you do save to a new file, the Studio says so in a warning that names both files.
Keeping in step. Each computer looks at the file when you come back to the Studio, about every minute while it's in view, and before each automatic backup write. If only the file has changed, a banner offers to bring its work in, and what you had is kept in Version history first. If both have changed since they were last in step, the banner asks whether to use the file's work or keep this computer's, and the one you don't keep goes into Version history - nothing is lost. Until you choose, the automatic backup writes nothing to the file. The Studio doesn't look at the file while it is writing it, so something you type during a write isn't taken for a change on both sides. Nor does it ever write over a file saved by a newer Research Studio: reload the page to update first.
What it can't do. It can only see what your cloud app has already copied, so give it time before you switch computers. A file still being fetched (an online-only file) counts as not readable yet: when the Studio is only looking, it looks again later; if the automatic backup was about to write, it stops in that page, and reloading the page tries the file again. It doesn't merge two sets of changes - you choose one, and the other waits in Version history. If your cloud app makes a "conflicted copy" of the file, the Studio doesn't see it - open it with Load my data if it holds work you need. It works in Chrome and Edge, which can read and write a file you pick; in Safari and Firefox, use Save my data on one computer and Load my data on the other, through the same folder. Use one file for each project.
Earlier versions of your work
The Version history button, in the footer and in Settings, lists earlier versions of the project you're in, newest first, with the date and time (24-hour, Dublin time), why each was kept, and how many ideas, journal entries and tasks it held. (It isn't the guide's Version history tab, which lists what changed in each release of the Studio.)
What is kept: up to 20 automatic versions - the one from when you opened the Studio, then about one every 10 minutes while something changes, which reaches back about three hours of steady work and further when you change things less often. Up to 5 more are kept when you leave the page, so switching tabs all day doesn't push the spaced ones out. And up to 10 of each kind are taken just before something replaces your work: Load my data, restoring a version, Start empty, Reset everything, a new setup replacing the old one, deleting a project, a tab saving over work another tab had saved, or - with a synced file - bringing its work in, or keeping this computer's work over it (then the file's copy is the one kept). When a group is full, its oldest goes; if all your projects' versions together grow very large, the oldest go first.
Restore keeps your current work as a version first, then loads the one you chose. It goes ahead only when that copy is kept, this tab is up to date when you ask (no other tab has saved the project since it opened, and the browser has this project open), and the version can be read. Otherwise nothing changes. If another tab saves while the question box is open, that work is kept in Version history first.
A tab that has stopped saving keeps what you type in it as up to 5 versions of its own project ("Kept from a tab that had stopped saving"). The copy is taken a few seconds after you stop typing, and again when you press Reload this page. After the reload the tab opens with its own project; open Version history there and use Restore to bring back what you typed.
A deleted project keeps its last version, and Bring back puts it in your list of projects again. Versions need IndexedDB (the browser's built-in database); where the browser refuses it, the window says so.
If your browser clears its storage
Autosave and Version history both live in your browser's own storage, and a browser can clear that storage: Safari does it after seven days of use without a visit to the site (Apple's own rule, from its 2020 tracking-protection update), and any browser can when the disk runs short or you clear site data. A backup file saved to your computer survives that, and keeping it in a folder that syncs (Dropbox, OneDrive or Google Drive) protects you if you lose the computer too. Autosave and Version history don't.
Asking the browser to keep your work. The first time you Save my data, the Studio asks the browser to treat its storage as permanent - once, not on every save. If the browser agrees, the Version history window (and the backup line's tooltip, for a mouse) says "This browser has agreed to keep this Studio's stored work" - the browser's own promise, and a backup file is still the safe copy. If it declines or can't be asked, the same place says the storage isn't guaranteed.
Warnings. If you use Safari and haven't saved a backup file, you see one note about its seven-day rule; it goes after that visit whether or not you dismiss it. A banner appears when this browser has used 80% of the space it gives the Studio, and another when autosave stops working, or Version history can't run, because the browser refuses the storage. The Studio can't tell whether you're in a private window, where everything it stores goes when the window closes - if you use one, Save my data before you close it. Each banner offers Save my data.
Several projects
The Projects button keeps more than one project in this browser - a new one with the starter ideas (New blank project), one started from a plan path or your lecturer's template, a copy of an existing one. New blank project and New from a plan path or template both open Guided setup on the new project - the second at its Template step - so a new project starts with the walk-through; Duplicate does not, since a copy has its answers already. Each has its own Settings (your name, student number, email, supervisors' addresses, project name, dates and scoring criteria), plan, ideas, journal, setup, Claude folder, version history and backup line. A new project starts with its Settings blank or at their defaults: the To do banner asks for your name again, Email to supervisors stays inactive until you add addresses, and the welcome page opens once more (unless you started it with one of the two New buttons, which open Guided setup instead). Duplicate copies your Settings and everything else under the name "Copy of ...", and the copy counts as never backed up until you use Save my data in it; to start on a different plan, use New from a plan path or template. Switching saves where you are first; a project you delete leaves a recovery copy in this browser. Save my data saves the project you are in, so switch to each one to back it up.
Copy link gives a link that opens that project in this browser only. After you open it in a second tab, work in that tab: the browser holds one open project, so the first tab stops saving.
What updates keep
A new version of the Studio reads what older versions saved: old JSON backups import through a chain of upgrade steps, and a backup from a newer version is refused rather than half-read.
If the Studio can't read what is stored in the browser, it leaves the raw text under a recovery key in this browser and starts a fresh sample project. No screen in the Studio opens that key (it takes a technical person and the browser's developer tools), and Version history can't reach the earlier project's versions. A Save my data file is the way back.
What the research project asks of you
Four connected deliverables, produced over roughly twelve weeks. Everything in this panel and the next comes from the course's own Topic 1-3 videos, transcripts and slides on Moodle, the Digital4Business (D4B) learning platform, and the Module Handbook.
Deliverable
What it is
Proposal
A literature review plus a project plan, 2,500 words - 30% of your grade (Module Handbook). Watch Moodle Announcements for the date; estimated around weeks 7-8.
Project Work
A focused dissertation of about 20 pages (4,000-6,000 words, up to 20 pages per the Handbook). Take ownership of a real, relevant challenge in your area, identify the problem through a literature review, then propose a solution - software, code, a digital strategy, a product concept or a detailed case study. Suggested outline: Introduction (400-600 words, written last) → Literature Review (1,200-1,800 words) → Methodology → Solution or Proposed Approach → Discussion → Conclusion → References in APA (American Psychological Association) style.
Digital Artefact
A demo of your solution - a presentation, prototype or mock-up, short demo video (a demo video can be just a few minutes) or any digital format that shows what the result could look like. The Handbook asks for a software artefact specifically; Moodle allows any shareable format - check with your tutor once your area is confirmed. Build it alongside the writing, not after it, and submit it in a shareable form, ideally a PDF or a link.
Video Presentation
Within 10 minutes of you presenting your research question, the main findings in the literature, then your solution, with the artefact as one part of it. It serves as your viva (oral examination); the final submission is the exam itself, and a live week-12 viva session hasn't been confirmed.
How they're marked. No weighting has been published for the September 2026 intake beyond the proposal's 30% (Handbook). Topic 6 (Project Evaluation and Reflection) doesn't include the project's own marking rubric - it covers evaluation-criteria theory, self-assessment and reflection. Compare your drafts against the Submission readiness list at the foot of the Plan until the course publishes its own marking criteria.
The six topics on the platform
Six short video topics from the partner universities. They open in sequence as you mark each one complete on Moodle, and each university releases its material on its own schedule.
#
Topic (Moodle title)
Delivered by
What it gives you
1
Introduction and Project Proposal Development
UNIBO (University of Bologna)
The three deliverables, the twelve-week structure, and moving from a question to a plan
2
Research Methodologies
UNIBO
Writing the introduction, and the literature review step by step
3
Scientific Writing for Projects
UNL (Universidade NOVA de Lisboa - NOVA University Lisbon)
What makes scientific writing good, drafting habits, readability and the structure of a paper
4
Ethical Considerations and Sustainability in Digital Projects
NCI (National College of Ireland)
Governance, ethics, regulation and sustainability in your project, with a reflection exercise
5
Project Presentation and Communication Skills
LiU (Linköping University)
Structuring your narrative, visual materials and delivery - the groundwork for the video presentation
6
Project Evaluation and Reflection
UNIBO
Evaluation-criteria theory, self-assessment and reflection on what you'd do differently - it doesn't include the project's own marking rubric
The four thematic areas
Code
Area
Tutor team
LiU
Data-Driven Decision Systems and Ethical AI Solutions for Business - data, intelligence and responsibility: cybersecurity, risk, compliance, ethics and law of AI (artificial intelligence) in business
Linköping University
NOVA
Data Science for Business - the full data science lifecycle with ethics and privacy built in
NOVA IMS (Information Management School), Lisbon
NCI
Cloud Computing for Business - cloud fundamentals, the NIST (National Institute of Standards and Technology) framework, governance and data protection in cloud adoption
National College of Ireland
UNIBO
Digital Transformation - strategies, platform business models, digital competences, sustainability and the UN SDGs (United Nations Sustainable Development Goals)
University of Bologna
Choosing your area. You pick your area, and with it your supervising university, in a Moodle activity with capped places (25 per area for the September 2026 intake). Read the area descriptions and tutor contacts on the activity page before the window opens - it isn't a form to leave to the last day. Once you've chosen, contact your tutor team with your idea.
Timeline and milestones
Weeks
Phase
1-5
Explore and orient - work through the platform topics, read, and find your question.
5-6
Choose your track - select your thematic area on Moodle. By then you should know your research question, have found the problem in the literature and have started thinking about the solution.
7-12
Build your project - write the Project Work and develop the Digital Artefact, with tutor support and office hours.
12-14
Submit - after the exam period, upload all three deliverables.
Dates below count from your start date ( - change it in Settings), so moving the start moves every milestone, the Moodle area-choice window included, except the final one, Submit the Project Work, which stays on your submission date. The real window, set on Moodle, doesn't move: the dates here use the September 2026 intake's window relative to your start, so check Moodle after any change. A later start can also push later milestones past your submission date - move both if your plans change.
Doing the work well
Find your question, then plan (Topic 1)
A topic is broad; a question is focused. "Artificial intelligence in business" is a topic. "How do small and medium-sized enterprises (SMEs) manage the ethical risks of AI-driven hiring systems?" is a starting question.
Before you commit, run exploratory searches in Google Scholar, Scopus or Web of Science. If someone has already reviewed the topic thoroughly, find a different angle or narrow it. One specific idea researched thoroughly beats a broad theme skimmed.
Turn the idea into a plan: broad aims, broken into objectives that each have a timeline and an expected output. Make them SMART (specific, measurable, achievable, realistic, time-bound) - not "write the literature review" but "complete a first draft of the literature review covering at least 15 sources by the end of week 9". Put the timeline in a Gantt chart and review it every week.
Writing the introduction (Topic 2)
About 400-600 words, roughly 10% of the project. It has five components. They don't need their own headings - treat them as a checklist, and they'll usually flow across three or four paragraphs.
Component
What it does
Rough length
Background
The wider context: what's happening in the field that makes this relevant now. Orientation, not the literature review.
200-250 words together
Research focus
Narrow to your corner of the field and state your research question explicitly - don't bury it.
Aim and objectives
One aim (what you want to achieve) and a short list of specific, active objectives (how you'll get there), each tied to a phase of the work.
100-150 words
Methods and timescales
A high-level note on how you did the research - literature review, case study, prototype or a mix - and its scope and timeframe.
60-80 words
Value of the research
The "so what?": who benefits, what it contributes that didn't exist before, and the practical implications. The component most students underwrite.
80-120 words
Write it last. Draft a rough placeholder at the start to orient yourself, then write the real introduction once the literature review, solution and conclusions exist.
Doing the literature review (Topic 2)
It's an argument, not a list of summaries. Map what's known, show where knowledge is incomplete or contested, and end on what remains unknown and how your project contributes. That gap is where your solution starts.
The five-step loop: identify the topic → define your terms (key terms and their synonyms) → set boundaries (inclusion and exclusion criteria such as date range, geography, study type and language - you'll justify them in the methodology) → select sources (titles and abstracts first, then full text) → analyse sources (does each one confirm, contradict, extend or challenge the others?). Then loop back as findings reshape the question.
Search at least two or three databases: Google Scholar (the easy starting point), DOAJ (Directory of Open Access Journals), CORE (an aggregator of open-access papers), Semantic Scholar and SSRN (Social Science Research Network).
Build your search string from a concept map and combine the concepts with Boolean operators, written in capitals: AND narrows (every concept must appear), OR broadens (use it for synonyms), NOT excludes - carefully, as it can drop relevant papers. For example: (artificial intelligence OR machine learning) AND (hiring OR recruitment) AND (ethics OR fairness OR bias). Long strings work best in Semantic Scholar or Scopus; keep Google Scholar searches simpler, with a few quoted phrases.
Three more techniques: truncation - organ* finds organisation, organisational and organise; phrase search - "digital transformation" in quotes finds the two words together, in that order; citation chasing - take one relevant, well-cited paper, look at who has cited it since, and work back through its own reference list.
Keep a synthesis matrix (author, year, aims, methods, findings, strengths, limitations, relevance). Organise the write-up by theme - usually the strongest choice for a Project Work - or chronologically, or by method.
Aim for 1,200-1,800 words, the longest section. Under 1,000 is likely too thin to justify a solution.
Set up Zotero before you start searching and save each paper the moment you find it; it formats APA citations in Word and Google Docs.
Specialised AI research tools (Consensus, Elicit, Research Rabbit, Connected Papers, SciSpace) search real literature and are fine for exploring - but verify every source in Google Scholar or CORE and read the paper before citing it. General chatbots (ChatGPT, Claude, Gemini) can map a topic, suggest search terms and suggest sources - ask for credible academic sources as APA 7 references with each DOI or link written out, then find every one, open it and read it before you cite it: fabricated references are among the most common and serious mistakes.
Which kind of review? Topic 2's decision tree, "What Type of Review Is Right For You?" (on Moodle, login needed), points a solo twelve-week project to a literature (narrative) review. Systematic, scoping and umbrella reviews assume a team of three or more and 12-18 months; a rapid review applies systematic methods with shortcuts under time pressure; a meta-analysis combines quantitative results statistically.
Writing it well (Topic 3)
Five qualities: clarity (unambiguous), conciseness (every word earns its place), structure (a logical progression - journal papers use IMRaD: Introduction, Methods, Results and Discussion), objectivity (evidence, not belief) and consistency (the same terms and tone throughout). "Performed really well on some datasets" becomes named datasets and measured results.
Let verbs do the work. Avoid nominalisations - verbs turned into abstract nouns. "The evaluation of the model's accuracy was followed by a comparison of its performance" becomes "We evaluated the model's accuracy and compared its performance".
Draft in stages - Franklin's (1986) three-stage model: outline (a few words, sentences or a visual map), draft (then shift and sort, moving whole paragraphs), and only then edit each sentence. Avoid both extremes: perfecting every sentence before moving on, and rushing a draft without caring how messy it is. With an hour to write, try four 15-minute drafts rather than one.
Start from one page. Before designing the full project, draft a one-page overview: problem, research question, aims, data sources, method and why it matters.
Make writing a habit: small, regular amounts while you're fresh, in protected half-hour blocks. Track time spent writing, pages finished and the share of planned tasks done (Creswell, 2014).
Readability: use one term per concept throughout - no synonyms for your key variables - and keep the same order whenever you mention independent and dependent variables. Wilkinson's hook-and-eye exercise tests flow: circle the words that carry a new idea forward (hooks) and box the words that refer back (eyes). Too few eyes reads as disjointed; too few hooks reads as repetitive.
Final pass (Creswell, 2014): cut unnecessary words, prefer the active voice, keep at most one qualifier, drop overused phrases, go easy on quotations, italics and asides, and use strong verbs. Tense: past for the literature and your results, present to introduce the study and discuss results, future for a proposal.
Parts of a paper: the PLOS (Public Library of Science) author guides cover the title and the rest of the manuscript (study design, keywords, the finding), the abstract (background, aims, methods, results, conclusions), the methods section (enough detail for someone to reproduce the work), reporting statistics (never manipulate results), discussions and conclusions (your results, related research, how they compare with your starting hypothesis, and one take-home message) and editing (set goals first, check the draft against them, rest it for a day or two, one idea per sentence, no double negatives, and say exactly how often and which sources).
Do's and don'ts (Topics 1 and 2)
Area
Do
Don't
Question
Narrow to a specific, researchable question with a gap the literature shows.
Settle on a broad topic like "AI in business" with no gap and no boundary.
Literature review
Build the argument for why your project is needed.
List paper summaries without synthesis.
Solution and artefact
Propose a realistic, well-reasoned solution that answers the gap, and make it tangible in an artefact built alongside the writing. It doesn't need to be fully built or tested.
Start with a solution and hunt for a problem to attach it to, or build the artefact after the text is finished.
Video
Keep to about 10 minutes: your project, your thinking and your solution. It's your viva.
Leave it to the end - Topic 5 covers presenting in depth.
AI tools
Use them to rephrase an unclear sentence, as a thinking partner, or to steelman the opposing view and find weaknesses in your argument.
Let them write the text, cite a source you haven't found and read yourself, or confirm what you already think.
Your tutor
Bring a specific question, a draft paragraph, sources you're unsure of or a decision you can't make alone. Email a short summary afterwards.
Ask "am I on the right track?" in the abstract.
Time
Plan backwards from submission and review the plan weekly. On low-energy days, do the mechanical work - references, formatting, re-reading annotated sources.
Leave the reading and writing for the last few weeks.
Sources: the Topic 1-3 materials on Moodle; Creswell, J. W. (2014). Research design: Qualitative, quantitative, and mixed methods approaches. SAGE, as adapted in the Topic 3 slides; the PLOS author resources linked above.
The guidelines behind the Studio
Correct as of 27 September 2026, and 1 October 2026 for the two ethics sources added in v3.11 - rules change; check your own handbook.
The Studio's advice draws on national frameworks, institutional rules and good-practice codes from Ireland, Europe and the United Kingdom (UK). None of these bodies produced, reviewed or endorses the Studio. Your programme handbook and supervisor always take precedence - where they differ, follow them. Rules vary between institutions, so Project setup lets you enter your own dates, deliverables and requirements.
We read every source on the date in its reference - 27 September 2026, or 1 October 2026 for the two ethics sources - then re-checked the points the Studio uses against the original. Many address research degrees - a PhD (Doctor of Philosophy) or a master's by research. On a taught master's, treat them as good practice, not rules, unless your institution has adopted them.
Irish national frameworks
Only QG6 is statutory, and it covers research degrees; research-intensive programmes with taught elements are only "advised to consider" it. The good-practice framework says its statements "are not a set of rules, regulations or obligations".
Higher Education Authority (HEA) and Quality and Qualifications Ireland (QQI) - National framework for doctoral education, revised 2023. Studio takes: a planned programme of personal and professional development, with progress checked against published criteria; it covers master's research too.
QQI - Topic specific statutory quality assurance guidelines developed by QQI for providers of research degree programmes (QG6), March 2017. Studio takes: a development plan you agree with your supervisor soon after you start and revise as you go.
QQI - Ireland's framework of good practice for research degree programmes, 2019. Studio takes: a work plan with milestones, an agreed meeting schedule, and a note of progress and decisions after each meeting.
National Research Integrity Forum - Policy statement on ensuring research integrity in Ireland, revised edition, December 2024. Studio takes: integrity training covering ethics, data management and responsible AI (artificial intelligence) use; never hide AI use.
National Open Research Forum - National action plan for open research 2022-2030, 2022. Studio takes: the case for a data management plan (DMP); its planned national template hadn't appeared by September 2026.
European frameworks
The Council Recommendation, the doctoral principles and the European Commission (EC) AI guidelines are recommendations; Ireland's national integrity statement endorses the European code of conduct. Only the Dublin Descriptors cover every master's award, taught or research - and they set outcomes, not process.
Council of the European Union (EU) - Council recommendation of 18 December 2023 (C/2023/1640); Annex II is the European Charter for Researchers. Studio takes: keep records of your work, work to agreed milestones, tell your supervisor about delays or changes, and get approvals before you start.
ALLEA (All European Academies) - The European code of conduct for research integrity, revised edition, 2023. Studio takes: report any AI or automated tools with your methods; keep data "as open as possible, as closed as necessary".
European University Association - Salzburg II recommendations, 2010. Studio takes: clearly defined, written responsibilities for you, your supervisors and your institution.
Bologna Working Group on Qualifications Frameworks - A framework for qualifications of the European Higher Education Area, February 2005 - home of the Dublin Descriptors, unrevised since. Studio takes: the master's outcomes your write-up should show - originality, judgement with incomplete information, ethical reflection, communication to non-specialists and self-directed study.
EC, Directorate-General for Research and Innovation - Living guidelines on the responsible use of generative AI in research, 3rd edition, May 2026. Studio takes: AI is never an author; name the tool, version and date and say how you used it; keep unpublished work out of tools that might reuse it.
UK frameworks, for comparison
UK texts don't govern Irish or European awards, but they spell out routines the others leave open. No UK national source requires taught master's students to keep supervision records - university codes set that detail.
Quality Assurance Agency for Higher Education (QAA) - Characteristics statement: Master's degree and Characteristics statement: Doctoral degree, 3rd editions, February 2020. Studio takes: at least a third of a taught master's goes on the research project; you reflect on your progress.
QAA - UK Quality Code for higher education, June 2024, with QAA's guidance on research degrees (November 2018) and on principle 11 (September 2026). Studio takes: agree meeting frequency early and record what each meeting decides; the 2026 guidance expects every student to record and discuss their progress with staff.
UK Research Integrity Office - Code of practice for research, version 3.5, July 2025; it covers students doing research. Studio takes: plan your data at the design stage; record your AI use (inputs, tool versions, outputs); keep personal data out of AI tools; use AI in assessed work only where permitted and declared.
Vitae - Researcher development framework (RDF), 2025. Vitae licenses it separately, so the Studio doesn't reproduce or adapt it; find it and its conditions of use at vitae.ac.uk.
Institutional examples
These are examples, not rules for your course: each binds only its own students, and most cover research degrees only.
University College Dublin (UCD) - Academic regulations 2026-2027 (version 2.3, April 2026) and its Research and Professional Development Plan (RPDP) guide (version 4, 2026). Studio takes: you draft your plan before each Research Studies Panel meeting, the chair completes it afterwards, and you sign last.
Trinity College Dublin (TCD), University College Cork (UCC), University of Galway, Dublin City University (DCU) and Maynooth University - research degree regulations and policies, 2024-2026. Studio takes: a shared pattern - an early development plan (required at four of them), a yearly review by people other than your supervisor, recorded supervision meetings (UCC sets 10 a year full-time) and rules on declaring generative AI use (DCU asks you to declare non-use too).
Taught master's handbooks - the dissertation handbooks of National College of Ireland School of Business (2025-2026), Alliance Manchester Business School (2025/26) and Technological University Dublin (April 2026). Studio takes: a proposal agreed early, supervision you drive, an agenda before each meeting and agreed actions after it, and ethics review before you contact participants.
Digital4Business (D4B) - Module handbook (Appendix 3, March 2025). Studio takes: the D4B preset - 12 weeks, a 2,500-word proposal (30%), a 4,000-6,000-word report with a software artefact (70%) and a viva (oral examination) in week 12. Its public documents don't set out supervision records, an ethics approval route or AI rules, so check Moodle.
AI use, data management, ethics and data protection
With the codes above, these shape four habits the Studio encourages: record your AI use as you go, declare it where your programme asks, write a short dated DMP before you collect data, and get ethics approval before you contact anyone. AI rules differ between institutions, so check each assessment.
HEA - Generative AI in higher education teaching & learning: Policy framework (version 1.0, December 2025). Studio takes: the national context - it doesn't apply directly to students; your institution's rules do.
HEA - Generative AI in higher education teaching & learning: Principles for ethical AI adoption (version 1.0, December 2025). Studio takes: what an AI declaration covers - tool and version, purpose, sample prompts, how you checked the output, and what you and the AI each contributed.
DCU, TCD, UCC and UCD - DCU's Guidance for postgraduate research students and supervisors on declaring and reporting use of generative AI tools (version of 13 June 2025), the TCD Library's Generative AI: Acknowledging & referencing Gen AI (June 2026), UCC's GenAI declarations (August 2026) and UCD Graduate Studies' Guidelines for preparation, submission, examination and dissemination of research degree theses (version 1.4, September 2026). Studio takes: the layouts Build a declaration offers - DCU's TOPIC (Tools, Outputs, Prompts, Iterations and Critical Reflection) log and its sentence of non-use, TCD's minimum acknowledgement, UCC's first two statements and UCD's model sentence.
Irish Universities Association - High level principles for postgraduate researchers on the use of generative AI during doctoral programmes (May 2026). Studio takes: in doctoral work, use AI only with your supervisor's approval, and record prompts and tool versions.
Science Europe - Practical guide to the international alignment of research data management (extended edition, January 2021). Studio takes: the six DMP headings, and a dated plan you update as the project changes.
EC - EU grants: Data management plan (HE), the Horizon Europe template (version 1.1, April 2022). Studio takes: a second DMP layout, which the EC calls "recommended but not mandatory".
UCD Office of Research Ethics and UCC - UCD's page Research with students and UCC's Code of research conduct (version 2.4, 2021). Studio takes: approval comes before data. UCD says it does not give retrospective approval for a study that gathered data before seeking approval, and UCC's code says research that needs ethical approval must not begin before it is granted (section 3.7) - which is why a task that collects data from people shows a wait until your approval is recorded.
Data Protection Commission - Data protection impact assessments and Guidance on anonymisation and pseudonymisation (June 2019). Studio takes: screen your design for a data protection impact assessment - employees can count as vulnerable participants, as they may find it hard to refuse; pseudonymised data is still personal data under the General Data Protection Regulation.
How to use this list
Check the date and version. These texts change often - the EC's AI guidelines reached a third edition in May 2026 - so look for a newer edition before you rely on one.
Follow your own institution first. Your handbook, module descriptor and supervisor decide what applies to you. Use this list to understand the reasoning, or to sharpen a question for supervision.
Tell us if something has changed. A new edition, a broken link or a rule the Studio has wrong? Use Send Feedback/Ideas in the Studio's footer.
References
American Psychological Association (APA) style, 7th edition, copied from the Studio's source register. Entries for web pages whose content changes give the date we read them.
ALLEA - All European Academies. (2023). The European code of conduct for research integrity (Rev. ed.). https://doi.org/10.26356/ECOC
Council of the European Union. (2023, 18 December). Council recommendation of 18 December 2023 on a European framework to attract and retain research, innovation and entrepreneurial talents in Europe (C/2023/1640). Official Journal of the European Union, C/2023/1640. https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:C_202301640
Joe Houghton, the Studio's author, can send you the full register of all 377 sources consulted - with how far each was read and what it was used for - on request.
Version history
New idea
Add a task
Export for supervisor
Which format?
Research Studio
Seen this before? Go straight in.
Welcome to Research StudioYour research project, from first idea to submission.
Choose a topic, plan the work and keep the record in one calm place - for students, and for the people who guide them.
Runs in your browser
No account to create
Your work stays in this browser
The Studio never calls an AI (artificial intelligence) itself. When you paste one of its prompts into ChatGPT, Claude, Gemini or Copilot, that company's terms and your account's settings decide whether it is kept or used to train its models.
What it does for
Everything in the Studio, in one view
You don't need all of it on day one. Start with Project setup and the Plan - the rest waits until you need it.
Ready when you are.
Every part is explained in the , inside the Studio and as a PDF.
Made by Houghton Consulting
Roadmap
Your projects
Each project keeps its own plan, ideas, journal, setup and Claude folder in this browser. Switching saves where you are first. Save my data saves only the project you are in, so switch to another to back it up.
Version history of your work
The Studio keeps earlier versions of the project you are in: about one every 10 minutes while you change things, one when you leave the page, and one just before anything that replaces your work. They sit in this browser's own storage, so they are not a backup - a browser that clears its storage clears them too. A Save my data file in a folder that syncs is the backup.
Progress report for your supervisors
Built from your own plan and journal, as they stand now. Add a note if you like, download it as Word and PDF, then email it from your own mail app.
Fill this in with your supervisor at your first meeting, so you both know how you will work. It is your own record - not your institution's form - and it saves as you type.
Your team
Who is on the team, their roles and the lead. It saves as you type.
Choose what to keep
You and a teammate changed the same thing before either of you synced. Nothing is lost while you choose: your copy stays here, and theirs stays on the team's server.
Team history
Each change to the team's shared plan, newest first, with who made it and when - saved by the team's server, not typed by anyone. It shows what changed, never what it says.
Ask Research Studio to look at the team's work
For when something has gone wrong with the team's shared plan that the team can't sort out itself - changes that vanished, say, or a warning that the team's history changed.
Contribution statements
What each member says they did for the project, and whether their teammates confirm it.
Team reports
The Team summary and your Individual statement, in Word or PDF - formative feedback for the team and its lecturer, never a mark.
What is recorded about you
What Team projects keeps about you in this team, who can see it and how long it is kept. Every member sees the same page, about themselves.
Team charter
How your team agreed to work together, with each member's agreement dated. It saves as you type.
My tasks
One member's tasks - the ones they own and the ones they help with - and their meeting actions.
Ethics and other approvals
Where each approval stands, and which tasks wait on it. The Studio shows the wait; it never blocks you. It saves as you type.
Short data management plan
One to two pages on how you will look after your data, under the six headings of Science Europe's guide. It saves as you type, and it holds the plan, not the data.
Baselines and snapshots
Save your plan as a baseline, take dated and named snapshots as it changes, and compare any of them - or the plan as it is now - with the baseline. They are kept with this project.
This week
◆ It's Monday - a good moment to plan the week. Work down the list, or copy a planning prompt to talk it through with an AI tool.
Word counts
Type the words you have written so far for each deliverable, or paste text to count it here. It saves as you go - numbers and dates only, never your text.
Running late - your options
What your course says about late work, the last day to ask, and a short note you can send. It never promises an extension - asking doesn't mean you will get one - and nothing leaves the Studio unless you copy it.
Training and credits
The training you have done, its certificates and when they need renewing, and the credits you have earned. It saves as you go.
Draft feedback
What your supervisor has agreed to read, how long feedback takes, and the last day to send a draft so it comes back before you submit. It saves as you type.
Add a meeting
Write what you can now and add to it later. Keep to your supervisors' names, dates and the work.
AI use entry
One use of an AI tool. Write what you can now and finish it once you have read what came back. Keep participants' personal data out.
Declaration of AI use
Built from your AI use log, in the layout you choose. It is your own record, written from what you logged - your institution's declaration form and rules decide what you must submit, so check its current form before you hand anything in.
Draft your panel pack
A draft of your progress review, built from your plan and Journal for you to edit before you copy or download it - your institution's own form and rules govern what you submit.
What the Studio has no record of yet
Optional, and not saved. Generate a draft adds each box you fill in as a section of its own, after the ones it builds.
Nothing you type here is saved, except the date you last exported.
Send feedback
Your name and address are filled in from last time - kept on this browser only.
Privacy
What the Studio does with your information, in plain words. Last updated .
Guided setup
Agreed so far
Spark generator
Mechanical lenses, not AI - the richer your entry, the sharper and more specific the angles. Everything you write here is saved to the Journal with the run, so nothing is lost.
Settings
Scoring criteria and weights
Weights budget to exactly 100 points. The running total below tracks every change - Done stays greyed until it lands on 100.
Went too far? Earlier versions of your work are kept here for a while.
Looks through what you've already saved for details that are better left out.
Sign in to share a project with your team. It is still being tested.
Danger zone
Team projects account
Check my saved notes
This looks through the notes you've saved for the things the hints spot as you type: email addresses, phone numbers, Irish PPS numbers, Eircodes, bank account numbers, dates of birth, health and other sensitive words, and cues about research participants. It runs here, in this browser. Nothing is sent, and nothing it finds is kept.
It can't spot a name, so read your notes through yourself as well.
Project summary
Your ideas, plan progress, latest Journal entries and next milestone, as of today. Copy it into your own project log or report, then add anything the numbers can't say.