WEBVTT

1
00:00:00.310 --> 00:00:02.070
A company does not tell its whole story

2
00:00:02.200 --> 00:00:03.170
in one filing.

3
00:00:03.500 --> 00:00:05.840
You may find a workforce notice in one

4
00:00:05.930 --> 00:00:08.040
place, a corporate disclosure in

5
00:00:08.080 --> 00:00:10.020
another, and broader labor data

6
00:00:10.150 --> 00:00:11.000
somewhere else.

7
00:00:11.270 --> 00:00:13.290
LaborCurrent gives you several ways to

8
00:00:13.330 --> 00:00:15.040
bring those records into your research

9
00:00:15.130 --> 00:00:15.780
routine.

10
00:00:16.120 --> 00:00:18.770
Let’s build a simple process: start with

11
00:00:18.810 --> 00:00:21.820
an employer, add context, then decide

12
00:00:22.000 --> 00:00:23.930
how to keep track of relevant changes.

13
00:00:24.790 --> 00:00:27.020
Start with a question, not a score.

14
00:00:27.280 --> 00:00:29.300
What has this employer filed, in which

15
00:00:29.430 --> 00:00:31.520
places, and over what period?

16
00:00:31.900 --> 00:00:33.830
Look at the notice rows and dates before

17
00:00:34.060 --> 00:00:35.520
forming a conclusion.

18
00:00:36.030 --> 00:00:37.650
For a workforce team, the practical

19
00:00:37.790 --> 00:00:39.720
question may be where services could be

20
00:00:39.760 --> 00:00:40.320
needed.

21
00:00:40.700 --> 00:00:42.540
For a recruiting product, it may be

22
00:00:42.670 --> 00:00:45.050
which employer events are relevant to a

23
00:00:45.100 --> 00:00:45.750
market.

24
00:00:46.220 --> 00:00:48.650
The records describe events; they do not

25
00:00:48.830 --> 00:00:51.160
identify individual workers for you.

26
00:00:51.892 --> 00:00:53.692
Now add another source where it is

27
00:00:53.732 --> 00:00:54.512
relevant.

28
00:00:54.842 --> 00:00:56.772
SEC filings can provide corporate

29
00:00:56.822 --> 00:00:59.382
context, and bankruptcy records can add

30
00:00:59.472 --> 00:01:01.062
another part of the timeline.

31
00:01:01.402 --> 00:01:03.242
Check the employer match and each source

32
00:01:03.422 --> 00:01:04.002
date.

33
00:01:04.412 --> 00:01:06.162
The useful result is a documented

34
00:01:06.342 --> 00:01:08.002
sequence you can investigate.

35
00:01:08.282 --> 00:01:10.302
It is not a guarantee that one event

36
00:01:10.482 --> 00:01:12.862
caused another, or a prediction of what

37
00:01:12.912 --> 00:01:14.462
the company will do next.

38
00:01:14.932 --> 00:01:16.992
Keep observation and interpretation

39
00:01:17.312 --> 00:01:18.792
separate in your notes.

40
00:01:19.290 --> 00:01:21.760
If this is a recurring question, look at

41
00:01:21.800 --> 00:01:22.420
alerts.

42
00:01:22.760 --> 00:01:25.730
The page separates layoff notices, SEC

43
00:01:25.820 --> 00:01:28.690
alerts, a blog digest and reports.

44
00:01:29.190 --> 00:01:30.710
Choose the stream that matches your

45
00:01:30.760 --> 00:01:33.450
task, then review the available filters

46
00:01:33.590 --> 00:01:34.860
and delivery description.

47
00:01:35.240 --> 00:01:37.220
A focused set of relevant updates is

48
00:01:37.260 --> 00:01:39.460
more useful than a large inbox you never

49
00:01:39.550 --> 00:01:40.180
read.

50
00:01:40.580 --> 00:01:42.020
For this walkthrough, we are showing

51
00:01:42.160 --> 00:01:44.360
where setup begins; your confirmation

52
00:01:44.540 --> 00:01:46.330
and delivery settings belong to your own

53
00:01:46.420 --> 00:01:46.780
account.

54
00:01:47.207 --> 00:01:49.537
You do not have to use every product.

55
00:01:49.887 --> 00:01:51.997
A dataset download suits a defined

56
00:01:52.227 --> 00:01:53.567
offline analysis.

57
00:01:53.797 --> 00:01:55.947
An API suits a workflow you run

58
00:01:55.997 --> 00:01:56.867
repeatedly.

59
00:01:57.257 --> 00:01:59.317
A report is a different deliverable when

60
00:01:59.367 --> 00:02:00.977
you want a written briefing rather than

61
00:02:01.067 --> 00:02:01.967
raw rows.

62
00:02:02.327 --> 00:02:04.117
The store distinguishes a one-time

63
00:02:04.257 --> 00:02:06.427
snapshot from a refresh subscription,

64
00:02:06.727 --> 00:02:08.787
and reports are offered separately from

65
00:02:08.837 --> 00:02:09.957
API plans.

66
00:02:10.317 --> 00:02:12.157
Read those boundaries before deciding

67
00:02:12.247 --> 00:02:13.997
which purchase, if any, serves your

68
00:02:14.047 --> 00:02:14.587
work.

69
00:02:15.073 --> 00:02:17.133
Make the routine easy to repeat.

70
00:02:17.433 --> 00:02:19.633
Record the employer, the period you

71
00:02:19.683 --> 00:02:21.833
checked, the sources you used and the

72
00:02:21.883 --> 00:02:23.813
question that still needs an answer.

73
00:02:24.213 --> 00:02:25.883
Then choose the lightest way to stay

74
00:02:25.923 --> 00:02:26.753
informed.

75
00:02:27.183 --> 00:02:29.203
Start by researching one employer you

76
00:02:29.253 --> 00:02:30.193
follow already.

77
00:02:30.473 --> 00:02:32.583
If the records are useful, explore the

78
00:02:32.633 --> 00:02:34.563
relevant alert or delivery option.

79
00:02:34.923 --> 00:02:37.123
The value is a clearer, repeatable

80
00:02:37.303 --> 00:02:39.143
research process grounded in public

81
00:02:39.363 --> 00:02:41.163
filings, with your judgment still in

82
00:02:41.203 --> 00:02:42.013
control.