Guides and explainers

Learn

How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.

Guides 1 min read

Two coaches, one player decision

Playing time, a position change, or who travels. Facts you both saw. One decision. Keep the parent chat out of it.

Guides 1 min read

Your student ID, the hold name as the portal shows it, and one question — what clears it. Not the story of how you got here.

Guides 1 min read

The reagent, the amount, the grant line, and a yes or no. A PI who answers email will not open your session about why the project is exciting.

Guides 1 min read

The deadline is real. The draft is long. Ask for defects in the aims or the budget — not a read of every page they will not finish.

Guides 2 min read

Ask a classmate to hunt defects in a named section, with a time cap and a date. 'Nice job' is not a peer review, and the course already knew that.

Guides 2 min read

Tell them what you want from the hour so it is not a recap. One decision or two review targets, sent in time to read on the train.

Guides 2 min read

Name the lecture, what you will give back, and a no that costs them nothing. A guilt trip is how you get silence or notes you cannot repay.

Guides 2 min read

A student team gets a reply when the question is answerable from a spec the vendor already knows. A tour of the project is not that question.

Guides 2 min read

Say what you did, what is open, and the next action they own. The shared notebook stays where it is. A dump of files is not a handoff.

Guides 2 min read

If you cannot sit in the room, send one question a lecturer can answer in writing. A diary of the week is not a substitute for the queue.