Juristic, part of Board IntelligenceHelp centre
Browse guides

Make signing wait for earlier tasks

Make signing or closing tasks wait until the earlier work meets the conditions you set, and decide whether clients see the waiting items.

Screenshots are taken from the app on every release. Updated 16 November 2026.

The team is preparing to sign, but the conditions precedent are still being dealt with. A dependency on the deal board keeps the signing tasks waiting until the earlier work meets an agreed condition. You choose whether every earlier task must be ready, and whether the client sees the later tasks while they wait.

You need to be a board manager, and Dependencies must be enabled for your organisation. If Dependencies is missing from the Board menu, contact Juristic support. After it is enabled, sign out and sign in again.

Set what waits on what

  1. Open the checklist under Project management in the matter, click Board and choose Dependencies.

  2. Click Add dependency.

  3. Under Waiting, choose the tasks that must wait, or a whole group such as Signing and closing (whole group). Choosing a whole group includes tasks added to it later.

  4. Under Waiting on, choose the earlier tasks or groups, such as Conditions precedent (whole group). Swap sides reverses the two selections if you put them the wrong way round.

You can also start with Add dependency in a task's right-click menu, a group's three-dot menu or the selection bar. Those routes prefill Waiting. A task's menu applies to the whole selection when several tasks are ticked. Ticking a group's header checkbox selects the whole group; turn on Only these 2 tasks, for example, if the dependency should cover only the currently selected tasks. The number follows your selection.

Set when the later work becomes available

  1. Under Unlock when, click New filter and choose the Column whose value decides readiness. For a CP checklist with those status labels, choose Status, is any of, then Satisfied and Waived. Use the labels on your own board.

    Every board column is available, so the condition can also use a date, number or another value. A completed condition counts without pressing the filter editor's Save. Use Save to return to the condition list before reviewing the whole form. If you add several conditions, all must hold; conditions are combined with AND.

  2. Under Applies to, choose how many of the earlier tasks must meet the condition.

    The later work depends on Choose
    Every CP being satisfied or waived All of them
    One of several alternative preparatory tasks being ready Any of them
  3. Read the sentence below the choices, then click Add dependency. Check that it names the later work first and the earlier work last.

The list marks the dependency Waiting or Unlocked. Waiting tasks appear greyed out with a Waiting on Conditions precedent chip, or the name of what they await. Their cells and titles cannot be edited, and Add subtask is disabled. Managers can still comment on, move or delete them. People in permission sets cannot comment on, move or delete waiting tasks.

Decide what the client sees while waiting

  1. Return to Board → Dependencies and choose a display under Waiting tasks. This choice applies across the board and saves when you select it.

    What the client needs Choose
    The later work visible for context, while it waits Greyed out
    Only work that is ready to act on Hidden from people in permission sets

Managers still see waiting tasks greyed out in either mode. In hidden mode, the chip's tooltip explains that they are hidden from people in permission sets. A board without permission sets shows a note that nothing is hidden.

  1. Preview the client's permission set to check the result. Click Exit preview to return to the permission set editor, then close it to work on the board again.

Follow the work through to signing

  1. Update the earlier tasks as the documents arrive. When the condition is met, the later tasks stop waiting and return to the access their permission sets allow. In hidden mode they become visible again to people whose sets allow them to see those tasks.

  2. To change the sequence, open Dependencies, click the pencil (Edit dependency), change the choices and click Save changes. To remove a dependency, click Delete dependency and confirm. A task still waits if another unmet dependency applies to it.

Tips from practice

  • Use whole groups for a changing checklist. Later additions then follow the same dependency instead of being left outside it.
  • Keep the earlier work actionable. A task cannot wait on itself, and dependencies cannot form a circle in which tasks wait on each other.
  • Keep a source group populated. A source group with no tasks keeps the later work waiting; the dependency list flags it.
  • Explain the sequence before sharing. Tell the client which earlier deliverables make their next tasks available, especially if you hide the waiting work.

Before this: set up the deal checklist board and assign and follow up the work. Next: find what is outstanding before closing.

↑↓ to move↵ to open⌘K or / anywhere