WEBVTT

00:00:00.888 --> 00:00:04.015
Moving a schedule file is only part of the handoff.

00:00:04.275 --> 00:00:09.253
Your team also needs to know which project, version, and reporting period it represents.

00:00:09.538 --> 00:00:14.490
A representative exchange is a practical way to check how Kairos fits your process.

00:00:15.708 --> 00:00:20.385
Begin by agreeing the project, file format, version, and reporting period.

00:00:20.645 --> 00:00:23.222
Confirm the supported format with the team.

00:00:23.482 --> 00:00:27.772
A file import is a point in time exchange; it is not a continuous

00:00:27.772 --> 00:00:29.922
connection to your scheduling database.

00:00:31.160 --> 00:00:36.262
The Data and integrations page separates files and records from optional connections.

00:00:36.522 --> 00:00:39.888
Read the status and setup notes for the capability you need.

00:00:40.148 --> 00:00:44.550
An optional connection requires its own configuration and permissions.

00:00:45.748 --> 00:00:51.125
After an import, inspect dates, calendars, relationships, and project scope with the

00:00:51.125 --> 00:00:52.525
people who know the schedule.

00:00:52.798 --> 00:00:55.863
Keep the supporting narrative with the review context.

00:00:56.135 --> 00:01:00.725
Attaching a document does not mean its contents were automatically interpreted.

00:01:01.972 --> 00:01:06.950
If the workflow includes an export, inspect the result in the receiving environment

00:01:06.950 --> 00:01:08.250
before relying on it.

00:01:08.522 --> 00:01:11.562
Agree which fields and calculations must match.

00:01:11.822 --> 00:01:16.050
Record any differences and the team member responsible for resolving them.

00:01:17.268 --> 00:01:21.645
Bring one representative file type and a short checklist to the evaluation.

00:01:21.905 --> 00:01:25.833
Confirm the input, inspect its context, and review the output.

00:01:26.105 --> 00:01:30.645
That makes the handoff understandable to both your technical team and your manager.
