Coursework, a lab, a thesis, each on its own board.
Nobody hands a student a project plan, and nobody hands a lab group one either. Noots gives the module, the study and the thesis a board and a timeline apiece; puts every class and everything with a date on it on pages of their own, filled from your institution's Canvas where it allows that; records the lecture or the supervision you are in and hands back the concepts, the decisions and the actions with names against them; and keeps the dates that do not move - submission, review, the defence - in front of everyone working toward them.
10 apps queued at setup - untick any of them before you finishDefault project tabs
Classes carries the timetable and the Assignments extension what is due, Files and Timeline hold the papers and the fixed deadlines, and Goals tracks the term's outcomes; Capacity and Budget are off - a study group is not resourced like an agency.
Projects created on day one
- Research
- Coursework
- Thesis & Writing
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working - or install any one of them on its own, later, from the marketplace.
Codex
The group's memory, and it outlives whoever wrote it: literature notes, protocols, onboarding and how-tos as searchable pages, every change stamped with who touched it and when.
- Pages grouped by category, searchable
- Protocols and reading notes beside the work
- Every edit stamped with author and time
- The person who joins in October reads it on day one
Notes
The lab notebook, on the project it belongs to: freeform pages for the protocol, the reading notes, the half-formed argument and the figure that is not a result yet, second in the tab strip after the board.
- Freeform pages on a project - notes, decisions, callouts
- Thought flows you draw rather than type
- Second tab on every academia project, after Board
- Drafts and PDFs attach to the same project
Hands-On Scheduling
The submission moved by a fortnight, so move it. Drag the bar on the timeline, or the event on the calendar, instead of opening a form - and sweep across a run of days to block out the week the fieldwork actually takes.
- Drag a bar to a new date, or either end to change start or finish
- Sweep across empty days on the calendar to create an event, already dated
- A multi-day event draws as one continuous bar across the days it spans
- Undo and redo on the timeline, with the thing you just moved lit up
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
09:00
the lecture, and the fifteen minutes before it
Your phone said this was starting a quarter of an hour ago, because fifteen minutes before a class is what a student's reminders are set to. Record the hour from the seat you are in, or upload the file afterwards, and what comes back is written for revising rather than for minuting: the concepts, the definitions as they were given, the topics covered, the readings and the assignments set, and anything the lecturer flagged as assessed.
13:30
what is due, and when it stopped being a surprise
Assignments is one list of everything carrying a date, across every class: what it is for, when it is due, where the work has got to and what you wrote when you handed it in. If your university has enabled Noots on its Canvas, that list fills itself and stays filled. The reminder lands three days out and again the day before, which is while a deadline is still a thing you can do something about.
17:00
supervision, and what was agreed survives it
The weekly supervision runs to the agenda on the invite itself, happens on Meet, Teams, Zoom or a Noots call, and the bot sits in with the steer written for a supervision. What comes back is not an hour of audio you will never replay: it is the decisions, and a list of actions each landing on the thesis board with a name against it. Next week's meeting already exists, because it is a Recurring Task. Next week opens on what was agreed rather than on what anyone remembers.
These sit on top of the whole product.
- Classes hold the timetable: when each one meets, who teaches it, where it is, and the materials that go with it
- Assignments hold what is due: the date, the class it belongs to, where the work has got to, and the notes you made when you handed it in
- Canvas sync fills both pages from your own institution's Canvas, once that institution's Canvas admin has enabled Noots on their instance
- Reminders arrive already set for a student: three days before an assignment is due, again the day before, and fifteen minutes before a class starts, and every one of those is yours to change
- Record a lecture from the device in front of you, or upload the recording afterwards, and get back the concepts, the definitions, the readings set and whatever was flagged as assessed
- The meeting bot joins supervisions and group calls on Meet, Teams or Zoom and returns a summary with owned action items
- Timeline and calendar carry the dates a syllabus or a submission window fixed months ago, and Goals track what the term is measured against: pass the module, submit the paper, schedule the defence
- Team Availability finds the one hour five different timetables can all make, and Polls & Surveys settles which paper you are presenting in one post with the tally live as the votes land
- Every project can add, rename, re-date and drag a milestone straight on its timeline and its calendar, in every plan and with no extension at all - so a submission date that moves is a drag rather than a delete and a retype, and the checklist hanging off it comes with it
- Files keep drafts, datasets and annotated PDFs on the project they belong to, rather than in a mailbox; a Codex page keeps the citation formats and the boilerplate you paste every week
- Recurring Tasks puts the weekly lab meeting and the reading-group slot on the calendar without anyone re-creating them, and the supervision's running order rides on the meeting itself; Checklists & SOPs run a protocol the same way every time, with a name against each step
- Offered at setup, one tick each: the Decision Log; Dependencies; Standups; and GitHub linking, which connects commits and pull requests to tasks for the groups that ship code
- The Corkboard is the reading wall and the whiteboard after a supervision - notes you drag, strings between the ones that connect, and a thread on any of them
- Ten interface languages, a high-contrast palette and a text-size setting on every account
The honest edges.
- Noots is not a reference manager and not an LMS. It can read your courses and assignments out of Canvas, and that is the whole of it: no course content is hosted here, no submission is handed in here and nothing is graded here. Drafts and PDFs attach to the work, and your library stays in the tool built for it.
- Canvas sync needs your institution's permission rather than ours. Canvas issues a developer key per instance, so your university's Canvas admin has to enable Noots on their own Canvas before there is anything to connect to. We cannot grant ourselves that access, and we will not show you a connect button that could not work. Canvas is the only system of its kind Noots reads.
- Your university's systems stay the source of record for enrolment, grades and funding. Noots holds the work of studying and researching, not the institution's records.
- Noots records and summarises a lecture you record: a microphone recording from the seat you are in, a file you upload afterwards, or a call the bot joins. It is not a room-installed lecture-capture system - it installs no hardware, wires no theatre, and cannot reach a class you are not in. Ask before you record, every time: some departments do not allow it, and that is their call rather than ours.
- Noots holds no FERPA, SOC 2 or ISO 27001 attestation, and does not claim one.
How Academia & Research actually runs.
Each of these is a project in Noots - its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
Built for the way your trade actually runs.
The ones buyers ask first.
Is this for students or for research staff?
Does it connect to Canvas?
Can I record a lecture?
Can it manage my citations and reading list?
How does a five-person group project actually use it?
My supervisor will not have a bot in the room. Is that the end of it?
What does it cost a student?
Open a workspace that already knows Academia & Research.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required