BC
Brad CodyAdministrator
Current productPipelines and record experience
Reverse spec drafted

Record Tasks

Linked tasks and next steps with shared grid and create-task workflow.

Observed route/admin/leads/:id?tab=tasksFuture Spec 12
Current maturityWorking linked-task module with create form evidenced
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

Tasks & Next Steps is the record-scoped view of open, in-progress, blocked and closed work. The live opportunity has no tasks and suggests adding the first step or allowing a template to create tasks. Earlier evidence shows a shared task grid and a create form for title, description, type, state, priority, due date, owner, linked record and collaborators.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Scope and state copyExplains that open, in-progress, blocked and closed tasks are linked to this record.Verified live
Add taskPrimary and empty-state actions open task creation.Verified visible; no task created
Template cueEmpty state explicitly anticipates template-created tasks for new records.Verified live
Task gridEarlier evidence shows shared selection, filter, sort, export and column controls.Verified from earlier evidence
Create formCaptures work details, responsibility, timing, record link and collaborators.Verified from earlier evidence

User journeys

Current flows

01

Create next step

  1. Open Tasks
  2. Select Add task
  3. Enter details
  4. Assign owner and due date
  5. Confirm record link
  6. Save
Observed result

Form structure evidenced; submission not retested.

02

Template creates work

  1. Create or transition a record
  2. Match task template trigger
  3. Instantiate tasks
  4. Assign using configured rules
  5. Show in record and global Tasks
Observed result

Intended by current copy; engine behavior unverified.

State model

Current and expected states

Empty

No tasks for this record with manual/template guidance.

Open/in progress/blocked/closed

Named as supported states; populated live record not available.

Overdue

Not observed.

Unassigned

Form defaults and policy not verified.

Product rules

Non-negotiable boundaries

  • A task has one accountable owner and optional collaborators.
  • Record-scoped and global views reference the same task.
  • Closed tasks remain available.
  • Task templates create instances, not permanent links to mutable template text.
  • Visibility follows both task and linked-record permissions.
  • State and due-date changes emit Activity events.
Dependencies
Task serviceTask BuilderUser/team directoryRecord linkageNotificationsCalendar/resource scheduleActivity events

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 12 owns closure →
  1. No live populated record task was available.
  2. Subtasks, dependencies, recurrence, time tracking and resource scheduling are not shown here.
  3. Template instantiation and assignment fallbacks are unverified.
  4. Due-date timezone and reminder behavior are unverified.

Future alignment

Required evolution

  • 01Unify record tasks with Project schedules, Calendar, resource planning and time tracking in Spec 12.
  • 02Support dependencies, milestones and provider-facing task visibility.
  • 03Keep templates configurable while preserving historical task instances.
  • 04Add overdue, blocked and workload signals.

Current baseline

Acceptance record

  • Empty state and Add task are present.
  • The module declares supported workflow states.
  • Create form links task, owner, due date and collaborators.
  • The same task appears in record and global views.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented