Source date
MetricsPublishedHigh confidence
CompanyOrbit LabsFundJuniper Fund I
Signals, condensed.
Three options for a signal that works everywhere. The same information in each: a visible date, a clear update, distinct objects, and its source.
Proposed workflow:To review → Published or DismissedSee the simpler state model
Object keyFundCompanyPersonLabels and icons stay visible in every option.
Compare the same signals below. Open an update or its source for context. Review decisions are mirrored across the designs.
A
5 signalsDate-led stream
RecommendedDates align beside the update and its supporting details.
Source date
FundingTo reviewHigh confidence
CompanyFieldwork SystemsFundJuniper Fund I · Lead investor
Source date
TeamPublishedHigh confidence
PersonLea Rivera · Chief operating officerCompanyOrbit Labs
Received
ReadPublishedBy Maya Chen
CompanyOrbit LabsPersonLea Rivera
Source date
Next stepTo reviewLaterBy Maya · waiting for Lea’s availability
PersonLea RiveraFundJuniper Fund I
Best default for feeds, record pages, and small panels. Relationships sit just below the update.
B
5 signalsObject first
Objects come first, followed by the update.
CompanyOrbit LabsFundJuniper Fund I
Source date
MetricsPublishedHigh confidence
CompanyFieldwork SystemsFundJuniper Fund I · Lead investor
Source date
FundingTo reviewHigh confidence
PersonLea Rivera · Chief operating officerCompanyOrbit Labs
Source date
TeamPublishedHigh confidence
CompanyOrbit LabsPersonLea Rivera
Received
ReadPublishedBy Maya Chen
PersonLea RiveraFundJuniper Fund I
Source date
Next stepTo reviewLaterBy Maya · waiting for Lea’s availability
Best when quickly sorting mixed funds, companies, and people. More room goes to the connected objects.
C
5 signalsAligned ledger
Stable columns for dates, objects, updates, and sources.
- Date
- Source date
- Objects
- CompanyOrbit LabsFundJuniper Fund I
- Signal
- MetricsPublishedHigh confidence
- Source
- Date
- Source date
- Objects
- CompanyFieldwork SystemsFundJuniper Fund I · Lead investor
- Signal
- FundingTo reviewHigh confidence
- Source
- Date
- Source date
- Objects
- PersonLea Rivera · Chief operating officerCompanyOrbit Labs
- Signal
- TeamPublishedHigh confidence
- Source
- Date
- Received
- Objects
- CompanyOrbit LabsPersonLea Rivera
- Signal
- ReadPublishedBy Maya Chen
- Source
- Date
- Source date
- Objects
- PersonLea RiveraFundJuniper Fund I
- Signal
- Next stepTo reviewLaterBy Maya · waiting for Lea’s availability
- Source
Best for scanning a large review queue on a wide screen. Columns stack into a compact row in small panels.
Workflow proposal
One workflow. Three states.
Keep the main question simple: does this need review, is it published, or was it dismissed? Everything else explains the decision or the work still in progress.
To review
Not published. Ready for a decision, waiting for publication, or set aside for later.
Actions: Publish · Dismiss · Later
Published
Saved and visible on the relevant records. Edits, verification, and reported concerns stay in its context and history.
Actions: Open · Report a concern
Dismissed
Not part of the live record. The source, reason, and previous decisions remain available.
Action: Reopen for review
Where the existing states go
| Today | Proposed display |
|---|---|
| Proposed / pending | To review |
| Accepted, not yet published | To review Approved · publication pending. Show a publication retry if it failed. |
| Parked / held | To review Later, with the reason or return date. A manual hold stays held until resumed. |
| Live / edited / verified | Published Edited and verified become history details. |
| Rejected / removed | Dismissed Keep the reason and retained source history. |
Feedback belongs beside the action
To reviewPublishing…
Keep the saved state until publication is confirmed. A failed save leaves the signal here with Retry; it does not create a new lifecycle state.
Separate the review list into Now and Later. That is scheduling, not another kind of signal. Missing sources, unresolved objects, and reported concerns stay attached to the relevant information.
A saved decision stays saved. If refreshing the list fails afterward, show “Saved · refresh needed.” Never ask the user to repeat a decision that already succeeded.
The same action everywhere
One shared Publish or Dismiss operation from a fund, company, person, or review queue. Publication and its record links are saved together.
Retry without duplicates
A retry continues the original decision. If a response is lost, check its result before attempting the same write again.
Keep decision history
Save the decision and history together. Undo records a new event, and a shared signal is preserved when one proposal is reopened.
Suggested rollout: agree on this model, unify the decision and retry behavior, then migrate the stored states after checking holds, duplicates, undo, and publication failures. Simplifying labels alone will not remove the underlying failure cases.
Design proposals only. All examples are fictional; these controls change no real records.