A one-week workflow for keeping sources attached to research notes
A short research sprint is easiest to hand off when every claim points to something a teammate can open. If you’re choosing a tool, comparing three approaches, or preparing an internal guide, set aside one small Markdown file for evidence before you collect notes. Keep the working copy locally. You can share the checklist for the week and keep the evidence file for the next review.
Set up a source card on day one
For each source, record its title, URL or local filename, the date you checked it, and the smallest passage that supports your claim. Use a heading or page number so another reader can find it quickly. Write your interpretation on a separate line, with your initials or role if several people contribute.
For instance, if a software changelog says that PDF exports can preserve outbound links, record the version and quote the relevant sentence. Write the question you still need to test below it. A useful question might be whether a link inside a table also survives export. A single positive sentence in a changelog rarely answers every question about a format.
Keep a decision log during the week
Separate confirmed observations from questions. On Tuesday or Wednesday, take the three claims most likely to influence the decision and ask a second reader to open each source. If the reader lands on a different version, add both versions to the card and state which one the decision relies on. If a source moves behind a login, provide its title and access requirements and keep any private material in the team’s own workspace.
For a team working from a folder of project notes, Orkas is one way to organize the evidence file and make a review draft. Its Commander can coordinate a research or document specialist. Ask for a table with claim, source, locator, and open question, then review those four columns side by side. Orkas is an open-source, local-first desktop app for macOS and Windows. It can use managed models or a supported provider you connect. Remote model calls may send relevant excerpts to the selected provider, so use public or redacted notes when the team needs to keep source documents local.
End with one file another person can use
On Friday, write a short decision note that says what was selected, which two or three sources mattered most, and what would change the decision. Open every linked source from the final note. Put unresolved claims under a separate heading and give each one an owner and a review date. Save the list as Markdown alongside the project files.
When a temporary link expires, anyone who kept the file can still follow the same review steps. The next reviewer needs the claim, the evidence, and a way to find it again.
Disclosure. This note was prepared on behalf of the Orkas project.