FIELD NOTES · 2026

Activity sequence plan — a LAMP primer-design demonstration

This guide helps with recording software inputs and outputs without assessing clinical suitability. Use it as a personal worksheet; confirm activity details directly with the organiser.

How to use these notes

An activity sequence is different from a wish list. The plan should show what must finish before the next stage begins, including time to check information or travel between places.

Information for this activity

• software version and date of use
• input filename and its units
• settings changed during the demonstration

Procedure

1. Separate confirmed times from estimated times.
2. Record dependencies between stages and add breaks according to actual needs.
3. Set a decision time for a fallback plan if one stage is delayed. Tell participants when the sequence changes.

Worked example

If the second stage depends on an answer from the first, mark it “awaiting answer”. An empty time slot need not become an unagreed commitment.

Copyable format

Stage | Time | Time status | Prerequisite | Fallback option

Final check

Before sharing the notes, recheck software version and date of use, input filename and its units, settings changed during the demonstration. Remove unnecessary personal information and flag answers that are not yet confirmed.