Capstone Build: Student Technology Event

You will build a connected digital workspace for a fictional student technology event. The event is deliberately fictional so the project can demonstrate real workflow decisions without collecting real attendee information.

The system you are building

Your capstone must connect seven course tools:

DRIVE
├── DOCS project plan
├── SHEETS budget / data
├── SLIDES briefing
└── FORMS registration or feedback

GMAIL → invitation / coordination
CALENDAR → event / meeting

The goal is not seven disconnected screenshots. The files should reference and support one coherent event.

1 — Drive structure

Create a clear project folder with logical names. Include only the capstone files needed for the scenario.

Record the intended sharing boundary for the folder and for any file that differs from the folder's normal audience.

2 — Docs project plan

Create a structured one- to two-page plan containing:

• event purpose;
• intended audience;
• schedule/major tasks;
• responsibilities;
• resource links;
• one explicit privacy/access assumption.

Use headings and accessible link text.

3 — Sheets budget or planning data

Create a small synthetic budget or resource table with at least one formula and one useful chart or summary.

Example fields: item, category, quantity, unit cost, total.

Do not use real financial/account information.

4 — Forms registration or feedback instrument

Use synthetic/test responses only. Collect only fields necessary for the fictional event purpose. Include a field-purpose/privacy audit.

Connect responses to Sheets if useful, but keep response access narrow.

5 — Slides briefing

Build a concise visual briefing for the event proposal. Reuse the Week 6 five-part logic or another defensible structure. Include speaker notes and source/permission records for important visuals.

6 — Gmail communication draft

Draft an invitation or project-coordination message with a clear subject, action, and linked resource. Keep it inside the classroom scenario unless specifically authorized to send.

7 — Calendar event

Create an event with matching date/time/purpose and a link to the correct agenda or project plan. Verify file permission separately from event access.

Integration test

Before calling the build finished, run:

Build-day stop condition

Do not widen sharing just to make a test easier. If school policy blocks a desired setting, document the constraint and adapt the workflow.

Your capstone is ready for defense when the connections have been tested, not when you have seven open browser tabs.