How to use a Righthand with Basecamp

Start with the Basecamp project's actual tools

Use Righthand with Basecamp to prepare a project handoff that connects outstanding to-dos to their relevant discussion and schedule context. The project should be identified explicitly, and the report should state which tools were reviewed. An account can contain many projects with similar names.

Basecamp's official API guide describes the project dock as the source of available project tools. Review the enabled tools rather than assuming every project contains the same to-do, message, schedule, or file structure. This keeps missing material from being mistaken for an empty project.

Define a narrow handoff scope

Give the account and project identity, included to-do lists, relevant message-board threads, and approved schedule items. For an illustrative agency handoff, focus on unfinished launch tasks and the decision thread that defines acceptance.

Check the exposed reads through integrations. If the necessary project tool is unavailable, provide an approved export or authorize a browser review of the named project. A provider's API capabilities do not establish which native actions the selected Righthand connection supports.

A complete illustrative request

At 2 PM America/Los_Angeles on Thursday, review the approved Basecamp launch project, its specified to-do lists, and linked decision messages. Prepare a private handoff with project and to-do identity, completion state, explicit assignees, due information where available, and supporting message links. List missing owners and unresolved acceptance questions separately. Do not complete to-dos, post messages, or change the schedule. Send to me for project-owner review and reconcile the included lists and enabled project tools.

This example is illustrative. A discussion agreeing on a goal does not necessarily establish that the related to-do is complete or that a client approved the deliverable.

Define what the handoff shows

An example entry might say: “Launch checklist to-do remains incomplete; decision thread confirms required copy review; reviewer not explicitly assigned.” The assistant can propose asking the project owner to select a reviewer, while leaving the assignment itself unchanged.

Retain message context when it explains a due-date mismatch. A later message may supersede an earlier plan. If attachments or files are missing, link what is available and mark the unsupported interpretation instead of summarizing unseen content.

Reconcile unavailable and changed records

Match to-dos by identity and project on subsequent runs. A renamed list should not turn its existing tasks into new work. A missing endpoint or record can reflect disabled tooling, permissions, or deletion; report the ambiguity with its source reference.

If the owner later authorizes supported updates, target only the reviewed records and retrieve them again. Confirm the resulting completion, assignment, or schedule information independently. Delivering a report does not prove that any project record changed.

Use Righthand connection permissions for the selected account and reviewer. Check pricing before expanding the handoff into recurring coordination across several Basecamp projects.