Shared team schedule

Keep a team aligned around the same project dates.

A shared team schedule gives members one project timeline for milestones and event updates. In MOADAY, you can prepare the project, invite members with a time-limited code, and see the same updates on the web and Android instead of maintaining separate schedule copies.

MOADAY shared team schedule with a private project invitation flow

Fictional example: an in-person seminar

Write each event around the decision or handoff it represents. A member should be able to understand the state of preparation from the timeline alone.

  1. Five weeks before
    Confirm the venue

    Lock the address, available hours, and capacity so the event date can remain stable.

  2. Four weeks before
    Confirm speakers and topics

    Set the titles and order before preparing the attendee announcement.

  3. Three weeks before
    Open attendee registration

    Verify the location, time, and registration instructions before publishing them.

  4. One week before
    Close presentation materials

    Collect materials early enough to check screen formats and media playback.

  5. One day before
    Walk through the venue

    Check registration, presentations, questions, and cleanup in their actual order.

  6. Two days after
    Send follow-up material

    Keep the attendee follow-up and internal review date inside the same project.

Share the schedule in three steps

Organize the project before inviting people, so a new member sees useful context as soon as they join.

1

Create the project and key events

Set a clear project name and add the dates that everyone needs to recognize.

2

Send an invitation code

Create the code from the project's sharing controls and deliver it privately to the intended members.

3

Update the shared project

Once members join, review and change the project events instead of maintaining separate copies.

Privacy reminder: Project names and event details are visible to joined members. Do not enter passwords, government identifiers, health data, or other sensitive information that the schedule does not need.

Where this works and where it does not

MOADAY shared projects are designed for people who need to manage the same project schedule together.

Good fit: a small group with shared milestones

Use it for events, study groups, launches, and other work where members need the same dates.

Good fit: web and Android use

Organize dates at a computer and check the same project from the Android app while moving.

Not a fit: public calendars or complex permissions

Use a specialist system for public subscriptions, departmental approval layers, or workforce attendance.

Frequently asked questions

Understand the sharing boundary before sending an invitation.

How long does a project invitation code work?

An invitation code remains valid for seven days after it is created. Anyone with a still-valid code can join, so send it only to the intended members.

Does someone need an account to join a full project?

Yes. Joining a full project requires Google sign-in. If you need to send only one task to someone without an account, MOADAY provides a separate private external task link.

Does creating a project share it automatically?

No. A project is not shared simply because it was created. You must create and send an invitation code, and the other person must join the project.

One project instead of many copies.

Add the essential dates, then invite only the people who need access.