WEBVTT

1
00:00:00.270 --> 00:00:02.740
Once you have explored individual cases,

2
00:00:03.100 --> 00:00:05.160
the next question is how to follow the

3
00:00:05.210 --> 00:00:07.050
activity that matters to your team.

4
00:00:07.230 --> 00:00:09.120
You may care about a particular

5
00:00:09.250 --> 00:00:11.970
applicant, a corridor or a few cities.

6
00:00:12.400 --> 00:00:14.780
P&Z Radar’s public archive can help you

7
00:00:14.820 --> 00:00:15.990
define that focus.

8
00:00:16.360 --> 00:00:18.150
Let’s look at applicant history and

9
00:00:18.200 --> 00:00:20.350
market activity, then review the

10
00:00:20.400 --> 00:00:22.370
monitoring options without turning every

11
00:00:22.510 --> 00:00:24.960
filing into an inbox distraction.

12
00:00:25.999 --> 00:00:28.109
The petitioner index groups names found

13
00:00:28.209 --> 00:00:29.479
in the collected cases.

14
00:00:29.899 --> 00:00:31.879
Open one and you can review its recorded

15
00:00:32.009 --> 00:00:34.149
filings, cities and dates.

16
00:00:34.569 --> 00:00:36.059
This is useful background when

17
00:00:36.099 --> 00:00:38.209
researching who is active in a market.

18
00:00:38.609 --> 00:00:40.229
Treat the name as it appears in the

19
00:00:40.269 --> 00:00:42.699
record, and check the individual cases

20
00:00:43.059 --> 00:00:45.169
before assuming two similar names are

21
00:00:45.209 --> 00:00:46.719
the same organization.

22
00:00:47.279 --> 00:00:49.949
A filing history is research material,

23
00:00:50.289 --> 00:00:51.819
not proof that someone is currently

24
00:00:51.999 --> 00:00:53.089
buying your service.

25
00:00:53.800 --> 00:00:55.590
Next, look at trends.

26
00:00:55.950 --> 00:00:57.840
The charts summarize the archive by

27
00:00:57.880 --> 00:01:00.170
scheduled hearing month, case type and

28
00:01:00.220 --> 00:01:01.120
geography.

29
00:01:01.480 --> 00:01:02.960
They can help you decide where to

30
00:01:03.000 --> 00:01:05.070
investigate next, but they are not a

31
00:01:05.120 --> 00:01:07.140
count of completed construction or final

32
00:01:07.320 --> 00:01:08.060
approvals.

33
00:01:08.400 --> 00:01:10.150
Changes can also reflect what was

34
00:01:10.240 --> 00:01:11.610
captured in the archive.

35
00:01:11.860 --> 00:01:14.280
Use the chart to form a question, then

36
00:01:14.380 --> 00:01:16.170
move back to individual records and

37
00:01:16.220 --> 00:01:17.630
sources to answer it.

38
00:01:18.233 --> 00:01:20.203
Now define what your team actually needs

39
00:01:20.343 --> 00:01:21.063
to follow.

40
00:01:21.413 --> 00:01:24.203
One city, a county and a whole metro are

41
00:01:24.243 --> 00:01:25.593
different research scopes.

42
00:01:25.863 --> 00:01:27.793
Review the available coverage before

43
00:01:28.013 --> 00:01:29.113
choosing one.

44
00:01:29.633 --> 00:01:31.433
The product describes matching alerts

45
00:01:31.563 --> 00:01:33.903
and keyword filters; the public trial

46
00:01:33.993 --> 00:01:35.923
gives you a way to evaluate the data in

47
00:01:35.963 --> 00:01:36.583
a city.

48
00:01:36.933 --> 00:01:38.953
Start narrowly enough that you can read

49
00:01:39.053 --> 00:01:40.713
what arrives and judge whether the

50
00:01:40.753 --> 00:01:42.013
matches are relevant.

51
00:01:42.680 --> 00:01:44.790
For a team workflow, review how the

52
00:01:44.830 --> 00:01:46.430
information is delivered.

53
00:01:46.900 --> 00:01:49.640
The site describes email and private RSS

54
00:01:49.730 --> 00:01:52.740
options, with API access on the eligible

55
00:01:52.870 --> 00:01:53.560
plans.

56
00:01:53.980 --> 00:01:55.500
Developers should check the documented

57
00:01:55.680 --> 00:01:58.110
host, authentication and limits before

58
00:01:58.330 --> 00:01:59.570
connecting a system.

59
00:02:00.080 --> 00:02:02.330
Keep private feed links and API keys

60
00:02:02.460 --> 00:02:03.000
private.

61
00:02:03.310 --> 00:02:05.460
An integration is only useful when it

62
00:02:05.510 --> 00:02:07.750
brings the right records into a place

63
00:02:07.890 --> 00:02:10.090
your team actually checks and preserves

64
00:02:10.220 --> 00:02:11.730
a link back to the source.

65
00:02:12.393 --> 00:02:14.843
For your first week, choose one market,

66
00:02:15.093 --> 00:02:17.423
a small set of research questions and a

67
00:02:17.473 --> 00:02:19.223
simple way to review the results.

68
00:02:19.623 --> 00:02:21.603
Use applicant history to understand

69
00:02:21.733 --> 00:02:24.613
context, trends to spot areas worth

70
00:02:24.743 --> 00:02:27.083
investigating, and the original packets

71
00:02:27.173 --> 00:02:28.693
to check important details.

72
00:02:29.193 --> 00:02:31.573
Then evaluate whether ongoing monitoring

73
00:02:31.703 --> 00:02:33.423
earns a place in your routine.

74
00:02:33.743 --> 00:02:35.313
Start with the public archive and

75
00:02:35.363 --> 00:02:37.693
coverage page, and move into a trial

76
00:02:37.783 --> 00:02:39.363
when the records look relevant to your

77
00:02:39.403 --> 00:02:39.963
work.