Import from Google Drive.POD does the reading.
A shared Drive is where construction files go to be forgotten.
Your construction files already live in Google Drive: the daily reports, the pay apps, the schedule, the photos. Drive keeps them safe and does nothing with what is inside them. POD connects to the same Drive, you pick the files, and it reads each one into a live dashboard. Available today.
What Drive keeps, POD reads
Google Drive is very good at one thing: holding your files and sharing them. A folder of daily reports stays a folder of daily reports. The headcount, the quantities installed, the weather delay, the safety notes. All of it is in there, and none of it is a number anyone can see without opening each file by hand.
POD connects to the same Drive you already use and reads each file the way an experienced PM reads a daily report. You pick the files to bring in, POD opens each one, recognizes the construction data inside it, and maps it to the right fields. The file was already in your Drive. POD is the part that finally reads it.
What POD reads out of your Drive
The common construction file set you already keep in Drive. POD reads each kind and maps it to the dashboard automatically, with no column setup.
PDFs, Word, or plain text. POD reads headcount, hours, quantities, weather, and notes and maps them to the right KPI fields.
The master spreadsheet the team already shares. Labeled columns map straight to KPIs, which is the most complete read POD gets.
AIA pay applications, Primavera P6 (XER), and MS Project (XML export). POD reads them into your budget and schedule, with no manual re-entry.
JPG and PNG. POD reads handwriting, whiteboard tallies, and site conditions, and files each photo with its capture time and location.
How the import works
Connect once, then bring in the files you choose. It is a picker, not a folder watch. POD reads only what you select.
Link the Google account whose Drive holds your project files.
Choose the files to import from the Google picker. Only those are read.
POD opens each file and maps the construction data to KPI fields.
The project dashboard and reports update with what it found.
A worked example
One project keeps its schedule in a shared Google Drive: a Primavera P6 export in one folder, a month of daily reports in another. The export has 320 activities on it. Until someone opens the file and reconciles it against the dailies, nobody can say at a glance how many are moving and how many have slipped. Pick those files from the Drive picker, and POD reads them into one picture: of 320 activities, 180 complete, 46 in progress, 16 running behind, and 78 not yet started. The files did not change. What changed is that someone finally read them.
Every file maps to a live metric
Each file you import passes through POD's reader and lights up the metric it feeds. The daily report drives progress, the pay app drives budget, the schedule export drives the schedule, the RFI log drives quality, the photos drive safety. One import, five live metrics.
The schedule picture, read from the files
The same schedule export from the example, read out of the Drive folder: 320 activities broken into 180 complete, 46 in progress, 16 behind, and 78 not started. In this example, none of it was typed in; POD read the activity status straight from the file already sitting in the Drive.
Activity Status
You pick the files. Nothing is watched.
The import is deliberate by design. You choose the files from the Google picker, and POD reads only those into the project you select. There is no background folder watch and no automatic ingest of everything in a folder, so nothing in your Drive is read unless you bring it in.
Ongoing folder auto-sync, where new files flow in on their own, is on the roadmap, not live. And POD never becomes your storage: your Drive stays your system of record, and POD reads and keeps the copies you import within your plan. You are adding a reading layer, not migrating off the storage you already use.
Keep reading
The overview: keep the cloud storage you already use, and let POD read the construction files inside it.
The same picker-based import for Box: connect, pick your files, and POD reads them into your dashboards.
What happens after the import: the AI that recognizes construction data in any file and maps it to KPIs.
Where the imported files land: the executive and project dashboards that update as files come in.
The full picture of what POD reads on upload and import, and what is on the connector roadmap.
A side-by-side on reading your files into intelligence versus storing them in a system of record.
A folder vs a read
Your Drive stays the place the files live. POD is the layer that reads what is inside them.
| Your Google Drive | Plan of Day | |
|---|---|---|
| What it does | Holds, syncs, and shares files | Reads what is inside each file |
| A folder of daily reports | Stays a folder of daily reports | Becomes a live progress and safety picture |
| Finding one number | Open each file by hand | Mapped to a KPI automatically |
| A number never filled in | Nobody notices it is missing | Shows as missing on the dashboard, never invented |
Google Drive import questions
Can POD import construction files from Google Drive?▾
Yes, and it is available today. You connect Google Drive, pick the files you want from the Google picker, and POD reads each one into the project you choose. It is a file picker, not a folder sync: POD reads only the files you select, so nothing from your Drive is touched or read unless you bring it in.
What construction files can POD read from Google Drive?▾
The common construction file set you already keep there: PDFs such as daily reports and pay applications, Excel and CSV trackers, schedule exports (Primavera P6 XER and Microsoft Project XML), and jobsite photos. POD reads each one and maps the data to your dashboard. A clearly labeled table or report produces a more complete read than buried prose.
Does POD sync my whole Google Drive folder automatically?▾
No. You pick the specific files to import, and POD reads only those. There is no background folder watch and no automatic ingest of everything in a folder. Ongoing folder auto-sync is on the roadmap, not live, so today the import is deliberate and file-by-file by design.
Does POD move, copy, or replace my Google Drive?▾
No. POD does not move, copy over, or replace your Google Drive. It reads the files you import and keeps the imported copies within your plan, while your Drive stays your system of record. You are adding a reading layer on top of the storage you already use, not migrating off it.
Which other cloud storage can I connect?▾
Box and Dropbox import are also available today, the same way: connect, pick files, and POD reads them in. OneDrive and SharePoint are coming soon, and you can request early access to those from the Integrations page inside your POD account.
How does importing from Google Drive turn into a dashboard?▾
POD reads each file you import, recognizes the construction data inside it, and maps that data to the right KPI fields automatically, with no manual column setup. Your project dashboard and reports then update with what it found. The clearer each value is stated in the source file, the more complete the dashboard that comes out of it.
Let POD read the files already in your Drive
Connect the Google Drive you already use, pick the files, and watch them become a live dashboard. Box and Dropbox import work the same way, today.