WEBVTT

00:00:00.400 --> 00:00:01.460
Meet Maya Chen.

00:00:02.040 --> 00:00:05.600
She manages Cedar Grove and she relies on people she knows.

00:00:07.000 --> 00:00:09.600
Jordan Ellis is the local fire marshal.

00:00:10.100 --> 00:00:13.400
Maya needs her report tied to the right system with findings

00:00:13.400 --> 00:00:14.200
she can follow.

00:00:16.500 --> 00:00:18.280
David maintains the elevators.

00:00:18.880 --> 00:00:20.900
His training documentation has expired.

00:00:21.740 --> 00:00:23.140
Maya requests the current version.

00:00:24.800 --> 00:00:27.040
Marcus keeps the heating and cooling running.

00:00:27.600 --> 00:00:29.300
His documentation needs an update.

00:00:30.100 --> 00:00:33.880
Maya works with two preferred vendors, and Jordan, the local fire

00:00:33.880 --> 00:00:34.400
marshal.

00:00:34.960 --> 00:00:37.560
Different responsibilities, clear next steps.

00:00:38.300 --> 00:00:40.800
Maya starts on the ComplySync landing page.

00:00:42.890 --> 00:00:45.490
She explores the workflow, then opens her workspace.

00:00:47.330 --> 00:00:50.470
Here, she can turn a missing document into a clear request,

00:00:51.050 --> 00:00:53.370
a response, and an accountable review.

00:00:55.500 --> 00:00:59.680
Maya uses ComplySync to request updated documentation from Marcus.

00:01:00.440 --> 00:01:04.420
She identifies the document she needs and adds instructions so Marcus

00:01:04.420 --> 00:01:06.160
knows exactly what to send.

00:01:06.800 --> 00:01:10.060
Before sending, she checks the recipient and delivery choice.

00:01:10.720 --> 00:01:12.800
The request now has a clear status.

00:01:13.380 --> 00:01:17.100
The documentation is still needed and Maya can follow its progress.

00:01:17.100 --> 00:01:21.300
Later, Marcus receives her text message and opens the request.

00:01:22.250 --> 00:01:25.890
To open the private request, Marcus enters the code sent to

00:01:25.890 --> 00:01:27.130
his invited phone number.

00:01:27.610 --> 00:01:30.990
He can respond right in the browser without downloading an app

00:01:30.990 --> 00:01:32.290
or creating an account.

00:01:34.510 --> 00:01:37.510
With his current document attached, he submits it to Maya.

00:01:38.090 --> 00:01:41.710
The confirmation tells him his response is stored and awaiting review.

00:01:44.110 --> 00:01:47.250
Maya then inspects the documentation and records her decision.

00:01:53.550 --> 00:01:58.170
David's training documentation has expired, so Maya asks for the current

00:01:58.170 --> 00:01:58.590
version.

00:01:59.170 --> 00:02:02.110
Her feedback explains what needs updating and why.

00:02:05.700 --> 00:02:08.420
When David opens it, the next step is clear.

00:02:08.980 --> 00:02:12.540
Provide the revised document with its issue and expiration dates.

00:02:15.530 --> 00:02:19.110
He submits that revision while the earlier version stays in history.

00:02:23.570 --> 00:02:27.870
Maya reviews the new evidence separately, keeping the decision connected to

00:02:27.870 --> 00:02:29.670
the document she actually inspected.

00:02:30.550 --> 00:02:34.070
Maya also receives findings from Jordan, the fire marshal.

00:02:34.690 --> 00:02:36.650
Jordan is the external report author.

00:02:37.390 --> 00:02:39.270
Maya manages the record in ComplySync.

00:02:39.850 --> 00:02:43.050
She connects the findings to the property and fire alarm system,

00:02:43.330 --> 00:02:46.910
records the inspection details, and preserves the received report.

00:02:47.410 --> 00:02:51.350
Here, the finding concerns an illegible detector location label.

00:02:51.790 --> 00:02:54.890
The report and its photos give Maya the context she needs

00:02:54.890 --> 00:02:56.250
to organize follow -up.

00:02:56.950 --> 00:02:58.550
Photos document visible conditions.

00:02:58.830 --> 00:03:02.890
They do not establish functional test results or a complete system

00:03:02.890 --> 00:03:03.350
inspection.

00:03:05.450 --> 00:03:09.030
Maya opens the exact report version and reviews the evidence.

00:03:09.950 --> 00:03:12.030
Jordan remains the external report author.

00:03:12.870 --> 00:03:16.090
Maya manages the record and records her own internal review.

00:03:18.450 --> 00:03:23.130
Maya's internal review does not grant regulatory clearance or resolve a

00:03:23.130 --> 00:03:23.650
deficiency.

00:03:24.610 --> 00:03:26.090
Corrective work remains separate.

00:03:27.550 --> 00:03:30.410
Reviewing the report is only part of Maya's work.

00:03:30.970 --> 00:03:34.510
The finding has a separate corrective action task with the source

00:03:34.510 --> 00:03:36.890
report and next action kept together.

00:03:37.390 --> 00:03:39.870
Accepting the report leaves that task open.

00:03:40.410 --> 00:03:44.670
When corrective evidence arrives, Maya checks it against the finding before

00:03:44.670 --> 00:03:47.230
recording an internal resolution and a note.

00:03:47.590 --> 00:03:51.390
That completes her follow -up, not the Fire Marshal's official case.

00:03:51.950 --> 00:03:56.230
The retained history shows the report, the resolution note, and who

00:03:56.230 --> 00:03:57.250
recorded the decision.

00:04:02.450 --> 00:04:05.730
With the immediate follow -up recorded, Maya looks ahead.

00:04:06.230 --> 00:04:09.490
The agenda lists dated work, while the month view places it

00:04:09.490 --> 00:04:10.110
on the calendar.

00:04:13.810 --> 00:04:17.510
She filters to Marcus's company and selects the expiration date to

00:04:17.510 --> 00:04:19.190
see which document needs attention.

00:04:23.450 --> 00:04:26.810
From there, she opens the source record, then returns to the

00:04:26.810 --> 00:04:27.830
same calendar view.

00:04:31.510 --> 00:04:35.470
No Date Set keeps open work visible across the workspace, and

00:04:35.470 --> 00:04:38.150
acceptance never stops a document from expiring.

00:04:38.550 --> 00:04:40.710
Marcus may optionally connect an account.

00:04:41.450 --> 00:04:44.030
Permission to reuse documents remains separate.

00:04:45.550 --> 00:04:46.530
Marcus can respond.

00:04:49.930 --> 00:04:51.290
David can correct his evidence.

00:04:53.730 --> 00:04:55.250
Jordan can document findings.

00:04:57.750 --> 00:04:59.310
And Maya knows the next step.

00:05:00.550 --> 00:05:01.350
Know the document.

00:05:02.370 --> 00:05:02.910
Follow the finding.

00:05:03.550 --> 00:05:05.870
ComplySync, a HiveSync product.

00:05:06.650 --> 00:05:07.990
Explore ComplySync.
