Organize research and development project records

Record project uncertainties, activities and effort in an exportable package; whether records meet a particular grant or tax program's requirements depends on that program and qualified review.

Why contemporaneous documentation matters

Documentation expectations differ by grant, jurisdiction, and program. Some frameworks consider questions such as uncertainty, investigative process, and when records were made, but an activity log cannot establish eligibility or replace advice from a qualified professional. Researchers decide what evidence is relevant and ensure records are accurate.

AIScholar's R&D module can organize selected project actions and user-entered records. Check the activity log and add work done outside the platform; do not assume it is a complete account without review.

The evidence, piece by piece

  • Uncertainty statements

    Record project uncertainty statements and use available AI drafting or feedback as assistance, not as a determination that the statement meets a program's criteria.

  • Contemporaneous activity log

    View available logged pipeline actions and add manual entries for work outside the platform. Review coverage and export the records in supported formats.

  • Effort tracking

    A floating start/stop timer on every pipeline page, manual time entry, weekly summaries by activity category — investigation & design, experimentation, analysis, support — and CSV timesheet export.

  • Knowledge progress tracker

    Track notes about learning, evidence, remaining uncertainty, and status. These records help organize project history but do not predict an auditor's assessment.

  • Inactivity nudges

    An inactivity reminder can prompt you to review records; reminders cannot identify every documentation gap.

  • ZIP evidence package

    Export available summaries, uncertainty statements, activity records, knowledge notes, and effort information. Inspect the package for completeness before submitting or sharing.

How teams use it

  1. Enable R&D mode per project

    Enable the optional documentation mode for a project where structured records are useful. Enabling it does not indicate that work qualifies for a particular program.

  2. State the uncertainty early

    Record the question or uncertainty and its date as accurately as possible. If you use AI drafting, verify that it reflects the actual project history.

  3. Work; the log writes itself

    Use available automatic logs, timers, and knowledge notes, then review and supplement them to reflect work and effort accurately.

  4. Export for your advisor

    Review and export the records for discussion with a tax, grant, or institutional advisor. Confirm the recipient's evidence requirements separately.

For an example of how a model-response study can be documented, browse the study walkthroughs. The separate scientific provenance feature is reproducibility — one tracks protocol and trial provenance, the other organizes project activity and effort records.

Study LLM behavior with a guided research workflow.

Design controlled text studies, collect model responses, and explore what changes across conditions. You decide what the evidence means.