How to Use Google Drive Files in Your Performance Review

The evidence for your review may already be sitting in Google Drive. A launch plan explains the choice you helped make. A customer readout shows what the team learned. A training guide captures something you made easier for everyone else. The problem is that a folder full of files does not tell your career story by itself. You still need to choose the useful pieces and explain your part. Here is how to do that without turning review prep into a tour of every document you touched this year.

Look for files that answer a review question

Instead of opening Drive and searching for your own name, start with a question. What did I improve? Which difficult choice did I help the team make? Where did someone rely on my work? A question gives you a reason to select a file rather than collecting everything that looks vaguely relevant.

• A plan or proposal can show the problem, options, and recommendation behind a decision.
• A research readout can show the evidence that changed the team’s direction.
• A finished guide can show how you made a process easier to follow.
• A launch recap can connect the work to a measured result or a lesson.
• A permitted feedback note can explain how someone else used or benefited from your work.

The best file is not necessarily the longest or most polished one. A short decision note that names the problem and your recommendation may tell the story better than a fifty-page presentation. Start with the smallest piece that supports what you want to say.

A file supports a story. It does not prove the whole story.

Having a document in your Drive does not mean you wrote it. Editing a slide does not mean you led the project. A launch recap may show a result without showing who made each contribution. Keep those limits in mind before you turn the file into a review claim.

For a fictional example, suppose Maya saves an Account Setup Refresh recap. It says activation rose from 54% to 68% after the launch and describes the two setup barriers the team addressed. That supports the team’s reported result. It does not establish that Maya designed the screens, wrote the software, or caused the entire improvement herself.

Her note supplies the missing part: “I gathered the customer interviews and recommended narrowing the first release to these two barriers. Priya led design; Daniel’s team built the changes. We used this recap to review the first results.” The file and the note are useful together because they answer different questions.

Add the context you will forget by December

A file often leaves out why the work was hard, which option you rejected, or what changed halfway through. Do not write a second version of the document. Leave a few lines about the part that will be difficult to reconstruct later.

• What was the problem before this work?
• What did I personally own or contribute?
• Who else was involved, and what did they own?
• What happened afterward, and what is still unknown?
• Which responsibility or skill does this help explain?

“The full redesign would have missed the release window, so I used the interviews to recommend a smaller first step” is useful context. “Demonstrated exceptional strategic excellence” is not. The first sentence lets a reviewer understand your judgment without asking them to accept an adjective.

How selected Google Drive files work in Bloomly

Bloomly uses the iPhone’s Files picker to import files you choose. Google Drive can appear there as a file location when its app is installed and enabled. In Bloomly, go to Settings, open Connected Work, and use Choose files under Google Drive. If you have more than one Role, choose the Role the evidence belongs to.

This is a selected-file import, not a connection that watches your Drive. Bloomly does not browse your account in the background, collect your Drive activity, or keep an ongoing Drive account connection. Choosing a file gives Bloomly a copy of that file to process. Its contents are read for artifact processing; it is not a metadata-only import.

Supported imports are PDFs, images, and plain-text files, with a 25 MB limit per file. A native Google Doc or Sheet is not the same as one of those files. Export the material you want into a supported format, such as PDF, and inspect the exported copy before selecting it. Check that the relevant pages and any important dates are included.

If Drive is missing from the picker, open Apple’s Files app, go to Browse, then use the More menu and Edit to enable Google Drive. You will need the Drive app set up first. Apple’s instructions for adding cloud providers and Google’s download instructions are linked in the sources below.

What the artifact adds to the document

An imported file becomes a work artifact in Bloomly. That gives the evidence a place in your Role’s record, where it can be used alongside other artifacts and your text or voice entries. The useful step is connecting the material to your work context, rather than leaving it as a forgotten attachment.

For Maya, the recap can support the launch result while her entry explains the research and scope decision. With relevant resume and Role context, Bloomly can help connect that evidence to the expectations she is working toward. She can then use BloomBar to ask which examples support a review point, or use her record when preparing a report.

That does not turn missing facts into known ones. Check the artifact’s summary, names, figures, and claims about your involvement. If the file does not establish authorship, a generated summary should not be treated as proof of it. Add or correct the context before relying on it in a review.

Keep workplace boundaries intact

Access to a work file is not the same as permission to copy it into a personal app. Follow your employer’s rules, especially for customer details, financial information, internal plans, and other people’s personal information. If you are unsure, ask before importing. A private career record still needs to respect those boundaries.

Sometimes a plain note about your own contribution is the better choice: “Updated the renewal handoff to make ownership and timing clear.” You may not need the customer’s name, contract value, or original document. Leave out details you are not allowed to store elsewhere, and do not assume that removing a company logo makes a file safe to copy.

Watch for three easy mistakes

Saving the file but not your part

A shared deck can be good evidence of the team’s work and weak evidence of yours. Add a short, honest note about what you contributed. If you only reviewed one section, record that. Useful feedback on one section can still matter.

Expecting an export to include every conversation

Do not assume a PDF includes comments, previous versions, or the decision trail behind the finished text. Inspect it. If an important point is missing, add an allowed summary in your own words rather than claiming Bloomly retrieved a history it never received.

Treating the imported copy as a live file

An import is a snapshot. If the source changes later, do not assume the copy or artifact updates with it. Note which version or date you used. When a meaningful result arrives, add the new information to your record and make clear that it is an update, not a second accomplishment.

Try one file before organizing a whole folder

Pick a project you remember well. Choose one permitted file, add your contribution in a few lines, and ask whether the result helps someone understand your work. If it does, repeat the process for another important project. You are building a usable review record, not making a backup of Google Drive.

Start with one piece of work you want your manager to understand. Choose a file that supports it, check what you are allowed to copy, and add the context the document cannot supply on its own. You do not need your entire Drive in a career journal. A few well-chosen files, connected to an honest account of your contribution, can be much more useful than a long list of things you edited.