WEBVTT 1 00:00:00.400 --> 00:00:01.460 Meet Maya Chen. 2 00:00:02.040 --> 00:00:05.600 She manages Cedar Grove and she relies on people she knows. 3 00:00:07.000 --> 00:00:10.660 Jordan Ellis is the fire marshal, a code compliance authority. 4 00:00:11.540 --> 00:00:14.900 Maya needs her report tied to the right system with findings 5 00:00:14.900 --> 00:00:15.680 she can follow. 6 00:00:16.500 --> 00:00:18.280 David maintains the elevators. 7 00:00:18.880 --> 00:00:20.900 His training documentation has expired. 8 00:00:21.740 --> 00:00:23.140 Maya requests the current version. 9 00:00:24.800 --> 00:00:26.960 Marcus keeps the heating and cooling running. 10 00:00:27.620 --> 00:00:29.360 His documentation needs an update. 11 00:00:29.960 --> 00:00:32.680 Two preferred vendors and a code compliance authority. 12 00:00:33.010 --> 00:00:33.950 Different responsibilities. 13 00:00:34.360 --> 00:00:35.180 Clear next steps. 14 00:00:35.800 --> 00:00:38.300 Maya starts on the ComplySync landing page. 15 00:00:40.390 --> 00:00:42.990 She explores the workflow, then opens her workspace. 16 00:00:44.830 --> 00:00:47.970 Here, she can turn a missing document into a clear request, 17 00:00:48.550 --> 00:00:50.870 a response, and an accountable review. 18 00:00:51.700 --> 00:00:55.880 Maya uses ComplySync to request updated documentation from Marcus. 19 00:00:56.700 --> 00:01:00.440 Maya selects the required document and adds instructions for Marcus. 20 00:01:01.750 --> 00:01:05.590 She checks the recipient and delivery choice, then sends the request. 21 00:01:13.550 --> 00:01:16.930 Marcus receives Maya's text message and opens the request. 22 00:01:19.520 --> 00:01:21.900 He verifies his invited contact in the browser. 23 00:01:24.050 --> 00:01:26.550 Marcus needs no app or account to submit. 24 00:01:27.250 --> 00:01:31.010 He selects his current file, checks its details, and attaches it. 25 00:01:32.050 --> 00:01:33.430 Marcus chooses submit. 26 00:01:36.400 --> 00:01:37.980 A receipt confirms his response. 27 00:01:38.920 --> 00:01:40.480 Maya can now review the evidence. 28 00:01:41.250 --> 00:01:46.410 Maya opens Marcus's submission, inspects the documentation, and records her review. 29 00:01:51.050 --> 00:01:55.290 Maya checks David's expired documentation and requests the current version. 30 00:01:56.050 --> 00:01:59.950 Her feedback explains which version she needs and why the earlier 31 00:01:59.950 --> 00:02:01.610 evidence cannot be accepted. 32 00:02:03.050 --> 00:02:04.730 David reads Maya's feedback. 33 00:02:12.750 --> 00:02:14.810 David submits the revised document. 34 00:02:16.950 --> 00:02:19.270 The earlier version remains in history. 35 00:02:21.050 --> 00:02:23.250 Maya reviews this revision separately. 36 00:02:23.830 --> 00:02:26.870 A newer upload never inherits an earlier approval. 37 00:02:28.050 --> 00:02:31.290 Maya receives the fire marshal's report and adds it to the 38 00:02:31.290 --> 00:02:33.230 property's private inspection records. 39 00:02:34.050 --> 00:02:38.090 Maya records the property and fire alarm system, the inspection date, 40 00:02:38.830 --> 00:02:41.010 Jordan as report author and the findings. 41 00:02:41.690 --> 00:02:45.530 This private inspection record stays separate from vendor certifications. 42 00:02:51.250 --> 00:02:54.670 Maya preserves the received report and its supporting photos. 43 00:02:55.690 --> 00:02:57.250 Photos document visible findings. 44 00:02:57.830 --> 00:03:01.730 They do not establish functional test results or a complete system 45 00:03:01.730 --> 00:03:02.130 inspection. 46 00:03:02.950 --> 00:03:06.530 Maya opens the exact report version and reviews the evidence. 47 00:03:07.450 --> 00:03:09.530 Jordan remains the external report author. 48 00:03:10.370 --> 00:03:13.590 Maya manages the record and records her own internal review. 49 00:03:15.950 --> 00:03:20.630 Maya's internal review does not grant regulatory clearance or resolve a 50 00:03:20.630 --> 00:03:21.150 deficiency. 51 00:03:22.110 --> 00:03:23.590 Corrective work remains separate. 52 00:03:25.050 --> 00:03:27.310 How does Maya keep corrective work accountable? 53 00:03:28.110 --> 00:03:31.130 She follows the finding into its separate ActionHub task. 54 00:03:31.890 --> 00:03:34.730 The source report and next action remain connected. 55 00:03:35.230 --> 00:03:37.290 Report acceptance leaves that work open. 56 00:03:45.150 --> 00:03:49.450 Maya reviews the corrective evidence and records an internal resolution with 57 00:03:49.450 --> 00:03:49.870 a note. 58 00:03:50.470 --> 00:03:52.510 This completes her corrective follow-up. 59 00:03:53.090 --> 00:03:56.410 It does not mean the fire marshal accepted the correction or 60 00:03:56.410 --> 00:03:57.690 closed an official case. 61 00:04:04.850 --> 00:04:09.150 The saved history preserves the report, the resolution note, and the 62 00:04:09.150 --> 00:04:09.490 reviewer. 63 00:04:11.050 --> 00:04:13.170 How does Maya see what's coming next? 64 00:04:14.050 --> 00:04:15.530 Agenda lists her dated work. 65 00:04:18.550 --> 00:04:19.770 Month shows it on the calendar. 66 00:04:22.290 --> 00:04:25.950 Maya filters to Marcus's company and selects the expiration date. 67 00:04:32.350 --> 00:04:33.470 She opens the document 68 00:04:36.350 --> 00:04:38.310 returns to the same calendar view. 69 00:04:39.750 --> 00:04:43.350 No date set keeps open work visible across the workspace. 70 00:04:44.050 --> 00:04:46.310 An accepted document can still expire. 71 00:04:47.050 --> 00:04:49.210 Marcus may optionally connect an account. 72 00:04:49.950 --> 00:04:52.530 Permission to reuse documents remains separate. 73 00:04:54.050 --> 00:04:55.030 Marcus can respond. 74 00:04:58.430 --> 00:04:59.790 David can correct his evidence. 75 00:05:02.230 --> 00:05:03.750 Jordan can document findings. 76 00:05:06.250 --> 00:05:07.810 And Maya knows the next step. 77 00:05:09.050 --> 00:05:09.850 Know the document. 78 00:05:10.870 --> 00:05:11.410 Follow the finding. 79 00:05:12.050 --> 00:05:14.370 ComplySync, a HiveSync product. 80 00:05:15.150 --> 00:05:16.490 Explore ComplySync.