Send, answer and review requests; manage templates, changes and deletion.
Reviewed · 2026-10-12
On this page · 9
1. Incoming requests, sent requests and received reports
- Today’s research, request lists and follow-up lists share the order Research suggestions → Received reports → Incoming requests → Sent requests → Follow-ups. Only the current tab is highlighted; swipe the row on narrow screens. Sent requests and Request a report appear when you have request permission. Incoming means you should answer; Sent means you requested it; Received reports contains submissions/shares addressed to you.
- A red number counts requests whose body you have not yet opened. Select it to inspect new requests. Reading and submitting a response are separate states.
- Opening a request marks it read, but it remains pending until submitted. Revision needed is separate. Without JavaScript, use I have read this request.
- Use search, filters and pagination. Sent requests show the newest requests first; the response deadline and creation time are different values.
- Request a report is available to platform administrators and currently authorized PIs within their permitted scope. Ordinary researchers can answer requests and use personal notes/actions.
2. Select recipients and exclusions
- Choose individuals, a grant, a project or your full management scope. First verify the lab and scope you may manage.
- Search individuals by name/username. Grant/project choices target participating researchers; expand Exclude recipients to remove unnecessary recipients.
- Duplicate participation records are consolidated in the final recipient list. Review the actual names and count in the next step.
- Loading a built-in or personal template preserves selected recipients, exclusions, period and deadline. It applies the request title, description and questions.
- Participation and roles are rechecked at sending. Typing an unavailable person's name in the body does not add them as a recipient.
3. Write the request, period and deadline
- Set the title, reporting start/end dates and response deadline. The period says which activities to describe; the deadline says when to answer. Check the displayed time zone.
- Expand built-in/personal templates or write your own content. Read the Markdown preview and switch to Edit to change it.
- Ask answerable questions, such as experiments performed, result links, blockers, decisions needed and next actions. Do not presuppose completion or submission.
- AI drafting uses permitted context. Group drafts restrict context to avoid mixing one person's private notes into a group request. Personal allowances and access apply.
- Review wording, recipients and period. Check the readable preview rather than sending raw JSON or internal identifiers. Saving a draft does not send it.
4. Preview, send and understand notifications
- After saving a draft, review the final recipient list/count, title, period, deadline and questions. Return to edit if anyone is missing or incorrect.
- Explicit sending makes it appear in recipients' incoming requests. AI generation or preview alone does not deliver it.
- Platform notifications and new-request indicators reflect the request state. Email/push depend on recipient preferences and delivery configuration; the sending screen does not prove email arrival.
- Recheck a fresh preview after content or recipient changes. Do not reuse earlier approval when access or the request has changed.
- Sending, reading, submitting a response and reviewing that response are separate stages. Inspect progress in Sent request details. The request instructions and questions are always visible.
5. Answer, save and submit an incoming request
- Open an incoming request and read the requester, period, deadline, questions and latest changes. Check the state first if the request was withdrawn.
- Answer each question or import selected personal-note content. Share relevant outcomes and evidence rather than your whole private record.
- When AI response drafting is available, still review actual work, links and uncertainty. Saved responses and AI drafts remain private before submission.
- Review the submission preview and submit explicitly. Saving a personal goal or checking a daily box does not submit this answer.
- For a revision request, read feedback, improve the response and resubmit. Inspect earlier content/change history and add the needed evidence.
6. Review reports, give feedback and remind
- Use Received reports for submitted responses and PI check-in shares. Use an unread filter when available to prioritize unseen reports.
- In sent request details, inspect each recipient's submitted, outstanding and review state. Read the body and evidence before giving feedback.
- Below a requested report, Review and feedback shows all saved comments newest first. The feedback count excludes initial submissions and reviews without a comment. The top jump link and each comment's direct link preserve the report's current access checks.
- Use Write new feedback below the saved comments. After saving, the server reads the saved comments again; Send feedback alone does not change workflow state. Submission and status history can be collapsed separately. Existing comments do not record edit timestamps, so edit status is not inferred. Reading or saving feedback itself has no AI cost.
- For revisions, specify which answer needs what additional information. Review/read acknowledgment does not certify experimental validity or approve achievements.
- Use the provided reminder control for outstanding recipients, subject to the 24-hour limit. Email/push delivery is different from an actual response.
- Submissions are visible only to authorized recipients. Receiving private material from another scope does not authorize resharing it.
7. Edit, withdraw or permanently delete
- Edit allowed title, description, period and deadline fields in Sent requests. Create a new request to change recipients or question structure after sending.
- Existing responses and change history are preserved. Recipients may have answered an earlier version, so explain changes clearly.
- Withdrawal stops the request while retaining responses/history. It differs from irreversible permanent deletion.
- The author with current management permission can permanently delete draft, sent or withdrawn requests. Read the confirmation scope covering the request, linked responses, history and notifications.
- Deletion does not undo personal check-ins, saved templates or AI usage. Review the scope carefully when responses need to be retained.
8. Create, edit, duplicate and delete templates
- Open Template management beside built-in/personal template selection. Distinguish editing a template from the recipients/period of an in-progress request.
- Edit a personal template's name, request title, description and questions, then save. Use a descriptive name such as Weekly experiment check.
- Copy a built-in template into a personal one. Duplicate keeps a reusable original while creating a variation.
- Confirm deletion to remove the template. It does not delete sent requests or responses. Template changes do not automatically update existing requests.
- Period/deadline placeholders are filled when applied to the current request. Previously typed fixed dates are not automatically changed; check the preview. Saving and applying to the current request are separate choices.
9. Translation, privacy and troubleshooting
- Korean requests/responses use existing automatic translation in English reading mode. Compare View original and inspect original text when editing.
- The original can remain visible if browser translation is unsupported or not ready. Free on-device translation and generated AI translation are different features.
- If Request a report is missing, check platform-admin or PI permission in the current scope. Ordinary project participation or changing language does not grant management rights.
- If recipients look unexpected after loading a template, inspect selected conditions and the final list. Templates preserve recipients, exclusions, period and deadline while applying title, description and questions.
- For deletion, withdrawal or edit conflicts, reopen the latest request. Send support the URL and error text, not private responses or tokens.