Research workflows
Verify a signal against its source
A two-minute source check for market signals, so the claims you share stand up to a second reader.
On this page
A relevant signal still needs checking before you repeat it. Use the summary to decide what deserves your attention, then open the source before a claim goes into a decision, a deck or a team update. Every signal in Flowy links to the article, publication or document it came from.
Open a signal to see its summary next to the source site and date. Read article takes you to the original.
The two-minute check
Confirm who is speaking
A regulator's formal publication, a company announcement, a journalist's report and an analyst's projection carry different weight. When an article quotes someone else, find the original statement for anything important.
Check the date and the period
The publication date and the period the data covers are often different. A full-year forecast, a first-half result and a year-to-date figure can't be compared as if they describe the same thing. Write the period next to every premium, growth or market-size number.
Check the scope
Look for differences in product line or segment, gross versus net premiums, individual versus group business, company versus industry figures, national versus regional operations, and announced availability versus real uptake. Two accurate numbers can still make a misleading comparison.
Name the status precisely
Say "proposed" for a consultation and "in force" only for a rule that has taken effect. The status table below has the wording for every case.
Separate evidence from interpretation
Write what the source says, what you think it means and what to do next as three labeled lines. There's an example below.
Keep the source link
Put the link beside the claim, so a reviewer can check it without repeating your search, and a later correction is easy.
Status wording
| Status | Say |
|---|---|
| Proposed or out for consultation | "is proposed", "is under consultation" |
| Under review | "is being evaluated" |
| Approved, not yet in force | "has been approved and takes effect on…" |
| Enacted and in force | "is in force", "is effective" |
| Company announcement | "the company announced", "launched" |
| Forecast | "is projected", "the analyst expects" |
Never turn an evaluation or a projection into a finished regulatory or pricing change.
Evidence, interpretation, action
Label each part of the note. For example:
- Evidence: the source reports that the company launched the service in 31 locations.
- Interpretation: this could strengthen its EV service proposition.
- Action: check real coverage and service levels in our priority regions.
When to hold a signal back
Don't share it yet when:
- the source won't open or can't be found
- the summary and the source disagree
- a number has no clear period, unit or scope
- the regulatory status is ambiguous
- the claim rests on an unnamed source or an unverified projection
- it could drive a material product, legal, compliance or commercial decision
Send these to the right reviewer and leave the gap open until someone has checked it.
A review record for important claims
| Field | Example |
|---|---|
| Claim | One precise statement |
| Source | Publisher and link |
| Published | The date the source shows |
| Data period | The period the claim applies to |
| Status | Proposed, under review, effective, announced or projected |
| Verdict | Supported, partly supported, unsupported or unclear |
| Reviewer | Who checked it |
Next: build a watchlist that feeds this check, or use the same discipline on product documents in Compare products with RIPLAY evidence. Regulatory teams can see the full routine in regulatory monitoring.
Check your own feed
Every signal in Flowy links straight to its source. Set up a tracker and try the check on real items.