MyDot Consultancy

Featured image: AI-generated conceptual illustration. Sources checked 26 October 2026.

A new project member needs a map: the objective, current plan, important decisions, responsible people and where to ask questions. They rarely need every document and message the project has accumulated. An onboarding agent should help them navigate the work without creating a sprawling copy of the team’s history.

The proposed workflow prepares a role-specific, source-linked orientation packet for review. It does not grant access, infer hidden politics or make claims about colleagues’ personalities. Its value is helping someone find the right evidence and understand which parts of the project remain unsettled.

Start with the person’s assignment

Imagine a hypothetical analyst joining a customer migration project. Their initial responsibility is to validate reporting requirements. They need the approved scope, data definitions, current milestones and the owner of unresolved reporting questions. They do not need unrelated commercial negotiations or every technical incident from the project’s beginning.

Ask the manager or project owner to define the onboarding objective and intended audience. A packet for an external contractor may differ from one for an internal lead. Use those differences to select sources, not to speculate about what the person should be trusted to know.

Keep access decisions in the source systems. Google Drive’s roles and permissions documentation provides the relevant access model for Drive material. The agent should assemble information the recipient is authorized to receive, not use its own broad access as a shortcut.

Build a source map with status labels

Identify the project charter, current plan, decision log, working documents and operational channels. For each, record the owner, purpose and status: authoritative, working draft, historical or unresolved. A new joiner needs to know which document governs the work, not merely which one ranks highly in search.

Use stable links and concise descriptions. “Current reporting definitions, maintained by the analytics owner” is more useful than a long generated summary that may become stale. Where a short summary helps, keep it tied to the source and the date checked.

If two documents appear current but conflict, surface the conflict to the owner. Do not choose one based on its title or polish. An onboarding packet should make uncertainty manageable rather than hide it to create a tidy story.

Recover only the decisions that matter now

Search project discussions for decisions that explain the current plan or the new member’s immediate tasks. Slack’s contextual search documentation describes a search interface that can support focused retrieval. The application still needs to respect access and query constraints.

Separate proposals from confirmed decisions. A thread discussing a possible migration date may not establish the schedule. Look for the final confirmation or an updated authoritative plan. If the evidence is incomplete, label the decision as unresolved and identify the appropriate owner.

Avoid copying entire discussions into the packet. Preserve the decision, relevant conditions and links for further reading. This reduces unnecessary disclosure and gives the new joiner a path to context without overwhelming the first day’s work.

Describe responsibilities without profiling people

List roles and verified ownership: who approves scope, who maintains the data dictionary and who handles access requests. Use explicit project records or manager confirmation. Do not infer influence, reliability or interpersonal relationships from message tone or activity volume.

A person who posts frequently is not necessarily the decision-maker. A quiet specialist may own a critical dependency. If ownership is unclear, make that a question for the project lead rather than filling the gap with a confident guess.

Keep contact details limited to the business purpose and approved directory information. The packet should help the new member reach the right role, not aggregate personal information about colleagues.

Create a first-week route, not a reading mountain

Organize the packet around a sequence of practical questions: what are we delivering, what is my part, what is already decided, what remains open and what should I do first? Link a small set of essential sources to each question.

For the fictional analyst, the first task might be to review the reporting definitions and prepare questions about unresolved metrics. The agent can suggest that task as a proposal for the manager. It should not assign work, change deadlines or message colleagues without the appropriate authorization.

Include a short “not yet established” section. Missing access, conflicting definitions and unconfirmed ownership are important onboarding facts. A packet that admits those gaps can prevent the new member from treating a draft as settled policy.

Review the packet as the recipient will see it

Have the project owner verify the scope, current status and proposed first steps. Then test the links using the recipient’s intended access, where an authorized process permits that check. A link visible to the agent may not be visible to the new joiner.

If access is missing, provide the approved request route. Do not change sharing to make the packet work unless explicitly authorized. Keep the packet itself in a location with appropriate permissions, especially if it combines information from several sources.

• The project objective and the recipient’s specific assignment.
• Current authoritative sources with owners and status labels.
• A small set of confirmed decisions relevant to the role.
• Open questions and unresolved dependencies.
• Verified responsibility and access-request routes.
• A manager-reviewed first-week reading and action sequence.

Test freshness and relevance

Use a project with an outdated plan, a superseded decision and a restricted document. Check whether the agent chooses current evidence, preserves historical context correctly and avoids disclosing restricted material. Ask a reviewer whether the packet answers the new member’s actual questions.

Measure corrections, broken links and time to locate essential information. Do not equate a longer packet with better onboarding. The operating costs include source retrieval, owner review and refreshing the map when the project changes.

Keep the map alive without hoarding history

Set a clear owner and review trigger for the packet. A major milestone change or responsibility change may require an update. Preserve source links and concise summaries rather than repeatedly copying full documents into a new store.

If the project already has a well-maintained onboarding page, the agent may only need to tailor a reading route. Where information is fragmented, it can assemble the map and expose gaps. In both cases, the goal is orientation: helping a person understand the current work and where to verify it, not manufacturing a permanent memory of everything the team has said.

Sources and further reading

Google Drive: Roles and permissions. Source and artifact access model; checked October 26, 2026.

Slack: assistant.search.context. Contextual search interface and constraints; checked October 26, 2026.