Live project · coordination

Coord.

Temporary multi-party coordination through constraints, preferences, feasibility and explanation.

Objective

Find an option that actually works, not only the option with the most votes.

Coord is for situations where preferences are only part of the decision. A meeting may need a minimum number of people, specific participants may be required, and a popular time can still be infeasible.

It checks those rules first, ranks the feasible alternatives, explains why options fail, and suggests the smallest relaxation when nothing works.

Key value

Constraint-based coordination.

Simple enough to use like a poll, but built around feasibility rather than vote counting alone.

01

Hard rules first.

Minimum attendance and required participants cannot be overruled by popularity.

02

Preferences still matter.

Participants mark options preferred, acceptable or unavailable; feasible options are then ranked.

03

No solution is still a result.

When every option fails, Coord explains the blockers and proposes the smallest useful relaxation.

Process

How it works.

Create → respond → solve → decide.

01

Create

Set the proposed times, duration and minimum attendance.

02

Respond

Participants choose preferred, acceptable or unavailable without needing an account.

03

Solve

Coord checks hard constraints, ranks feasible options and explains failures.

04

Decide

Select a feasible option or use the suggested relaxation when no option works.

Difference

Coord vs typical scheduling polls.

The comparison is conceptual: common scheduling polls are designed primarily to collect availability; Coord centers the decision rules around that availability.

Typical scheduling pollCoord
Primary questionWhen are people available?Which option is feasible under the rules?
Participant inputAvailability / preferencePreferred / acceptable / unavailable
ConstraintsUsually interpreted by the organizerExplicit minimum attendance and required participants
When nothing worksOrganizer reworks the poll or negotiates manuallyCoord identifies blockers and proposes minimal relaxation

Interface

The recommendation stays visible.

A compact host view shows feasibility, ranking and the reason behind the result.

ELSEHEIM / COORD · RECOMMENDATION

Project review

01
Tue 15 Sep · 14:00 — FEASIBLE

3 preferred · 1 acceptable · score 83

02
Wed 16 Sep · 10:00 — INFEASIBLE

Required participant unavailable.

Smallest relaxation: make the blocking required participant optional → 1 feasible option.

Simplified representation of the current Coord host flow.