Skip to main content
Create a shared tracker for study startup work: which sites are preparing, who owns each task, and what is blocking readiness. Start with one study and a few sites.

​
1. Build the linked tables

  • Studies: study ID, name, owner, target start date.
  • Sites: site ID, name, study link, site contact, readiness status.
  • Startup tasks: task, site link, owner, due date, status, blocker, and document reference.
Create these tables in one project. Keep study and site IDs unique, then use Link fields to connect sites to studies and tasks to sites. Use date, user, and single-select fields for deadlines, owners, and status.

​
2. Show the work and send reminders

Create a grid grouped by site and a Kanban view grouped by task status. Add a view filtered to incomplete, overdue tasks. Follow the deadline reminder example to email task owners; test the recipient and filter before enabling it.

​
3. Build a team interface

Use App Builder to create a study overview, site checklist, and task update form. Configure app login and test what each app user can read and change. For teammates working directly in the project, configure role permissions and test access with each role.

​
4. Try one site before rollout

Add a sample site, assign two tasks, complete one, and leave one overdue. Check the links, status views, reminder recipient, and saved edits. Have the study owner review readiness criteria before marking a site ready.
Use this setup for operational coordination. Keep regulated study records and patient data in systems approved by your organization; assess validation, audit, and regulatory requirements for your intended use separately.
For a broader study operations workflow, explore Teable for clinical trial management.
Last modified on October 21, 2026