Construction

Procore

< Back to All Connectors
Connect your AI to Procore
Project managers, construction accountants and finance controllers, and company administrators and executives run every job through Procore, but the answers they need sit across projects, commitments, change orders, RFIs and companies that Procore's screens show one at a time. AI can bring those answers together in plain language, but only if access follows the connected Procore user's permissions per company and project.

‍

Start a Trial
Get a Live Demo

Why it matters

Capabilities that matter most for Procore

01

Eight servers, one per Procore area

Procore is split into company admin, construction financials, core, project management, preconstruction, resource management, platform developer tools and Helix servers, so each AI client loads only the area a role works in.
02

A tool for every Procore list

More than 1,100 read tools cover Procore lists from budgets and commitments to RFIs, submittals, drawings and daily logs, each returning the fields people recognise instead of raw API payloads.
03

Ready-made jobs, not just tools

More than 400 ready-made prompts turn those tools into jobs such as RFI aging reviews, commitment reconciliations and punch list roundups that you start by asking in plain language.
03

Procore beside your finance systems

Cross-system prompts pair Procore with Business Central, Sage Intacct, NetSuite, Ramp and Rillet, so project costs and commitments can be checked against the ledger in one conversation.
05

Governed by the connected user

Every answer follows the connected Procore user's permissions per company and project. The write tools are built Inactive and untested end to end, so try one in a sandbox before switching any on.

Use cases

Example AI Use Cases for Procore

Filters

scenario

-

Adding a location to a Procore project means finding the right project, scanning the location tree for the same name, and picking the parent by eye. Add it under the wrong parent, or twice, and daily logs, punch items and inspections end up filed against the wrong place.

What popdock provides

--

Give a location name, a project and optionally a parent location, and it finds the one matching project, checks the project's locations for the same name under that parent and confirms the parent is exactly one location. It stops on a duplicate or an ambiguous parent. You see the project, name and parent, and nothing is created until you confirm. It creates the location once and reads the tree again to report its id and parent. It never edits existing locations.

Business outcome

---

New locations land once under the right parent, so the project's location tree stays clean and nothing is filed in the wrong place.
See Full Use Case

scenario

-

Adding a comment to a Procore task item starts with the task number, and it is easy to copy the wrong one or comment on a task someone has just updated. The comment lands on the wrong task and the right assignee never sees it.

What popdock provides

--

Give a project, a task number and the comment text, and it finds the one task with that number and shows its title and status. It displays the last three comments so you can see what yours follows. You see the exact comment text, and nothing is added until you confirm. It adds the comment once, leaves the task status alone, then reads the comments again to confirm it appears. It stops if the task match is not exact.

Business outcome

---

Comments reach the task they were meant for, with the status untouched and proof that the comment was saved.
See Full Use Case

scenario

-

Adding a company user to a Procore project means finding the person, the project and the right permission template in separate screens. Pick the wrong template and they get the wrong access, or you add someone who is already a member and muddy who has what.

What popdock provides

--

Give a user, a project and optionally a permission template, and it finds one matching user and one matching project. It checks whether the user is already on the project and stops if so, reporting their template. It lists the templates available on that project and matches yours, or asks you to choose. You confirm the user, project and template before anything is changed. It adds the user once and reads the membership back with the template assigned. It never changes existing access.

Business outcome

---

People join the right project with the right permission template the first time, and nobody's existing access is touched.
See Full Use Case

scenario

-

Insurance expiry dates live in the Procore company directory, while bidders are tracked on the Preconstruction bid board. Nobody checks one against the other until a certificate has lapsed, and the chase-up task is never logged against the bid.

What popdock provides

--

Name a bid board project and it finds the project and its estimator, collects every vendor that has bid, and checks each vendor's insurance in the company directory. Vendors with an expired policy, one expiring within your window (30 days by default) or no policy on file are flagged. You see them with policy number and expiry date, plus the proposed task text, assignee and due date. One estimating task is added only after you say yes, and it asks who to assign if no estimator is set. Insurance records, bids and proposals are never changed. The task creation has not been run end to end, so try it in a sandbox first.

Business outcome

---

Lapsing bidder insurance is caught before the bid decision, with one chase-up task logged for the estimator instead of vendors slipping through.
See Full Use Case

scenario

-

Adding a configuration to a Procore app installation by hand means confirming the app is still installed, checking whether a configuration with that title already exists and choosing the scope. Skip a check and you get a duplicate, or a configuration attached to an app that has been uninstalled.

What popdock provides

--

Give a title, an app installation and optionally the projects it applies to, and it checks the installation exists and is installed, and that any projects are part of it. It looks for an existing configuration with the same title and stops unless you want a second one. You see the title, installation and scope, and nothing is created until you approve. It creates the configuration once, applying it to the company when no projects are named, then reads the configurations again to show the new record. Updates and deletes are never allowed. This write has not been tested end to end, so try it in a sandbox first.

Business outcome

---

Configurations are created once, against a live installation and the intended scope, with the new record shown back to you.
See Full Use Case

scenario

-

Adding a cost item to a Procore estimating catalog by hand means checking the catalog is not sealed, that the item does not already exist, and which unit and type the other items use. Guess the type wrong and pricing reports start to drift.

What popdock provides

--

Give a catalog, an item name, a unit and optionally a type. It finds the one matching catalog and stops if it is sealed, then checks the catalog for an item with the same name. It reads the types the existing items use, picks the most common when you give none, and asks you to confirm a type nobody uses yet. You see the catalog, name, unit and type, and nothing is created until you say yes. It adds exactly one item, sets no price or sub items, and reads the stored item back. This write has not been tested end to end, so try it in a sandbox first.

Business outcome

---

New cost items join the catalog once, with a unit and type that match the rest, so pricing reports stay consistent.
See Full Use Case

scenario

-

Vendors in Procore use trade names that the company trade list has never heard of, so admins retype them one at a time. Along the way they create near-duplicates, such as a plural or an abbreviation of a trade that already exists.

What popdock provides

--

Name the company, and optionally a minimum number of vendors, and it compares the trades vendors use with the company trade list, ignoring case and spaces. It proposes the missing ones with how many vendors use each and a few vendor names, and marks probable duplicates such as plurals or abbreviations and leaves them out. You choose which to create. Before writing it reads the company list again so a trade added in the meantime is not repeated, then creates each confirmed trade one at a time, stopping at the first error. It reports created, skipped and failed trades with ids. Vendors are never edited and nothing is deleted. This write has not been tested end to end, so try it in a sandbox first.

Business outcome

---

Trades vendors already use join the company list once each, without near-duplicates or retyping, and only the ones you approved.
See Full Use Case

scenario

-

To see where a bid total comes from, you open each line item group on a bid board proposal and add up item cost and labor by hand. With dozens of groups and hundreds of items, the biggest drivers and the zero-cost lines are easy to miss.

What popdock provides

--

Name a bid board project and optionally a proposal, and it finds the project and its proposals, stopping if the project name matches more than one. It reads the line item groups and line items for each proposal, ranks the groups by cost with each group's share of the total, and lists the ten most expensive items. It flags groups with no labor cost and items with no cost, and shows several proposals side by side. Everything shown is a figure Procore returned, an empty proposal is called out, and nothing is changed.

Business outcome

---

You see where a bid total sits and which lines carry no cost in one pass, from figures Procore returned and nothing guessed.
See Full Use Case

scenario

-

Giving someone a company role on a Procore project means looking up the role, the user and the project's current holders in separate screens. An inactive user or a role the company does not define slips through, and the same person gets assigned twice.

What popdock provides

--

Name a role, a project and a user, and it checks the role exists in the company, listing the company's roles if it does not. It finds one project and one active user on that project, refuses inactive or ambiguous users and stops if they already hold the role. You see the user, permission template, role and anyone else holding it, and nothing is assigned until you say yes. It makes one assignment with no retry and reads the project roles again to confirm it appears. It never edits or deletes roles. This write has not been tested end to end, so try it in a sandbox first.

Business outcome

---

The right person gets the right company role on a project once, with current holders in view and no roles invented or changed.
See Full Use Case

scenario

-

RFIs stall when nobody checked who can manage them, who can be assigned and who is on the default distribution before the job started. The setup lives in several places, and the gaps show up only when an RFI sits unanswered.

What popdock provides

--

Name a project and it reads who can manage RFIs, who can be assigned them and who is on the default distribution. It compares those lists with the RFIs actually in use, looking at responsible contractors and who created them, and checks the project's rounding rule. It reports empty lists, people on the distribution who cannot be assigned, contractors on RFIs who are not in the setup and a missing rounding configuration, then the three fixes that matter most. It is read-only and marks missing values as missing.

Business outcome

---

You find RFI setup gaps before the first RFI stalls, with the three fixes that matter most laid out.
See Full Use Case

scenario

-

Procore administrators lack a clear view of which apps are installed, uninstalled, agentic or still waiting on a request across projects. Answering it means paging through installations and requests, and the odd installer or recently removed app goes unnoticed.

What popdock provides

--

Optionally name a developer app or project and it reads the app installations and the pending installation requests. It groups them by app, type and status, and flags apps installed on many projects by one installer, recently uninstalled apps, agentic apps called out separately, requests still pending and installers who appear only once. You get summary counts by status and type and a table of flagged items with app, project, installer, install date and issue. It is read-only and reports facts without labelling any app unsafe.

Business outcome

---

You get one view of installed, removed, agentic and pending apps with the items to look at, and no verdicts imposed.
See Full Use Case

scenario

-

Conditional rules on Procore assets refer to fields that can later be removed, and broken rules surface only when a user saves an asset. Checking them means opening grouped rules and asset type rules one at a time and comparing every field with what is still available.

What popdock provides

--

Optionally name a rule type and it pulls the grouped rules, the asset type rules, the available fields and the system states. It flags rules that use a field that is no longer available, rules with no fallback, rules last modified by a user who is now inactive and gaps or duplicates in rule order. You get a table of rules with type, field, value and fallback, then each problem with its rule. It is read-only, lists every write action as off limits and reports only what comes back.

Business outcome

---

Broken or fragile asset rules are found before a user hits them on save, from a review that changes no rules.
See Full Use Case

scenario

-

Asset naming standards are set at company and project level, with rules, fields and codes spread across several screens. A bad code or an unused field is only noticed when two asset names collide.

What popdock provides

--

Optionally name a project and it pulls the company naming standard, its fields, codes and rule expressions, and the project's standard when you name one. It flags rules whose expression uses a field that is not a naming field, inactive codes still used by a rule, fields available on all asset types that no rule uses, and differences between the company and project rules. You get a short summary of the standard with fields in order and fallbacks, then each problem and difference. It is read-only, never resets sequences or collision counters and never upserts codes.

Business outcome

---

Naming standard problems and project differences are found before asset names collide, with no counters reset and no codes changed.
See Full Use Case

scenario

-

Asset registers are reviewed by exporting and filtering, and incomplete assets go unnoticed until someone needs them. Missing types, statuses, locations and parents sit in a long grid of project and company assets.

What popdock provides

--

Name projects, and optionally a location, and it pulls the project and company assets and the valid statuses. It flags assets with no type, status, location or trade, assets whose status is not a valid one, and assets whose parent is not in the register. You get a table of counts by type and status, then each problem group with a count and the first 20 examples. It is read-only, lists every write action as off limits and reports only rows Procore returned.

Business outcome

---

Incomplete assets are counted and listed by problem before anyone needs them, without exporting or filtering a register by hand.
See Full Use Case

scenario

-

Asset type settings are spread across several screens: fieldsets, status groups, available fields, rules and the type hierarchy. Missing rules or fields only show up when people start entering assets.

What popdock provides

--

Optionally name an asset type and it pulls the company asset types with their available fields, field rules, grouped rules and parent types. It flags types with no fieldset or status group, types with available fields but no rules, rules naming a field that is not available and parent types that do not exist. You get a table of types with fieldset, status group, field count and rule count, then each problem with the type name. It is read-only, lists every write action as off limits and changes no settings.

Business outcome

---

Asset type gaps are found before people start entering assets, with every problem named against its type.
See Full Use Case

scenario

-

Budget reviewers scroll a long Procore budget grid looking for blank amounts, quantity lines with no unit cost and codes that do not match the cost code list. It is slow, and a line with a zero amount hides among hundreds.

What popdock provides

--

Name a project and it reads the budget line items and the project's cost codes. It lists lines with a zero or blank original amount, quantity-based lines with no quantity or unit cost, lines with a quantity but no unit of measure, codes flagged as budgeted that have no line, and lines whose code is not in the cost code list. You get counts per problem type and a table of offending lines, then the codes. It is read-only, never edits or deletes lines and says when the result covers only the first page.

Business outcome

---

Incomplete or inconsistent budget lines are listed by problem type in one pass instead of found by scrolling the grid.
See Full Use Case

scenario

-

Security and timesheet settings in Procore live on different screens, so reviews are skipped or done from memory. A session timeout left very long or a password reset interval that was never set goes unnoticed.

What popdock provides

--

Optionally name a company and it reads the company security settings, such as session timeout and password reset interval, and the company configuration, such as currency, timesheet type, week start day and cost type defaults. It says what looks unusual, such as a very long or unset timeout or interval, and notes which choices are blank. You get two short tables, security and configuration, each with setting, value and note, then up to three recommendations. It is read-only, never reads or reports support pins and changes no setting.

Business outcome

---

You review company security and configuration settings in one read, with unusual values flagged and nothing changed.
See Full Use Case

scenario

-

Subcontract compliance is checked contract by contract, across missing requirements, insurance requirements and document status for both purchase orders and work orders. Uninsured or non-compliant work carries on while large balances are still open.

What popdock provides

--

Name a project and a contract type, purchase orders, work orders or both, and it reads requirements and insurance requirements that have not been created, then the compliance and insurance status of contracts and the documents that are not approved. It groups the findings by contract number, listing missing requirements, documents not approved and the remaining balance, and puts contracts with large open balances first. A contract with no gaps is reported as clear. It is read-only, creates no requirements and uploads or approves no documents.

Business outcome

---

Contracts with compliance and insurance gaps are ranked by what is still owed, so you chase the biggest exposure first.
See Full Use Case

scenario

-

Overdue correspondence items hide in project lists, and it is not obvious who owns them. Chasing them means filtering by due date and status, then opening each item to find the assignee.

What popdock provides

--

Optionally name a project, a status and a company, and it reads correspondence items and treats those past their due date and not closed as overdue. For the ten oldest overdue items it looks up the assignees. You get a table with the item, project, status, due date, days overdue and assignees, sorted by days overdue. It is read-only and never updates items, runs batch updates or deletes anything. If nothing is overdue it says so.

Business outcome

---

Overdue correspondence is listed oldest first with an owner against each item, so the chasing can start straight away.
See Full Use Case

scenario

-

Catalog items with no unit cost, no unit or a duplicate name are usually found only after an estimate has been built on them. Checking means paging through every estimating catalog and comparing the same item across catalogs.

What popdock provides

--

Optionally name a catalog and it lists the estimating catalogs and reads their cost items, including a separate read of zero-priced items. It flags items with no or zero unit cost, items with no unit, names that appear twice in a catalog, and the same name in different catalogs with different units or a unit cost more than 25 percent apart. You get counts per catalog and problem, then the worst fifty items and how many more there are. It is read-only, notes sealed catalogs cannot be edited and never changes an item.

Business outcome

---

Pricing and naming problems in estimating catalogs are ranked before an estimate depends on them.
See Full Use Case

scenario

-

Project cost code lists drift from the company standard, and nobody notices until costs are posted to the wrong code. Comparing them means lining up project codes, standard codes and sub jobs by hand.

What popdock provides

--

Name a project and it reads its cost codes, the company's standard cost codes and the project's sub jobs. It finds duplicate full codes, codes with no standard cost code, codes whose name differs from the standard code with the same full code, and sub jobs that no cost code uses as a prefix. You get a count for each check, then tables of the offending codes with the standard code each should map to, labelled as suggestions. It is read-only and nothing is created or changed.

Business outcome

---

Cost code drift from the company standard is found and mapped before costs are posted to the wrong code.
See Full Use Case

scenario

-

Crew rosters are checked crew by crew, and crews with no lead, no members or inactive members affect timecards. Comparing a crew's members with its employees means opening both lists for each crew.

What popdock provides

--

Name a project and it reads its crews and, for each crew, its members and employees. It flags crews with no lead, crews with no members, inactive members, and employees listed on a crew who are not members, and the reverse. You get a table of crews with lead, member count and employee count, then the problems against the crew name. It is read-only, lists every write action as off limits and changes no crews.

Business outcome

---

Crew roster gaps are found before they hit timecards, with each problem named against its crew.
See Full Use Case

scenario

-

Admins click through custom field screens one by one to find definitions nobody uses, and clutter builds up unnoticed. Whether a definition sits in any field set, or a list field has any values, is not visible in one place.

What popdock provides

--

Optionally name a company and a data type and it lists every custom field definition with its field set count. It flags definitions in no field set as unused, and list-type definitions with no entries, and for up to ten of the rest it checks which field sets use them. You get a table of definition, data type, field set count and finding, then cleanup recommendations. It is read-only, lists every write action as off limits and recommends deletions without ever performing them.

Business outcome

---

Unused and incomplete custom field definitions are found in one review, ready for you to clean up.
See Full Use Case

scenario

-

A messy equipment catalog splits one machine type across three spellings, so reports undercount, and nobody can tell which entries are safe to clean up. Checking means comparing categories, types, makes and models, then counting which units use each.

What popdock provides

--

Optionally name a category and it reads the equipment categories, types, makes and models, compares names ignoring case and punctuation, and counts units per category and make from the equipment register. It lists exact duplicates, near duplicates such as a trailing plural or an abbreviation, orphans such as types with no category and models with no make or type, and unused entries, each with id, name and unit count. It recommends which entry to keep but changes nothing, and never recommends deleting an entry that units still use.

Business outcome

---

You know which catalog entries are duplicates, orphans or unused, and which are safe to tidy, before reports split one machine type apart.
See Full Use Case

scenario

-

Safety tickets and certifications lapse unnoticed, and a crew member cannot be assigned until it is fixed. Finding what is about to expire means checking tag instances person by person and matching employees to their groups.

What popdock provides

--

Optionally give a number of days, a start date and a tag, and it reads the workforce tags, then the tag instances on people that expire within the window (60 days by default) and those already expired, matching employee numbers to their groups. It reports two tables, expired and expiring soon, with tag, employee number, group, expiry date and days left, counts per tag and flags tags whose people all expire in the same month. Instances with no expiry date are listed separately. It is read-only, shows no personal data beyond employee numbers and never edits a tag.

Business outcome

---

Lapsed and expiring certifications are listed by tag and group in time to renew them, with personal data kept to employee numbers.
See Full Use Case

scenario

-

Field production reports feed unit rates and forecasts, but a row with zero budgeted hours, work logged against no quantity or a percent complete over 100 hides in the grid. You scan the report row by row, and the bad numbers keep distorting the rates until someone happens to notice.

What popdock provides

--

Name a project and how many rows to look at, and it reads the project's field production report and applies five data-quality checks: missing or zero budget, hours with no quantity, percent complete or earned hours over the limit, remaining plus actual hours far from the forecast, and blank units or sub-jobs. You get a count per check and the offending rows with cost code, sub-job and the specific problem, plus how many rows were clean. It only reads, quotes figures as returned and never corrects a row.

Business outcome

---

You see which field production rows cannot be trusted, and how many are fine, before the numbers feed a rate or a forecast.
See Full Use Case

scenario

-

Form templates build up over the years. Archived ones sit in the recycle bin, duplicates keep the same name and old versions are never revisited. Checking means opening the company templates, the recycle bin and each project's templates separately and comparing them by eye.

What popdock provides

--

Optionally name a company or part of a template name, and it reads the active company templates, the archived ones in the recycle bin and the templates used on projects. It flags archived templates that a project still uses, duplicate names and templates not updated in over a year, then lists each template with its state, dates and finding. It only reads, and it never restores, archives or deletes a template.

Business outcome

---

You get one clean-up list of risky, duplicate and stale form templates without opening three screens or touching a template.
See Full Use Case

scenario

-

Admins export the inactive user list, then compare it with active users by hand to see who has not logged in, who never got a welcome email and who is inactive on a project but still active in the company. Unused accounts and unfinished onboarding stay unnoticed for months.

What popdock provides

--

Optionally give part of a name or a project, and it pulls inactive company and project users, compares them with the active users and sorts people into three lists: never logged in, never onboarded and stale for more than 180 days. It also lists anyone inactive on a project but still active at company level. It reports only what Procore returns, treats every write action as off limits and never recommends deleting a user.

Business outcome

---

You see which accounts are unused or never onboarded without exporting and matching lists, and no user is changed or removed.
See Full Use Case

scenario

-

Incident alerts only work if each severity level is tied to a recipient, and hazards and contributing factors have been defined. These sit on several configuration pages, so a severity level with nobody to alert, or factors nobody ever uses, goes unnoticed until a serious incident is logged and nobody hears about it.

What popdock provides

--

It reads the company's incident severity levels, alert recipients, alerts, hazards, contributing behaviors and conditions and action types. If you give a project, it also reads the project's incident configuration and incidents to compare setup with use. You get each list with a count and findings such as severity levels with no recipient, no hazards defined and factors never used. Without a project it skips the usage check and says so. It only reads and edits nothing.

Business outcome

---

Gaps in incident alerting show up before an incident exposes them, and you see them in one report without any configuration being changed.
See Full Use Case

scenario

-

Recurring inspections depend on a template for each inspection type and a schedule that has not ended or lost its assignees. Compare company templates, project templates and schedules by hand and a lapsed schedule or an inspection type with no template slips through, so inspections quietly stop happening.

What popdock provides

--

Name a project and it resolves it to one match, then reads the project and company inspection templates, the project's recurring schedules, how many inspections each schedule will generate and its recent change history. You get templates by inspection type and schedules with next due date, end date and total inspections, plus findings: company templates not used on the project, schedules that have ended or have no assignees and types with no template. If the project is unclear it stops and asks. It only reads.

Business outcome

---

Lapsed schedules and uncovered inspection types are found before inspections are missed, from one report and with no schedule changed.
See Full Use Case

scenario

-

Job title rates drift as pay changes year after year. Titles end up with no group, near-duplicate names or hourly rates far from their peers, and the outliers go unseen until a bid is priced from a rate that is too low. Checking means opening titles, groups and people wages in separate places.

What popdock provides

--

Optionally give a job title type, and it reads the job titles, the groups each title is available to and how many people earn outside each title's rate range. It reports three lists: titles with no group, titles whose hourly rate is more than 25 percent from the median for their type and duplicate or near-duplicate names, with rate and group count. It shows only wage ranges and counts, never individuals' pay, and it never edits a title.

Business outcome

---

Rate outliers and duplicate titles are found before they price a bid, with no personal pay data exposed and no title changed.
See Full Use Case

scenario

-

Observation types and distribution lists are inherited from the company and rarely checked against what the site actually raises. Types go unused, categories appear that are not project types and the default distribution can be empty or include people who are not eligible, all spread over several settings screens.

What popdock provides

--

Name a project and it resolves it to one match, then reads the project's observation types, configurable field sets, default distribution and potential distribution members. It reads the project's observations and compares the categories in use with the project's types. You get the setup and findings: types never used, categories not in the project types, an empty default distribution and people on it who are not eligible members. It only reads and edits no configuration.

Business outcome

---

You can see where observation setup and site practice disagree, from one report and with no configuration changed.
See Full Use Case

scenario

-

Project types, stages, regions, bid types, owner types and programs are maintained in separate lists, and each one drifts. Names appear twice with different case or a trailing s, some lists sit empty and nobody reviews them together, so reports split the same thing into two groups.

What popdock provides

--

Optionally name a company, and it reads the project types, stages, regions, bid types, owner types and programs. It flags names that differ only by case, punctuation or plural, lists that are empty, and for stages notes the category and whether bidding stages are marked. You get a short section per list with its count and findings, then a prioritized clean-up list. A list that returns nothing is reported as empty. It only recommends merges or removals.

Business outcome

---

You get one prioritized clean-up list for every project taxonomy, so reports stop splitting the same thing in two.
See Full Use Case

scenario

-

Before a vendor starts work, someone checks that its certificate of insurance is on file and current. Doing that for every vendor on a project means matching the vendor list against policies by hand, and gaps in coverage show up late, once work is under way or an audit asks.

What popdock provides

--

Name a project and how many days ahead to look, and it pulls the project's vendors and the policies that expire inside that window, then matches policies to vendors by name or vendor ID. Each vendor is marked as no policy, only expired policies, expiring in the window or current. You get a table with the newest policy, status, expiration date and verdict, listing no policy first, then expired, then expiring. It only reads, treats every write action as off limits and does not judge coverage amounts.

Business outcome

---

You find vendors with missing, expired or expiring insurance on a project before they work, without judging coverage or changing a record.
See Full Use Case

scenario

-

To see which milestones have slipped, a project manager opens each project's timeline and compares planned dates with today. A milestone with no actual date is easy to miss, and a project that never had dates set up never shows up as a problem at all.

What popdock provides

--

Name a project, or leave it blank for all, and set how many days to look back (90 by default). It pulls milestone dates for that window, finds those planned before today with no actual date and reports days late, with hidden-on-timeline milestones listed separately as lower priority. It also checks which matching projects have no dates at all. You get a table by project sorted by days late, then the list of projects with no dates. It works only from returned dates and changes nothing.

Business outcome

---

Slipped milestones and projects with no dates are visible in one ranked list, with no timeline opened and nothing edited.
See Full Use Case

scenario

-

Location trees are built by hand and by import, so the same name appears twice under one parent, codes go missing and some locations point at a parent that no longer exists. Reports and daily logs then get confusing, and finding the culprits means expanding the tree level by level.

What popdock provides

--

Name a project and it pulls the project's locations and its assets. It checks for the same name twice under one parent, locations with no code, locations whose parent does not exist and leaf locations holding no assets. You get the location tree as an indented list, then each problem group with the location name and id. With more than 500 locations it reports problems only. It treats every write action as off limits and changes no locations.

Business outcome

---

Duplicate, uncoded and orphaned locations are named in one pass, so you can fix the tree knowing exactly where to look.
See Full Use Case

scenario

-

To check who has access to a project, IT or an admin compares the user list, the role assignments and the permission templates on separate screens. People with no template, no role or a role they should not hold are easy to miss, and the mismatch only shows when someone cannot do their job.

What popdock provides

--

Name a project and it resolves it to one match, listing the choices if there are several. It pulls the project's active users with their permission template, the role assignments, the raw memberships and the available templates. It finds users with no template, users with no role, roles held by someone not in the user list, memberships with no matching user and templates used by only one person. You get a table of users with template and roles, then each problem group. It only reads and never changes access.

Business outcome

---

Access gaps and mismatches on a project show up in one report, without any permission being changed.
See Full Use Case

scenario

-

Project setup is checked screen by screen: which tools are on, which required tools were left off and which links have been added twice. A deleted link that was later recreated, or a required tool that is switched off, is easy to miss until someone on the project cannot find what they need.

What popdock provides

--

Name a project and it pulls the project's tools, links, deleted links in the recycle bin and the available project templates. It flags required tools that are not active, links with the same title twice and deleted links that have a newer link with the same title. You get a table of tools in position order with active and required flags, the links with date created and the list of deleted links. It treats every write action as off limits and restores nothing.

Business outcome

---

Switched-off required tools and duplicate links are caught in one review, with nothing restored or changed.
See Full Use Case

scenario

-

Punch items get stuck when nobody was ever set as a final approver or the default distribution was left empty. The setup is spread across managers, approvers, assignees, distribution and templates, and the gap only shows once items start piling up unclosed or are closed by someone who should not have.

What popdock provides

--

Name a project and it resolves it to one match, stopping to ask if several fit. It reads the available punch item managers, final approvers, default distribution, assignee options and templates, then reads the project's punch items and compares who closed items with the final approvers list. You get each list, then findings: empty lists, templates with no assignee or approver and items closed by someone who is not an available final approver. It states when a read is capped, and it edits nothing.

Business outcome

---

Punch list gaps that block closure show up before items get stuck, from one report and with no setup changed.
See Full Use Case

scenario

-

Before a submittal log is shared with the design team, someone has to confirm the next number is free and that every submittal sits in a package. Duplicate numbers and orphaned packages are found by scrolling the log, and fixing them after it has been shared means rework for everyone.

What popdock provides

--

Name a project and optionally a proposed submittal number. It resolves the project, reads the next available number and, if you gave one, tests whether your number is free. It then reads the submittal packages and the submittals to find those in no package. You get the next free number, whether your number is available, a table of packages with number, title, submittal count and last update and a list of submittals not in any package, flagging empty packages. It only tests numbers and creates no submittals.

Business outcome

---

Number clashes and orphaned packages are found before the log goes to the design team, with no submittal created.
See Full Use Case

scenario

-

Tax and currency settings are rarely reviewed. A tax code can lose its rate or keep an old one that expired, two rate periods can overlap and exchange rates can go months without an update. The problem usually shows up as a wrong total on an invoice rather than in the setup screens.

What popdock provides

--

Optionally name a company and a project. It reads tax codes and their rates, then flags codes with no rate, rates that ended while the code is not archived and codes with overlapping rate periods. It reads the currency configuration and exchange rates, plus the project's if you gave one, and flags multicurrency with no exchange rates and rates not updated in more than 90 days. If multicurrency is off it skips the exchange rate checks and says so. Findings are grouped by tax and currency. It only reads and changes no rate.

Business outcome

---

Expired, overlapping and stale tax and currency entries are found before they cause a wrong invoice total, with no rate changed.
See Full Use Case

scenario

-

Finance checks vendor certificates one vendor at a time, and an expired policy is often found only when a claim or an audit asks for it. Vendors with no insurance on file at all are the hardest to spot, because there is no row to look at.

What popdock provides

--

Optionally name a vendor and how many days ahead to look (60 by default). It pulls policies expiring in that window or already expired, and finds any with missing dates. It then reads the vendor list and compares names to find vendors with no insurance rows at all. You get a table sorted by expiration date with vendor, policy number, status, effective and expiration dates, then the vendors with no policy. It says no policy on record, never uninsured, treats every write action as off limits and changes nothing.

Business outcome

---

Expired, expiring and missing insurance is listed in one table before a claim or audit asks, with careful wording and no records changed.
See Full Use Case

scenario

-

Vendor lists grow by import and by hand. The same vendor gets added twice with a slightly different name, contact details are left blank and child vendors point at a parent that is no longer there, and the problems surface later as payment and compliance issues.

What popdock provides

--

Optionally give part of a vendor name, and it pulls the active and the inactive vendors. It flags possible duplicates by name, abbreviated name or business ID, vendors with no email, phone, city or state, child vendors whose parent is not in the list and active vendors whose name also appears in the inactive list. You get counts of active and inactive vendors, then each problem group with vendor names and ids. Duplicates are marked as possible, and it never suggests which record to keep. It changes nothing.

Business outcome

---

Possible duplicates and incomplete vendor records are listed in one pass, with the choice of which to keep left to you.
See Full Use Case

scenario

-

Nobody keeps a list of the company and project webhooks. Over time some have no triggers and can never fire, some are inactive, two send to the same address and others still use http or an older payload version. The only way to see it is to open hooks one at a time in two places.

What popdock provides

--

Optionally name a project and a namespace, and it reads the company webhook hooks and the project hooks. It flags hooks with no triggers, a status other than active, a destination shared with another hook in the same namespace, an older payload version than their peers and http rather than https. You get a count of company hooks, project hooks and flagged hooks, then a table of the flagged ones with scope, project, id, destination, namespace, issue and suggested action. It never shows authorization headers, says when results may be partial and changes no hook.

Business outcome

---

Dead, duplicated and insecure webhooks are listed with a suggested action, without exposing credentials or touching a hook.
See Full Use Case

scenario

-

Workflow setup is spread across template, preset and tool screens, at company and project level. An archived template can still be used by a preset, a preset can be invalid and a tool can have no default, and users only find out when they start a workflow and it fails.

What popdock provides

--

Optionally give a template format, and it pulls the company workflow templates, company presets, project presets and the tools that can use workflows. It flags archived templates still used by a preset, invalid presets, tools with no default preset and projects whose presets differ from the company presets. You get counts of templates by format and tool type, then each problem group with the template or preset name. It treats every write action as off limits, reports only returned values and changes no preset.

Business outcome

---

Broken workflow setup shows up before a user hits it, from one report and with no preset changed.
See Full Use Case

scenario

-

Workforce planning custom fields are looked after separately from the other custom fields in Procore. Fields get duplicated by name, and nobody sees their type, visibility or required settings in one place, so the setup drifts without anyone noticing.

What popdock provides

--

Optionally name a company and part of a field name, and it reads the workforce planning custom fields and the custom field metadata. You get a table of each field with its type and its visibility or required flags where Procore returns them, with fields that share a name flagged as duplicates. If nothing comes back it says so. It only reads, and it never calls any action that adds, changes, reorders or deletes a field or its values.

Business outcome

---

You see every workforce planning custom field and any duplicate names in one table, with nothing edited.
See Full Use Case

scenario

-

Proposals get created on bid board projects and then never priced. Estimators find the ones with a zero total or no line items only when an owner asks why a bid is zero. Spotting them means opening every proposal on every project and checking the total and the line items separately.

What popdock provides

--

Optionally give a bid board status and a minimum total (1 by default). It reads proposals with a total below the threshold, then reads the remaining proposals and their line items to find proposals that have none. You get a table of project, proposal, type, total, reason and project due date, sorted by due date with the earliest first, and a count of each reason. If a read is capped it says the audit is partial. It reports only returned values and never edits a proposal.

Business outcome

---

Unpriced and empty proposals are ranked by due date before an owner asks about them, with no proposal touched.
See Full Use Case

scenario

-

To brief a pursuit, an estimator opens the bid board project, then the proposals, the tasks, the notes and the custom fields on separate screens and pieces the story together. Overdue tasks, a proposal with a zero total or a missing estimator are easy to overlook in that scramble.

What popdock provides

--

Name a bid board project, and optionally ask for line item groups. It finds the one matching project, listing the matches and stopping if there are several. It then reads that project's proposals, tasks, notes newest first and custom fields, and the line item groups only when you ask. You get a briefing with a summary, proposals, open tasks, recent notes, custom fields and risks, with overdue items, zero-total proposals and a missing estimator under risks. Empty sections say none on file. It reads only, never merges two projects and edits nothing.

Business outcome

---

You walk into a pursuit meeting with one briefing and its risks, without opening five screens or mixing up projects.
See Full Use Case

scenario

-

A weekly status is assembled from six or more screens: RFIs, submittals, punch items, observations, inspections, coordination issues, daily logs, manpower and the schedule. It takes an afternoon, and it is already out of date by the time it is sent, with the real problems buried in the numbers.

What popdock provides

--

Name a project and a week-ending date (today by default). It resolves the project, then reads RFIs, submittals, punch items, observations, inspections and coordination issues for new this week, open and overdue. It adds daily logs completed against days in the week, manpower totals, the schedule data date and pending requested changes. You get a one-page status ending with the three items that need attention, each with the numbers behind it. It limits itself to the counts returned, says when a read is capped and creates and changes nothing.

Business outcome

---

A one-page weekly status with its top three issues is ready in minutes, built only from the counts Procore returns.
See Full Use Case

scenario

-

Setting up a proposal on a bid board project means finding the project, making sure the name is not already used, creating the proposal and then keying each line item by hand. Miss one and you are left with a half-built proposal that someone has to find and finish later.

What popdock provides

--

Give a project, a proposal name, optionally a type and the line item names. It finds the one matching project and stops if a proposal of that name already exists. If you leave the type blank it uses the type of the project's existing proposals, and asks if there are none. You see the project, proposal name, type and every line item, and nothing is created until you confirm. It then creates the proposal and each line item once, stops at the first failure and reads the proposal back next to what you asked for. It sends only the names you gave and invents no costs.

Business outcome

---

A proposal and its line items are created once from a confirmed plan, with the result checked against your list.
See Full Use Case

scenario

-

Changing the status of a piece of equipment in Procore means finding the unit in the equipment register, finding the status you want and opening the right screen. Mistype the unit number and the wrong machine is marked as down, and nobody notices until it is needed.

What popdock provides

--

Give an equipment identification number and the new status, and it finds the one matching unit and the one matching status in Procore. It stops if the unit is ambiguous or the status does not exist, and lists the valid statuses. You see the unit, its current status and the new status, and nothing changes until you confirm. It makes one change, then reads the unit again to confirm the new status shows.

Business outcome

---

The right machine gets the right status once, with the change checked afterwards, so a typo no longer takes the wrong unit out of service.
See Full Use Case

scenario

-

A payment on hold has to be chased, but the hold sits in the financials and the vendor email, phone and insurance sit in the company directory. Whoever chases it opens both, copies contact details by hand, and holds age unanswered while vendors get several calls.

What popdock provides

--

Optionally name a project and a hold status, and it lists the payment holds with the vendor's email, phone and insurance standing beside each one. Holds are listed oldest first with the invoice, claimed amount and hold age, then suggested next steps are grouped by vendor so each vendor is contacted once. It is read-only and never releases or changes a hold. It passes the vendor id through unchanged, and reports missing contact details instead of guessing.

Business outcome

---

Every hold gets chased once per vendor with the right contact in hand, and nothing is released or altered along the way.
See Full Use Case

scenario

-

When RFIs run past their due date, the project team has to work out which contractor owes each answer and then find that contractor's contact in the directory. Stale or inactive contacts are easy to miss, so the chase goes to the wrong person or nowhere.

What popdock provides

--

Name a project and optionally an as-of date, and it lists the RFIs past their due date that are not closed. Each one is matched to the responsible contractor in the Procore directory, with email, phone and whether the contractor is still active. Results are grouped by contractor with the most overdue first. It stops if the project name is ambiguous, flags inactive contractors and several matches, and never sends or updates anything.

Business outcome

---

Each late contractor is chased once, with a current contact and a list of what they owe, and you never contact a stale address by mistake.
See Full Use Case

scenario

-

Bulk operations in Procore run in the background, and a failed one shows nothing on screen. Someone finds out only when records are missing, and then has to work out which operation failed, when and why.

What popdock provides

--

Optionally name a company and a status, and it reads the recent asynchronous operations from Procore. It groups them by status and by operation type, then lists the failures with their start and completion dates and any failure details. You get counts by status first and a table of failed operations. It only reads, so it never reruns or cancels an operation, and it says so plainly when none are found.

Business outcome

---

Failed background operations are spotted the same day, with dates and details, instead of surfacing later as missing data.
See Full Use Case

scenario

-

Estimators are assigned to bid board projects by user, but whether that person is still an active user is only visible in the company directory. Work sits with people who have left or been deactivated, and it is found when a bid deadline is already close.

What popdock provides

--

Optionally give a bid board status, and it reads the open bid board projects from Preconstruction, with due dates and totals. It looks up each assigned estimator in the Procore user directory, including the inactive users, and reports each estimator's workload. A separate list shows projects that need reassignment, including unassigned and unknown estimators. It reads only, and never proposes or assigns a replacement.

Business outcome

---

Bids stop sitting with deactivated estimators, because every gap is listed before the deadline rather than after it.
See Full Use Case

scenario

-

Before a bid is awarded, someone opens the project's bids in Procore Preconstruction, then looks up each bidder's insurance and status in the company directory one by one. A lapsed policy or an inactive vendor is easy to miss in the rush to award.

What popdock provides

--

Name a project and optionally how many days ahead to look, and it lists every vendor that has bid with its bid amount. Each bidder is checked against the company directory for insurance expiry and for active or inactive status. Vendors are flagged as expired, expiring soon, no insurance on file, inactive or not in the directory. It is read-only, matches on exact name, lists ambiguous matches rather than guessing, and never treats missing insurance as compliant.

Business outcome

---

Awards go to bidders whose cover and status have been checked, with every problem raised before the decision, not after.
See Full Use Case

scenario

-

Finding which Procore zone and web address a company runs on, and which app installation requests are waiting, means separate lookups in different places. Pending requests are easy to forget, and it is unclear whether the app is already installed.

What popdock provides

--

Ask for the company's zone and pending installation requests, and it reports the Procore web address and zone first. It then lists each waiting installation request with the developer app it is for and whether it is implicit, and can check whether an installation by that app already exists. It only reads, and it forbids every write, including any change to webhooks, installations or app configuration. If nothing is waiting, it says none are pending.

Business outcome

---

The zone, the web address and every waiting request are in one answer, so nothing pending is left unnoticed.
See Full Use Case

scenario

-

Open observations and daily logs get assigned to people who have since left or lost access to the project. The items sit with nobody, and the only way to find them is to compare each name against the project's user list by eye.

What popdock provides

--

Name a project and optionally how many days of daily logs to look back, and it collects the people assigned to open observations and the people who completed recent daily logs. It matches each name against the project's active and inactive users. You get three lists: inactive people with the observation numbers or log dates affected, names not found in the project directory, and a count of matched active people. Ambiguous names are reported, not assumed, and it only reads.

Business outcome

---

Field items stop sitting with people who no longer have access, because each one is traced back to the observation or log it affects.
See Full Use Case

scenario

-

Before subcontractors are paid, someone reads each requisition in one screen and hunts for the vendor's insurance in another. Names are spelled differently in each, and a lapsed policy slips through to a payment.

What popdock provides

--

Name a project and optionally a status, and it reads the project's requisitions and builds the list of vendors owed money. Each vendor is matched to the project roster and to its insurance records, with the company record used when the project has none. Vendors with money due and no current cover are ranked first, with a total of payment due held by uninsured vendors. It is read-only, lists ambiguous matches rather than guessing, and reports undated policies as undated.

Business outcome

---

Payments go out knowing which vendors have lapsed or missing cover, and the total at risk is clear before you approve anything.
See Full Use Case

scenario

-

Payroll and compliance staff go through the company's people records looking for missing or outdated work classifications. The mistakes only come to light when a report comes out wrong, and classifications nobody uses clutter the company list.

What popdock provides

--

Name a company, or use the only company on the connection, and optionally limit it to vendors whose name contains some text. It reads the company's work classifications and its people, then labels each person as classified, with no classification, or with an unknown classification. You get the people to fix first, then a table showing how many people use each classification, and counts for the whole company. It only reads, stops if the data is missing instead of flagging everyone, and lists inactive people separately.

Business outcome

---

Payroll and compliance work from classified people, with gaps and unused classifications found before a report goes out wrong.
See Full Use Case

scenario

-

A company sets the allowed project types, regions and stages, but project records are typed or imported separately. Admins compare them by eye, so typos and retired values sit unnoticed and break reporting.

What popdock provides

--

Name a company, or use the only company on the connection, and optionally limit the check to projects whose name contains some text. It reads the company's project types, regions and stages and every project, then marks each project's type, region and stage as ok, not set or not in list. You get a table of the projects with a problem, the values missing from each company list with how many projects use them, and overall counts. Inactive projects are reported separately, and it only recommends fixes.

Business outcome

---

Project records line up with the company's lists, so reports group correctly and typos are caught instead of sitting in the data.
See Full Use Case

scenario

-

Purchase orders go to vendors that turn out to be inactive, missing from Procore or uninsured, because the vendor directory is never checked against them. The names on a purchase order are spelled differently from the directory, which makes a manual check slow.

What popdock provides

--

Optionally give a purchase order status and a project, and it reads the open Resource Management purchase orders and groups them by vendor. Each vendor is looked up in the Procore vendor directory and its insurance, ignoring case, punctuation and suffixes such as Inc or LLC. You get one row per vendor with a verdict: ok, not in Procore, inactive, insurance expired or no insurance on file, with the verdicts that block delivery first. Orders with no vendor are listed as such, ambiguous matches are listed without choosing, and it only reads.

Business outcome

---

Open purchase orders go out only to vendors that exist, are active and are insured, with blockers found before delivery.
See Full Use Case

scenario

-

Requisitions can arrive from vendors who were removed from a project or never added to it. Nobody compares each requisition's vendor with the project roster, so the problem is found after the payment has gone out.

What popdock provides

--

Name a project and optionally a billing start date, and it reads the requisitions billed since then, defaulting to the last 90 days. It compares each vendor with the project's active and inactive roster and, for any that are in neither, searches the company directory. You get three groups: requisitions from inactive vendors, from vendors not on the project, and from vendors unknown to Procore, with the claimed amount in each. It only reads, will not call a vendor inactive unless the inactive roster shows it, and stops on an empty roster.

Business outcome

---

Requisitions from vendors who do not belong are caught before payment, with the amount at stake counted up.
See Full Use Case

scenario

-

People added in Procore are not always added to the Resource Management roster, and their job titles drift away from their Procore work classifications. Staff reconcile the two lists by hand, matching employee ids that are formatted differently.

What popdock provides

--

Optionally give part of a name, and it reads the Procore people who have an employee id, skipping and counting those without one. It matches each to the Resource Management roster by employee number, ignoring spaces and leading zeros, and checks that a job title with the name of their work classification exists. You get a table with a verdict for each person, plus roster-only employee numbers and counts. It flags duplicate ids without picking one, stops if either side is empty, and only reads.

Business outcome

---

The Procore people list and the planning roster agree, with missing people and mismatched job titles found before scheduling relies on them.
See Full Use Case

scenario

-

Superintendents often retype daily logs that are close to the day before. Picking the wrong source day, or cloning onto a date that already has logs, means copied manpower and notes that are wrong or doubled.

What popdock provides

--

Give a project, the log types, the date to copy from and the date to copy to. It resolves the project and checks both dates in Procore, warning if the target date already has logs of the same types. You see exactly what will be cloned and nothing happens until you confirm. It then clones the logs once, checks that a log now exists on the target date, and reminds you to review the copied content before it is distributed. It changes nothing else.

Business outcome

---

A near identical day starts from a copy of the right source, with the target date checked first and the result confirmed.
See Full Use Case

scenario

-

Starting a similar pursuit often means rebuilding the proposals from scratch, or copying a live project and cleaning out what should not carry over. A name that is already taken adds another copy to untangle.

What popdock provides

--

Give the source bid board project, optionally a new name, and whether it should be a template. It finds the one matching project, shows the proposals and totals the copy will start from, and checks the new name is not already in use. You see source, new name, template or live, and the proposals involved, and nothing happens until you confirm. It clones once, then searches for the new project and reports its name, status and id. It never deletes anything, even if it finds a duplicate.

Business outcome

---

A new pursuit starts from the right proposals under a unique name, cloned once, with no clean up needed.
See Full Use Case

scenario

-

Leveling bids means copying totals from several bid forms into a spreadsheet to rank bidders and test the alternates. An outlier is often noticed only once the award discussion has started, and explaining the gap means digging through line items.

What popdock provides

--

Name a bid form, optionally with its project, and it finds the one matching form, stopping if more than one matches. It reads the base bid and alternates totals and ranks bidders by base bid with the gap to the lowest in money and percent. Any total more than twenty percent from the median is marked as an outlier, with the line items that explain most of the gap. You get a ranking table, the outliers and a neutral summary. It only reads and never recommends an award.

Business outcome

---

Bidders are ranked and outliers explained by line item before the award discussion, with no recommendation made for you.
See Full Use Case

scenario

-

An overdue open item count shows that a project is behind, but not whether overdue punch items and observations are the cause. Reviews stay vague because the open item summary and the field backlog sit in different parts of Procore.

What popdock provides

--

Optionally give a minimum number of overdue open items and a project, and it reads the open item summary for each project that meets the threshold. For each of those projects it counts the punch items and observations past due that are not closed, and adds up the punch cost impact. You get a table sorted by overdue open items, with projects noted where the overdue count is high but the field backlog is empty, and the reverse. It only reads, and does not claim the two counts should match.

Business outcome

---

Project reviews start with the field backlog beside the overdue count, so you can see which projects are behind and why.
See Full Use Case

scenario

-

Operations leads who want to know how crew productivity on the same work differs between jobs export field production reports and build rate formulas in a spreadsheet. Zero quantities break the maths, and a rate built on a little completed work looks more meaningful than it is.

What popdock provides

--

Give a cost code, and optionally part of a project name or a company, and it reads the field production rows for that cost code across projects. It works out the budgeted and actual production rates and the ratio between them, states the unit of measure and skips zero-quantity rows rather than dividing by zero. You get a table by project, slowest first, with percent complete, a note on the spread between best and worst and which rates rest on little completed work. It only reads, and quotes figures as returned.

Business outcome

---

Productivity on the same work is compared across jobs in one answer, with weak data flagged rather than hidden.
See Full Use Case

scenario

-

Project asset setup starts as a copy of the company defaults and then drifts as projects change their own asset types, field rules and statuses. Nobody notices until reports on the two levels disagree, and finding the difference means comparing screens one by one.

What popdock provides

--

Name a project, and optionally a company, and it reads the company's asset types, field rules and statuses and the same three things on the project. It compares them and lists the asset types found on only one side, types whose field set, status group or parent differs, field rules on one side only or with a different rule type, and statuses on one side only. You get a table of differences with the company and project values, and a one line summary of how far the project has drifted. It only reads, and every write is off limits.

Business outcome

---

You see how far a project's asset setup has drifted from the company before reports start to disagree.
See Full Use Case

scenario

-

To find out which custom field sets drive a project's forms, you check the project's settings screen by screen. It is slow, and nobody ends up with one clear picture of what extra data the project collects.

What popdock provides

--

Name a project, and optionally a company, and it finds the one matching project, asking you to choose if several match. It lists the project's configurable field sets with the part of Procore each belongs to, and the sections inside each one. You get each field set with its class name and sections, ending with a two line summary of what extra data the project collects. It only reads, does not infer field sets that were not returned, and never changes an assignment.

Business outcome

---

One clear list of the custom field sets on a project, without opening settings screen by screen.
See Full Use Case

scenario

-

The portfolio view of project stage and estimated value never lines up with the prime contract and commitment figures, because they live on different parts of Procore. Projects whose numbers disagree are found at year end rather than when it happens.

What popdock provides

--

Optionally give a project type and a start date, and it reads the projects, taking the thirty with the largest estimated value and saying so if there are more. For each it reads the prime contract and adds up the commitment change orders, invoices and payments. You get a table per project and flags for no prime contract, an active project at a completed stage, a contract more than twenty percent away from the estimate, and commitments paid above payments received, with portfolio totals. It only reads, shows no contract as no contract and never uses a near name match silently.

Business outcome

---

Projects whose stage, estimate and contract figures disagree are found now, not at year end.
See Full Use Case

scenario

-

A project manager checks the Procore team list against the staffing schedule by eye. People end up on the team but never scheduled, or scheduled but not on the team, and vendor staff with no employee number make the matching harder.

What popdock provides

--

Name a project and optionally a start date for assignments, defaulting to today. It reads the project team from Procore and the people scheduled on the same project in Resource Management, then matches them by employee number, ignoring spaces and leading zeros. You get three lists: on the team and scheduled with start and end days, on the team but not scheduled, and scheduled but not on the team, with counts. People with no employee number are listed separately, labelled as vendor staff where that fits, and it stops on ambiguous project names and only reads.

Business outcome

---

The team list and the staffing schedule agree, with gaps in both directions found before they become a site problem.
See Full Use Case

scenario

-

Vendor trades are typed in freehand while the company trade list is kept separately, so the two drift apart. Trade searches then miss vendors, and near-duplicates such as Electrical and Electric multiply.

What popdock provides

--

Name a company, or use the only company on the connection, and optionally limit it to vendors whose name contains some text. It reads the company trade list, the trades assigned to vendors, and the vendors themselves. You get three sections: trades vendors use that the company does not define, with the vendors using them, company trades no vendor uses, and active vendors with no trade, then counts and near-duplicates. It only reads, handles empty trade data without calling every trade unused, and reports inactive vendors separately.

Business outcome

---

Vendors and the company trade list agree, so a trade search finds the vendors you expect.
See Full Use Case

scenario

-

Raising an RFI means finding the project, picking the right RFI manager and assignee from the lists Procore allows, and checking nobody has already asked the same question. Choose the wrong manager or assignee, or duplicate an open question, and the RFI stalls or splits the answer.

What popdock provides

--

Give a project, a subject, the question and who it is for, and it resolves the project and matches the assignee against the people Procore allows. The RFI manager must come from the allowed list, and it asks you if you did not name one. It checks recent RFIs for a similar subject and shows you any it finds. You see the exact values and nothing is created until you confirm. It creates the RFI once, checks it now appears, and reports the number, subject, manager, assignee and due date. Schedule and cost impact stay blank unless you gave them.

Business outcome

---

RFIs go to the right people once, without duplicating an open question, and you see the new RFI confirmed.
See Full Use Case

scenario

-

A new Procore lookahead usually starts from a blank page. Someone finds last period's lookahead, retypes its tasks, and checks by eye whether the dates collide with one that already exists. Tasks get dropped along the way and overlapping ranges go unnoticed.

What popdock provides

--

Give a project, a start and end date and optionally the label of the lookahead to copy, and it finds the project and picks that lookahead, or the most recent one if you name none. It shows you the source and warns if the new range overlaps an existing lookahead. Nothing is created until you confirm the exact values. It creates the lookahead once, reads the list again to confirm it exists, and never deletes or edits a lookahead.

Business outcome

---

Each new lookahead starts from the last one with its tasks carried over, so overlaps are caught and no one rebuilds the plan by hand.
See Full Use Case

scenario

-

A field note about a safety or quality issue sits in a notebook or a text message until someone keys it into Procore. By then the type is guessed, the assignee is whoever comes to mind, and a similar open observation may already exist.

What popdock provides

--

Give an observation name, a project, a type and an assignee, and it finds the project, matches the type and checks the assignee against the people who can be assigned. It looks for an open observation with a similar name and shows what it found. You see the exact values and nothing is created until you confirm. It creates the observation once, reads the list again to report its number, type, assignee and status, and never sends it by email.

Business outcome

---

Field observations reach Procore with a real type and a named owner, without duplicates or an email going out before you intended.
See Full Use Case

scenario

-

Adding a punch item in Procore means picking a category from the project's list and scanning open items to avoid repeating a title. Choose the wrong category or repeat a title and the item lands with the wrong trade, and the first comment explaining it is typed separately.

What popdock provides

--

Give an item name, a project and a category, and optionally a first comment. It finds the project, matches the category to the project's own punch item types and looks for an open item with the same title. You see the exact values and nothing is created until you confirm. It creates the item once, adds the comment only if you gave one, reads the list again to report the title, category and status, and never sends emails.

Business outcome

---

Punch items start with the right category and their first comment, without duplicate titles or an email going to the trades by accident.
See Full Use Case

scenario

-

Site instructions are entered by hand: choose the instruction type, check whether the same title is already logged, and pick a status that the project actually uses. Get the type wrong or log it twice and the instruction never reaches the right people.

What popdock provides

--

Give a title, an instruction type, a project and a status, and it finds the project, matches the type and looks for an instruction with the same title. The status is required, and if you leave it out it asks rather than guessing. You see the exact values and nothing is created until you confirm. It creates the instruction once, reads the list again to report its number, title, type and status, and leaves cost and schedule impact blank unless you gave them.

Business outcome

---

Site instructions are logged once with the right type and a real status, so they reach the people who have to act on them.
See Full Use Case

scenario

-

Building a submittal register means giving each entry a number that is not already used and a title that is not already logged. Two people pick the same number, or an entry is added twice, and the design team ends up reviewing the same package under two numbers.

What popdock provides

--

Give a title, a project and optionally a number, and it finds the project and asks Procore for the next free number. If you supplied a number it checks that exact number is available and refuses it if not. It looks for a submittal with the same title and shows you the exact values. Nothing is created until you confirm. It creates the submittal once and reads the list again to report its number and title.

Business outcome

---

Each submittal enters the register once with a number that is actually free, so the design team reviews each package under one number.
See Full Use Case

scenario

-

Creating a Procore task by hand starts with finding the right project, then the right person, then a category, and checking nobody has already logged the same title. Pick the wrong project or assignee and the task is lost, and duplicate titles pile up.

What popdock provides

--

Give a task title, a project and optionally a due date and an assignee. It finds the one matching project, matches the assignee to a person who can be assigned, and shows the categories without choosing one for you. It looks for a task with the same title and asks whether to create another. You see the project, title, assignee, category and due date, and nothing is created until you confirm. It creates the task once and reads it back with its number, status and due date.

Business outcome

---

Tasks land on the right project with the right owner and a due date, with no duplicate titles and no updates or deletes along the way.
See Full Use Case

scenario

-

Every new pursuit has to be keyed into the Preconstruction bid board by hand. Someone checks the board for a similar name, types a status the estimating settings may not use, and hunts for the customer's company id. Duplicates and invalid statuses follow.

What popdock provides

--

Give a project name and status, and optionally a customer and due date. It checks the bid board for the same or a very similar name and stops if it finds one. It checks the status against the statuses your estimating settings define, and finds the customer from existing bid board projects, asking before it creates without one. You see the exact values and nothing is created until you confirm. It creates one project, never retries on failure, and reads back the stored record.

Business outcome

---

New pursuits reach the bid board once, with a valid status and the right customer, instead of as duplicates to clean up.
See Full Use Case

scenario

-

A bid package needs the right project id, a title that has not been used and a message for bidders. Look up the id from the wrong place, repeat a title or leave the message blank, and the package goes out wrong or sits in the list twice.

What popdock provides

--

Give a package title, a bid board project, a due date and a bidder message. It finds the project id from the bid board, falling back to estimating projects, and stops if the name matches more than one. It looks for a package with that title and stops if one exists. You see the project, id, title, due date and message, and nothing is created until you confirm. It creates the package without optional fields, invites no bidders, and reads back the stored package.

Business outcome

---

Bid packages are created once on the right project with the message you approved, and no bidders are invited by accident.
See Full Use Case

scenario

-

Change events are raised in a hurry when scope shifts on site. Nobody searches for an existing event first, so the same change appears under different titles, and the budget team later has to work out which one is real.

What popdock provides

--

Give a project, a title and the scope of the change. It resolves the project from the budget and stops if no project or more than one matches. It looks for a change event with a similar title and asks whether to continue if one exists. Scope is required, so it asks if you left it blank. You see the project, title, scope and project id, and nothing is created until you confirm. It creates one change event, never retries, and reads back its number and status.

Business outcome

---

Each scope change is raised once as a single change event, so duplicates stop piling up under different titles.
See Full Use Case

scenario

-

Cost codes are typed into a project by hand. Someone checks the list for the code, finds the company standard code to link, and keys in a name. Skip a check and you create a duplicate code, or one that is not linked to the company standard.

What popdock provides

--

Give a code, a name, a project and optionally a standard cost code. It resolves the project and stops if the match is not unique. It checks whether the code already exists and stops if it does. If you gave a standard code it finds a single match for it, and stops if there is none or several. You see the project, code, name and standard code and nothing is created until you confirm. It creates the code once and reads it back with its id.

Business outcome

---

Cost codes are added once and linked to the company standard, so project budgets stay consistent and free of duplicates.
See Full Use Case

scenario

-

A bid due date lives in Preconstruction, but the reminder to review bids before it has to be typed into Procore tasks by hand. It is created late, created twice, or forgotten, and then nobody reviews the bids until the deadline has passed.

What popdock provides

--

Give a project id and a bid package title, and optionally how many days before the deadline the task is due (7 by default). It finds the package, stops if more than one matches, and reads its due date. It checks the project is active and that no open task already mentions the package. You see the proposed task with its due date, project and a description with the package number and deadline. One task is created only after you say yes. Preconstruction data is never touched.

Business outcome

---

Every bid deadline gets one review reminder in Procore, due ahead of time, instead of a task someone forgot to type.
See Full Use Case

scenario

-

A payment hold is noticed in the finance view but the follow up is never assigned. The hold reason, vendor and amount have to be copied into a task by hand, and without an owner nobody on the project knows the hold is theirs to clear.

What popdock provides

--

Give a hold reference or invoice number and a project, and optionally an assignee and a due date (three business days by default). It reads the payment hold, resolves the project, vendor and assignee, and checks for an existing task. It stops on ambiguous or inactive holds, an unknown assignee or an existing task. You see the task with the hold reason, claimed amount and vendor, and one task is created only after you say yes. It reads the task back and never changes the hold.

Business outcome

---

Each payment hold gets one task with a named owner and a due date, so the follow up no longer depends on someone remembering it.
See Full Use Case

scenario

-

An RFI is overdue, someone notices, and no one is assigned to chase it. Making a task means checking the due date, finding the right person on the project, checking nobody else already raised one, and typing the title by hand.

What popdock provides

--

Give an RFI number, a project and the person who should chase it. It reads the RFI and checks it is overdue and not closed, then resolves the project and finds exactly one matching person. It looks for an open task that already mentions the RFI. You see the task, built from the RFI number, subject and responsible contractor, with the assignee and a due date three days out. One task is created only after you say yes, and it is read back. The RFI is never changed.

Business outcome

---

Overdue RFIs get a named person and a task to chase them, with no second task and no change to the RFI itself.
See Full Use Case

scenario

-

A new Procore project needs a matching project in Resource Management before staff can be planned on it. Someone retypes the name and status, and without a check for an existing one, a duplicate project splits the planning.

What popdock provides

--

Give a Procore project name, the Resource Management group id and optionally a status (active by default). It reads the Procore project and stops if none or several match. It checks Resource Management by name and by project number and stops if one already exists. You see the name, status and group id, and nothing is created until you confirm. It creates the project once and reads it back. It never invents a group id and never writes to Procore.

Business outcome

---

Each Procore project gets one matching Resource Management project, so staff can be planned without a duplicate to merge.
See Full Use Case

scenario

-

Superseded proposals are cleared from the bid board without anyone checking what was in them. Names are similar across revisions, a proposal can be the only one on the project, and the wrong one is lost with its totals and line items.

What popdock provides

--

Give a bid board project and a proposal name. It finds the project and the one exact proposal, and lists the proposals if the name does not match exactly one. It shows the total, the number of line item groups and line items, and whether it looks like the only proposal on the project. Deletion cannot be undone from here, so it asks you to type the exact proposal name. It deletes that one proposal, checks it is gone, and never deletes line items or notes separately.

Business outcome

---

Superseded proposals are removed deliberately, with their contents shown first and a typed confirmation, so the wrong one is not lost.
See Full Use Case

scenario

-

When a company webhook stops delivering, a developer opens the hook list, then the deliveries, then each failed attempt one by one, reading response codes and bodies on separate screens. The pattern across hooks is easy to miss and the fix order is guesswork.

What popdock provides

--

Say how many days to look back (7 by default) and optionally name one hook. It lists the company hooks with their status, destination and trigger count, finds failed deliveries in the window, and groups them by hook, status and event type. For the worst hooks it reads the failed attempts and classifies the cause as bad destination or credentials, receiver down, network trouble or a hook that never fires. You get a table per hook and the one to fix first. It is read-only and does not guess causes the attempts do not show.

Business outcome

---

You find out why company webhooks are failing and which one to fix first, without paging through delivery and attempt screens.
See Full Use Case

scenario

-

Tracing a failing project webhook means hopping between the project's hooks, its deliveries and the individual failed attempts, then reading response bodies to work out whether it is credentials, a missing endpoint or a receiver that is down.

What popdock provides

--

Give a project id and optionally how many days to look back (7 by default). It lists the project's hooks with status, destination and trigger count, then finds deliveries in the window and groups them by hook, status and event type. For hooks with failures it reads the failed attempts and classifies the cause as auth, not found, receiver error, timeout or never triggered. You get one line per hook with the likely cause and the fix, and what to fix first. It is read-only and stops if the project has no deliveries.

Business outcome

---

You see the likely cause for each failing project webhook in one report, without opening each delivery and attempt yourself.
See Full Use Case

scenario

-

Projects are marked inactive or closed in Procore while invoices and costs keep landing on them. Nobody compares the project list with requisitions, direct costs and billing periods, so the leak is found at month end when the books are already closing.

What popdock provides

--

Say how far back to look (60 days by default) and optionally which stage to treat as closed. It finds projects that are inactive or in that stage, then reads requisitions, direct costs and open billing periods for the first 25 and says so. You get a table by project with amounts billed and booked, open periods and the latest activity date, highest amount first. It ends with the total booked and which projects look finished or wrongly closed. It is read-only, and never reopens a project or changes a billing period.

Business outcome

---

Spend landing on closed projects is found within days rather than at month end, with the total and the projects to look at first.
See Full Use Case

scenario

-

Project teams scan a project's task list by eye to see what is late and who owns it. Items without a due date or an assignee are easy to overlook, and overdue tasks sit until someone complains in a meeting.

What popdock provides

--

Name a project and optionally how many days ahead to look (7 by default) and a status. It pulls the task items due within that window or already overdue, and sorts them into overdue, due soon and no due date. Tasks are grouped by assignee, with unassigned tasks in their own group, and it states which statuses it treated as closed. You get each assignee's overdue count and tasks with number, title, due date, status and category, and the three assignees with the most overdue. It is read-only.

Business outcome

---

You see what is overdue and who owns it in one view, so late tasks are chased before the next progress meeting.
See Full Use Case

scenario

-

Project managers read through a field production report line by line to find cost codes running over their budgeted hours. The forecast overruns are the ones that matter, and they are the hardest to see when you are comparing actual and projected hours by eye.

What popdock provides

--

Name a project and optionally how many rows to look at (50 by default). It pulls the field production rows and flags any cost code where actual hours are above budgeted hours, or where projected hours at completion are above budget. It works out the overrun in hours and as a percentage, and uses percent complete and utilisation to separate rows already over from rows trending over. You get a table sorted by overrun hours and two sentences on where the risk sits. It is read-only, and rows with zero budgeted hours are left out of the ratios.

Business outcome

---

The cost codes heading for an hours overrun are ranked in one view, so you act on them while there is still time to recover.
See Full Use Case

scenario

-

Quiet sites are only noticed when something goes wrong. The company project list sits in one place and the daily logs in another, and nobody lines them up to see which active projects have stopped filing logs.

What popdock provides

--

Say how many days to look back (14 by default) and optionally a project stage. It lists active projects, keeping only the stage you name, then checks each for daily log headers since the cutoff. Projects with none are reported as quiet, with the date of their last log if one exists. You get a table of quiet projects and counts of those checked, quiet and with logs. It says how many it checked and which it skipped if there are too many. It is read-only.

Business outcome

---

Projects that have stopped filing daily logs are spotted within days, before a gap in the record becomes a problem.
See Full Use Case

scenario

-

Before building a Procore webhook you have to find the right resource and the event to subscribe to. The catalog is long, resource names do not always match the feature names, and you scan it page by page and compare payload versions yourself.

What popdock provides

--

Give a topic, such as a Procore feature, category or resource name, and optionally a project id. It searches the company or project webhook resource catalog by name, then by feature and by category if nothing matches. You get a table of resource name, feature, category, supported actions and payload version, with the payload version that has the most coverage. If several match, it says which looks closest. It never invents a resource name, and it asks for a different term after three misses. It is read-only.

Business outcome

---

You find the right webhook resource, its events and its payload version in one lookup instead of scanning the catalog.
See Full Use Case

scenario

-

Missing lien waivers are found when a payment run stalls, because invoices and waivers are checked on separate screens. Matching each invoice to its waiver, then checking subtier waivers on top, is slow and easy to get wrong.

What popdock provides

--

Name a project and optionally the date to look from (60 days back by default). It reads the invoices billed since that date and the lien waivers and subtier waivers on the project, and matches waivers to invoices by invoice number. You get three lists: invoices with no waiver, incomplete waivers and incomplete subtier waivers, each with vendor, invoice number and amount, plus a count for each. It states which statuses it counted as complete. It is read-only and sends no waiver requests.

Business outcome

---

Missing and incomplete waivers are listed before a payment run, so nothing is held up at the last minute.
See Full Use Case

scenario

-

Leave is recorded in Resource Management while the project team lives in Procore. To plan a critical stretch, a planner matches employee ids between the two by hand and checks each person's leave dates against the window.

What popdock provides

--

Give a project and a date window. It reads the project's team from Procore, then reads time off from Resource Management and keeps only the leave that overlaps the window. Team members are matched on employee id, ignoring spaces and leading zeros, and anyone without an employee id is listed separately. You get a table of each person's leave dates, reason, paid status and working days inside the window, then who has none. Recurring leave is shown once and said so. It is read-only.

Business outcome

---

You see which project team members are away during a critical stretch before it starts, so the gaps are planned for rather than discovered.
See Full Use Case

scenario

-

Rented equipment stays on site while the rental vendor's insurance certificate has expired in Procore. The equipment register is in Resource Management and the insurance is on the vendor record, and nobody lines the two up until an incident or an audit.

What popdock provides

--

Say from which rental end date to look (today by default) and optionally a status. It reads the rented equipment from Resource Management, then checks each vendor's insurance in Procore. Vendor names are matched ignoring case, punctuation and suffixes such as Inc or LLC, and similar names are listed instead of guessed. You get a table by vendor with equipment count, latest rental end, best policy expiry and a verdict, worst first, with the equipment under each flagged vendor. Equipment with no vendor is listed as unattributed. It is read-only.

Business outcome

---

Rented equipment on site with lapsed or missing vendor cover is flagged before an incident, with the worst vendors listed first.
See Full Use Case

scenario

-

The insurance register sits in the company directory and the site logs sit on each project, so nobody lines the two up. A vendor whose certificate ran out last month can keep turning up in manpower and inspection logs because the expiry date and the sign-in record are never put side by side.

What popdock provides

--

Give a lookahead window in days, and optionally a project, and it finds vendor insurance that has already expired or expires inside that window. It then searches the last 30 days of manpower and inspection logs for those vendors and lists where and when each was on site, lapsed cover with recent site presence first. Near matches on a name are labelled unconfirmed, a vendor not found in the logs is reported as not seen on site, never as compliant, and nothing in Procore is changed.

Business outcome

---

You see which vendors are working on site with lapsed cover, so the certificate chase starts with the right names and nothing in Procore is touched.
See Full Use Case

scenario

-

Finding out what BIM content a project holds means opening models, then revisions, files, levels and plans in turn. Models with no revision or files nobody refers to sit unnoticed, and a project can have models but no levels without anyone saying so.

What popdock provides

--

Give a project name, and optionally part of a model title, and it reads that project's models, revisions, files, levels and plans. You get counts of each, a table per model with its revisions, and flags for models with no revision, files no revision refers to, and a project with models but no levels. It stops and lists the options if the project name matches more than one project, flags based on file names are labelled as indications, and nothing is changed.

Business outcome

---

You get a clear picture of a project's BIM content in one request, with the gaps flagged and nothing edited.
See Full Use Case

scenario

-

Delays get recorded days later from memory, so the cause and the date drift. Or two people log the same delay, and the duplicate or vague entry weakens a delay claim when it matters.

What popdock provides

--

Give the project, the date and the delay comments, and it resolves the project, finds that day's daily log header and shows any delays already logged for the date. You see the exact values it will record and nothing is written until you say yes. It then records one delay entry and reads the day's delay logs again to confirm it, or reports the exact error and stops. This writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

Delays are logged the day they happen, once, with the existing entries in view, so the record stands up later.
See Full Use Case

scenario

-

Service is done in the yard and written up days later from memory, or never. The maintenance history for a machine ends up incomplete, and the same service can be keyed twice for one day.

What popdock provides

--

Give the equipment identification number, the type of maintenance, a start date and any notes, and it finds that one unit in the equipment register. It checks whether a maintenance record already starts on the same date and shows it first. You see the unit, type, date and notes, and nothing is saved until you confirm. It then writes one record, reads the unit's maintenance records again to confirm, and never edits or deletes existing ones. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

Maintenance is logged when it is done, once, so each machine has a history you can trust.
See Full Use Case

scenario

-

Follow-ups agreed on a bid call never reach the bid board because keying a note or task is one more step after the meeting. When someone does add it, the same note often gets entered a second time.

What popdock provides

--

Say whether it is a note or a task, name the bid board project and give the text, plus a due date for a task. It finds the one matching project and checks the existing notes or tasks for the same text, showing any repeat before you decide. You see the project, kind, exact text and due date and nothing is saved until you confirm. It adds one entry, sets no assignee, and reads the list again to show the new entry. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

Bid follow-ups land on the bid board the same day, once, with the exact words you approved.
See Full Use Case

scenario

-

Estimators hunting for the right unit cost open each catalog separately, and the same item can be priced differently in two of them without anyone seeing it. Units differ between catalogs too, so two numbers that look comparable are not.

What popdock provides

--

Give the item name to search for, and optionally a catalog name or a top unit cost. It finds the matching catalogs, then every cost item whose name contains your search, and lays out catalog, type, unit, unit cost, unit labor cost, item margin and labor margin. Items are grouped by name so the same item in different catalogs sits together, with the cheapest unit cost marked. When units differ it says the costs are not comparable and does not convert them. It never guesses a price, and nothing is changed.

Business outcome

---

You see every price for an item side by side with the cheapest marked, without opening catalog after catalog.
See Full Use Case

scenario

-

Project lists in Procore and Resource Management are maintained by hand, so a project added to one is forgotten in the other. Staff then get planned against a job that does not exist on the other side, or against a closed one.

What popdock provides

--

Optionally give a name filter and a Resource Management status, and it reads the Procore projects and the Resource Management projects. It matches on project number first, ignoring case, spaces and leading zeros, then on exact name when a number is missing, and marks those as name only. You get one row per project with a verdict: matched, name differs, stage or status differs, in Procore only, or in Resource Management only, plus counts. Duplicate numbers are listed rather than chosen between, closed and inactive pairs are not flagged, and nothing is created or changed.

Business outcome

---

You see exactly which projects are missing from Resource Management or out of step, so staff are planned against the right jobs.
See Full Use Case

scenario

-

Billing periods are created by hand on each project, and an overlapping or backwards date range is easy to enter. An overlap breaks how invoices are dated, and it is awkward to unpick once invoices reference it.

What popdock provides

--

Give the project and the start date, end date and due date as YYYY-MM-DD. It finds the single matching project and reads its existing billing periods, stopping and showing any period that overlaps the dates you asked for. It also stops if the end date is before the start date or the due date is before the end date. You see the project and dates, nothing is saved until you confirm, and then it creates one period using the status of the most recent one and reads the periods back. Existing periods are never changed. It writes to live Procore data only after you confirm, so test it in a sandbox first.

Business outcome

---

New billing periods are created once, in clean date order, with no overlap to break invoice dating.
See Full Use Case

scenario

-

Assets get deleted without anyone seeing what is attached to them or connected to them, and there is no undo. The delete preview, the attachments and the recent history live in different places, so most people skip the check.

What popdock provides

--

Give the asset name and the project, and it runs the delete previews for that name at project level and at company level. It then adds the attachments and recent history for the same assets, so you see the impact before any deletion. You get a table of the assets that would be affected with code, location, parent asset, last modified by and attachment count, and a one line count of company versus project level and which have attachments. It only previews: it never deletes, and if you want to proceed you are told to delete elsewhere after reviewing the list.

Business outcome

---

You see exactly what a deletion would touch, attachments included, before anyone presses delete, with nothing removed by this check.
See Full Use Case

scenario

-

Before awarding work, someone pieces together a vendor's business address, coverage areas, classifications, provided services and attachments from several tabs on the project vendor record. It takes a while and the picture is never in one place.

What popdock provides

--

Give the vendor name and the project, and it finds that one project vendor, stopping and listing candidates if more than one matches. It then pulls the vendor's business addresses, coverage areas by country and region, classifications, provided services and the attachment file names, and writes a short profile. Only rows for the matched vendor are used, sections that return nothing are named, and nothing is changed. Every write is off limits.

Business outcome

---

You get a one page vendor profile from the project record in a single request, with empty sections called out and nothing edited.
See Full Use Case

scenario

-

To judge a bidder, someone pulls their bids and invitations in Preconstruction, then separately checks the vendor record, insurance and ratings in the company directory. The two views are never combined, so a bidder with expired cover or poor ratings can look fine on the bid side.

What popdock provides

--

Give a vendor name and it reads their bids and bid invitations from Preconstruction, then their directory record, insurance policies and ratings from the Procore company directory. The join is the exact vendor name, and it stops to ask if the name matches more than one vendor. You get one profile: group, active status and location, invited count, bids submitted with lowest, highest and average lump sum, insurance with expiry dates, a ratings summary and a closing line of concerns. A vendor with bids but no directory record is reported as a finding, empty sections say none found, and both systems are only read.

Business outcome

---

You judge a bidder on bidding history and company standing together, with concerns such as lapsed cover or no directory record stated outright.
See Full Use Case

scenario

-

Understanding one vendor means opening the company record, its insurance, every project it is on and every requisition it billed, each on a separate screen. The totals are never added up, and a vendor can be inactive but still billing, or billing with expired cover, without anyone noticing.

What popdock provides

--

Give a vendor name and optionally a billing start date, defaulting to the last 12 months. It finds the vendor, stopping and listing candidates if the name is ambiguous, then reads its projects and insurance. For up to ten of the most recent projects it reads the requisitions and direct costs billed by that vendor, and reports count, total claimed, total payment due, direct cost total and latest billing date per project. You also get the vendor's total billed and flags such as inactive but billing, or expired cover with money due. Names are matched after normalising and both spellings are shown, the cap of ten is stated, and nothing is changed.

Business outcome

---

One profile shows who the vendor is, whether cover is current and what it has billed, so you can raise flags before money moves.
See Full Use Case

scenario

-

Matching a purchase order to what shipped and what was received takes three screens and a calculator. Short or damaged deliveries get paid for anyway because the ordered, shipped, received and defective quantities are never put on one page.

What popdock provides

--

Give the purchase order name and the project, and it reads the purchase order, its lines, the shipments, the receipts and the defect lines. You get one row per line with ordered, shipped, received, defective and outstanding quantities, a flag where shipped plus outstanding does not equal ordered or received is more than shipped, totals and a list of lines needing follow-up. It works only from returned quantities, shows a missing number as missing and does not flag that line, says when a read hit its cap, and stops if the purchase order or project is ambiguous. Nothing is changed.

Business outcome

---

Short, over and damaged deliveries are caught line by line before payment, from the actual quantities and with nothing guessed.
See Full Use Case

scenario

-

Time off is entered without seeing which jobs it clashes with, so the clash is found by the foreman on the day. Overlapping assignments and existing leave sit on different screens from the entry form.

What popdock provides

--

Give the employee number, the start and end day and a reason. It finds the person from their assignment data, then shows overlapping time off and assignments in those dates so the clashes are visible first. You see the person, dates, paid or unpaid, reason and overlapping assignments, and nothing is saved until you confirm. It then creates one time off entry and lists any assignments that now clash and need rescheduling. It never edits existing assignments or time off, and it checks the dates are real and in order. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

Time off is booked with the clashes already in view, so rescheduling is planned before the day instead of found on it.
See Full Use Case

scenario

-

Certificates are keyed into the vendor record by hand, often against the wrong vendor or with the wrong dates. Overlapping policies then hide a lapse, because the older policy appears to cover the gap.

What popdock provides

--

Give the policy name, the vendor and the effective and expiration dates. It finds the single matching vendor and lists the policies already on file with their dates, stopping to ask if one with the same name overlaps. It also stops if the expiration date is not after the effective date. You see the vendor, policy name and dates and nothing is saved until you confirm, then it creates one policy and reads the vendor's policies back to show it. Existing policies are never edited. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

Insurance certificates are recorded against the right vendor with correct dates, once, and without hiding a lapse behind an overlap.
See Full Use Case

scenario

-

New machines are added to the equipment register with the wrong category or a duplicate identification number, because the type, category and status ids have to be hunted down first. A wrong category then sends the unit into the wrong reports.

What popdock provides

--

Give the name, identification number, category and type. It first checks that the identification number is unused and stops if a unit already has it. It then resolves the category and type from the register's own lists, asks you for the starting status and whether the unit is owned or rented, and looks up a make or model if you name one. You see every value and nothing is saved until you confirm, then it creates one unit and reads the register back to show it. It never guesses a category, status or ownership. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

New equipment is registered once, with the right category, type and status, and no duplicate identification number to clean up later.
See Full Use Case

scenario

-

RFI replies get entered against the wrong RFI, or marked official by accident, because the number and the project are easy to mix up on a busy job. Once an official reply is in, most workflows treat the question as answered.

What popdock provides

--

Give the RFI number, the project, the reply text and whether it is an official reply. It resolves the project, finds the single matching RFI and shows the replies already recorded so you can see what is there. It warns that an official reply closes the question in most workflows, shows you the exact values and waits for an explicit yes. It then records one reply, reads the replies again to confirm it and reports the RFI status afterwards. It never advances ball in court, which stays your separate decision. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

Replies land on the right RFI, official only when you mean it, with ball in court left exactly as it was.
See Full Use Case

scenario

-

Extending a bid deadline means re-entering the package, and an unchanged field such as a message can get blanked on the way through. Bidders who already submitted a bid can also be caught by surprise when the date moves.

What popdock provides

--

Give the bid package title, the project if you want to narrow it, and the new due date. It finds the single matching package and carries over the title and the existing messages so nothing is blanked, asking you for the web message if it was not returned. It shows the current due date, invites sent and bids already received, and warns when bids are in. You see the old date, the new date and the carried values, nothing is saved until you confirm, and it changes only the due date, then reads the package back to report the stored date. It writes to live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

The bid deadline moves without re-keying the package or blanking a message, and bidders who already submitted are flagged first.
See Full Use Case

scenario

-

Deleting a webhook hook without checking its activity can break a live integration that nobody remembered was using it. The hook, its triggers and its recent deliveries sit on separate screens, so the check is easy to skip.

What popdock provides

--

Give the hook id, and a project id if it is a project hook, otherwise it treats it as a company hook. It shows the hook and its triggers and reads the last 30 days of deliveries, saying prominently if the hook has recent successful deliveries and is in active use. It tells you deletion is permanent and waits for a clear yes. It then deletes the triggers and the hook itself and reads the hooks back to confirm it is gone. It deletes only that hook and its triggers, stops if any delete fails and changes nothing if you decline. It acts on live Procore data only after you confirm, so try it in a sandbox first.

Business outcome

---

A webhook hook is retired only after you have seen its triggers and recent deliveries, so a live integration is not broken by surprise.
See Full Use Case

scenario

-

Failed BIM file extractions are noticed only when a model looks empty, because nobody checks the extraction list. A job marked complete can also have produced no items at all and still look fine on the list.

What popdock provides

--

Optionally give a project name and a start date, and it reads the BIM file extractions that match and groups them by status. For extractions that did not fail it checks the items each one produced against its status, so a complete extraction with no items is flagged as suspect. You get counts by status and a table of failed or suspect extractions with project, file name, status and created date. It says plainly that the cause of a failure is not in this data, shows unfamiliar statuses as returned without interpreting them, and changes nothing.

Business outcome

---

Failed and empty extractions are found before someone opens an empty model, with the status shown exactly as returned.
See Full Use Case

scenario

-

Cost and schedule impacts buried in RFIs never reach the change order conversation until the money is already spent. Finding them means filtering the RFI log by impact, adding up the values and reading the question and reply behind the biggest ones.

What popdock provides

--

Give the project and optionally a minimum cost impact. It resolves the project, then pulls RFIs with a cost impact at or above that value and those with a confirmed cost or schedule impact, and merges them. For the five largest it reads the question and the replies to see whether they justify the impact. You get a table of number, subject, cost impact, cost and schedule status, due date and whether it was replied to, a total, RFIs with a schedule impact but no cost, and those most likely to become change events. Zero or blank cost is listed separately as not confirmed, nothing is edited, and a capped read is called out.

Business outcome

---

RFI impacts reach the change order conversation early, with confirmed and unconfirmed amounts kept apart and no RFI edited.
See Full Use Case

scenario

-

RFQs stall because nobody sees which have had no reply and which came back over the estimate. The quotes, responses and change order package status are on different lists, so the follow-up is driven by whoever happens to look.

What popdock provides

--

Give the project, and optionally a status. It reads the RFQs, their quotes and their responses and matches them on RFQ number. It flags RFQs past their due date with no quote or response, RFQs where a quote exceeds the estimated amount, and RFQs with responses but a change order package that has not started. You get a table with RFQ number, title, status, due date, estimated amount, quotes received and the lowest and highest quote, then the flagged items. It is read-only, sends no reminders, changes no RFQ, and reports the filters if nothing matches.

Business outcome

---

Stalled, unanswered and over-estimate RFQs are visible in one table, so follow-up goes to the right ones with nothing sent or changed.
See Full Use Case

scenario

-

Work breakdown structure code lists grow by hand, and the inconsistencies are found only when a budget will not roll up. A code with more parts than its pattern allows, a duplicate, or an inactive code still on a budget line is easy to miss.

What popdock provides

--

Give the project, and optionally a code status. It reads the WBS patterns, their segments and the project's codes, then checks for codes with more parts than their pattern has segments, duplicate codes, codes with a blank attribute name where others have one, and inactive codes still referenced by budget lines. You get a pattern summary and the findings per check, each with the code and the reason. If the project has no WBS codes it says it is not using WBS. It is read-only, edits no code or segment, and reports only what it reads.

Business outcome

---

Structural problems in the WBS are found while setting up, not when a budget refuses to roll up, with no code touched.
See Full Use Case

scenario

-

Action plans stay open because items have no assignee and approvals are never chased. Counting open and overdue items per plan, and finding which approvers are still pending, means opening each plan one at a time.

What popdock provides

--

Give the project and optionally a plan type. It resolves the project, then pulls the action plans, their items, approvers and item assignees. You get a table with plan number, title, type, manager, status, open items, overdue items and approvers pending, then the plans with overdue items or no approver, and the items with no assignee. It is read-only, changes no plan or approval, marks missing values as missing, says when a read hit its cap, and stops if the project cannot be resolved.

Business outcome

---

Overdue items, missing approvals and unassigned work across all action plans are visible in one table, with nothing changed.
See Full Use Case

scenario

-

Inventory write-offs and direct issues get posted without a reason, and the shrinkage only shows up at year end. Reading each adjustment and issue document and its lines for a period is slow, so the blank reasons and the large negative adjustments are never reviewed.

What popdock provides

--

Give the project and optionally a start date, defaulting to the last 30 days. It reads the adjustments and their lines, then the direct issues and their lines for the period. You get a table of adjustments with name, created by, state, line count and net quantity, and a table of issues with name, issued to, state and line count. It lists adjustment lines with no reason and the largest negative adjustments, and the items adjusted most often. A blank reason is flagged, not corrected, nothing is edited, and a capped read is called out. It stops if the project name matches no records.

Business outcome

---

Write-offs without a reason and large negative adjustments are caught within the month, not at year end, with nothing edited.
See Full Use Case

scenario

-

Procore app installations pile up across projects, and each one should carry a configuration. Checking means opening every installation, then its configuration screen, and comparing dates by eye. An installation with nothing configured, or a configuration nobody touched in years, goes unnoticed until the app misbehaves.

What popdock provides

--

Name an installation or a project, or leave both out for everything, and it lists each Procore app installation with its app name, project and status. It then pulls the configurations for each one with their title, who created them and when they were created and last updated. Active installations with no configuration are listed, as are configurations whose installation is uninstalled, and anything not updated in over a year is flagged as possibly stale. The review only reads, and no write is ever made.

Business outcome

---

Missing and stale app configurations show up in one review, so you fix them before an installation fails, with nothing changed in Procore.
See Full Use Case

scenario

-

A Procore marketplace listing is judged on its pictures, videos and helpful links. To check one you open each media type for the app and look for missing descriptions, unlabelled links and entries on inactive installations. Gaps are easy to miss, and the listing looks unfinished to the people deciding whether to install it.

What popdock provides

--

Name an installed app, and optionally a project, and it reads the app's videos, pictures and helpful links. It flags apps with no pictures, videos or pictures with no description, helpful links with no label, entries on installations that are not active and links that are not https. You get counts per media type and a list of issues with the entry name, installation and project. It judges from the data returned and never opens or fetches the links.

Business outcome

---

Gaps in an app's marketplace listing are listed in one review, so you fix them before customers see an unfinished page.
See Full Use Case

scenario

-

Files on Procore assets are only found by opening each asset, so you cannot see where documentation is missing. Attachments with no description, and asset types that hold files at type level but none on the assets themselves, stay hidden. Coverage differs from project to project and nobody sees it.

What popdock provides

--

Give a project name, and optionally an attachment level, and it pulls attachments at asset, company and asset type level. It flags attachments with no description, counts them by project, level and source, and shows who last modified them. Asset types that have files at type level but none on assets are called out. You get a table of counts and a list of attachments missing descriptions with the asset id. It reports only returned rows, and every write action is off limits.

Business outcome

---

Uneven asset documentation and undescribed files are visible in one report, with nothing changed in Procore.
See Full Use Case

scenario

-

Asset audit trails in Procore are read row by row, so a spike of edits or a run of deletes is only noticed after the fact. Working out who changed what, and on which days activity jumped, means scrolling history and tallying by hand.

What popdock provides

--

Give a start date, which defaults to the last 30 days, and optionally a person, and it pulls the company and project asset history. It counts changes by operation and change type and by user, finds days with more than three times the daily average, and lists deletes with the date and who made them. You get a table of counts by user and operation, the spike days and the deletes. It reports only returned history rows, and every write action is off limits.

Business outcome

---

Unexpected bulk changes and deletes on assets are spotted from one summary, rather than found weeks later in the history.
See Full Use Case

scenario

-

Estimators scan the Procore bid board by hand to see which pursuits are overdue, have no estimator or are priced at nothing. Statuses mean different things in each company's estimating settings, so open and lost work get mixed up. The late ones surface after the bid is lost.

What popdock provides

--

Optionally give a status, customer or due date cut off, and it pulls the bid board and the estimating settings that say which statuses are open work and which are lost, delayed or complete. It flags projects past their due date that are still open, with no estimator, with an empty or zero total or with no customer. You get a table sorted by due date and the three projects to act on first with a sentence on why. It never changes a project and says when the result is capped.

Business outcome

---

The pursuits most at risk are named at the top of a ranked list, so estimators act before a bid is lost to lateness.
See Full Use Case

scenario

-

To confirm bidders were told about the latest drawings, a coordinator checks the correspondence on one screen, the attachments on another and the planroom revisions on a third. Comparing dates across them by hand is slow, and a new revision can sit unannounced while bidders price from the old one.

What popdock provides

--

Name a bid package, and optionally a subject to search, and it finds the package, stopping with a list if more than one matches. It merges the package's correspondence with its attachments and the planroom documents with their revisions into one dated timeline. It flags when the latest planroom revision is newer than the latest correspondence, which can mean bidders were not told. The package due date and invite count are shown at the top. It lists file names only and never opens a file.

Business outcome

---

You see in one timeline whether bidders were told about the latest revision, before the bid due date, with nothing sent or changed.
See Full Use Case

scenario

-

Bid packages live in Preconstruction, while the project's stage, status and dates live in the core Procore project record. Nobody lines the two up, so a bid due after the planned start, or a package attached to an inactive project, is only noticed when it causes trouble.

What popdock provides

--

Give a project id and it reads the project's bid packages with their due dates, invites sent and bids received, then reads the core project record and its milestone dates. It flags a package when the project is inactive, when the bid is due after the project start or a milestone, when no invites were sent or when the due date has passed with no bids. If either side has no record it stops with a clear message, and it says when a flag rests on a missing date. Both sides are read only.

Business outcome

---

Timing and status conflicts between bid packages and the project record are found in one check, before they delay award.
See Full Use Case

scenario

-

Preconstruction teams check each Procore bid package by hand to see who has been invited and who has bid. A thin package, with few bids close to its due date or no invites at all, is spotted after the deadline has passed.

What popdock provides

--

Give a due date window and optionally part of a package title, and it pulls the matching bid packages. For each one it compares invites sent with bids received and gives the response rate, flags packages due in the next seven days with fewer than three bids and packages with no invites, and notes any pre-bid RFI deadline still ahead. You get a table sorted by due date and the packages that need a chaser today. It states the date it used, and never sends or changes anything.

Business outcome

---

Packages at risk of too few bids are named while there is still time to chase, rather than after the deadline.
See Full Use Case

scenario

-

Budget transfers, changes and edit history sit in separate logs in Procore. A finance reviewer cannot easily see what moved, which transfers were large, which changes never synced to the ERP or which budget codes keep being edited.

What popdock provides

--

Give a project name and a start date in the form year, month, day, or leave the date for the last 30 days, and it reads the budget changes, modifications and edit history. It flags the three largest transfers, budget changes whose ERP status is blank or not synced, and budget codes edited more than three times. You get three short sections, changes, transfers and edit history, each with a table, and a paragraph on net movement and anything unusual. It asks for a valid date rather than guessing, reports only returned values and never writes.

Business outcome

---

Large transfers, unsynced changes and repeated edits are visible in one review, so finance can question them before month end.
See Full Use Case

scenario

-

When someone leaves, their workflow assignments are moved in bulk in Procore. The requests, their new assignees and the project areas they cover sit on separate screens, so a request that stopped or ran past its end date is easy to miss. Work stays with a person who is no longer there.

What popdock provides

--

Give a status, which defaults to all, and optionally the person being replaced, and it pulls the bulk workflow replacement requests. For each request it adds the new assignees and the affected project areas. You get a table with the old assignee, new assignees, new workflow manager, areas affected, start date, end date and status, and a list of requests that are stopped or still running past their end date. It is read only and never stops, updates or creates a replacement request.

Business outcome

---

Stopped and overrunning bulk reassignments are listed in one table, so unfinished handovers get chased before work stalls.
See Full Use Case

scenario

-

Finance staff open each Procore commitment one by one to see how much unapproved change sits on it. Draft and pending change orders are spread across contracts, so exposure is missed until the invoices arrive and the balance is already committed.

What popdock provides

--

Give a project name, which defaults to all projects, and optionally a minimum approved change total, and it pulls the commitment contract summary. For the five contracts with the most draft and pending revised change it adds the change orders, noting which are unsigned or past their due date. You get a table of contract number, title, status, approved, draft and pending change totals, invoices and payments, and the five contracts with the most unapproved exposure with a reason each. It reports only returned values, does not total across currencies without saying so, and never writes.

Business outcome

---

The commitments carrying the most unapproved change are ranked in one report, so finance can act before invoices arrive.
See Full Use Case

scenario

-

Procore's company reference lists, departments, work scopes, delivery methods and project templates, collect near duplicates over the years. Departments end up on no project, delivery methods have no description, and names differ only by case or spacing. Filters become confusing and nobody has the time to review each list.

What popdock provides

--

It pulls the company departments, the departments used on projects, work scopes, delivery methods and project templates. It lists departments that are on no project, delivery methods with no description, and names that differ only by case or spacing. You can name a project to narrow the departments in use. You get counts per list, then the unused departments and the near duplicate names. An empty list is reported and the review continues, and every write action is off limits.

Business outcome

---

Unused and near duplicate reference values are found in one pass, so filters stay clear and tidy-ups can be planned with confidence.
See Full Use Case

scenario

-

BIM coordination issues in Procore sit open with no owner, and nobody sees which are blocked, overdue or untouched. Getting a status mix means opening the issue list, then each issue's assignees and change history, and counting by hand.

What popdock provides

--

Name a project and it resolves it, stopping to ask which one if several match. It pulls the coordination issues, their status totals and assignees, then reads the change history to find issues touched in the last 14 days and those with no change since creation. You get the status totals, a table of open issues with number, title, source file, status, due date and days overdue, and lists of blocked, overdue and untouched issues. It says when a read hit its record cap, marks missing values as missing and creates or changes no issue.

Business outcome

---

Blocked, overdue and ownerless coordination issues are listed in one report, so the coordination meeting starts with the real picture.
See Full Use Case

scenario

-

Each Procore project sets its own correspondence type defaults, default statuses and default distribution members. Checking them means opening the settings for each type on each project. A type with no default distribution or no statuses is only found when a message goes to nobody.

What popdock provides

--

Name a project, with the company if you need one, and it finds the one matching project, listing the matches and stopping if more than one appears. It reads the correspondence type defaults, the default statuses and the default distribution members for that project. You get the defaults, statuses and distribution members, with a flag on any project that has no default distribution or no statuses. Empty results are reported as none, and nothing is ever created, edited or removed.

Business outcome

---

Gaps in correspondence defaults are found in one read, so messages reach the right people from the first day.
See Full Use Case

scenario

-

Resource planners in Procore cannot easily see who rolls off a job and when. Availability dates, tags and time off live in separate reports, so people sit idle while the next job is short of crew. Checking a group by hand means cross matching dates for every person.

What popdock provides

--

Name a group, and optionally an as of date that defaults to today, and it reads the group's look-ahead report, each person's job title and tags, and their time off. It compares each person's time off with the date they become available. You get a table of employee number, job title, available after, tags and time off in the next 30 days, sorted by earliest availability and grouped by job title, with how many people are free now and in 14 days. A person with no availability date is listed as unknown, not available, and no assignment is ever edited.

Business outcome

---

Planners see who is free and when, by job title, in one table, so crew is matched to the next job instead of sitting idle.
See Full Use Case

scenario

-

Superintendents skip daily logs, and nobody notices until a dispute needs the record. Checking a project means listing the calendar dates and comparing each one with the logs in Procore, then separating weekends from real misses.

What popdock provides

--

Name a project and a date range, and it resolves the project, asking which one if several match. It pulls the daily log headers for the range and compares them with the calendar. A date with no header is missing, a header with no completed date is incomplete and one with no distributed date is not distributed. You get counts of days with a log, completed, distributed and missing, then the missing and incomplete dates with who completed each. Weekends are listed separately, and no log is ever created.

Business outcome

---

Missing and undistributed daily logs are found in one check, so gaps are closed before a dispute needs the record.
See Full Use Case

scenario

-

Delay claims need a documented record, but Procore delay entries are never totalled by cause or vendor. Adding up durations, matching them against weather and daily notes, and checking the units all happen by hand across several logs.

What popdock provides

--

Name a project and a date range, and it resolves the project and pulls the delay logs with the delay type names. It then reads the notes and weather logs for the same dates to see whether they explain each delay. You get a table of date, vendor, cost code, duration and comments, the total delay grouped by cause and by vendor, and the delays where weather or notes do not match the stated cause. If durations use different units it says so rather than adding them, and no delay entry is ever created.

Business outcome

---

Delay time is totalled by cause and vendor with its context, giving a documented record you can rely on for a claim.
See Full Use Case

scenario

-

Direct costs in Procore are posted outside the contract flow, so there is no commitment to prompt a check. Unpaid entries, entries with no invoice number and line items with no cost code slip through month end because nobody reads them.

What popdock provides

--

Name a project, an optional start date that defaults to 30 days ago and optionally a status, and it reads the matching direct costs. For the five entries with the highest grand total it reads the line items with cost code, cost type, amount and description. It flags entries older than 30 days with no paid date, entries with no invoice number and line items with no cost code. You get totals by status, a table of the largest five with their lines and the flagged entries. It reports only returned amounts and changes no direct cost.

Business outcome

---

Unpaid, unreferenced and uncoded direct costs are found before month end, with no entry changed in Procore.
See Full Use Case

scenario

-

Email distribution groups in Procore go stale. People leave, projects close and groups end up empty, so a notice goes to nobody. Some people sit in a long list of groups, and project groups share a name with a company group but hold different users, and none of this shows without opening each group.

What popdock provides

--

Optionally name a group, a project or both, and it pulls the company and project distribution groups with their users. It flags groups with no users, users in more than five groups and project groups that share a name with a company group but hold different users. You get a table of groups with user counts and then the problems. If nothing returns it says so and stops. The review only reads, and every write action is off limits.

Business outcome

---

Empty and overlapping distribution groups are found in one review, so notices reach someone instead of vanishing.
See Full Use Case

scenario

-

Teams build from stale drawings because nobody can see which sheets have unpublished revisions. Revisions, sets, areas, disciplines and upload status are on different screens in Procore, so working out what is current, superseded or unpublished means a lot of clicking and cross checking.

What popdock provides

--

Name a project, and optionally a discipline, and it resolves the project and pulls the drawing revisions, sets, areas and disciplines. It checks drawing uploads and notes any that are not complete. You get counts by discipline and area, the latest revision per drawing with its date, sets with their unpublished drawing counts, and uploads still processing or failed. Drawings whose latest revision is older than 90 days are flagged. It never publishes or sends a drawing, marks missing values as missing and says when a read hit its record cap.

Business outcome

---

Stale, superseded and unpublished sheets are visible in one register review, so crews build from the right drawings.
See Full Use Case

scenario

-

Equipment coordinators export the Procore equipment register and pivot it by hand to see what is idle, down or assigned. Owned and rented units, status meanings and project assignments all have to be matched, and the answer is out of date by the time it is built.

What popdock provides

--

Optionally name a category and a status, and it reads the company equipment register, the list of statuses with their types and the project assignments. It uses each status type rather than guessing what a status name means, and treats a unit with no project row as unassigned. You get counts by status, by category and by owned or rented, then the units in an out-of-service status and unassigned units with identification number, name, make, model and status. It ends with the three most stretched or idle categories. It notes when a read hit its record cap, and never edits a unit.

Business outcome

---

Fleet status, ownership and the units needing attention are summarised on demand, without exporting and pivoting the register by hand.
See Full Use Case

scenario

-

Failed inspection items are logged in Procore, but nobody checks whether an observation was raised to fix each one. Finding the gaps means opening each inspection, working out which responses count as failing in that project, and searching for a matching observation.

What popdock provides

--

Name a project and a start date that defaults to 30 days ago, and it resolves the project and pulls the inspections created since then. It reads the project's own response set to learn which responses count as failing, then keeps only the items with one of those responses. It checks each failed item for an observation raised against it. You get a table of failed items with inspection, item, response, responder and whether an observation exists, the failures with no observation and the failure count per inspection. Nothing is created, and failure is never assumed.

Business outcome

---

Failed inspection items with no follow-up observation are found in one review, so nothing failed is left unaddressed.
See Full Use Case

scenario

-

Working out what a Procore configurable field set contains means opening its sections, then the custom fields it uses, then the list of projects it applies to. The details sit on several screens, so cross checking by hand is slow, and empty sections or unassigned sets are easy to miss.

What popdock provides

--

Name a field set, and a company if needed, and it finds the one that matches, listing the matches with their id, name and class name and stopping if there is more than one or none. It then reads the set's sections, the custom field definitions it uses and the projects it applies to or is available for. You get the set name and class name, its sections with their fields, the projects it covers and anything unusual such as empty sections or no projects assigned. It never edits or duplicates the set.

Business outcome

---

What a field set holds and where it applies is described in one answer, with empty sections and unused sets called out.
See Full Use Case

scenario

-

Forecast numbers and budget amounts in Procore are compared by exporting both and joining them in a spreadsheet. Manual forecasts add a third source, and lines that appear in a forecast but not in the budget are quietly lost in the join.

What popdock provides

--

Name a project and optionally a forecast to complete threshold, and it reads the budget line items, the advanced forecast rows and the manual forecast line items. It joins forecast rows and manual entries to budget lines and shows each line's original budget, forecast to complete and manual forecast total. You get a table of budget code, original budget, forecast to complete, manual forecast and the difference, with lines that have a forecast but no budget amount listed separately. Forecast rows with no matching budget line are listed as unmatched, not dropped, and nothing is written.

Business outcome

---

Forecast and budget are compared line by line in one table, with unmatched rows listed rather than lost.
See Full Use Case

scenario

-

Photo and form documentation is thin in some areas of a Procore project, and nobody finds out until a claim needs it. Checking means counting forms by template, photos by album and uploader, and looking for deleted forms in the recycle bin.

What popdock provides

--

Name a project and a date range, and it resolves the project, then pulls the forms for the range and the deleted forms. It also reads the photos and their albums, keeping those created in the range. You get forms by template with counts and creators, albums with photo counts and the uploaders with the most photos. Empty albums and forms deleted in the range are flagged. It says when a read hit its record cap, marks missing values as missing, and restores and deletes nothing.

Business outcome

---

Thin photo and form coverage, empty albums and deleted forms are visible before a claim depends on them.
See Full Use Case

scenario

-

Understanding how a custom tool is set up in Procore means opening its statuses on one screen, the statuses it could use on another and its items on a third. Counting items by status and spotting the ones past their due date is done by eye, and a title that matches two tools is easy to open wrongly.

What popdock provides

--

Give the title of a generic tool, and optionally a Procore company, and it finds the one matching tool. If several tools share the title it lists them and stops, and if none match it says so. For the tool it finds, it reports the statuses in use, the statuses available, and a snapshot of its items counted by status with the ones past their due date noted. If there are no items it says so and still lists the statuses. It is read-only and never creates or edits tools, items or statuses.

Business outcome

---

You see how a custom tool is configured and where its items stand in one answer, with nothing in Procore changed.
See Full Use Case

scenario

-

A workforce group in Procore spreads its crew over separate views: the people, their job titles, the tags and the projects the group supports. A planner has to stitch these together by hand to see a crew's real size and status, and inactive people or closed projects are easy to miss.

What popdock provides

--

Give the name of a workforce group and it finds the matching group, asking which one if several match. It then reads the people and their job titles, the tags and the projects the group supports, and puts them into one summary: contact details and timezone, headcount by status, job titles with rates, tags in use, and projects with stage and status. Inactive people and closed projects are flagged. It is read-only, leaves out personal data such as addresses and birth dates, and never edits the group.

Business outcome

---

Planners see a whole crew, its titles, tags and projects, in one summary without personal data repeated or any record changed.
See Full Use Case

scenario

-

A safety manager reviewing a project's incidents opens separate records for injuries, property damage, environmental events, near misses and corrective actions, then matches them by incident number. The incidents with no corrective action at all are the ones that get missed.

What popdock provides

--

Give a project, and optionally an incident status, and it resolves the one matching project, stopping and asking if several match. It then pulls the incidents and adds the injuries, property damage, environmental events, near misses and actions for each by incident number. You get a table of number, title, date, status, location, injuries, damage cost, environmental events and open actions, ranked by open actions and age, with incidents that have no corrective action listed. It reports facts only, speculates about no cause or fault, and is read-only.

Business outcome

---

Safety managers see each incident with its impact and actions in one table, and the ones with no corrective action stand out.
See Full Use Case

scenario

-

To see where a project's inspections stand, a quality manager filters the inspection list by date, works out the type and responsible contractor for each, and counts open and failed ones by hand. Inspections that are open past their date slip through, and daily log inspection entries sit in a separate place.

What popdock provides

--

Give a project and optionally a date range, and it defaults to the last 30 days. It resolves the one matching project, then pulls the inspections created in the range and the inspection entries from daily logs, and names the inspection types. You get a table of number, name, type, responsible contractor, location, date and status, counts by status and by type, the open inspections past their date, and the total of daily log inspection entries. It states the date range used, never changes an inspection and is read-only.

Business outcome

---

Quality managers see open, failed and overdue inspections at a glance for a stated date range, with nothing edited.
See Full Use Case

scenario

-

Site instructions can carry a cost or schedule impact, but the people who must price them may never have been told. Checking means opening each instruction, reading its type and impact, and then finding who it was addressed to and whether it was distributed at all.

What popdock provides

--

Give a project and optionally a minimum cost impact, which defaults to 0. It resolves the one matching project, pulls the instructions at or above that cost impact with their types, then adds who each was addressed to and its distribution members. You get a table of number, title, type, from, status, cost and schedule impact status and addressed to, a list of instructions with an impact and no distribution, and the total cost impact where a value is present. It is read-only and sends and creates nothing.

Business outcome

---

Project managers see which impactful instructions reached nobody, with cost impact totalled, and nothing is sent or created.
See Full Use Case

scenario

-

Before a payment run, accounts payable checks each invoice for manual holds, whether the lien waiver has arrived and whether compliance documents are approved. Each check lives somewhere different, so an invoice gets paid when one blocker was never looked at.

What popdock provides

--

Give a project and optionally an invoice status, and it defaults to anything not yet paid. It reads the invoices with their vendor, amount claimed and payment due, then matches the active manual holds, the lien waivers not yet received and the compliance documents not yet approved, on invoice number only. You get a table with a Blocked by column, blocked invoices first by amount due, and counts of ready and blocked. An invoice is ready only if nothing matched its number. It releases no holds, approves nothing and is read-only.

Business outcome

---

Accounts payable sees which invoices are ready and exactly what blocks the rest, before the payment run starts.
See Full Use Case

scenario

-

Late deliveries are usually found when a crew is waiting for material, because the shipment log is never compared with the receipts. Working it out means checking each shipment's estimated date, what is still on it against the purchase order lines, and whether a receipt was started.

What popdock provides

--

Give a project and optionally an as-of date, which defaults to today. It reads shipments whose estimated delivery is before that date and are not delivered or closed, then their line items and linked purchase order lines to see the quantity remaining, and checks whether a receipt has been started for each purchase order. You get a table ranked by days late with line count, remaining quantity and receipt started, and the shipments to call about first. It is read-only, never edits a shipment and keeps shipments with no delivery date separate.

Business outcome

---

Buyers learn which deliveries are late and what is still undelivered before the crew is left waiting.
See Full Use Case

scenario

-

Manpower, work hours, productivity and quantity logs are recorded separately in Procore, so nobody checks whether the labor on site lines up with the work reported. Comparing them by vendor means pulling four logs for a period and matching names by hand.

What popdock provides

--

Give a project, a date range and optionally a vendor. It resolves the one matching project, pulls the manpower, work, productivity and quantity logs for the range and the daily manpower totals, and keeps only that vendor if you named one. You get a table by vendor of log days, workers or hours, productivity entries and quantities, the busiest and quietest dates, and vendors that appear in work logs but not in manpower logs. Vendors are matched on the exact names returned. It is read-only and edits no log.

Business outcome

---

Operations teams see whether labor lines up with reported work for each vendor, and the vendors missing from manpower logs stand out.
See Full Use Case

scenario

-

Deleted materials in Procore are usually only noticed when a report stops working, and the recycle bin does not make it obvious who did it or whether the same name has since been recreated. Checking means reading the bin for a window and then searching for each name again.

What popdock provides

--

Give a project and optionally how many days back to look, which defaults to 30. It reads the materials recycle bin for that window, scoped to the project, then checks each recycled name to see whether a record with the same name exists again. You get a table of name, resource type, subtype, date created, date recycled and recycled by, with whether a same-named record is live, a count by user and a flag on anyone who recycled more than ten records. It is read-only, never restores or purges anything and only lists what could be restored.

Business outcome

---

You see what was recycled, who did it and what is still missing, and the decision to restore stays with you.
See Full Use Case

scenario

-

Foremen often learn about missing material on the day of the install, because requirements, stock and open orders sit in different views. Working out the real gap means comparing required, available and ordered quantities line by line, then checking stock and what is in transit.

What popdock provides

--

Give a project and optionally an availability percentage, which defaults to 100. It reads the material requirements below that availability and their lines, comparing quantity required, available and ordered to size each gap, then checks on-hand, in-transit and left-to-receive stock for each short item. You get a table ranked by earliest date required, then gap, with items that have a gap and nothing ordered flagged as unplanned shortages and the three items to order or expedite first. Gaps use only returned quantities. It is read-only and places or changes no order.

Business outcome

---

Foremen see which materials will run short and which have nothing on order, days before the install date.
See Full Use Case

scenario

-

Stock counts are re-keyed into spreadsheets, so a project does not see damaged or in-transit quantities until material runs out. Getting a real position means reading each material's availability, finding where it sits and checking recent movement.

What popdock provides

--

Give a project and optionally part of a material name. It reads the project's materials, looks up the locations of the top ten items by quantity on hand and reads the change history for items with the largest damaged or in-transit quantities. You get a table of available, damaged, in transit, issued, left to receive and ordered quantities, with flags on damaged stock, zero available with quantity left to receive, and large issued quantities against little available. Missing quantities are marked missing. It is read-only and never edits stock.

Business outcome

---

Stock problems such as damaged, depleted or over-issued items are visible before the project runs out of material.
See Full Use Case

scenario

-

Action items from owner, architect and contractor meetings get buried in the minutes, and nobody keeps a running list of who owes what. Finding them means opening each meeting, reading its topics and assignments and checking attendance.

What popdock provides

--

Give a project and a date range. It resolves the one matching project, reads the meetings in the range, then their topics, assignments, parent minutes and attendees. You get a table of meeting, topic number, title, due date, status and assigned to, with open items ranked by due date, items past due listed and attendance counts per meeting. Minutes are quoted only when Procore returned them. It is read-only and creates no topics.

Business outcome

---

Project managers get a list of open meeting action items by owner, with overdue ones highlighted, without rereading minutes.
See Full Use Case

scenario

-

Observations raised in the field pile up in Procore with no owner, and nobody sees which are past due. Reading the backlog means opening the observations, working out which statuses count as open, then checking who is assigned and whether anyone has responded.

What popdock provides

--

Give a project and optionally an as-of date, which defaults to today. It resolves the one matching project, reads the observations, the status values that project uses and the observation types, then checks the assignees and the response logs. You get a table of number, name, category, assignee, vendor, status, due date, days overdue and responded, with open items counted by assignee and category, and overdue observations with no response and those with no assignee listed. It uses the project's own statuses, flags unassigned items rather than assigning them, and is read-only.

Business outcome

---

Operations teams see the open observation backlog by owner and age, and unassigned or unanswered items stand out.
See Full Use Case

scenario

-

Office and trade lists in Procore are rarely reviewed, so a missing state or country code or two trades spelled slightly differently can sit there for years. Spotting them means scrolling each list and comparing names by eye.

What popdock provides

--

Name a Procore company if you want one, and it reads the offices and the trades. It reports offices missing a state or country code and trades whose names differ only by case or punctuation, with counts for each list and clean-up suggestions. Empty lists are reported as empty. It is read-only and only recommends, so nothing is created, changed or merged.

Business outcome

---

Office and trade lists get a short clean-up list of gaps and likely duplicates, without anything changed in Procore.
See Full Use Case

scenario

-

Damaged deliveries are logged in Procore but rarely chased, so vendor credits are missed and the same vendor keeps shipping bad stock. Finding the unresolved ones means reading each defect, its lines and its history, then counting by vendor.

What popdock provides

--

Give a project and optionally a defect status. It reads the project's defects, skipping resolved or closed ones unless you ask for a status, then their lines with condition, quantity and resolution decision and the purchase order and receipt each came from, and the change history. You get a table by vendor with open defect counts, and unresolved defects with no change in 14 days listed as stalled. It is read-only and never changes a defect or its resolution.

Business outcome

---

Buyers see which defects are unresolved or stalled and which vendors cause most of them, so credits get chased.
See Full Use Case

scenario

-

Buyers read the purchase order log line by line to find what has not arrived, and vendors who keep slipping stay invisible. Late lines, outstanding quantities and vendors live in separate views, and lines with no delivery date get lost.

What popdock provides

--

Give a project and optionally an as-of date, which defaults to today. It reads the open purchase orders, skipping closed or cancelled ones, then the lines due on or before that date with quantity outstanding, shipped and received, and the vendors. You get a table of purchase order, vendor, status, contract delivery date, days late, lines outstanding and quantity outstanding, ranked by days late, with the vendors who have the most late lines and the three purchase orders to chase first. Lines with no delivery date go in their own list, and it notes when a read hit its record cap. It is read-only.

Business outcome

---

Buyers see which purchase orders and vendors are slipping and which three to chase first, without guessing missing dates.
See Full Use Case

scenario

-

Project managers scroll the RFI log by hand to find what is late and who is holding it, and the RFIs with a cost or schedule impact are the easiest to miss. Ball in court and reply status live on other screens, and an RFI with no due date drops out of the count.

What popdock provides

--

Give a project and optionally an as-of date, which defaults to today. It resolves the one matching project, reads the RFIs due by that date and the full count, skipping closed and draft ones for ranking, then adds the ball in court and replies, so an RFI with a reply is treated as waiting on acceptance. You get a table of number, subject, contractor, due date, days overdue, status, ball in court and replied, ranked by days overdue with cost and schedule impact flagged, the three RFIs to chase first and overdue against total open. RFIs with no due date are listed separately, and it is read-only.

Business outcome

---

Project managers see which RFIs are overdue, who is holding each and which three to chase first.
See Full Use Case

scenario

-

People and vendor records in Procore drift apart. A person with no vendor and no employee ID, or the same name in both active and inactive lists, is found only when someone happens to search for it.

What popdock provides

--

Give a name, and optionally a vendor, and it reads the active people and the inactive people matching them. It flags active people with no vendor and no employee ID, people who are not Procore users and have no contact, names that appear more than once across the lists, and inactive people whose name is also active. You get counts of active and inactive people and each problem group with the vendor and ids. Duplicates are marked possible only, when the full name matches. It is read-only and every write is off limits.

Business outcome

---

Operations teams get a short list of unlinked and possibly duplicated people to fix, without any record changed.
See Full Use Case

scenario

-

A foreman asking where someone is booked has to open assignments, time off and project history in three places, and still can miss a clash between a booking and a day off. Dates have to be compared by hand.

What popdock provides

--

Give an employee number and optionally a project. It finds the person's name and job title, reads their current and upcoming assignments, their time off and their past project history, keeping only history for the project if you named one. You get a chronological table of assignments, time off and past project hours, with any overlap between time off and an assignment flagged. If a start or end day is missing it says the overlap cannot be checked, and it stops if the employee number matches nobody. It leaves out personal data such as addresses and birth dates, and is read-only.

Business outcome

---

Foremen see a person's assignments, time off and history together, and clashes between time off and bookings are flagged.
See Full Use Case

scenario

-

Finding out what was said on a project means searching project emails, communication threads and call logs separately. The topics with many emails and no reply from the responsible party are the ones that matter, and they are easy to miss.

What popdock provides

--

Give a project, a date range and optionally subject text. It resolves the one matching project, reads the project emails sent in the range, the communication threads and the call logs for the dates. You get emails grouped by topic type with sender and sent date, the threads with the most messages, call logs by vendor, and topics with many emails and no reply from the responsible party highlighted. It quotes only fields Procore returned, sends no email and is read-only.

Business outcome

---

Project managers see what was said, by whom and where a topic stalled, without searching three places.
See Full Use Case

scenario

-

Project document folders fill up with untagged files, and empty or misplaced folders are found only when someone goes searching. Checking by hand means walking the folder tree, opening documents to see their tags and watching for recent changes.

What popdock provides

--

Give a project and optionally a document type. It reads the project's folders, its documents and its custom tags. It flags folders with no documents, documents with no custom tag, documents changed in the last 14 days and folders with a missing parent. You get counts of folders and documents by type, the problem groups with names and the most recently updated documents. It is read-only and every write is off limits, so no folder or file is changed, and it stops if the project has no documents.

Business outcome

---

Document managers get a list of empty folders, untagged files and recent changes to tidy, with no file or folder touched.
See Full Use Case

scenario

-

Getting a project level view of earned versus actual hours means adding up dozens of cost code rows by hand. Overall efficiency, the weakest cost codes and the ones with the most hours left are not visible in the report itself.

What popdock provides

--

Give a project number and optionally a minimum number of budgeted hours, which defaults to 0. It reads the project's field production rows and totals budgeted, actual, earned, remaining and projected hours at completion. Overall efficiency is earned hours divided by actual hours, and it names the three cost codes with the lowest efficiency and the three with the most remaining hours, then gives a one paragraph verdict of ahead, on plan or behind. Zero or blank values are excluded from ratios, figures are quoted as returned, and it stops with the filters used if no rows come back. It is read-only.

Business outcome

---

Project managers get a project's earned hours, efficiency and weakest cost codes with a verdict, without adding up rows.
See Full Use Case

scenario

-

Superintendents often do not know which machines are really on their job, which are down and which rentals are about to expire. The register, the maintenance records and the rental dates are in different places, and units with no service record go unnoticed.

What popdock provides

--

Give a project and optionally an equipment status. It reads the equipment assigned to the project, its maintenance records and the rental dates, comparing them with today and checking company rental end dates within 30 days if needed. You get a table of identification number, name, category, status, ownership, rental end date and last maintenance date, then units out of service, rentals ending in 30 days and units with no maintenance record, with a one line risk summary. If the project name matches nothing it says so and stops. It is read-only and never edits equipment.

Business outcome

---

Superintendents see which machines are down, which rentals expire soon and which have no service record before it costs them.
See Full Use Case

scenario

-

Leadership scrolls the Procore project list by eye to see what is active and which projects are missing key fields. Totals by stage and type have to be added up by hand, and incomplete records stay hidden among the rest.

What popdock provides

--

Name a project, or leave it open for all projects, and optionally a project type. It reads the matching projects, groups them by stage and then project type with a count and the total and estimated value for each group, and flags active projects with no number, no actual start date, no state or city or a total value of zero, and stages that look inconsistent with their dates. You get a table of stage groups, the flagged projects with the reason for each and the largest project by total value. Values in different regions or currencies are not totalled without saying so, and every write is off limits.

Business outcome

---

Leadership sees the portfolio by stage and type with values, and the incomplete project records that need fixing.
See Full Use Case

scenario

-

Someone deletes an RFI, submittal or punch item by mistake, and nobody notices until the log numbers do not add up. Finding it means reading three recycle bins and checking each deleted record against the live log.

What popdock provides

--

Give a project. It resolves the one matching project, reads the recycle bins for RFIs, submittals and punch items, then for each deleted record checks whether a live record with the same number or title exists. You get a table per record type with number, title or subject, status, date created, created by and whether a live record with the same number exists. Deleted records with no live twin, especially open ones, are flagged as likely mistakes. It is read-only, restores nothing and only recommends a restore.

Business outcome

---

Project managers find mistakenly deleted RFIs, submittals and punch items before the log gaps cause trouble, and decide any restore themselves.
See Full Use Case

scenario

-

Checking a Procore project's role assignments against the company role list means opening the company roles, then the project's roles, and comparing the two by eye. Key roles stay empty, or carry a name the company no longer uses, and nobody notices until a notification has nowhere to go.

What popdock provides

--

Name a project and optionally the Procore company, and it reads the company's roles and the project's role assignments. It matches them by role name, then reports roles nobody fills, assignments under a name the company does not define, and roles with more than one assignee. Roles of different type that share a name are kept separate and called out. It stops if the project name matches more than one project, and it never creates, updates or deletes a role.

Business outcome

---

You see which project roles are empty, unknown or doubled up in one report, and nothing in Procore is changed.
See Full Use Case

scenario

-

To see who is on a Procore job, what the project has asked for and what is still open, a project manager has to ask the resource planner or dig through assignment history, resource requests and group attachments one screen at a time. Gaps in staffing show up on site, not on paper.

What popdock provides

--

Name a project and it finds it in Procore workforce planning, then reads who has worked it, the open resource requests and the groups attached to it. You get the project's stage and status, a list of people with job title and dates, the open requests with percent allocated, and the requests starting within 14 days. If the project has no workforce record it says so, and it never assumes the job is fully staffed. It reads only and changes nothing.

Business outcome

---

Project managers see the whole staffing picture themselves, with open requests flagged, instead of waiting on the resource planner.
See Full Use Case

scenario

-

Knowing who is on a Procore project and whether they are covered means opening the vendor list, the trades and the insurance screens separately, then lining them up by hand. Vendors with no trade or no insurance on file slip through, and removed vendors are forgotten.

What popdock provides

--

Name a project and it finds the one matching project, then reads its vendors, their trades, their insurance status and expiry dates, and the vendors removed from the project. You get a single roster, plus lists of vendors with no trade, vendors with no insurance record and a count of inactive vendors. If the name matches more than one project it stops and lists them. It reports only returned rows and changes nothing.

Business outcome

---

One roster shows every vendor, trade and insurance status on the project, so coverage gaps are visible before work is awarded or paid.
See Full Use Case

scenario

-

Cost impacts on punch items sit on individual items, so the money at stake in close-out is never added up. Someone filters the punch list, exports it, groups by category in a spreadsheet and still has to decide what to do about items with no amount recorded.

What popdock provides

--

Name a project and optionally a minimum amount, and it finds the one matching project, then reads the punch items that carry a cost impact. It totals them by category with item counts and the largest item in each, lists the ten biggest items with status and assignee, and states the grand total. Items with no amount recorded are counted separately, never estimated. It stops if the project is ambiguous or unresolved, and changes nothing.

Business outcome

---

Close-out cost exposure from punch items is added up by category before it turns into a billing surprise.
See Full Use Case

scenario

-

When close-out stalls, the question is which trade is sitting on the oldest punch items. Answering it means pulling the punch list, working out days open and days overdue from the dates, and matching each item to the vendor holding it, usually in a spreadsheet.

What popdock provides

--

Name a project and optionally an as-of date, and it finds the one matching project and reads its punch items with their assignments and who holds the ball. It works out days open and days overdue for every open item, groups them by vendor with a count each, ranks vendors by overdue items and lists the ten oldest open items with an open versus closed count. Missing dates are marked as missing. It never changes an item.

Business outcome

---

You can tell which vendor is holding up close-out and which punch items are oldest, from one report, with no item touched.
See Full Use Case

scenario

-

Rental returns are often tracked in a spreadsheet kept apart from the equipment register, so a unit can roll past its end date and keep billing. Finding what ends soon means filtering the register by date, checking which project holds each unit and whether maintenance is open.

What popdock provides

--

Give a look-ahead window in days and optionally a start date, and it reads rented equipment whose rental ends in that window. It shows which project holds each unit and whether it has open maintenance, sorted by end date with days remaining and the total hourly rate where one is returned. Units already past their end date are listed separately at the top, not folded into the window. It never extends or returns a rental.

Business outcome

---

Rentals are extended or returned before they overrun, and units already late are visible at the top of the report.
See Full Use Case

scenario

-

When a subcontractor invoice amount changes, finding out why means digging through the requisition's change log and then the schedule of values to see which billed items moved. The log shows user ids, not names, and a change after approval is easy to miss.

What popdock provides

--

Give an invoice number and a project, and it finds the one matching requisition, then reads its change history and billed items. You get a timeline of status and claimed amount changes with dates and the user id behind each action, then a table of billed items with scheduled value, balance to finish and stored material. It notes any claimed amount that changed after approval. It never guesses user names and changes no requisition.

Business outcome

---

You can explain why an invoice amount changed, and spot post-approval edits, without trawling through change logs.
See Full Use Case

scenario

-

Resource requests accumulate in a queue, and the group that has to supply the people finds out late that it cannot cover them. Working it out means listing the upcoming requests, finding each project, then checking the group's look-ahead to see who is actually free by the start date.

What popdock provides

--

Give a start date and optionally a group, and it reads the resource requests starting on or after that date, adds the project for each and checks how many people in the group become free before it starts. You get a table ranked by start day with percent allocated, work scope and people available, and requests starting within 14 days with too few people are flagged. When headcount needed is not returned it shows availability only and never claims a shortfall. It edits no request.

Business outcome

---

Planners see which upcoming requests the group cannot cover while there is still time to find people.
See Full Use Case

scenario

-

Reviewing how roles are set up in Procore usually happens one role at a time, so two roles that differ only by a capital letter or a trailing number go unnoticed. Roles of the wrong type and gaps in the ordering pile up until someone asks why the list looks odd.

What popdock provides

--

Optionally name a company and a word the role names must contain, and it reads the company's roles with their type and position. It groups them by type, flags roles whose names differ only by case, spacing or a trailing number, and flags gaps or repeats in the ordering. You get a table of role, type, position and finding, then recommended clean-ups. The recommendations are advice only, and it never creates, edits, reorders or deletes a role.

Business outcome

---

Admins get a clean-up list for the role setup in one pass, with every change left for them to make.
See Full Use Case

scenario

-

Safety violations, accidents, incidents and near misses are logged in separate places, so the full picture of a project's record is never seen at once. Pulling it together for a date range means opening each log, filtering by date and working out which items are still open or past their compliance date.

What popdock provides

--

Name a project and a date range, and it finds the one matching project, then reads the safety violation and accident logs for that range, plus incidents, near misses and injuries created in it. You get counts by type and a table with date, type, company, status and compliance due date, with violations past due and open incidents listed first. It reports facts only, never assigns fault, says a trend only when the data supports it and creates no records.

Business outcome

---

You see a project's whole safety record for a period in one factual report, with overdue compliance items first.
See Full Use Case

scenario

-

Procore schedules go stale when updates are not loaded, and requested changes stack up waiting for review. Checking means opening the schedule, the import status, the requested changes, the lookaheads and the tasks separately, then judging how old the data is.

What popdock provides

--

Name a project and it finds the one matching project, then reads its schedule, schedule import status, requested changes, lookaheads and tasks. You get the schedule's data date and how stale it is, the import status, pending requested changes with old and new start and finish dates, the lookaheads with date range and status, and the tasks with the worst variance. A data date older than 30 days is flagged. It never approves a change, imports a schedule or infers a critical path.

Business outcome

---

You see how current the schedule is and what is waiting for review, without approving or importing anything.
See Full Use Case

scenario

-

Specification uploads sit unreviewed while the team keeps working from older sections. Checking the register means looking through sections by division, comparing issue dates to the newest set and hunting for uploads nobody has reviewed.

What popdock provides

--

Name a project and optionally a division number, and it finds the one matching project, then reads its specification sections, sets, areas and uploads, including the unreviewed ones. You get sections by division with revision and issued date, sets with section counts, and a list of unreviewed uploads with file name and age. Sections issued before the newest set are flagged. It never publishes or deletes a specification.

Business outcome

---

Unreviewed uploads and out-of-date sections are found before the team builds from the wrong specification.
See Full Use Case

scenario

-

Workflows in Procore stall when an approval sits with one person, and the overdue ones run quietly. Finding them means opening each workflow instance to see its state, who holds it and how long it has been there.

What popdock provides

--

Give a project name and optionally a number of days, and it reads workflow instances on matching projects with their current state, who holds the ball and the pending activity and role. It classes instances as overdue when the overdue date has passed and as stale when the state has not changed within the window, 14 days by default, and leaves out terminated ones. You get a table grouped by who holds it. It never responds to, restarts, refreshes or terminates a workflow.

Business outcome

---

You see which workflows are overdue or stuck and who is holding each one, without touching any of them.
See Full Use Case

scenario

-

Submittal logs show a status per item but hide which ones are stuck with an approver and which keep bouncing through revisions. Finding the late ones means checking due dates by hand, looking up who holds each submittal and counting revisions.

What popdock provides

--

Name a project and optionally an as-of date, and it finds the one matching project, then reads its submittals, revisions, ball in court and approvers. It compares each due date with the as-of date, ranks submittals by days late and calls out those with three or more revisions and those where an approver has not responded. Submittals with no due date are listed separately. It uses the returned status fields only and never infers a status from a title.

Business outcome

---

Late and stuck submittals are ranked with who is holding each, so reviewers are chased before the schedule takes the hit.
See Full Use Case

scenario

-

Managers count tasks per person by hand, so uneven workloads are noticed only after something slips. Counting means filtering the task list by assignee and status, then checking who can be assigned work but holds none.

What popdock provides

--

Name a project and it reads the task items, the people who can be assigned, the people who currently hold tasks and the default distribution list. It counts tasks per assignee by status, finds assignees with more than twice the average open tasks, people who could take work but hold none, and distribution members who are not assignees. You get a table of open, overdue and total counts per person. It counts only returned rows and changes nothing.

Business outcome

---

Uneven task loads show up in one table, so work can be rebalanced before something slips.
See Full Use Case

scenario

-

Time and material tickets go unsigned or arrive without timecards, equipment or materials behind them, and the money is disputed when it is billed. Finding them means checking each entry's signatures and its supporting records one at a time.

What popdock provides

--

Name a project and optionally a status, and it finds the one matching project, then reads its time and material entries with their signatures, timecards, equipment logs and materials. You get a table with number, status, work date, who signed, timecard hours, equipment quantity and material lines, then lists entries with no customer signature and entries with no timecard, equipment or material support. It reports only what comes back, sends no emails and creates no entries.

Business outcome

---

Unsigned and unsupported T&M tickets are found before billing, when they are still easy to fix.
See Full Use Case

scenario

-

Time off is often approved without checking it against the jobs people are booked on, so a crew is short on the day. Finding the clashes means comparing each person's time off with their assignment dates, matched on employee number, group by group.

What popdock provides

--

Give a window with start and end dates and optionally a group, and it reads time off that overlaps the window and the group assignments with their dates. It matches them on employee number and reports, for each person, the time off dates, the assignment project and dates, the days overlapping and whether the time off is paid. Recurring time off is listed separately. If a date is missing it asks, and when nothing overlaps it reports how many people and assignments it checked.

Business outcome

---

Planners see which approved time off lands on booked assignments before the crew is short on the day.
See Full Use Case

scenario

-

Timecard defaults are spread across several settings screens, so payroll leads rarely check that start, stop and lunch times agree with the company's timesheet type. A stop time before a start time or lunch tracking with no default lunch goes unnoticed until timecards look wrong.

What popdock provides

--

Optionally name a Procore company, and it reads the company configuration and the default start, stop and lunch times along with lunch time tracking. You get a table of each setting and its value, with flags for a stop time before the start time, lunch tracking switched on with no default lunch time, and a missing cost type when timesheets are enabled. An empty record is reported as not set, never assumed. It never changes a default.

Business outcome

---

Payroll leads see every timecard default side by side with inconsistencies flagged, with nothing changed.
See Full Use Case

scenario

-

Timecards reach payroll with no cost code, in draft or edited after approval, and nobody sees it until the labour cost report looks wrong. Spotting them means opening timesheets by status, scanning entries for blank cost codes and reading the change history for edits.

What popdock provides

--

Name a project and optionally a timesheet status, and it finds the one matching project, then reads its timesheets, timecard entries, time types and recent edit history. You get timesheets by status, entries by cost code and crew with hours, and findings for entries with no cost code, timesheets still in draft and entries edited after approval. It reports only what comes back, and it approves and edits nothing.

Business outcome

---

Missing cost codes, drafts and post-approval edits are found before payroll and cost reports rely on the data.
See Full Use Case

scenario

-

Transfers between locations and between projects get started and never finished, so stock shows in two places or none. Tracking them down means reading transfers and inter-project transfers, their lines and their change history, then working out which have gone quiet.

What popdock provides

--

Name a project and optionally a state, and it reads the transfers and inter-project transfers that are not complete, with their line items and change history. You get two tables with name, state, status, creator, days open, line count and total quantity. Any open transfer with no activity in 14 days is marked stalled, and the items most often moved are listed. If the project name matches no records it stops. It reports only returned values and never completes or edits a transfer.

Business outcome

---

Half-finished transfers surface with how long they have been open, so stock is not left double counted or missing.
See Full Use Case

scenario

-

Receipts sit unposted, so invoices cannot be matched and payables are held up, and nobody sees the backlog. Finding it means listing receipts, comparing the received date with the posted date for each, and checking the lines on the ones not yet posted.

What popdock provides

--

Name a project and optionally a number of days and a start date, and it reads the receipts created since then and compares received and posted dates. A receipt received but never posted counts as unposted, and a gap above your limit, 7 days by default, counts as late. For unposted receipts it reads the lines for status and quantity expected. You get a table with unposted first, then late, and the total quantity sitting in unposted receipts. It never posts or edits a receipt.

Business outcome

---

The unposted receipt backlog is visible with the quantity affected, so invoices can be matched and payables released.
See Full Use Case

scenario

-

Cleaning up the Procore user directory means reading hundreds of user rows, and missing permission templates and contact details go unnoticed. A user with no template, or one pointing at a template that no longer exists, can sit in the directory for months.

What popdock provides

--

Optionally name a user or part of a name, and it reads the active company users and the company's permission templates. It checks each user for a missing permission template, a missing email address, no business phone and no job title, and for a template that is not in the template list. You get counts of users by template, a list of users with gaps and which fields are missing, and the number of complete records. It reports only returned fields and never changes a user.

Business outcome

---

Admins get a short list of incomplete user records to fix, instead of reading the whole directory.
See Full Use Case

scenario

-

Before inviting a vendor to bid again, someone searches each project for their past bids and contacts. Bids filed under a slightly different company name get missed, and nobody is sure which contacts the vendor has on file.

What popdock provides

--

Name a vendor and optionally a date the bids must be created on or after, and it reads the vendor's bids and the contacts on file for them. You get the number of bids and the projects, the lowest, highest and average lump sum where the amounts are returned, the contacts and their permission templates, and projects where the vendor bid but has no contact on file. If the name matches several vendors it asks which one. It never states a win rate, since the data does not say who won, and it changes nothing.

Business outcome

---

You see a vendor's full bid and contact history before inviting them again, without searching project by project.
See Full Use Case

scenario

-

Vendor feedback is spread across individual records, so poor performers are not visible when new work is awarded. Seeing a pattern means opening each vendor's comments, averaging the ratings and checking attachments, one vendor at a time.

What popdock provides

--

Optionally name a vendor or part of a name, and it reads vendor comments with their ratings and attachments. It averages each vendor's ratings, counts comments, flags vendors whose latest rating is below their average and those rated 2 or below on a 5 point scale, stating the scale it saw, and notes comments with attachments. You get a table with rating count, average and latest rating, and a list of vendors needing attention with the latest comment date. It quotes only returned text and changes nothing.

Business outcome

---

Poor performers and declining ratings are visible across all vendors before new work is awarded.
See Full Use Case

scenario

-

A Procore webhook hook can have triggers on resources or events that do not exist, so it silently never fires. Checking one means finding the hook, listing its triggers and comparing each against the catalog of supported resources and events.

What popdock provides

--

Give a hook id, and a project if it is a project hook, and it finds the hook and its triggers, then loads the matching catalog of resources and events. It reports triggers whose resource or event is not in the catalog and so will never fire, duplicate triggers, and resources in the same area as the hook's triggers that have no trigger, labelled as suggestions only. A hook with no triggers is reported as one that can never fire, with candidate resources listed. It never creates, edits or deletes a hook or trigger.

Business outcome

---

Webhook triggers that can never fire are found and explained, with every fix left for the developer to make.
See Full Use Case

scenario

-

Work classifications are kept at company level and again on each project, and the two drift apart. Nobody compares them until a timecard fails because the classification is missing or inactive on the project.

What popdock provides

--

Give a project name and it reads the company's work classifications, then the classifications set up on the matching project. It reports which company classifications are missing from the project and which project classifications have no company equivalent. If the name matches more than one project it lists them and stops for you to choose. Nothing is changed, and the classification write actions are off limits.

Business outcome

---

Classification gaps are found before a timecard fails, with no risk of changing a setup you only meant to check.
See Full Use Case

scenario

-

Procore workflows each need a manager and a pool of people who can be assigned. Admins have no single view of which workflows have no manager, or which people are managing so many that a holiday stalls the lot.

What popdock provides

--

Name a workflow, or leave it blank for all, and optionally a project. It pulls the workflow managers and the possible assignees at company level and, when you name a project, at project level. It flags workflows with no manager, managers who are not also possible assignees and people managing more than five workflows. It reports only what Procore returns, and no assignments are changed.

Business outcome

---

Workflows without a manager and over-reliance on one person are visible in one report, with no assignments touched.
See Full Use Case

scenario

-

Open change orders sit on four separate screens: potential, commitment, prime and requests. A project manager chasing them has to add them up by hand, and the large or overdue ones are easy to miss.

What popdock provides

--

Name a project and optionally a status. It collects the potential, commitment and prime change orders and the change order requests, drops approved and executed ones unless you ask otherwise, and ranks the rest by amount. Items past their due date are flagged overdue and items with no due date are flagged instead of guessed. It reports one table per type with the open total and the three items to deal with first. Nothing is written.

Business outcome

---

Open change orders are ranked in one report, so the large and overdue ones get attention first.
See Full Use Case

scenario

-

Commitment change orders stall because it is unclear who should nudge the vendor. The orders sit in the financials list and the people sit in another list, so someone matches vendors to contacts and to an internal owner by hand.

What popdock provides

--

Name a project and optionally a status, and it lists the commitment change orders in that status, pending or draft by default. It reads the project's users and its people directory, then pairs each order with the vendor's own contact and the internal person to chase, chosen from job titles. It shows a missing contact as not found and will not name an internal owner it cannot justify. It only reads and creates no tasks.

Business outcome

---

Each stalled change order has a named vendor contact and a justified internal owner, with no guesswork.
See Full Use Case

scenario

-

Setting up a project meeting in Procore means creating the meeting, then typing each agenda topic one at a time. It is easy to clash with a meeting already booked that day, or to leave a topic out.

What popdock provides

--

Give a meeting title, a project, a date and the agenda topics, one per line. It resolves the one matching project, checks that day's meetings for a similar title and asks whether to continue if one exists. You see the exact values and nothing is created until you confirm. It then creates the meeting and each listed topic, and reads the topics back to verify them. It never distributes the meeting or adds attendees.

Business outcome

---

Meetings are created once with the full agenda, checked for clashes first and verified afterwards.
See Full Use Case

scenario

-

Setting up a Procore company webhook by hand means getting the namespace, resource and event names exactly right, then adding a trigger for each event. A typo gives you a hook that never fires, and an existing hook for the same URL is easy to duplicate.

What popdock provides

--

Give the namespace, destination URL, resource and optionally the events, otherwise all events the catalog lists for that resource. It validates the resource and every event against Procore's webhook catalog, and lists valid values if one is wrong. It checks for a hook already using the URL, warns on http and shows the exact hook and triggers. Nothing is created until you confirm. It then creates the hook, one trigger per event and reads them back, and stops on the first failure.

Business outcome

---

A company webhook is created once, with valid events, no duplicate hook and a read-back of what exists.
See Full Use Case

scenario

-

A webhook on a single Procore project needs the project, resource and event names to line up. Set one up by hand and it is easy to pick an event the project does not offer, or to add a second hook for a URL that already receives events.

What popdock provides

--

Give a project, the namespace, a destination URL and a resource, and optionally narrow the events. It checks the resource and events against that project's webhook catalog and stops with the valid values if they do not match. It looks for an existing hook using the same URL and asks whether to reuse it. You see the hook and triggers and nothing is created until you confirm. It only creates, never updates or deletes, and stops on the first failure.

Business outcome

---

A project webhook starts with valid events and no duplicate, created only after you have approved it.
See Full Use Case

scenario

-

Checking margin on a project means setting prime contract billing against what you have committed to subcontractors and suppliers. Prime contracts, purchase orders and work orders sit on separate screens, so the totals are copied across by hand.

What popdock provides

--

Name a project and optionally a minimum contract value. It reads the prime contracts, purchase order contracts and work order contracts and shows the revised amount, invoiced, payments, remaining balance and draft change orders for each. It works out percent invoiced, shows n/a where the revised amount is zero and flags contracts over 100 percent invoiced or with large draft change orders. It ends with project totals, and changes no contract.

Business outcome

---

Prime billing and commitment balances sit side by side, so margin and overbilling questions are answered in one pass.
See Full Use Case

scenario

-

To reconstruct one day on site you open weather, manpower, equipment, deliveries, visitors, delays, safety and notes logs one by one. It takes a dozen screens, and a log with no entries is easy to mistake for one you forgot to check.

What popdock provides

--

Give a project and a date. It resolves the one matching project and reads each daily log type for that date, plus the log header and the day's manpower totals. It writes a single brief with weather, workers and man hours, equipment, deliveries, visitors, delays and their cause, safety violations, accidents and notes. Empty log types are reported as none logged, nothing is invented, and it says when a call hit its record cap.

Business outcome

---

The day on site is one short brief, with empty logs stated plainly instead of left blank or guessed.
See Full Use Case

scenario

-

Leaders who want to know where overdue work is piling up end up asking each project manager. The answers arrive late, in different formats, and nobody can compare projects on the same basis.

What popdock provides

--

Optionally name a project or part of a name, otherwise it covers all of them. It pulls open item counts for your own items and for all the items you can see, then ranks projects by overdue count, showing open and upcoming counts and last activity. It flags projects with open work but no activity in 30 days and compares your share to the total. Counts follow your Procore permissions, and nothing is changed.

Business outcome

---

Overdue work is ranked across projects on one basis, so leaders see where to step in without chasing updates.
See Full Use Case

scenario

-

Answering where RFI 12 stands means opening the question, the replies, the assignees, the ball in court and the distribution list on separate screens. You then piece the story together, and a deleted RFI looks the same as a missing one.

What popdock provides

--

Give an RFI number and a project. It resolves the one matching project and finds the RFI, asking which one if the number matches more than one and checking the recycle bin before saying it is missing. It then reads the questions, replies, assignees, ball in court and distribution list and writes a timeline. It shows each reply with its date and whether it is official, who holds the ball, the due date and any cost or schedule impact. Nothing is changed.

Business outcome

---

The full story of an RFI is one timeline, so you know who is holding it up without opening five screens.
See Full Use Case

scenario

-

The story of a machine is split across its equipment record, its service log and an audit trail of changes. Nobody puts them together until it breaks down, and a missing service history is easily read as a clean one.

What popdock provides

--

Give an equipment identification number, and optionally a date to start from. It finds the unit, stopping to ask which one if the number matches more than one record. It reads the maintenance records and the change history, and checks whether the unit is assigned to a project. It reports the current status, ownership, make, model and serial number, then one chronological list of service and change events. If there is no maintenance record it says the unit has no recorded service. Nothing is edited.

Business outcome

---

A machine's whole history is one timeline, and missing service records are called out instead of passing as up to date.
See Full Use Case

scenario

-

Working out who changed a generic item, who it was assigned to and what is attached means separate lookups for history, assignees, distribution, attachments and tasks. The picture only comes together after a lot of clicking.

What popdock provides

--

Give an item title, and optionally a project. It finds the item by title and lists the candidates, with their status and project number, if more than one matches. It then reads the change history, assignees, distribution members, attachments and tasks. It reports the item header, a chronological change list and each of the other sections, showing none where a section is empty. It never updates, deletes or responds to the item.

Business outcome

---

Everything about a generic item is in one report, with the change trail in date order and nothing altered.
See Full Use Case

scenario

-

Auditors ask who changed a purchase order or receipt, and the answer is spread across history screens and attachment lists. Each document type keeps its record in a slightly different place, so the trail takes time to rebuild.

What popdock provides

--

Give the document type, which can be a purchase order, shipment, receipt or transfer, the document name and the project. It reads the change history and the attachments for that document type, and for purchase orders and receipts also the related documents. It stops and asks if the name matches more than one record or more than one project, and if the type is not supported. It reports a dated change table, the attachments and related documents, who touched it last and how many status changes it had. Nothing is edited.

Business outcome

---

Who changed a material document, and what is attached to it, is answered in one report an auditor can use.
See Full Use Case

scenario

-

Finding out why one submittal has not closed means opening its approvers, responses, revisions, package and distribution on separate screens. Meanwhile the due date passes and nobody is sure who is holding it.

What popdock provides

--

Give a submittal number and a project. It resolves the one matching project and finds the submittal, asking which one if the number matches more than one and checking the recycle bin before saying it is missing. It reads the approvers, ball in court, distribution members, revisions and package, and the response names the project uses. It reports the status, due date, who holds the ball, each approver in workflow order with response and date, revisions so far and what must happen next. Nothing is changed.

Business outcome

---

Why a submittal has not closed is clear in one report, with the next step named.
See Full Use Case

scenario

-

When a customer or colleague asks what happened to a task item, support staff open the task, then each tab, to see who was told what and when. The comments, files, assignees and notified people are all kept apart.

What popdock provides

--

Give a task item number and a project. It finds the task and, if it returns nothing or several rows, reports what came back and stops. It then reads the comments, attachments, assignees and the people notified, and reports the title, status, category, due date and description. Comments come in date order with attachment names, current assignees and who was notified and when. It ends with one line on what looks outstanding. Nothing is changed.

Business outcome

---

Who was told what about a task, and when, is answered in one report instead of four tabs.
See Full Use Case

scenario

-

Reconstructing who held an approval and for how long means opening log screens one at a time. Time spent with each role is never added up, so slow steps in a workflow go unnoticed.

What popdock provides

--

Give the workflowed object id of an item, and optionally a project. It reads the permanent workflow log, falling back to the project's log if needed, then the attachments and the item's current workflow instance. It reports the log in date order with activity, role, who performed it and how long the ball sat in each court, then the current state, any overdue date and the file names. It finishes with total time per role. It stops if no log comes back, and every workflow action is off limits.

Business outcome

---

You can see who held an approval and for how long, with time per role totalled and nothing touched.
See Full Use Case

scenario

-

Tracing one change event to its RFQs and change orders means opening several screens and matching numbers and titles by eye. It is easy to link records that only look alike, and the real cost is hard to total.

What popdock provides

--

Give a change event number or part of its title and a project. It finds the event, listing the options if more than one matches, then reads its line items with budget code, cost and revenue estimates and RFQ status. It looks for RFQs and potential change orders that reference the event, and states which links are confirmed by a shared number or title and which are not. It reports a line item table and totals for estimated cost, estimated revenue and amounts already on change orders. Nothing is changed.

Business outcome

---

The cost path of a change event is traced in one report, with only provable links claimed.
See Full Use Case

scenario

-

Bid board statuses are changed by hand with no record of why. A typo can create a status that the reports do not recognise, and a similar project name makes it easy to update the wrong one.

What popdock provides

--

Give a bid board project name, the new status and optionally a reason. It finds the one matching project, stopping if several match, and checks the new status against the estimating settings. It shows the current and new status and the note text, and nothing changes until you confirm. It then changes only the status, logs the reason as a note if you gave one, and reads the project again to report the new status. It never deletes, moves or imports anything.

Business outcome

---

Bid board status changes use a valid status, carry the reason and are verified by a read-back.
See Full Use Case

scenario

-

Checking who can see a sensitive item means cross-referencing permissions by hand. The people with permission and the people who could read it are shown separately, so access that should not be there is easy to miss.

What popdock provides

--

Give an item title, and optionally a company. It finds the item by title and lists the candidates if more than one matches. It then reads the users with permission on the item and the users available to read it. It reports the two lists with company names and notes anyone who appears in the second list but not the first. It reports only what Procore returns, says so if no access rows come back and never changes access.

Business outcome

---

Who can see a sensitive item is answered in one report, with the gaps between the two lists named.
See Full Use Case

scenario

-

Gathering the recorded calls that cover a project's open RFIs means reading the RFI list in Procore, then searching Chorus for calls that mention each one. Building a shareable playlist from the hits is slow, and calls get missed.

What popdock provides

--

Give a playlist name and a project. It reads the project's open RFIs in Procore, then looks in Chorus for calls whose subject or summary mentions an RFI number or subject. You see the playlist name and the proposed calls with the RFI each one covers, and nothing is written until you say yes. It refuses if a playlist with that name already exists, then creates it and adds each approved call. It only writes to Chorus and never changes Procore.

Business outcome

---

A shareable playlist of the calls that cover open RFIs is built once, with your approval and Procore untouched.
See Full Use Case

scenario

-

When a submittal runs late, the project manager digs through call recordings and emails to prove what was said about the delay. The Procore submittal list and the Chorus conversations share no link, so the proof is often not found.

What popdock provides

--

Give a project. It reads the project's submittals in Procore and keeps the ones past their due date that are not approved or closed, with number, title and responsible contractor. It searches Chorus conversations and emails for each one by title and number, and also scans summaries and email bodies for the number or spec section. It reports days late and the matching conversations with date and an excerpt, and lists the submittals never discussed. It reads only, on both systems.

Business outcome

---

Late submittals come with the call and email evidence about them, and the ones nobody discussed are named.
See Full Use Case

scenario

-

Recorded meetings in Chorus and meeting records in Procore are compared by hand, if at all. Unrecorded meetings and minutes that were never distributed go unnoticed until someone asks for them.

What popdock provides

--

Give a project and a date range. It reads the project's meetings in Procore with their distribution dates, then the Chorus conversations for the same project and dates. It pairs them by date, allowing a day either side and preferring matching words in the title. You get matched pairs, Chorus conversations with no Procore meeting and Procore meetings with no recording. It flags meetings whose minutes were never distributed and says when a match is uncertain. It only reads.

Business outcome

---

Gaps between recorded and minuted meetings are listed, including minutes that were never sent.
See Full Use Case

scenario

-

A project manager reads call recordings and emails by hand to see whether the open RFIs and submittals were ever raised with the customer. The ones nobody mentioned are the ones that slip.

What popdock provides

--

Give a project and optionally how many days to look back, 30 by default. It reads the project's open RFIs and submittals in Procore and stops if the name matches several projects. It searches Chorus calls and emails for each item's subject, title or number and marks it Discussed, with the conversation and date, or Not discussed. It reports one table with due date and responsible contractor, the conversations that mention no open item and the three overdue items not yet discussed. It reads only.

Business outcome

---

Every open RFI and submittal is marked discussed or not, so the overdue ones nobody raised stand out.
See Full Use Case

scenario

-

Overdue observation items sit with vendors that nobody has spoken to. Checking contact history means finding each vendor in Procore, then searching Chorus for calls and emails, so it rarely gets done.

What popdock provides

--

Give a project and optionally how many days to look back, 21 by default. It reads the project's overdue observation items that are not closed, grouped by vendor with the count and oldest due date. For each vendor it searches Chorus for emails and calls inside the window. It reports a table with overdue count, calls, emails and last contact date, with vendors with no contact first, and shows No contact recorded instead of an error. It covers at most 15 vendors and says how many were left out. It only reads.

Business outcome

---

Vendors with overdue observations and no recent contact are listed first, so follow-up goes where it is needed.
See Full Use Case

scenario

-

Before calling a subcontractor, you pull its open observations and RFIs out of Procore, then dig through Chorus for who you spoke to and when. The company names differ between the two, so contacts get missed and you walk into the call not knowing how long it has been since anyone talked to them.

What popdock provides

--

Give a vendor name and optionally a project, and it lists the vendor's open Procore observations and RFIs with due dates and age in days. It then finds the vendor's contacts, recent calls and emails in Chorus and works out the days since last contact. Names rarely match exactly, so it shows which names it treated as the same. A vendor with overdue items and no contact in 30 days is marked Needs follow-up. Nothing is changed in either system, and access follows the connected Procore user's permissions per company and project.

Business outcome

---

You start each subcontractor conversation knowing its open field issues, who to ask for and how long it has been since contact.
See Full Use Case

scenario

-

Direct costs in Procore name vendors that may never have been set up in Business Central. Someone scrolls the cost list, searches the accounting system for each name and retypes the missing ones one at a time, and a similar vendor that already exists gets duplicated.

What popdock provides

--

Give a start date, or leave it at the last 90 days, and it reads the vendors on Procore direct costs with their total spend. It checks each one in Business Central, up to 40 vendors, and separates Missing vendors from Possible matches it will skip. You see the Missing list with the Procore spend and choose which to create, up to a limit that defaults to 10. Nothing is created until you answer. Vendors are created one at a time by name only, it stops at the first error, and Procore is never changed.

Business outcome

---

Vendors that direct costs depend on exist in Business Central once, without duplicates, ready for accounts payable to complete.
See Full Use Case

scenario

-

When Procore gets a new office, someone retypes its name, address and phone into Business Central as a location and invents a code on the spot. Typos creep in, an office gets added twice, and a code clashes with one already in use.

What popdock provides

--

Name the Business Central company and, if you like, a limit that defaults to 5, and it reads the Procore offices and finds those with no location by city, state and country. It proposes a location code for each, upper case, up to 10 characters and unique against existing codes. You see the list and confirm which to create, and nothing is written before that. Offices without a city or country are skipped and listed. It then reads Business Central again to check each location exists, never retries a failed create and never changes Procore.

Business outcome

---

New offices appear in Business Central as locations once, with clean codes and details copied from Procore, and each one checked after creation.
See Full Use Case

scenario

-

New Procore vendors are retyped into Business Central by hand, with name, email, phone and city copied across one field at a time. It is slow, a typo makes a record nobody can find, and a vendor that already exists under a slightly different name is added again.

What popdock provides

--

Optionally give a name filter and a limit that defaults to 10, and it reads the active Procore vendors and compares them with Business Central, ignoring case and company suffixes. Close but unequal names are treated as possible duplicates and left out. You see each vendor to be created with email, phone, city and state, and nothing is written before you say yes. Vendors are created one at a time, it stops at the first error, then it reads each new vendor back and reports its number. Procore is never changed, and access follows the connected Procore user's permissions.

Business outcome

---

Active Procore vendors exist in Business Central once, with contact details copied accurately and each new record read back.
See Full Use Case

scenario

-

Procore shows a vendor's insurance has lapsed, but stopping payments is a separate job in Business Central. Someone has to find each vendor there, open it and set the block, and it is easy to miss one or to block the wrong company with a similar name.

What popdock provides

--

Give a cut-off date, or leave it at today, and it reads Procore insurance and keeps only vendors whose latest policy has expired. It looks each one up in Business Central, matching on name, and keeps those not already blocked. Ambiguous matches are listed separately and left out. You see each vendor with its number, expiry date and balance due, and nothing changes until you say yes. It sets only the payment block, one vendor at a time, stops at the first error and reads each vendor back to confirm.

Business outcome

---

Vendors with lapsed insurance are blocked for payment in Business Central after your confirmation, with nothing else on the vendor record touched.
See Full Use Case

scenario

-

RFIs with a cost impact are raised in Procore while the budget lives in Business Central. A project manager works through scope questions without seeing how much cost budget is left on the job, and has to open both systems to find out.

What popdock provides

--

Give a Procore project and a Business Central job number, and it lists the project's open RFIs flagged with a cost impact, oldest due date first, with days until or past due. It reads the job's status and its tasks with budget, usage and remaining cost, flagging any task at or below zero. The job number is the one you give and is never guessed. The two lists sit side by side, because the RFI amounts and cost codes are not available. Nothing is changed in either system.

Business outcome

---

You see how much cost budget remains on the job next to the open cost-impact RFIs, before deciding which questions to push.
See Full Use Case

scenario

-

A controller checks by hand that Procore and Business Central use the same currency, reading the company setting in one and scanning job and vendor currencies in the other. Records set up in a different currency slip through until invoices disagree.

What popdock provides

--

Name the Business Central company and, optionally, the job status, and it reads the currency Procore uses for the company. It then reads the currency on Business Central jobs and vendors and flags every record that differs. An empty currency code means the company's local currency, and it says so before comparing. If Procore returns conflicting codes it lists them and stops. You get the count of jobs and vendors per currency and one closing line on whether the systems agree. Nothing is changed in either system.

Business outcome

---

You know whether Procore and Business Central agree on currency, with every mismatched job and vendor listed before an invoice exposes it.
See Full Use Case

scenario

-

Procore timesheet settings and Business Central timesheets are compared by eye, usually when payroll is already running. A rounding increment that lines do not follow, or a week that starts on the wrong day, only surfaces at the worst moment.

What popdock provides

--

Name the Business Central company and a date range, or leave it at the last 30 days, and it reads the Procore timesheet setup: type, week start day, rounding increment and enabled cost type. It reads the Business Central timesheet lines and counts the resources that use timesheets. It then checks each line against the rounding increment and counts lines by status and posted state. Unset Procore values are reported as not set rather than guessed, and settings that cannot be compared are named. Nothing is changed in either system.

Business outcome

---

Rounding and week-start mismatches between Procore and Business Central show up in one report before payroll relies on the timesheets.
See Full Use Case

scenario

-

Before committing estimators to a bid, someone checks the customer's open bids in Procore, then switches to the accounting system for their balance and credit. The second check is often skipped, and the team prices work for a customer who is already over their limit.

What popdock provides

--

Give a customer name and optionally a bid status, and it finds the customer in Business Central, stopping to let you choose if several match. It reads their open Procore bid board projects with status, due date and proposal totals. It shows the Business Central balance, balance due, credit limit, blocked flag and open sales documents, with anything past due marked. It ends by comparing open bid value with credit headroom, says when no credit limit is set and never adds different currencies. Nothing is changed in either system.

Business outcome

---

Estimators see a customer's open bid value next to their balance and credit headroom before more effort goes into a bid.
See Full Use Case

scenario

-

Payments released against Procore commitments are compared with the Business Central vendor ledger by scrolling both lists side by side. Payments missing from the ledger, or posted for the wrong amount, are found at month end when the books will not agree.

What popdock provides

--

Give a date range, or leave it at the last 30 days, and optionally a project, and it reads the Procore contract payments and the Business Central vendor ledger payment entries around those dates. It matches each payment by check or payment number, or failing that by equal absolute amount and a posting date within 14 days, and says which rule matched. You get a table with each payment marked Matched, Amount differs or Not in ledger, plus ledger payments no Procore payment matched. Unapplied entries are flagged, not called missing. Nothing is changed in either system.

Business outcome

---

Payments missing from the ledger or posted at the wrong amount are listed before month end, with the matching rule shown for each.
See Full Use Case

scenario

-

Direct costs are coded in Procore against vendor names that may not exist, or may be blocked, in the accounting system. Nobody checks until a payment run fails or a vendor is held up, and then it is a scramble to find which names are the problem.

What popdock provides

--

Give a start date, or leave it at the last 90 days, and optionally a project, and it groups Procore direct costs by vendor with cost counts, totals, projects and the latest invoice number. It looks up each vendor in Business Central, up to 40, and marks it Found, Blocked, Possible match, Several matches or Not in Business Central, with the balance due. It never chooses between several matching vendors, and tells you how many were left unchecked. Nothing is changed in either system.

Business outcome

---

Vendors on recent direct costs are checked against Business Central for existence, blocks and balances before they hold up a payment run.
See Full Use Case

scenario

-

A project manager wants to know whether each Procore project role has someone in the ERP who could fill it. That means searching the staff list for each role one at a time and judging whether a job title is close enough.

What popdock provides

--

Name the Business Central company and optionally a role filter, and it reads the Procore roles and looks for active Business Central employees whose job title fits each one. If nothing matches it tries the last word of the role name once and marks the result as a loose match. Plain archetype roles such as Admin are skipped and noted as having no job title equivalent. It cross-checks the people found against job managers, and shows only names and job titles. Nothing is changed in either system.

Business outcome

---

You see which Procore roles have people to fill them in Business Central and which have none, before staffing a project.
See Full Use Case

scenario

-

Insurance expiry is tracked in Procore while payables live in Business Central. Nobody lines the two up, so vendors with lapsed cover keep getting paid, and the issue surfaces when a claim or an audit asks for the certificate.

What popdock provides

--

Give a number of days ahead, or leave it at 30, and optionally a minimum balance, and it reads the Procore policies that are expired or expiring within that window. For each vendor it uses the latest policy, reporting it as lapsed only if that one has expired. It looks each vendor up in Business Central for the balance due, block and payment terms. You get a table sorted by balance due with totals for expired and expiring balances. Vendors with no Business Central match are listed as unmatched, not treated as zero. Nothing is changed in either system.

Business outcome

---

You see how much is owed to vendors whose insurance has lapsed or is about to, so payment can be held until a certificate is on file.
See Full Use Case

scenario

-

Payroll and project accountants compare who was scheduled where in Resource Management against Business Central timesheets by hand. Under-booked weeks and time booked to the wrong job go unnoticed until the close.

What popdock provides

--

Give an employee number and a date range, and it reads that person's scheduled assignments in Resource Management and finds the same person in Business Central, listing candidates and stopping if several match. It checks the duration unit before comparing, carries each project number across as the job number and reads the timesheet lines. You get a table per project of scheduled time, hours booked, the difference and how many lines are unapproved or unposted. It stops when the person does not use timesheets. Nothing is changed in either system.

Business outcome

---

Gaps between scheduled and booked time are visible per project before the close, including time booked to jobs nobody scheduled.
See Full Use Case

scenario

-

Materials managers track stock and orders per project in Resource Management but buy and cost items in Business Central. A material with no item, a blocked item or mismatched quantities is found only when an order is rejected.

What popdock provides

--

Give a Resource Management project and optionally a material name, and it reads the materials with available, ordered and left to receive quantities. It looks each material up as an item in Business Central, trying the first two words if the full name finds nothing, and lists candidates instead of choosing when several match. It compares quantity ordered with quantity on purchase orders and available with inventory, noting exact and approximate matches and differing units. It flags missing and blocked items and never creates the missing ones. Nothing is changed in either system.

Business outcome

---

Materials with no Business Central item, a blocked item or different quantities are listed before an order is rejected.
See Full Use Case

scenario

-

A vendor is made inactive in Procore but nobody blocks it in Business Central, so purchase orders and payments can still go to a company the project team has stopped working with.

What popdock provides

--

Optionally give a date, or leave it at the last 180 days, and it reads the vendors Procore holds as inactive and updated since then. It looks each one up in Business Central, matching on name and ignoring case and company suffixes, and asks which vendor applies when a name matches several. You get the vendors that are not blocked, with the date updated in Procore, vendor number and balance due, highest balance first. It also lists inactive vendors with no Business Central record and counts those already blocked. Nothing is changed in either system.

Business outcome

---

You can stop payments to vendors that Procore has made inactive but Business Central still allows, starting with the largest balance.
See Full Use Case

scenario

-

Estimators price from catalog unit costs that quietly go stale while purchasing costs move in the accounting system. Comparing the two item by item by hand is slow, and a catalog can drift far from real costs before anyone notices.

What popdock provides

--

Name a Procore estimating catalog and optionally a tolerance that defaults to 10 percent, and it reads the catalog items with unit and unit cost. It matches each to a Business Central item by item number, then by description, and records approximate and ambiguous matches separately. It compares the catalog cost with the Business Central last direct cost only when the units agree, and reports a unit mismatch otherwise. You get the items outside tolerance and counts by match type. It stops if the catalog does not map to Business Central items, and nothing is changed.

Business outcome

---

You see which catalog items have drifted from current purchasing costs, with the match type shown, before the next estimate is priced.
See Full Use Case

scenario

-

Time and material hours are signed off in Procore and costed from Business Central timesheets. Compared by hand, person by person, differences in hours go unnoticed until a customer queries the invoice.

What popdock provides

--

Give a Procore project, a Business Central job number and a date range, and it totals hours per person from the Procore time and material timecards, skipping deleted ones. It totals the Business Central timesheet lines per resource for the same job and dates. People are matched only when the name is the same after lower-casing and swapping Last, First, never on first name or initials alone, and anyone on one side only is listed as unmatched. You see each person's hours, the difference and posted status. Nothing is changed in either system.

Business outcome

---

Hour differences between signed-off time and costed timesheets are listed per person before they reach a customer invoice.
See Full Use Case

scenario

-

A project accountant sets up the Business Central job from a budget spreadsheet and has no quick way to see whether it still matches the original budget approved in Procore. The gap shows up late, by cost code, when the job is already being charged.

What popdock provides

--

Name a Procore project and optionally a Business Central job number, and it reads the project's original budget lines and finds the matching job. It stops if more than one project or job matches, and reports a missing job rather than guessing. It reads the job tasks with cost budget and usage and matches each budget line by code or description. You get totals in each system, a table of each line as Matched, Amount differs, Only in Procore or Only in Business Central, and the three biggest differences. If the currencies differ it shows both and no difference. Nothing is changed in either system.

Business outcome

---

You see whether the job was set up with the budget the project team approved, with the biggest gaps named by cost code.
See Full Use Case

scenario

-

Estimators set hourly rates on job titles in Resource Management while finance holds resource costs in Business Central. Nobody compares the two, so the rates drift apart and a job loses margin before anyone notices.

What popdock provides

--

Optionally give a job title filter and a tolerance that defaults to 10 percent, and it reads the Resource Management job titles with hourly rates, listing titles with no rate separately. It reads the Business Central resources, ignoring blocked ones and keeping people, and groups them by job title. It matches each rate to the group with the same title, or an approximate one it says is approximate. You get the lowest, average and highest unit cost, the percentage gap and a flag beyond tolerance. A rate and a cost are different things, so gaps are a prompt to look. Nothing is changed in either system.

Business outcome

---

You see which job title rates have drifted from what the same job titles cost in Business Central, before a job loses margin.
See Full Use Case

scenario

-

Bids are worked in the estimating tool while the sales pipeline is kept in the accounting system, so open bids are re-keyed by hand as opportunities. The ones that are forgotten never appear in the pipeline.

What popdock provides

--

Optionally give a bid status, which defaults to Bidding, and it reads the Procore bid board projects with customer, value and due date. It checks Business Central for an existing open opportunity for each and finds the customer contact where exactly one matches. You see a table of the opportunities it would create, with value, closing date and contact, and choose all, some or none. Nothing is written until you answer. Each opportunity is created once, then read back to confirm it exists. It never updates or deletes, and it stops if the create step is switched off.

Business outcome

---

Open Procore bids reach the Business Central pipeline once, with value and closing date filled in, and each new opportunity is checked.
See Full Use Case

scenario

-

New subcontractors start work on site before anyone sets them up as vendors in accounting. Their first invoice then stalls while someone works out the company is missing and re-keys its details.

What popdock provides

--

Give a Procore project and optionally a start date, which defaults to the last 30 days, and it collects the companies on the manpower logs. It checks Business Central for each, skipping those that exist and listing similar names as possible duplicates. You see the companies that need a vendor with the date last logged, and nothing is created until you choose which. Each confirmed vendor is created one at a time by name exactly as written in Procore, then read back with its number. Addresses, tax numbers and payment terms are left for accounts payable, and existing vendors are never changed.

Business outcome

---

Contractors working on site have a Business Central vendor before their first invoice arrives, created once and read back.
See Full Use Case

scenario

-

Buyers retype a Resource Management purchase order into Business Central by hand, copying the vendor, items and quantities line by line. A typo or a missed line creates a mismatch that only surfaces at invoice time.

What popdock provides

--

Give a Resource Management purchase order name and optionally a project, and it reads the order and its lines. It checks Business Central does not already have a copy, finds exactly one unblocked vendor and finds each line's item, leaving out lines with a missing, blocked or ambiguous item or no cost to use. You see a draft with vendor, dates and every line, and the lines left out and why. Only after you answer yes does it create the purchase order and its lines, then reads back what was stored. It never creates vendors or items and never changes Resource Management.

Business outcome

---

A Resource Management purchase order becomes a Business Central purchase order once, with lines copied accurately and the leftovers listed.
See Full Use Case

scenario

-

Accounting keeps jobs open and forecasts cost against them while the field has stopped logging, or the field keeps logging against a project whose job was closed. Nobody compares the two lists, so both go unnoticed.

What popdock provides

--

Give a start date, or leave it at the last 14 days, and optionally a project, and it reads the open Business Central jobs and groups the Procore daily logs by project with log counts and latest date. It matches a job to a project when the job number appears in the project name or the descriptions agree, and lists partial matches as Possible with the reason. You get three lists: open jobs with no daily logs, projects with logs but no open job, and possible matches, with counts. A job that has not started yet is noted as such. Nothing is changed in either system.

Business outcome

---

Open jobs with no field activity and projects logging against no open job are listed together, so each can be closed, started or fixed.
See Full Use Case

scenario

-

A project manager chases overdue submittals without knowing the contractor is blocked or has an unpaid balance in the accounting system. The chase stalls for a reason the field team cannot see.

What popdock provides

--

Give a Procore project and optionally an as-of date, which defaults to today, and it lists the submittals due before that date that are not closed or approved. It looks up each responsible contractor in Business Central, matching only on the same name after tidying case, punctuation and company suffixes. A contractor with no match is shown as Not found, not as clear. You get a table sorted by days overdue with the vendor's blocked status and balance due, then the contractors who are blocked or owed money with how many overdue submittals each holds. Nothing is changed and nobody is contacted.

Business outcome

---

You see why an overdue submittal may be stalled, because the contractor is blocked or owed money, before you chase again.
See Full Use Case

scenario

-

A bid is won, and only when the first invoice is due does anyone find the customer was never set up in Business Central, or is blocked. Someone then chases records by hand across Procore and the accounting system, copying names between screens and guessing at near matches.

What popdock provides

--

Say which bid board status to check, or leave it blank for all, and it reads the customer company on each Procore bid board project. It looks each distinct customer up in Business Central and reports the ones with no match, the ones that exist only as a contact, the blocked ones, and balances that would pass the credit limit once the bid value is added. Matches are marked exact or approximate, several candidates are listed instead of guessed, and amounts in different currencies are never added together. Nothing is created or changed in either system.

Business outcome

---

Won bids reach invoicing with the customer already set up and clear to bill, so the first invoice is not held up by a missing or blocked record.
See Full Use Case

scenario

-

Procurement picks a winning subcontractor from the Procore bids, and only later learns the vendor was never set up in Business Central, is blocked, or has overdue invoices. Checking every bidder and invitee against the vendor list by hand is slow, so it is skipped.

What popdock provides

--

Name a Procore project and it reads everyone who has bid or been invited to bid. It looks each vendor up in Business Central and reports who is not set up, who is blocked, the balance due and payment terms, and for matched vendors with a balance it checks the open invoices for overdue ones. Each match is labelled exact or approximate, several candidates are listed instead of chosen, and an empty vendor list is reported as a likely wrong company rather than everyone missing. It only reads, and never creates vendors.

Business outcome

---

You know which bidders can be awarded work and which need setting up or clearing first, before the purchase order is held up.
See Full Use Case

scenario

-

Project numbers and names are keyed separately into Procore and Business Central, so they drift. A live Procore project can have no job in accounting, a job under a different name, or a job that is blocked or complete, and costs have nowhere to post.

What popdock provides

--

Optionally name a project or part of a name, and it reads the active Procore projects and the Business Central jobs. It matches on project number first and then on name, and reports active projects with no job, matches where the name differs, jobs that are blocked or complete while the project is live, and jobs with no active project. Projects with no number are matched on name only and marked as weak matches. It only reads, never creating or editing a job or a project, and ends with the count of clean matches.

Business outcome

---

Every live project has a working job behind it, and drift between the two systems is caught before costs and invoices are rejected.
See Full Use Case

scenario

-

Accounts payable keys approved Procore subcontractor invoices into Business Central by hand. Months later nobody can say which approved invoices were never posted, were posted twice, or were posted for a different amount than the subcontractor claimed.

What popdock provides

--

Say which invoice status to check (Approved by default) and optionally a project. It reads those Procore invoices and looks each one up as a posted purchase invoice in Business Central by vendor invoice number. Each is reported as matched, amount differs, not posted or duplicate, with a vendor name check. Lookups stop at 50 and it says how many were left unchecked. A draft is never counted as posted, amounts in different currencies are shown side by side, and nothing is written to either system.

Business outcome

---

You see which approved subcontractor invoices never reached the ledger and which were posted for the wrong amount, before payment runs or month end.
See Full Use Case

scenario

-

Project managers plan crews against projects in Resource Management, but the job that costs and bills the work lives in Business Central. A missing, blocked or already closed job is found only when time entries or invoices are rejected.

What popdock provides

--

Optionally give a project status or a single project number, and it reads the workforce planning projects from Resource Management. It looks each project number up as a job in Business Central, falling back to a name search that is labelled approximate, and compares whether the work is open or closed on both sides. It lists projects with no job, jobs found only by name and blocked or complete jobs still planned against. Several name matches are listed instead of chosen. It only reads, and never creates a project or a job.

Business outcome

---

Crews are only planned against projects that have an open job to cost and bill them, so rejected time and invoices are caught early.
See Full Use Case

scenario

-

Site teams receive materials against a purchase order in Resource Management while accounts payable matches the same order in Business Central. Before paying, someone compares vendor, status and quantities line by line across two screens, and a short delivery slips through.

What popdock provides

--

Give the name of one Resource Management materials purchase order, and optionally its project. It reads the order and its lines, then finds the matching purchase document and lines in Business Central. It compares vendor, status, delivery date and, line by line, quantity ordered against received, saying which line matches are approximate and which document type it matched. It stops if more than one order matches, and flags different units of measure instead of reporting a difference. It only reads, and never updates an order on either side.

Business outcome

---

Accounts payable sees where ordered and received quantities disagree before paying, so short deliveries and wrong vendors are caught first.
See Full Use Case

scenario

-

Site teams log subcontractors and equipment suppliers in Procore daily logs, but nobody checks those companies against the accounts payable vendor list. A company working on site turns out to be missing or blocked in Business Central only when its invoice stalls.

What popdock provides

--

Give a Procore project and a start date (the last 30 days by default), and it collects every company on the manpower and equipment logs. It looks each one up in Business Central and reports whether it is matched, blocked, a possible match or missing, with its balance due. Names are compared after removing punctuation and company suffixes, close names are listed as possible rather than forced, and nothing is reported missing if either side returns no data. It only reads, never creating a vendor or changing a log.

Business outcome

---

Companies working on site are known to accounts payable before their first invoice, so payment is not held up by a missing or blocked vendor.
See Full Use Case

scenario

-

Someone compares the Procore office list against the Business Central locations by hand. Names and addresses are typed differently in each system, so an office goes missing, a location has no office, or two are mismatched, and nobody notices.

What popdock provides

--

Name the Business Central company, and optionally a country code, and it reads the Procore offices and the Business Central locations. It matches each office to a location on city, state and country, using name similarity only to break a tie, and lists matched pairs with any difference in city, postal code or phone, offices with no location and locations with no office. Ambiguous matches are listed rather than picked, and in-transit locations are kept out of the unmatched count. It only reads, and never creates or edits an office or location.

Business outcome

---

Offices and locations line up across both systems, with differences shown side by side so you decide which value is right.
See Full Use Case

scenario

-

Owner billing is tracked on Procore prime contracts while the invoices are issued from Business Central. Finance compares the two totals by hand, and under-billed contracts and invoices that do not reference any contract are missed.

What popdock provides

--

Optionally name a project (all by default) and a from date, and it reads the Procore prime contracts and the posted sales invoices for each owner customer in Business Central. It attaches an invoice to a contract only when it references the contract number or project, lists unreferenced invoices separately, and compares the invoiced total with the Procore owner invoices. Each contract is reported as matched, under-billed, over-billed or no customer found, with the open balance. Customer lookups stop at 20 and it says what was left unchecked. It only reads, and never writes to either system.

Business outcome

---

Finance sees which prime contracts are under-billed or have unreferenced invoices before owners ask, without totalling invoices by hand.
See Full Use Case

scenario

-

An accountant exports Procore purchase order contracts and Business Central purchase orders into two sheets and matches contract numbers by eye. Commitments that were never set up as orders, and amounts that drifted after change orders, go unnoticed.

What popdock provides

--

Optionally name a project (all by default) and a tolerance (1.00 by default), and it reads the Procore purchase order contracts and the Business Central purchase orders. It matches them on contract number only, ignoring case, spaces and leading zeros, and compares the revised contract amount with the order total. Contracts are reported as matched, amount differs, possible match or missing in Business Central, and orders with no contract are listed too. Title matches are shown as possible, never certain, and amounts in different currencies are not compared. It only reads, and never writes to either system.

Business outcome

---

Finance sees which commitments never became purchase orders and where amounts disagree, so the ledger reflects what was committed in Procore.
See Full Use Case

scenario

-

Joiners and leavers are handled in HR and Business Central separately from Procore. Leavers keep their Procore access, new staff are missing from the employee records, and nobody lines the two lists up until an audit asks.

What popdock provides

--

Optionally give part of a name, and it reads the Procore users marked as employees and the Business Central employees. It matches on email first and then on first and last name together, marking name matches as weak. It reports active Procore employee users with no Business Central employee, active Procore users whose employee is not active in Business Central, and job titles that differ, ending with counts and the number of weak matches. If two employees match one user it lists both and does not choose. It only reads, and never changes a user or an employee.

Business outcome

---

Leavers still holding Procore access and staff missing from the employee records are found in one review instead of at audit time.
See Full Use Case

scenario

-

Someone compares the Procore vendor directory with the Business Central vendor list by eye. Vendors that are missing, blocked or carry different contact details in accounting slip through and surface at payment time.

What popdock provides

--

Optionally give part of a vendor name, and it reads the active vendors in Procore and the vendors in Business Central. It matches on name, ignoring case, punctuation and suffixes such as Inc or LLC, and reports vendors absent from Business Central, vendors that are blocked there, and vendors whose email or state differs, shown side by side. It ends with counts and the number of clean matches. Several candidates are listed instead of guessed, and a partial result is flagged when the record cap is reached. It only reads, and never creates or updates a vendor.

Business outcome

---

Missing, blocked and mismatched vendors are found before payment, so invoices are not held up and contact details agree across systems.
See Full Use Case

scenario

-

Payroll and cost staff compare Procore labor classifications with Business Central job titles by eye. Classifications with nobody in them and employees whose title matches no classification go unnoticed, so labor costs land in the wrong class.

What popdock provides

--

Name the Business Central company and optionally an employee status (Active by default). It reads the Procore work classifications, then counts employees and resources per job title in Business Central. It matches each classification to a title on whole names or abbreviations, ignoring case and plurals, and never on a partial word. It reports classifications with a matching title and headcount, classifications with none, and titles with headcount that match no classification, largest first, and counts employees with no title separately. Ambiguous matches are left to you. It only reads.

Business outcome

---

Payroll sees which classifications and job titles do not line up, ranked by how many people they affect, so the biggest gaps are fixed first.
See Full Use Case

scenario

-

HR and resource planners keep one list of workers in Resource Management and another in Business Central payroll, and compare them by eye. Leavers and new hires drift out of step, and a person can be active in one system and gone from the other.

What popdock provides

--

Optionally give a status (Active by default) or a single employee number, and it reads the workforce people in Resource Management and the employees in Business Central. It matches only on employee number, never on names, after trimming spaces and ignoring case and leading zeros. It reports people missing from either side and matched people whose status or hire date differs, showing both values, and gives counts first. If the number schemes on the two sides look different it shows samples and stops. It only reads, and never creates or updates a person or employee.

Business outcome

---

HR and planners see who is missing or out of step between workforce planning and payroll, matched on employee number so no guesses are involved.
See Full Use Case

scenario

-

When a bid is won, someone has to confirm the accounting system has a matching job, bills the right customer and carries a budget that agrees with the bid. It is checked by eye across two systems, and often missed until costs start posting.

What popdock provides

--

Say which bid board status to check (Won by default), and it reads those Procore bid board projects. It finds each one as a job in Business Central, retrying with the first words of the name, and adds up the job task budgets to compare with the bid total. It reports projects with no job, jobs whose bill-to name does not resemble the Procore customer, budgets that differ beyond your tolerance (5 percent by default) and jobs that are blocked or complete. Matches are marked exact or approximate and several candidates are listed. It only reads, and never creates or edits a job.

Business outcome

---

Won bids start with a job that exists, bills the right customer and carries the agreed budget, so cost posting and billing do not stall.
See Full Use Case

scenario

-

Before closing out a project, the team chases vendors for open punch work without knowing which of them are still owed money or are blocked in accounting. Final payments cannot be discussed with the full picture, and each vendor is looked up by hand.

What popdock provides

--

Name a Procore project, and it counts the open punch items held by each assigned vendor, with the categories and the oldest item. It then looks each vendor up in Business Central and reports blocked status, balance and balance due, matching only when the name is the same after removing punctuation and company suffixes, otherwise showing the vendor as not found. The result is one table sorted by open items, with a count of items that have no assigned vendor. It reports facts only and does not suggest withholding payment. It only reads, and never changes a punch item or a vendor.

Business outcome

---

Close-out conversations start with each vendor's open punch count beside what they are owed, so final payments are discussed with the full picture.
See Full Use Case

scenario

-

Action items agreed in a meeting have to be retyped into the Procore meeting as topics. It is slow, so some commitments are dropped, and others are entered twice because nobody checked what was already there.

What popdock provides

--

Name the Granola meeting, the Procore project and optionally the Procore meeting, and it reads the action items and decisions from the Granola note with the owner and due date where stated, never inventing either. It finds the Procore meeting for that day, skips commitments that already have a topic, and shows you a numbered list of the topics it would create. Nothing is written until you say which to create. It then creates only the topics you confirm, one at a time, stops on the first error and reads the meeting back to report what was created, skipped or failed.

Business outcome

---

Meeting commitments land in Procore once, with the owner and due date from the notes, so nothing agreed in the room is lost or duplicated.
See Full Use Case

scenario

-

The attendee list on a Procore meeting is set up in advance and rarely checked against who actually joined the call. The minutes then show people who were absent and miss people who were there, which matters when decisions are disputed later.

What popdock provides

--

Give the meeting date and the project, and optionally the meeting title, and it finds that Procore meeting and its attendee list. It finds the Granola note for the same day and reads its attendees and invitees. It reports who is on the Procore list but not in Granola, who is in Granola but not on the Procore list, who was invited but did not attend, and any ambiguous name matches, with the Procore status as returned. It stops if the meeting or note is ambiguous and never infers attendance from Procore alone. It only reads.

Business outcome

---

Meeting minutes can list who was actually there, with absences and unrecorded attendees found in minutes instead of by memory.
See Full Use Case

scenario

-

A question raised in a meeting often never becomes an RFI, or becomes one with the wrong people attached and a subject that duplicates an existing RFI. Someone has to find the question in the recording, then check Procore and pick the manager and assignee.

What popdock provides

--

Name the Granola meeting and the Procore project, and optionally a hint about the question. It searches the transcript for unanswered questions about drawings, specifications, materials, sequencing or scope and shows up to five with the speaker. You pick one, it checks Procore for an RFI with a similar subject, and you name the RFI manager and assignee, which are matched to real people rather than guessed. It shows the full draft and waits for your yes before creating one RFI, then reads Procore back to report its number, status and due date. It never replies to, updates or deletes RFIs.

Business outcome

---

Questions raised in meetings become one correctly worded RFI with the right people, without a duplicate and without anyone retyping the question.
See Full Use Case

scenario

-

Action items agreed in a meeting are lost when nobody enters them as topics on the Procore meeting. Finding which ones were missed means reading the notes beside the Procore topics and checking them off one at a time.

What popdock provides

--

Name the Granola meeting and the Procore project, and it reads the note and lists every action item and decision with the owner and due date where the note states them, never inventing either. If the summary is thin it searches the transcript and quotes the line. It finds the Procore meeting for that day and its topics, and shows each commitment as covered by a topic number or missing, marking partial matches for you to judge. It ends with the missing commitments ready to be entered. It stops if no Procore meeting exists for that day, and only reads.

Business outcome

---

Commitments that never reached Procore are listed in one pass, so nothing agreed in a meeting is quietly lost.
See Full Use Case

scenario

-

Overdue RFIs, punch items and observations can sit for weeks because nobody checks whether any meeting ever raised them. Searching recordings and notes for each item by hand is slow, so the quiet ones stay quiet.

What popdock provides

--

Name the Procore project and, if you like, how many days of meetings to look back (30 by default). It lists the overdue open RFIs, punch items and observations, oldest first and capped at the 15 most overdue. It then searches the Granola transcripts for each item by its number or title, skipping labels too short to search and marking generic title matches as possible. You get one list of items never mentioned in a meeting and one of items that were discussed, with the meeting and speaker, plus how many items were not checked. If Granola has no notes for the period it stops. It only reads.

Business outcome

---

Overdue items that no meeting has raised are surfaced for the next agenda, instead of sitting unnoticed for weeks.
See Full Use Case

scenario

-

Checking whether every Procore project meeting has meeting notes means opening two systems side by side and comparing dates and titles. Undocumented meetings go unnoticed, and notes taken for the project may never be tied to a Procore meeting.

What popdock provides

--

Name the Procore project and optionally a date range (the last 30 days by default), and it reads the project's meetings and the Granola notes for the same dates. It pairs a meeting with a note when they fall on the same day and share a distinctive word in the title, and lists both notes when two fit one meeting. You get Procore meetings with no note, notes on that project with no meeting, and matched pairs, with a line of counts. Unrelated notes are counted separately, it stops on an ambiguous project name, and it only reads.

Business outcome

---

Undocumented meetings and orphan notes are found in one pass, so every project meeting has a record and every record has a meeting.
See Full Use Case

scenario

-

Finding out what was said about an RFI means searching many meeting recordings by hand for its number and subject. Even then nobody can tell whether the conversation matches the RFI's status, or whether it was ever discussed before its due date.

What popdock provides

--

Give the RFI number and the Procore project, and optionally how many days of meetings to search (90 by default). It reads the RFI with its subject, status, due date, responsible contractor and drawing number. It searches the Granola transcripts for the RFI number written several ways and for distinctive words from the subject, labelling weak subject matches as possible mentions, then adds the meeting date and summary for each hit. You get a dated timeline and a short assessment against the due date and status, with stated decisions quoted. It never claims the RFI was ignored when nothing was recorded. It only reads.

Business outcome

---

You see what was said about an RFI beside its status and due date, without listening back through recordings.
See Full Use Case

scenario

-

Crews log time against cost codes that were never set up as tasks on the Intacct project. The hours cannot post, so someone compares the timecard codes with the task list by hand and adds the missing tasks one at a time.

What popdock provides

--

Name the Procore project and a start date (the last 30 days by default), and it collects the cost codes used on timecards. It finds the one matching Intacct project, stopping if there is none or more than one, and compares each cost code with the project's tasks, ignoring case and spacing. You see the codes with no task, and nothing is written until you confirm. It then creates only the confirmed tasks, once per code, never duplicating an existing one, and reads the tasks back to confirm each exists. A failed create is reported and not retried.

Business outcome

---

Timecard hours post cleanly because every cost code in use already exists as a task, with no duplicates and nothing created without your approval.
See Full Use Case

scenario

-

Vendors who bill on Procore jobs are not always set up in Intacct, so their bills stall until accounts payable finds the gap. Someone then compares invoice and direct cost vendors with the vendor list and keys each missing vendor in by hand.

What popdock provides

--

Name the Procore project, an optional prefix for new vendor ids and a limit on how many vendors to check (25 by default). It collects the vendors on the project's invoices and direct costs and looks each one up in Intacct, treating close name matches as existing. You see a table of the missing vendors with the proposed name and vendor id, and nothing is written until you say which to create. It then creates only the approved vendors, once each, skips ids that already exist and reads each vendor back to confirm. A failed create is reported and the rest continue.

Business outcome

---

Vendors billing on a project exist in Intacct before their invoices arrive, with ids you approved and no duplicates created.
See Full Use Case

scenario

-

Before a Procore to Intacct integration goes live, someone opens the company settings in Procore, then checks bank account currencies, employee currencies and timesheet start days in Intacct, and compares them by eye. A mismatch only shows up later as wrong week totals or amounts in the wrong currency.

What popdock provides

--

Optionally give a start date for timesheets and an employee status, and it reads the Procore company currency, timesheet type and week start day. It then reads the Intacct bank account currencies, counts employees by default currency and works out which weekday recent timesheets begin on. Each comparison is marked Agrees, Differs or Cannot tell, with the evidence. Nothing is changed in either system, and a line is never guessed when one side has no data.

Business outcome

---

You know before go-live where Procore and Intacct disagree on currency and week start, with the evidence in hand and no setting changed.
See Full Use Case

scenario

-

Bids are leveled in Procore, and the winning bidder is looked up in the accounting system only when the first invoice arrives. By then the vendor may be missing, on hold or carrying a balance, and the award has already gone out.

What popdock provides

--

Give a project name, and optionally a vendor name, and it lists the bids on that project from Procore and builds the list of distinct bidding vendors. Each one is looked up in Intacct for status, balance and last payment. The report puts missing and inactive vendors first and says which would block an award. Name matches are labelled as name matches, ambiguous matches are listed and never chosen, and no vendor is created.

Business outcome

---

Missing or inactive bidders are found at bid leveling, before an award goes out, with nothing created in either system.
See Full Use Case

scenario

-

Cost codes in Procore and tasks in Intacct are set up separately, often in different formats. Codes that carry budget have nowhere to post, and nobody finds out until costs fail to sync.

What popdock provides

--

Give a project name, and optionally the Intacct project id, and it reads the Procore cost codes and the tasks on the matching Intacct project. Codes are matched by full code once spaces, dashes and dots are ignored, then by name, and name matches are labelled. It reports matched codes, Procore codes with no task, ranked by budget, and Intacct tasks with no code, with the total budget on unmatched codes. It stops if the Intacct project is ambiguous and changes nothing.

Business outcome

---

You see which budgeted cost codes have no Intacct task before costs fail to post, with nothing changed in either system.
See Full Use Case

scenario

-

Equipment vendors are keyed into Procore and into Intacct separately. A rental or equipment supplier can be missing or inactive in the ledger, and you find out when its bill arrives and cannot be coded.

What popdock provides

--

Optionally give an equipment status and category, and it reads the equipment register in Procore and builds the list of distinct supplying vendors. It looks each vendor up in Intacct, up to 40, and reports vendors found with status and amount due, vendors not found and vendors not active. Exact name matches are confirmed and partial ones are labelled possible, ambiguous matches are listed without choosing, and nothing is changed.

Business outcome

---

Equipment suppliers missing or inactive in Intacct are found before their bills arrive, with the affected equipment counted.
See Full Use Case

scenario

-

Superintendents record the subcontractors on site in the daily manpower logs, and nobody checks that those vendors are set up and active in accounting. The first sign is a subcontractor bill that gets stuck.

What popdock provides

--

Give a project name, and optionally a start date, and it reads the manpower logs from Procore and collects each distinct vendor with its number of logs. Each vendor is looked up in Intacct for vendor id, status and amount due. The report groups vendors as active, inactive or on hold, and not found, says which were matched on a partial name, and reports a log with no vendor name separately. It changes nothing in either system.

Business outcome

---

Subcontractors working on site are confirmed as active vendors in accounting, so their bills are not held up later.
See Full Use Case

scenario

-

A project manager's contract and billing figures in Procore drift from the project record in Intacct. Contract value, approved changes, invoices and payments sit on different screens in two systems, and the gap is usually found at month-end close.

What popdock provides

--

Give a project name, optionally the Intacct project id and a tolerance percent, and it reads the prime contract, change and invoice totals and commitment cost totals from Procore and the project record from Intacct. It compares contract amount and cost invoiced, and shows billing as context only. Variances above the tolerance are flagged with a likely cause, empty figures show as not available rather than zero, and it stops if the project is ambiguous or missing. Nothing is changed.

Business outcome

---

Variances between Procore and Intacct are caught mid-month with a likely cause, not at close, and nothing is changed in either system.
See Full Use Case

scenario

-

Estimates are priced from Procore catalog unit costs, while the ledger carries its own standard cost for the same item in Intacct. The two drift apart over time, and bids go out on stale prices that nobody notices until the job is costed.

What popdock provides

--

Give a catalog name, and optionally an item name and a tolerance percent, and it reads up to 50 catalog items from Procore with unit costs. Each is found in Intacct by catalog number or name, and the unit cost is compared with the standard cost. Differences over the tolerance are flagged, items with differing units of measure are reported as a unit mismatch, and empty costs are skipped. Nothing in a catalog or an item is ever updated.

Business outcome

---

Stale catalog prices are found before a bid goes out, and every comparison is like for like, with nothing changed.
See Full Use Case

scenario

-

A person's planned project assignments sit in Procore Resource Management, and the hours they actually booked sit in Intacct timesheets. Comparing the two project by project is manual, so over-booking and under-booking are found only after payroll has run.

What popdock provides

--

Give an employee number and a date range, and it reads that person's planned assignments from Procore that overlap the range and the timesheet hours booked in Intacct for the same period. Both sides are grouped by project and matched on exact project name. The report shows planned duration, hours booked and billable hours, flags hours with no assignment and assignments with no hours, and says which timesheet states are included. It never guesses a project match and changes nothing.

Business outcome

---

Over-booked and under-booked people are spotted from planned against booked hours before payroll, with nothing guessed and nothing changed.
See Full Use Case

scenario

-

Reports that combine Procore and Intacct projects break because project types and stages are named differently in each system. Nobody has a list of the differences, so each report builder rediscovers them by pulling both sets of values and comparing them by hand.

What popdock provides

--

Optionally filter by Intacct project name text and status, and it lists every Procore project type and stage with its category. It then counts Intacct projects by project type and status and notes which statuses are active. Two tables follow, types and then stages against statuses, each split into matched by name, Procore only and Intacct only. Mappings are offered as up to five suggestions for a person to confirm, matched on name only, and nothing is changed.

Business outcome

---

Report builders get a clear list of where project types and stages differ, with suggested mappings to confirm, not guessed.
See Full Use Case

scenario

-

Schedule dates drift in Procore while the project record in accounting keeps its original begin and end dates. Billing and cost forecasts then run against the wrong window, and nobody opens both screens to notice.

What popdock provides

--

Give a project name and it reads the Procore schedule activities, taking the earliest start, the latest finish and the percent complete. It finds the project in Intacct and reads its begin date, end date, status and percent complete. The report shows the difference in days at each end and says plainly whether the dates agree, the schedule runs past the Intacct end date, or the Intacct project is closed or on hold with work still open. It stops on ambiguous or absent projects and changes nothing.

Business outcome

---

Schedule drift against the accounting project is spotted early, so forecasts and billing use the right window.
See Full Use Case

scenario

-

Project engineers compare field timecards in Procore with the timesheets in the accounting system by eye, worker by worker and day by day. A missed worker means unpaid or unbilled hours that are found weeks later.

What popdock provides

--

Give a project name and a date range, 14 days by default, and it reads the Procore timecard entries with each worker, date and cost code. It finds the project in Intacct and reads its timesheet entries for the same dates, matching workers by name regardless of first and last name order. You get a row per worker and date with Intacct hours or none, workers with no Intacct entries, and Intacct names with no Procore timecard. Unsure name matches are marked probable, and it changes nothing.

Business outcome

---

Workers with field time and no timesheet entry are found within days, not weeks, before hours go unpaid or unbilled.
See Full Use Case

scenario

-

Procore and Intacct vendor lists are compared in spreadsheets, one name at a time, with spellings, suffixes and punctuation that never quite match. Duplicates, missing vendors and status differences linger because the comparison is tedious and rarely repeated.

What popdock provides

--

Optionally give a vendor name, and it reads up to 40 vendors from Procore, or the first 40 if no name is given. Each is looked up in Intacct, with names compared after trimming spaces, ignoring case and dropping suffixes such as Inc, LLC and Ltd. The report shows each vendor with match type, status and email match, then lists Procore vendors with no Intacct vendor, vendors active in one system and inactive in the other and Intacct vendors with a balance that are inactive in Procore. Partial matches are never confirmed, and nothing is changed.

Business outcome

---

Duplicate, missing and mismatched vendors are listed in one pass, with every uncertain match labelled and no record changed.
See Full Use Case

scenario

-

Won bids are handed to operations, and the matching project is never opened in the accounting system, so time and cost have nowhere to post. Checking each won bid against Intacct by hand means a list from Procore and a search per project.

What popdock provides

--

Give a bid status, and optionally a customer name, and it lists the matching bid board projects from Procore with customer, proposal value and due date. Each is looked up in Intacct by project name, preferring the match with the same customer when several exist, and the proposal value is compared with the contract amount. The report puts projects missing from Intacct first. Differences are described as things to check, not errors, and nothing is created or updated.

Business outcome

---

Won bids without an Intacct project are found while the hand-off is fresh, before time and cost have nowhere to post.
See Full Use Case

scenario

-

Field staff appear on Procore timecards under names that do not always match the payroll records in Intacct. Time gets logged for people who are not active employees, or who left before the date on the timecard, and the problem surfaces at payroll.

What popdock provides

--

Give a project name, and optionally a start date, 30 days back by default, and it reads the Procore timecards and collects each distinct worker with their number of entries. Each worker is looked up in Intacct for employee id, status and end date, retrying on surname when needed. The report groups workers as active, inactive or past an end date, and not found, flags anyone who worked after leaving, and says which matches were on a partial name. It never chooses between several matches and changes nothing.

Business outcome

---

Workers on timecards are confirmed as active employees before payroll, and anyone who worked after leaving is flagged.
See Full Use Case

scenario

-

When a bid is won, the accountant retypes the customer from the Procore bid board into Intacct. If the existing customer was spelled differently, a second record is created, and invoices and balances end up split across two customers.

What popdock provides

--

Give a bid board project name, and optionally a customer id, and it reads the customer company on that project from Procore and checks Intacct for it, by exact name and then by partial name. If any match exists it shows the customer id and status and stops without creating anything. Otherwise you see the exact customer record, and nothing is created until you say an explicit yes. It then creates the customer once, reads it back to confirm and never touches Procore or retries a failure.

Business outcome

---

A new bid customer is added to Intacct only when none exists, after your yes, and read back so you know it landed.
See Full Use Case

scenario

-

A project set up in Procore needs a matching Intacct project before costs can post. Retyping the project name and number into Intacct leads to typos and duplicate projects, and a missing customer or category stalls the setup.

What popdock provides

--

Give a Procore project number, a project category and optionally a customer id, and it reads the project name and accounting number from Procore. It checks Intacct by id and by name, and if a project exists it shows it and stops. If a customer id is given, it must exist in Intacct. You see exactly what will be created, and nothing is saved until you say an explicit yes. It then creates the project once, reads it back, and never writes to Procore or invents a customer, manager or dates.

Business outcome

---

A Procore project gets its matching Intacct project once, with the right name and number, and with no duplicate or invented details.
See Full Use Case

scenario

-

Awarded bidders are set up in the ledger from an email or a bid form. Tax and payment details are retyped, and a vendor already in Intacct under a slightly different name gets a second record that splits the payment history.

What popdock provides

--

Give a vendor name and the project they bid on, and optionally a vendor id, and it confirms the bid in Procore and uses the vendor name exactly as Procore spells it. It then checks Intacct by exact and partial name, and if a match exists it shows the vendor id, status and amount due and stops. If no bid is found, nothing is created either. You see the vendor record, and nothing is saved until you say an explicit yes. It creates the vendor once, reads it back and never touches Procore.

Business outcome

---

An awarded bidder becomes an Intacct vendor only when none exists, after your yes, with no duplicate and a read-back.
See Full Use Case

scenario

-

Setting up a Procore vendor in Intacct means copying the name, email and phone across by hand. That invites typos, and a vendor that already exists under a slightly different name gets a second record.

What popdock provides

--

Give a Procore vendor name and an Intacct vendor id, and it reads that one vendor from Procore with its name, abbreviated name, email, phone and active status. It checks Intacct by name and by the first two words, and if anything similar comes back it shows it and stops. You see the values it would send, and nothing is saved until you say an explicit yes. It creates the vendor once, reads it back with the stored values and never retries or changes anything else.

Business outcome

---

A Procore vendor is copied into Intacct once, with matching details and a read-back, only when Intacct has no similar vendor.
See Full Use Case

scenario

-

Accounts payable pays bills without knowing the vendor's insurance in Procore has expired, because the two systems are never checked together. Someone would have to find each lapsed policy in Procore, then search Intacct for that vendor's unpaid bills.

What popdock provides

--

Optionally give a number of days ahead, 30 by default, and it finds vendors in Procore whose insurance has expired or expires inside that window, keeping the policy that expires last. For each one it looks up unpaid bills in Intacct, marking any match made on a partial name. You get a table of policy number, days to expiry, open bills, total due and earliest due date, lapsed vendors with open bills first. It reports facts only and does not recommend holding a payment.

Business outcome

---

Accounts payable sees which vendors with lapsed insurance still have unpaid bills, and how much, before the next payment run.
See Full Use Case

scenario

-

Estimators bid for customers the accountants have never set up. Nobody checks the bid board against the Intacct customer list, and the gap is found only when the win is invoiced and there is no customer to bill.

What popdock provides

--

Optionally give a bid status and a customer name, and it lists the bid board projects from Procore and builds the list of distinct customer companies with their bid counts and total value. Each customer is looked up in Intacct for id, status, amount due and credit limit. The report gives Matched, Inactive in Intacct, Ambiguous or Missing from Intacct for each, with Missing and Inactive first. Matches are labelled as name matches, ambiguous hits are listed and never picked, and no customer is created.

Business outcome

---

Bid customers missing from Intacct are found while bids are open, not when the win is invoiced, and nothing is created.
See Full Use Case

scenario

-

Someone compares the Procore project list with the Intacct project list by hand. Projects with a missing or mistyped project number go unnoticed, and the first sign is costs that have nowhere to post.

What popdock provides

--

Optionally give a project name and a company, and it reads up to 25 active projects from Procore with their numbers, stages, start dates and values. Each project number is looked up in Intacct as a project id as text, falling back to the name and marking those as name only. The report shows a row per project, then lists projects with no number, projects with a number but no Intacct project and matched projects whose start dates differ by more than 30 days. A name-only match with a different id is a conflict, never counted.

Business outcome

---

Procore projects with no Intacct counterpart, or the wrong number, are found before costs have nowhere to post.
See Full Use Case

scenario

-

Procore user access and Intacct employee records are kept by different teams and drift apart. Leavers keep project access, new staff are missing from one system, and nobody sees it without comparing a list of users with a list of employees.

What popdock provides

--

Optionally give a name and a company, and it reads up to 40 Procore users with their active status, employee flag, job title and permission template. For each user flagged as an employee it looks up the Intacct employee by full name, listing ambiguous matches without choosing. The report shows match type and status per person, then lists employees with no Intacct record, users active in Procore whose Intacct employee is inactive or ended, and job title differences. It skips users not flagged as employees and says how many.

Business outcome

---

Leavers with live Procore access and staff missing from either system are listed in one pass, with no record changed.
See Full Use Case

scenario

-

Staff planned in Procore Resource Management are checked against the Intacct employee list by eye. People without an employee record, or with the wrong status or dates, are missed and only show up when time cannot be booked.

What popdock provides

--

Optionally give a status, Active by default, and a hire date, and it reads the people planned in Procore with employee number, status and hired date, setting aside anyone with no employee number. It reads the Intacct employees and matches on employee number, ignoring case and spaces, never on name. The report lists people with no Intacct employee, active Intacct employees with no Procore person and matched pairs whose status or dates disagree, with counts. It does not repeat wage values and changes nothing.

Business outcome

---

Planned staff with no employee record, or mismatched status and dates, are found before time cannot be booked.
See Full Use Case

scenario

-

Someone compares the projects planned in Procore Resource Management with the Intacct project list by hand. Projects that exist on only one side go unnoticed, and a project closed in one system stays open in the other.

What popdock provides

--

Optionally give a status, Active by default, and a project name, and it reads the planned projects from Procore with number, stage, percent complete and closed date, counting those with no project number. It reads the Intacct projects and matches Procore project number to Intacct project id, ignoring case and trying the number without leading zeros. It never matches on name alone, and an identical name is only a possible match. You get four lists, with counts: in both, Procore only, Intacct only and matched but disagreeing. Nothing is changed.

Business outcome

---

Projects missing from one system, or open in one and closed in the other, are listed together by project number.
See Full Use Case

scenario

-

Projects planned in Procore Resource Management are rekeyed into Intacct by hand. The name and project number are retyped, and without a check of both id and name, typos and duplicate projects creep in.

What popdock provides

--

Give a Procore project number and an Intacct category, and it reads that one planned project from Procore, stopping if there are none or several. It checks Intacct by project id and by the Procore name, and if a project exists under either it shows it and stops. You see the name, project id, category and status it will send, and nothing is saved until you confirm. It then creates the project once and reads it back, and it never updates, never writes to Procore and never invents a category.

Business outcome

---

A planned Procore project gets one Intacct project, created only if none exists and after you confirm, with a read-back.
See Full Use Case

scenario

-

A won bid is announced in a meeting and the accounting project is opened days later from memory. The customer is picked from a long list, the name is retyped, and the Procore bid board never learns what the project was called in Intacct. A typo or a second project for the same job follows.

What popdock provides

--

Name the won bid board project and it reads the bid in Procore, then checks Intacct for a project with that name and for the customer, stopping if a project already exists or the customer is missing or inactive. You see the project it would create and nothing is written until you say yes. It creates the Intacct project once and reads it back. A second yes lets it record the new project id as a note on the bid in Procore. A failed write is reported, not retried.

Business outcome

---

A won bid becomes one correctly named Intacct project for the right customer, and the bid board shows which project it became.
See Full Use Case

scenario

-

When a job is won in Procore, someone retypes the project into Intacct from the contract. A typo in the name, the wrong customer, or a project that already exists under a slightly different name splits the job's costs across two records.

What popdock provides

--

Give a Procore project and an Intacct category, and optionally a customer. It confirms the project and its prime contract in Procore, then checks Intacct for a project with a matching name and for exactly one matching customer, using the contract owner when you name none. It stops on a duplicate or an unclear customer. You see the proposed project and nothing is created until you say yes. It creates the project once and reads it back. It never creates customers or tasks.

Business outcome

---

Each won job gets one Intacct project that matches the Procore contract, so costs land in a single record from the first bill.
See Full Use Case

scenario

-

Materials purchase orders raised in Procore have to line up with purchasing documents in Intacct, and the check is done by hand, vendor by vendor. An order that was never recorded in accounting, or an Intacct document with no matching order, is found late.

What popdock provides

--

Name a Procore project and optionally an order status, and it reads the project's materials purchase orders, then looks up each vendor's purchasing transactions in Intacct. Orders are matched to Intacct documents by reference and number, and a same vendor, similar date pairing is only labelled a possible match. You get each order with its matched document, total and state, the Intacct documents that match no order, and counts of matched, possible and unmatched. It stops when the project name is ambiguous, and nothing is changed in either system.

Business outcome

---

Unrecorded and orphaned materials orders show up in one review, instead of surfacing when a vendor asks about payment.
See Full Use Case

scenario

-

Owner invoices sit in Procore and customer invoices sit in Intacct, so someone exports both into spreadsheets and matches them by eye. A missing or mis-keyed invoice goes unnoticed until the owner disputes a balance.

What popdock provides

--

Name a Procore project, and optionally the Intacct customer and a start date. It finds the prime contract, reads its owner invoices from Procore and the customer's invoices from Intacct, and matches them by invoice number. A same amount within seven days is labelled a fuzzy match. You get a table with a finding for each invoice (only in Procore, only in Intacct, amount differs, paid differs, matched) and billed and paid totals for each side. It stops on an ambiguous contract or customer, never mixes currencies and changes nothing.

Business outcome

---

Owner invoice gaps and amount differences are found in one review, before the owner raises a disputed balance.
See Full Use Case

scenario

-

Finance staff compare the Procore project list with the Intacct project list by eye. A project whose accounting number never made it into Intacct is found only when a bill will not post, and a closed Intacct project can still have open work in Procore.

What popdock provides

--

Optionally name a project number or an Intacct status. It collects up to 25 Procore projects with work items and the accounting project number on each, then looks each number up as an Intacct project, matching on the exact id first. A name-only match is flagged as a conflict and not counted. You get one row per project and three groups: no accounting number, no Intacct project, and Intacct closed or inactive while Procore still has open items. Nothing is changed in either system.

Business outcome

---

Projects that cannot take bills, and closed projects that still have open work, are found in one pass before they cause a failed posting.
See Full Use Case

scenario

-

Subcontractor invoices approved in Procore are keyed again into Intacct by hand, and nobody checks that the bill and the payment came out the same. A missing bill, a different amount or a payment recorded in only one system shows up when the subcontractor chases it.

What popdock provides

--

Name a vendor, and optionally a project. It reads the vendor's subcontractor invoices and payments in Procore, finds the vendor in Intacct and reads its bills and payments. Invoices are matched to bills by number, and a same amount within 14 days is labelled a fuzzy match. You get one table of invoices and one of payments, with findings such as only in Procore, only in Intacct, amount differs or paid in one system only. It stops on an ambiguous vendor, keeps draft and void invoices out of totals, asks before treating two spellings as one vendor, and changes nothing.

Business outcome

---

Subcontractor invoices and payments are checked across both systems in one pass, so gaps are found before the vendor calls.
See Full Use Case

scenario

-

Finance approves credit by looking at the Intacct ledger alone, while the Procore bid board shows more work coming for the same customer. Nobody adds the open balance to the proposals in play, so exposure is understated.

What popdock provides

--

Name a customer and optionally a look-ahead window, 60 days by default. It finds the customer in Intacct and reads its status, total due, credit limit and last invoice date, then reads the customer's open bid board projects due in the window and the highest proposal on each in Procore. It adds the balance to those proposals, labelled potential exposure and an estimate, and states whether the total is within, near or over the limit. It refuses to pick between several matching customers, skips the ratio when no limit is set, and changes nothing.

Business outcome

---

Credit decisions use the balance and the bids in play together, so exposure is visible before a new proposal is awarded.
See Full Use Case

scenario

-

Equipment used on site is logged in Procore but billed through accounts payable. Matching the two by hand means grouping log days by vendor, then hunting for each vendor's bills, and vendors that were used but never billed go missed.

What popdock provides

--

Name a Procore project and optionally a date range, the last 30 days by default. It reads the project's equipment logs and groups the log days by vendor and equipment, then finds each vendor in Intacct and reads its bills for the period. You get a table per vendor with log days, number of bills, total billed and total due, with vendors that have log days but no bills flagged, and vendors with bills but no log days. It warns that Intacct bills are not tied to the project, skips vendors with ambiguous matches, and changes nothing.

Business outcome

---

Equipment used on site but never billed is found while the period is open, with the limits of the comparison stated plainly.
See Full Use Case

scenario

-

A project manager checking whether field activity matches the money has to open Procore for the items, then Intacct for bills and timesheets, and line them up by hand. Cost with no activity, or open items on a project accounting shows as complete, are easy to miss.

What popdock provides

--

Name a Procore project number and optionally a start date, the start of the year by default. It finds the project's accounting number in Procore and the matching project in Intacct, then reads the Intacct bill lines and timesheet hours posted to it. You get the Intacct project's status and amounts, Procore items by status, bill lines by vendor, and hours by employee, then three observations: open Procore items on a project Intacct shows complete, Intacct cost with no Procore activity, and bill lines missing a vendor or account. It stops if there is no accounting number or more than one project, never converts currency or infers zero spend, and changes nothing.

Business outcome

---

Field activity and posted cost are read side by side in one report, so mismatches between the work and the money are seen early.
See Full Use Case

scenario

-

Understanding one subcontractor means opening Procore for the projects they are on and their insurance, then Intacct for their balance, bills and payments. The two views are rarely put side by side, so an inactive vendor or an expired policy goes unnoticed.

What popdock provides

--

Name a vendor, and optionally a company. It finds the one matching vendor in Procore and reads the projects they are on and their insurance policies, then finds the vendor in Intacct and reads recent bills and payments. You get four short sections, the Procore vendor, its projects, its insurance with status and expiry, and the Intacct vendor with total due, open bills, last bill date and last payment date, then a list of anything inconsistent. It stops on an ambiguous vendor, reports only the Procore side when Intacct has no match, and changes nothing.

Business outcome

---

One subcontractor is understood across both systems in a single answer, with inconsistencies called out rather than left to chance.
See Full Use Case

scenario

-

When HR adds a role in NetSuite, someone has to retype it as a job title in Procore resource planning. Titles get missed, or entered with a different spelling and the wrong rate, and planners then cost staffing plans against titles that do not match the roles HR holds.

What popdock provides

--

Name a Procore planning group and optionally a limit, five titles by default. It reads the job titles held by active NetSuite employees and the existing titles in Procore, matching by name while ignoring case, punctuation and plurals. You see each missing title with its employee count, and the existing Procore types and rates for reference. Nothing is created until you confirm the list, the type and the hourly rate for each, and a rate is never guessed. Each title is created once, then read back as Created, Not found or Failed. NetSuite is never written to.

Business outcome

---

Roles HR already holds reach Procore resource planning with the rates and types you confirmed, without retyping or guessed values.
See Full Use Case

scenario

-

After NetSuite starts using a new project status, an admin has to key a matching project stage into Procore by hand. If it is missed or spelled differently, the two lifecycles drift apart and portfolio reports no longer agree.

What popdock provides

--

Optionally limit it to one NetSuite status or give a category for new stages. It reads the Procore project stages and the statuses in use on NetSuite projects, then proposes a stage for each status that has none, matching by name while ignoring case and punctuation. Categories are chosen only from values already in Procore, and it says when it cannot choose confidently. Nothing is created until you confirm the exact list. It then reads the stages again to verify. It never creates a duplicate, renames or deletes a stage, or writes to NetSuite.

Business outcome

---

Procore gains the project stages NetSuite already uses, each confirmed and verified, with no duplicates or edits to existing stages.
See Full Use Case

scenario

-

Payroll and project accountants eyeball NetSuite time entries against the rounding rules set up in Procore. Entries that break the rule slip into billing, and weeks that straddle the Procore week start are read against the wrong week.

What popdock provides

--

Give a date range and optionally a project. It reads Procore's timesheet rounding increment and week start day, asking which company applies if there are several configurations, then reads the NetSuite project time entries for the range. Every entry whose duration is not a whole multiple of the increment is flagged, and weeks that cross the week start boundary are noted per employee. You get the settings used, the flagged entries with a reason, the number checked and flagged, and who has the most flags. It skips the test when no rounding is set, never edits an entry, and changes nothing.

Business outcome

---

Time entries that break the rounding rule are found before they reach billing, with the settings used stated plainly.
See Full Use Case

scenario

-

A contractor holding up an RFI may also be owed money by your company, but the RFI is in Procore and the balance is in NetSuite. Nobody sees both at once, so the team chases an answer without knowing they owe the contractor a payment.

What popdock provides

--

Name a Procore project and optionally a balance threshold. It reads the project's open RFIs with the responsible contractor on each, then looks each contractor up as a vendor in NetSuite and reads the balance. You get a table of contractors with open RFIs, overdue RFIs, RFIs with a cost impact, the NetSuite vendor and balance, with balances over the threshold first, and contractors absent from NetSuite listed separately. Matches are by company name only and shown as probable, not confirmed, and several matching vendors are listed rather than picked. It stops on an ambiguous project and changes nothing.

Business outcome

---

The team sees which contractors are both holding up RFIs and owed money, so answers and payments can be handled together.
See Full Use Case

scenario

-

Before awarding a bid, someone searches the NetSuite vendor list name by name for each bidder. A vendor spelled slightly differently is missed, and the award stalls on vendor onboarding that could have started earlier.

What popdock provides

--

Name a Procore project and optionally a minimum bid amount. It reads the bids on the project and looks each bidding vendor up in the NetSuite vendor master, matching by name while ignoring case, punctuation and suffixes such as Inc and LLC. You get a row per bidder marked matched, probable or missing, with the NetSuite ids, email and balance, then the vendors missing from NetSuite as an onboarding to-do list. Probable matches show both spellings. It stops if the name covers more than one project, never adds or updates vendors, and changes nothing.

Business outcome

---

Vendors that need onboarding are known before an award, so a bid is not held up waiting for a NetSuite vendor record.
See Full Use Case

scenario

-

Buyers raise materials purchase orders in Procore against vendors that were never set up in NetSuite. Finance finds out only when the invoice cannot be paid, after searching the vendor list for a name that may be spelled differently.

What popdock provides

--

Optionally name a Procore project, or check all projects. It reads the vendors on Procore materials purchase orders, de-duplicates them and notes which projects use each, then looks each one up in NetSuite and reads the balance. Each vendor is marked as an exact match, a possible match with every candidate listed, or not in NetSuite, and matched vendors with a balance are flagged as owed money. A possible match is never reported as exact. It never creates a missing vendor and changes nothing.

Business outcome

---

Vendors missing from NetSuite are found while orders are being raised, so no invoice waits on a vendor that cannot be paid.
See Full Use Case

scenario

-

An accounts payable clerk checks each Procore subcontractor invoice against NetSuite bills by hand. An approved requisition that never became a vendor bill is found only when the vendor chases payment.

What popdock provides

--

Give a billing date range, and optionally a project. It reads the Procore requisitions billed in the range and looks each vendor invoice number up as a NetSuite vendor bill. Each requisition is classed as billed, billed to a different vendor, missing in NetSuite, ambiguous or not checkable, with approved or paid requisitions that have no bill first. Invoice numbers differing only by leading zeros or dashes are retried once in normalised form, and it says so. Draft and void items are shown but left out of the missing count. It never claims an amount agrees and changes nothing.

Business outcome

---

Approved requisitions with no vendor bill are found and totalled before the vendor chases payment.
See Full Use Case

scenario

-

Resource planners pick job titles in Procore that were typed in by hand and do not follow the roles HR holds in NetSuite. Rates and staffing plans drift, and roles that cannot be staffed or costed are noticed late.

What popdock provides

--

Optionally limit it to one NetSuite location. It reads the Procore resource planning job titles with their type and hourly rate, and the job titles on active NetSuite employees with headcounts, skipping terminated employees. Titles are matched by name while ignoring case, punctuation and plurals, and each NetSuite title is marked matched, possible or missing. Possible matches are never counted as matched. You get a table, the missing titles ordered by headcount, and the Procore titles no employee holds. It reports titles and counts only, with no employee details, and changes nothing.

Business outcome

---

Planners see which roles cannot be staffed or costed in Procore, and which titles nobody holds, from titles and counts alone.
See Full Use Case

scenario

-

Stock counts in the Procore materials list and in NetSuite inventory are compared by eye. Shortages and phantom stock go unnoticed until a crew is waiting for material, and units of measure may not even match.

What popdock provides

--

Name a material, or a project to check its first 25 materials. It reads the Procore availability for each material, including ordered, in transit, damaged and issued, then looks up the same item number in NetSuite and sums quantity on hand and available across locations. A description-only hit is shown as a candidate and no difference is calculated for it. You get a table with the difference and a result of aligned, Procore higher, NetSuite higher or not in NetSuite, then the three biggest differences. It warns when units may differ, never adjusts stock, and changes nothing.

Business outcome

---

Stock differences between the project's materials list and NetSuite inventory are seen before a crew is left waiting for material.
See Full Use Case

scenario

-

Project end dates drift between the Procore schedule and the NetSuite project record because nobody compares them. Revenue and resource forecasts in NetSuite then run on a finish date the site team stopped believing weeks ago.

What popdock provides

--

Name a Procore project and optionally a tolerance in days, 14 by default. It finds the one matching project in Procore, reads its key milestone dates, uses the actual date where one is set, and finds the NetSuite project by project number. You get the milestones beside the NetSuite end date and projected end date, with the completion milestone compared with the projected end and the gap in days flagged when it exceeds your tolerance. It stops on an ambiguous project, reports the project as absent from NetSuite rather than guessing, says so when no completion milestone exists, and changes nothing.

Business outcome

---

End date drift between the site schedule and the NetSuite record is seen with the gap in days, so forecasts can be corrected.
See Full Use Case

scenario

-

A project controls lead lines up Procore project stages with NetSuite project statuses by hand. Mismatched lifecycles mean a project is Active in one system and Pending in the other, and portfolio reports disagree.

What popdock provides

--

Optionally limit it to one NetSuite status. It reads every Procore project stage with its category, and counts NetSuite projects per status. It then proposes a mapping, marking each status as matched, a loose match with the reason given, or no Procore stage, and lists the stages no status maps to. The mapping is stated plainly as a judgment for you to confirm. You get a table with project counts and the unmatched stages and statuses. Nothing is created or renamed in either system.

Business outcome

---

The two project lifecycles are lined up in one table, with every gap named, so portfolio reports can agree.
See Full Use Case

scenario

-

Checking a Procore schedule against NetSuite project tasks by hand means two exports and a lot of eyeballing. Dates and progress drift between the two, and the difference goes unnoticed until a forecast or a bill depends on it.

What popdock provides

--

Name a Procore project and optionally a tolerance in days, seven by default. It reads the project's schedule activities with their start, finish and percent complete, and the NetSuite project tasks with the same fields. Activities are matched to tasks by project name, then task name ignoring case and punctuation. You get a table of matched tasks with both sets of dates, the day difference and the progress difference, then tasks present on only one side and a count of agreements and disagreements. It stops on an ambiguous project, lists duplicates instead of guessing, and changes nothing.

Business outcome

---

Dates and progress that disagree between the Procore schedule and NetSuite tasks are listed with their gaps, instead of drifting unseen.
See Full Use Case

scenario

-

A finance lead asked how much a subcontractor is owed has to open Procore requisitions and NetSuite payables separately. The two figures are built differently, and it is hard to tell whether they agree without matching invoices by hand.

What popdock provides

--

Name a vendor, and optionally a project. It reads the vendor's Procore requisitions and stops to ask which vendor if the name matches more than one. It finds the vendor in NetSuite and reads their balance and open payable items. It totals the current payment due on approved or awaiting payment requisitions, compares that with the NetSuite balance, and matches invoice numbers to open items, listing those on one side only. You get the vendor as each system spells it, both tables, the totals, the difference and a plain statement of whether they agree. It changes nothing.

Business outcome

---

A clear answer on whether Procore and NetSuite agree on what a subcontractor is owed, with the difference and the unmatched invoices.
See Full Use Case

scenario

-

People book time to a NetSuite project without being on the Procore roster, or the roster lists people who never book time. Nobody compares the two, so site access, cost and the real team on a project are out of step.

What popdock provides

--

Name a Procore project and optionally a start date, the first of the current month by default. It finds the one matching project in Procore and reads its people roster, then reads the time booked to the matching NetSuite project and totals it per person. People are matched on first and last name ignoring case. You get people with NetSuite time who are not on the roster with their total duration, roster people with no time, labelled informational since subcontractors do not book time, and the names that matched. It stops on an ambiguous project, and nothing is changed.

Business outcome

---

Time booked by people missing from the Procore roster is found, and the roster is checked against who is really working the job.
See Full Use Case

scenario

-

Sales and estimating each keep their own pipeline, one in NetSuite and one on the Procore bid board. The forecast numbers drift apart, with different values and close dates for the same job, until a review meeting exposes it.

What popdock provides

--

Optionally give a due date window, today to 90 days by default. It reads the Procore bid board projects due in the window and the NetSuite opportunities from 180 days before the earliest due date. A bid is matched to an opportunity by title, or by company with dates within 30 days, and every candidate is listed when a match is ambiguous. You get four lists: matched with value or date differences, matched and consistent as a count, bids with no opportunity, and opportunities with no bid. Value gaps under one percent count as consistent. It changes nothing.

Business outcome

---

Sales and estimating see one pipeline, with value gaps, date gaps and one sided records named before the review meeting.
See Full Use Case

scenario

-

When an opportunity is won in NetSuite, someone in estimating retypes the title, close date and memo into a new Procore bid board project. The bid board has to be searched first for an existing entry, and a retyped date or a second project for the same job is easy to miss.

What popdock provides

--

Give a NetSuite opportunity number and optionally a bid board status, and it reads the opportunity from NetSuite, then checks the Procore bid board for a project with the same name. It stops if the opportunity is not unique or the project already exists. You see the proposed name, status, due date and description, and nothing is created until you say yes. It creates one bid board project and reads it back to report its id and status. It never deletes or updates projects and never writes to NetSuite.

Business outcome

---

Won opportunities become one bid board project with the right close date, with no retyping and no duplicate to clean up.
See Full Use Case

scenario

-

Accounts payable releases subcontractor payments from NetSuite, while the insurance certificates live in Procore. Nobody opens both for every vendor, so a subcontractor with lapsed cover can be paid on the next run without anyone noticing.

What popdock provides

--

Give a number of days to look ahead, 30 by default, and it finds the vendors in Procore whose insurance has expired or expires within that window, keeping the earliest expiry for each. It then looks up each vendor in NetSuite and shows their open payables and due dates, and flags any vendor due for payment after the cover ends. Nothing is paid or held, and amounts are reported only when NetSuite returns them. A vendor it cannot find in NetSuite is reported as not found.

Business outcome

---

Payables reviewers see which vendors are paid on lapsed insurance before the run, without opening both systems vendor by vendor.
See Full Use Case

scenario

-

A project manager chases overdue submittals from contractors without knowing whether those same contractors are waiting on payment. The answer sits in NetSuite, so the chase goes ahead blind and a payment dispute stays hidden behind a late submittal.

What popdock provides

--

Name a Procore project and it finds submittals past their due date that are not approved or closed, then looks up each responsible contractor as a NetSuite vendor and checks for payables already past due. It reports each contractor with their late submittals, days late and past-due items, marking contractors with no NetSuite vendor as unmatched. A link is shown as a possibility, not a cause, and ambiguous vendor matches are left out. Nothing is changed in either system.

Business outcome

---

Project managers chase late submittals knowing which contractors may also be waiting on payment, so the conversation starts in the right place.
See Full Use Case

scenario

-

An accounts payable lead has to find approved Procore requisitions that have no vendor bill in NetSuite, then place a payment hold on each one by hand. A requisition that is missed gets paid with no ledger entry behind it.

What popdock provides

--

Give a project, a billing start date and the vendor id for the hold, and it reads the project requisitions that are approved or awaiting payment, then looks each invoice number up in NetSuite. It lists the ones with no bill, or a bill for a clearly different vendor, and asks you to confirm the exact list. Only then does it place a manual payment hold on each in Procore, and it reports the holds created, skipped and failed. It never holds a requisition that has a bill, edits or releases holds, or writes to NetSuite.

Business outcome

---

Requisitions with no ledger bill are held before payment, one confirmed list at a time, with no bill-backed requisition caught by mistake.
See Full Use Case

scenario

-

Someone building job cost reporting lines up Procore cost codes with NetSuite ledger accounts in a spreadsheet, by eye. Cost code numbering is often not the ledger numbering, so unmapped or misnamed codes make job cost totals disagree with the ledger.

What popdock provides

--

Give a project, or leave it empty for the company cost codes, and a record limit, and it reads the Procore cost codes and the NetSuite accounts. It matches each code to an account by number first, then by name, and marks it matched by number, matched by name, possible match with the reason, or no account. Ambiguous matches are flagged instead of chosen, and a missing match is treated as information, not an error. Budgeted codes with no account are listed first, and nothing is changed.

Business outcome

---

Cost reporting starts from a mapped list, with the budgeted codes that have no ledger account in front of you.
See Full Use Case

scenario

-

Finance finds out that a won bid has no customer in NetSuite only when the first invoice is due. By then someone has to compare the Procore bid board with the NetSuite customer list by hand, working around company suffixes and spelling.

What popdock provides

--

Optionally give a bid board status or a customer name, and it reads the bid board projects from Procore and looks up each distinct customer company in NetSuite. It reports the projects with a matching customer, the ones with only a probable match showing both names, and the ones with no NetSuite customer. Projects with a blank customer are listed separately. Ambiguous matches are listed rather than picked, and nothing is changed in either system.

Business outcome

---

Finance sees which won bids are missing a NetSuite customer before invoicing starts, not when the first invoice is due.
See Full Use Case

scenario

-

A controller ties payments recorded in Procore to the checks and vendor payments in NetSuite by hand each month. A payment posted in one system and not the other is easy to miss and tends to be found at audit time.

What popdock provides

--

Give a payment date range and optionally a project, and it reads the Procore contract payments in that range and the NetSuite vendor payments for the same dates. It matches them on check or payment number with dates within 7 days, and marks each one matched, date differs, missing in NetSuite or not checkable. NetSuite payments with no Procore match are listed as missing in Procore. Amounts are never stated to agree when NetSuite returns none, and nothing is changed.

Business outcome

---

Payments posted in only one system are found at month end, with the missing Procore total in front of you, not at audit.
See Full Use Case

scenario

-

Project managers check estimating project numbers in Procore against NetSuite projects one at a time. Projects with no number or no NetSuite match are found only after costs start posting and have nowhere to land.

What popdock provides

--

Optionally give a status, and it reads the Procore estimating projects and looks up each project number as a NetSuite project. It reports the projects found in both with the Procore and NetSuite status side by side, the projects with a number but no NetSuite project, and the projects with no number at all. A customer name that differs between the systems is flagged. It never guesses a match for a project without a number, and nothing is changed.

Business outcome

---

Unkeyed and missing projects are found while estimating is still open, not after costs start posting.
See Full Use Case

scenario

-

A receiving clerk records a delivery in Procore, but the matching item receipt is never posted in NetSuite. The vendor bill cannot be matched, the invoice sits, and the vendor starts chasing for payment.

What popdock provides

--

Name a Procore materials purchase order and optionally a day window, 3 by default, and it reads the order receipts, skipping drafts and deleted ones and saying how many. It then looks in NetSuite for an item receipt from the same vendor within the window of each receipt date. Each receipt is marked matched, several candidates or no NetSuite receipt, and unclaimed NetSuite receipts are listed. The report states that matches rest on vendor and date only, and nothing is changed.

Business outcome

---

Deliveries with no NetSuite item receipt are found before the vendor bill stalls, with the vendor and date basis made plain.
See Full Use Case

scenario

-

An admin lines up Procore roles and work classifications against HR job titles in a spreadsheet. Titles with no Procore equivalent are found only when someone cannot be assigned the right role or classification.

What popdock provides

--

Optionally give part of a job title, and it reads the Procore roles and work classifications and the job titles of current NetSuite employees, ignoring anyone already terminated. It groups the employees by title, matches each title to a role or classification by name, and ranks the titles with no Procore equivalent by headcount. Procore classifications that no title matched are listed. Only titles and counts are reported, with no contact details, loose matches are labelled as judgment calls, and nothing is changed.

Business outcome

---

Admins see which job titles have no Procore role or classification, ranked by headcount, before someone cannot be set up.
See Full Use Case

scenario

-

Leavers are removed from the ERP, but nobody checks whether they still hold active Procore accounts. Comparing the user list with the employee list by email, one person at a time, is slow, so a former employee can keep access to project data.

What popdock provides

--

Optionally give part of a user name, and it reads the Procore users, then looks up each one in NetSuite by email. It lists active Procore users whose NetSuite employee record shows a past termination date, with their permission template, users with no employee record, and matched users whose job title differs. External staff with no employee record are labelled informational, not errors. Users with no email are listed separately. It never changes a user or an employee.

Business outcome

---

Former employees who still have active Procore accounts are found and listed, without comparing two user lists by hand.
See Full Use Case

scenario

-

Vendor lists in Procore and NetSuite are checked by eye, so duplicates, missing vendors and different contact details go unnoticed. The problem usually appears when a payment fails or a vendor chases an unpaid bill.

What popdock provides

--

Optionally give part of a vendor name, and it reads the Procore vendors, then looks each one up in NetSuite by name and, if that fails, by email. It lists the Procore vendors with no NetSuite match, matched vendors whose email or phone differs, and inactive Procore vendors that still carry a NetSuite balance. Matches found only by email are labelled probable. The two systems vendor ids are never compared, and nothing is changed.

Business outcome

---

Vendor gaps and contact conflicts between Procore and NetSuite are found before a payment fails, not after.
See Full Use Case

scenario

-

Estimate figures live in NetSuite while the team works from the Procore bid board, so someone pastes the total, dates and customer into a note by hand. The note goes stale when the estimate changes, or lands on the wrong project.

What popdock provides

--

Give a bid board project name and a NetSuite estimate number, and it reads the estimate, then finds the one matching bid board project. It stops unless exactly one estimate and one project match, and warns if the customer differs. It drafts a note with the total, date, expected close and customer, using only values NetSuite returned, and shows it with the project name. Nothing is added until you say yes. It adds the one note and reads the notes back to confirm. It never changes anything else in either system.

Business outcome

---

Estimate summaries land once on the right bid board project, built from NetSuite values and confirmed by you first.
See Full Use Case

scenario

-

Site teams are not warned when a vendor working on their project has long past-due payables. Payment disputes then surface as site problems, with slow work or stop-work threats, and nobody had the picture in advance.

What popdock provides

--

Name a Procore project, and it finds vendors that logged manpower in the last 14 days, by default, and checks NetSuite for payables more than 30 days past due. Vendors with an ambiguous NetSuite match are excluded and listed. You see each vendor with the number of past-due items, the oldest due date and the observation it would raise, and nothing is written without a clear yes. It then skips vendors that already have an observation and raises one for each of the rest, keeping amounts out of the name. It never changes NetSuite.

Business outcome

---

Project teams are warned about payment friction with vendors on site, through one confirmed observation per vendor and no duplicates.
See Full Use Case

scenario

-

Someone compares the Procore office list against the NetSuite locations by hand. Names and addresses are typed differently in each system, so offices or locations get missed or mismatched, and sites exist in one system but not the other.

What popdock provides

--

Optionally give a state code, and it reads the Procore offices and the NetSuite locations. It matches each office to a location by name, ignoring case, punctuation and words like Office or Branch, and falls back to the same city and phone digits. Each office is marked matched, possible match with the reason, or missing in NetSuite, and locations no office matched are listed as missing in Procore. A name match with a different state is a possible match, doubtful pairs are flagged instead of merged, and nothing is changed.

Business outcome

---

Sites that exist in only one system are found in one pass, with doubtful matches flagged instead of merged.
See Full Use Case

scenario

-

A billing accountant checks each Procore owner payment application against the NetSuite invoice of the same number by hand. A changed amount or an invoice that was never raised shows up as a customer dispute, not at billing time.

What popdock provides

--

Give a billing date range and optionally a project, and it reads the Procore owner payment applications and looks each invoice number up in NetSuite. It marks each one as agrees within 1.00, billed amount differs, paid amount differs or missing invoice in NetSuite, with the difference shown. Several NetSuite invoices for one number are marked ambiguous, and it refuses to compare amounts across different currencies. It ends with counts and billed totals for each system, and never adjusts either side.

Business outcome

---

Billing differences and missing invoices are found by the accountant before the customer raises them.
See Full Use Case

scenario

-

Project controls staff check by hand that each Procore project points at the right NetSuite job. A missing or mistyped accounting number is not noticed until cost reporting breaks, and project names alone are not safe to match on.

What popdock provides

--

Give a project number, or leave it empty for the first 25 projects, and it reads the Procore projects with their accounting numbers, then looks each accounting number up as a NetSuite project. It marks each as linked, linked by project number only, no accounting number or not in NetSuite, and notes closed or inactive statuses and end dates already past. Several NetSuite projects for one number are marked ambiguous. Numbers are matched only on project or accounting numbers, never names, and nothing is changed.

Business outcome

---

Projects with a missing or wrong accounting number are found and listed for correction before cost reporting breaks.
See Full Use Case

scenario

-

Someone compares the Procore project list with NetSuite projects by hand, and misses jobs that exist in only one system. A project can also be open in one and closed in the other, and costs keep posting to the wrong place.

What popdock provides

--

Optionally give part of a project name, and it reads up to 50 Procore projects and looks each one up in NetSuite by project number. If nothing comes back it tries once by customer, and name-only matches are labelled unconfirmed. It lists Procore projects with no NetSuite match, NetSuite projects found with a different number, and pairs where the active status disagrees. It ends with counts, never guesses from similar names, and never changes either system.

Business outcome

---

Jobs that exist in one system only, or are open in one and closed in the other, are found in one pass.
See Full Use Case

scenario

-

An accountant compares the Procore purchase order list with NetSuite purchase orders line by line across two screens. A commitment that was never entered in the ledger goes unnoticed until the invoice arrives.

What popdock provides

--

Give a project, or leave it empty for every project, and a record limit, 50 by default, and it reads the Procore purchase order contracts and looks each number up as a NetSuite purchase order, retrying with digits only. It marks each contract matched, ambiguous or missing in NetSuite, and flags a NetSuite date more than 30 days from the contract date. Missing contracts are listed first, largest revised amount first. It compares existence, vendor and date only, never claims an amount matches, and changes nothing.

Business outcome

---

Purchase orders that were never entered in NetSuite are found before the invoice arrives, with the largest first.
See Full Use Case

scenario

-

Matching time and material hours in Procore to project time in NetSuite means totalling each person in two systems and comparing the two lists. It is slow, duration units differ, and unbilled or mismatched hours slip through.

What popdock provides

--

Name a Procore project and optionally a date range, the last 30 days by default, and it totals the Procore time and material timecard hours per person, ignoring deleted timecards. It totals the NetSuite project time per employee for the same window, converting hours and hh:mm and saying which form it saw. It then matches people by full name and shows the difference per person and overall, largest gap first, with people on one side only. People who share a name are listed, not merged, and nothing is changed.

Business outcome

---

Hour gaps between field timecards and the ledger are found per person, so unbilled or mismatched time is caught before invoicing.
See Full Use Case

scenario

-

A resource planner staffs projects in Procore while finance closes the same projects in NetSuite. Nobody lines the two lists up, so people get planned onto a job that finance has already finished.

What popdock provides

--

Optionally give a project number, and it reads the Procore workforce planning projects, 25 by default, and looks each project number up in NetSuite. It marks each project linked, not in NetSuite or no project number. For linked projects it flags Procore active but NetSuite closed or past its end date, a Procore closed date but NetSuite still open, and 100 percent complete with a future NetSuite end date. It matches on project number only, refuses to choose between duplicates, and changes nothing.

Business outcome

---

Planners see which staffed projects are missing or closed in NetSuite, before people are planned onto a finished job.
See Full Use Case

scenario

-

Estimators awarding a package have no quick view of the history each bidder has in the accounting system. They ask finance for balances, purchase orders and bills, and then wait, or award without the picture.

What popdock provides

--

Name a Procore project and optionally a start date, 12 months back by default, and it reads the bidding vendors on the project. It looks each one up in NetSuite and, for a single matching vendor, reads the purchase orders and vendor bills since the start date. You get a section per bidder with the match status, balance, counts and the most recent document and date of each, ending with the bidders new to NetSuite and those with the most history. A vendor missing in NetSuite is reported as new, amounts are never invented, and nothing is changed.

Business outcome

---

Award decisions are made with each bidder NetSuite history in front of the estimator, without waiting on finance.
See Full Use Case

scenario

-

Confirming that every vendor working on site is being billed means comparing the daily manpower logs in Procore with the vendor bill ledger in NetSuite by hand. A vendor on site for weeks with no bill is easy to miss.

What popdock provides

--

Name a Procore project and optionally a date range, the last 30 days by default, and it lists the vendors that logged manpower, with their logs and distinct days on site. It looks up each vendor in NetSuite for bills in the same window, and where there are none it checks a window starting 90 days earlier so late billing shows. You get a table grouped into billed, billed only in the wider window and not billed. Vendors that match several NetSuite vendors are listed, not combined, and nothing is changed.

Business outcome

---

Vendors on site with no bills are found in one pass, with late billing told apart from none.
See Full Use Case

scenario

-

A buyer checks a materials purchase order in Procore and again in NetSuite, line by line. A line whose quantity was changed in only one place is easy to miss, and a missing order is found only when the delivery or the bill arrives.

What popdock provides

--

Name a Procore materials purchase order and optionally a project, and it finds that order and reads its lines. It looks up the NetSuite order with the same document number and reads its lines, stopping if the Procore order is ambiguous. It lists lines only in Procore, lines only in NetSuite and lines whose quantity differs, compares vendor and line counts, and ends with a verdict: aligned, differences found or not in NetSuite. A vendor-only hit is never treated as a match, and nothing is changed.

Business outcome

---

Quantity and line differences between a Procore order and its NetSuite order are found in one check, before delivery or billing.
See Full Use Case

scenario

-

Answering a question about one vendor means opening Procore for their status and insurance, then NetSuite for their bills and open items. The two views are put together by hand, and conflicts between them are easy to miss.

What popdock provides

--

Name a vendor and optionally how many days of bills to look back, 180 by default, and it finds the one matching Procore vendor, stopping if more than one matches. It reads the vendor insurance, finds the vendor in NetSuite by name then email, and reads their bills and open items. You get the Procore status and group, insurance expiry, NetSuite balance, bills in the period, open items and the earliest due date. It ends with conflicts such as an inactive vendor with open payables. It says when no insurance exists, never merges NetSuite vendors, and changes nothing.

Business outcome

---

One vendor, seen across Procore and NetSuite in one answer, with conflicts called out.
See Full Use Case

scenario

-

A rental vendor on a Procore equipment record is missing from Ramp, so someone reads the vendor off the record, searches Ramp under a couple of spellings, and retypes the country and contact email. A search under the wrong spelling and the vendor is created twice.

What popdock provides

--

Give an equipment ID, the vendor's country and a contact email, and it reads the equipment record in Procore to get the rental vendor, then searches Ramp for that name, exact first and then partial. If any vendor matches, or the equipment has no vendor, it stops. You see the name, country and email, and nothing is created until you say yes. It creates the vendor once, does not retry on an error, and checks Ramp afterwards to report the new vendor id.

Business outcome

---

A rental vendor reaches Ramp once, with details you approved, so equipment spend can be paid without a duplicate vendor to clean up.
See Full Use Case

scenario

-

Setting up a Procore vendor in Ramp means copying its name, email and state across by hand and picking a country from memory. A typo in the email or a slightly different name gives you a second vendor, and payments end up split between two records.

What popdock provides

--

Give a vendor name and a country, and it finds the one matching vendor in Procore, using the name, contact email and state on that record. It stops if several vendors match, if the vendor is inactive or if there is no email, and it never invents an email, state or country. It then searches Ramp for the name. You see the exact values, including the Procore vendor ID it will store as the external ID, and nothing is created until you confirm. It creates the vendor once and checks Ramp to report the new ID.

Business outcome

---

Procore vendors are created in Ramp once, with their own details and a link back to the Procore record, so nobody retypes or duplicates them.
See Full Use Case

scenario

-

Once a bid is accepted, someone retypes the winning vendor into Ramp so it can be paid. If the name is spelled differently from an existing Ramp vendor, such as Inc against Incorporated, the search finds nothing and a duplicate is created.

What popdock provides

--

Give the bidder name, a contact email, a country and the project, and it first confirms in Procore that the vendor actually bid on that project. It then searches Ramp by name and by legal name and stops on any plausible match rather than creating a duplicate. You see the exact name, email and country, and nothing is written until you say yes. It never guesses the email or country, creates the vendor once without retrying, and then checks Ramp to report its ID and status.

Business outcome

---

Awarded bidders become Ramp vendors once, after the bid is confirmed, without a near-duplicate left behind by a spelling difference.
See Full Use Case

scenario

-

Site names used on Procore punch items have to match locations in Ramp, so someone lists the distinct sites, compares them with the Ramp locations and keys the missing ones in one at a time. Typos and near-duplicates such as Site A and Site A creep in along the way.

What popdock provides

--

Name a project, and optionally a Ramp legal entity, and it collects the distinct top-level site names from the project's punch items, then compares them with your Ramp locations ignoring case and spacing. You see the list of missing sites and approve it. Only the approved names are created, one at a time, and a name that differs from an existing location only by case or spacing is never added. Ramp is read again afterwards to confirm each location exists, and a failed create is reported without a retry.

Business outcome

---

Every site named on punch items gets a Ramp location once, so spend can be coded to it without typing each name in by hand.
See Full Use Case

scenario

-

Projects with bid packages due soon each belong to a Procore office, and that office needs a matching location in Ramp. Comparing the two by eye means a missing location is found only when someone cannot code spend to it.

What popdock provides

--

Give a date range, or let it use the next 30 days, and it lists the projects with bid packages due in that window and the office on each. It reads your Ramp locations and compares the two, ignoring case and surrounding spaces. The report shows offices found in both, offices with no Ramp location and the projects that use them, and projects with no office. Near matches such as Dallas and Dallas Office are reported separately as possible matches. Nothing is changed in either system.

Business outcome

---

Missing office locations in Ramp are found before bidding projects start spending, not when a payment cannot be coded.
See Full Use Case

scenario

-

Once a bidder is chosen, someone has to find out whether Ramp can actually pay them. That means finding the vendor, then opening its bank account, contact and agreement screens, and the gaps surface only when a payment is due and the vendor has to be chased.

What popdock provides

--

Name a bidder, and a project if you want to narrow it, and it confirms the bid in Procore, then finds the vendor in Ramp. It checks whether the vendor is active, has a bank account on file with a default, has a contact email and has an agreement covering today. The result is a checklist marked Pass, Fail or Unknown with what to fix. It shows only the last four digits of any account number, stops on an ambiguous vendor name and never edits bank accounts.

Business outcome

---

You know before award or first payment which bidders are ready to be paid in Ramp and which need chasing, with no bank details exposed.
See Full Use Case

scenario

-

A finance lead checks the currency set on the Procore company against the currency of each Ramp business entity by opening both admin screens. A mismatch is invisible until payments are converted and the numbers stop agreeing.

What popdock provides

--

Name a Procore company and, if you like, part of an entity name. It finds the one matching company and reads its currency setting, then reads the Ramp business entities and compares each entity's currency with it. The primary entity is called out first because it matters most. The report shows the Procore currency, each entity with a match or mismatch, and which entities would need conversion when Procore commitments are paid from Ramp. A mismatch is reported as a finding, and nothing is changed.

Business outcome

---

Currency mismatches between Procore and Ramp are known before payments are converted, with the primary entity checked first.
See Full Use Case

scenario

-

A controller has to confirm that the payments logged against a Procore commitment really went out in Ramp. That means opening both systems and matching invoice numbers and amounts line by line, and a payment paid in one place but not the other is easy to miss.

What popdock provides

--

Give a commitment number, a project and, if you like, a start date for payments (the default is the last 90 days). It reads the payments recorded in Procore and the commitment's totals, then looks for each payment in Ramp by amount and invoice number. Each payment is marked Paid in both, Paid in Procore only, Paid in Ramp only or Amounts differ, and the Procore total is compared with the Ramp total. It stops if the commitment number matches more than one project, never assumes which system is right, and changes nothing.

Business outcome

---

You see which commitment payments are missing or different in Ramp, with both figures shown and no write access needed.
See Full Use Case

scenario

-

New offices and yards get added to resource planning in Procore, but nobody adds them to Ramp, so spend cannot be coded to them. The gap is found when a card transaction has nowhere to go.

What popdock provides

--

Give a group name, or leave it empty to check every group, and it reads the Resource Management planning groups with their city, state, country and time zone. For each group it searches Ramp locations by name, then by a partial name to catch spelling differences. The report has two lists: groups with an exact Ramp location, and groups with no exact match, with any close name and the group's city and country so someone can create the location. A close name is never treated as a match, and nothing is created.

Business outcome

---

New offices and yards are caught as missing Ramp locations early, with the details needed to create them.
See Full Use Case

scenario

-

Rented equipment comes back, or is extended, without anyone checking that its rental vendor is set up and under agreement in Ramp. Someone lists the rentals ending soon, looks each vendor up, then hunts for an agreement that runs past the end date.

What popdock provides

--

Give a number of days (the default is 60) and, if you like, an equipment category. It finds rented equipment whose rental ends in that window and lists any item with no vendor on record. For each vendor it checks Ramp for an active vendor record and its spend over the last 365 days, then looks for an agreement that runs past the rental end date. The report has one row per rental with Ramp status and agreement status. It never creates or updates a vendor or agreement, and it reports unmatched vendors rather than guessing.

Business outcome

---

Rentals ending soon are checked for an active vendor and a covering agreement in Ramp, before they are extended or returned.
See Full Use Case

scenario

-

Controllers want spend coded the way projects are organised, but nobody checks whether the Procore programs, project types, regions and trades exist in Ramp as departments or accounting fields. Comparing four sets of names across two admin screens is slow, so the gaps stay.

What popdock provides

--

Name a Procore company and, if you like, one dimension: programs, project types, regions or trades. It reads those values, then reads the Ramp departments and accounting fields and matches each Procore name to a department or accounting field, ignoring case. For each dimension it reports how many values there are, how many matched and which did not, with the largest unmatched programs first and the least covered dimension at the end. It compares field names only, not the values inside a field, and says so. It never adds departments or fields.

Business outcome

---

You see how well Ramp coding mirrors how your projects are organised, and which dimension to fix first.
See Full Use Case

scenario

-

Before approving a subcontractor's next payment, a project manager checks the contract value in Procore against what the vendor has already billed in Ramp. With two systems and several requisitions, a bill for a different job slips in and the contract is quietly overspent.

What popdock provides

--

Give a subcontract or work order number and a project. It reads the contract value, invoiced and remaining balance from Procore, then the requisitions and claims for that commitment. It finds the vendor's bills in Ramp that match the requisition invoice numbers and notes any other bills for the vendor, which may belong to another job. The report gives contract value, total claimed and total billed, bills with no requisition and requisitions with no bill, and a verdict of Within contract, Close to limit or Over contract. Both systems are read only, and it asks before combining two possible spellings of a vendor.

Business outcome

---

You see whether a subcontractor's billing is within the contract before you approve the next payment, with unmatched bills left for review.
See Full Use Case

scenario

-

Spotting spend filed during someone's planned time off means reading time off entries in Resource Management, finding the same person in Ramp and checking their reimbursements against each date range. Done by hand across a team, it rarely happens.

What popdock provides

--

Give a date range, or let it use the next 30 days, and a maximum number of people (the default is 25). It reads planned time off from Resource Management and finds each person in Ramp through their employee number. For each person it looks for reimbursements dated inside the time off. The report lists each person with their time off dates and reason and each reimbursement date and amount, then lists people with no Ramp user. Items are presented for review, not as findings, and a match is never guessed. Nothing is changed.

Business outcome

---

Reimbursements dated inside planned time off are surfaced for a human to review, without cross-reading two systems.
See Full Use Case

scenario

-

Insurance expiries are tracked in Procore while payments go out through Ramp, so nobody sees a vendor being paid on an expired policy. Finding it means filtering insurance by date, then searching Ramp for each vendor's spend and agreements.

What popdock provides

--

Give a number of days ahead (the default is 30) and, if you like, a vendor name. It finds vendors whose Procore insurance has expired or expires inside that window, using each vendor's latest policy. For each one it looks the vendor up in Ramp and shows spend over the last 30 and 365 days and any agreements with their end dates. Vendors with spend in the last 30 days and an expired policy are marked Urgent, and vendors with no Ramp record are listed separately. It recommends actions but changes nothing, and it skips spend figures when a vendor name matches more than one Ramp vendor.

Business outcome

---

You see which vendors are being paid on lapsed insurance, ranked by recent Ramp spend, so you can act before the next payment.
See Full Use Case

scenario

-

Project teams track commitments in Procore while buyers raise purchase orders in Ramp. When a change order grows the contract but the Ramp purchase order stays at the old value, nobody notices until the bill arrives.

What popdock provides

--

Name a Procore project and, if you like, a commitment status (the default is Approved). It reads each purchase order commitment with its revised amount, invoiced and payments, then finds the Ramp purchase order with the same number, confirming the match rather than trusting a name search. The report gives a row per commitment with the Procore and Ramp values and a verdict of In step, Value differs, Billed differs or Not in Ramp, with the rows needing attention first and the total value gap. It lists ambiguous matches instead of picking one, notes that Procore revised amounts include change orders, and changes nothing.

Business outcome

---

You see where a Ramp purchase order has fallen out of step with its Procore commitment, usually a change order that was never carried across.
See Full Use Case

scenario

-

Cost codes are set up on projects in Procore and GL accounts in Ramp, usually by different people. Invoices get coded to codes that do not exist on the other side, and spend reports will not reconcile until someone compares thousands of codes line by line.

What popdock provides

--

Name a Procore project, and say whether to check only budgeted cost codes (the default). It reads the project's cost codes and the GL accounts in Ramp, then matches each code by code number first, ignoring spaces, dashes and leading zeros, and by name where the code does not match. The report opens with how many cost codes were checked and how many matched cleanly, then lists each exception as No Ramp account, Name match only or Inactive in Ramp. A GL code shared by several cost codes is reported as shared, not as a mismatch. It recommends fixes and says which system each belongs in, but changes nothing.

Business outcome

---

You get a short list of cost codes with no clean Ramp match, so spend coded in Ramp reconciles back to Procore.
See Full Use Case

scenario

-

Accounts payable staff compare a Procore project vendor roster with the Ramp vendor list by eye. Vendors with slightly different names, such as a missing Inc or LLC, get missed or created twice.

What popdock provides

--

Name a project and, if you like, a date to include only vendors created or updated since then. It reads the project's active vendors from Procore, drops inactive ones and tells you how many. Each remaining vendor is looked up in Ramp, first by exact name and then by abbreviated name, and a partial hit is treated only as a possible match. The report has a row per vendor with match type and 365 day Ramp spend, then lists vendors not in Ramp, in Ramp but inactive, and possible matches for a person to confirm. It lists every candidate rather than picking one and changes nothing.

Business outcome

---

You know which project vendors are missing or inactive in Ramp before invoices arrive, with doubtful names left for a person to confirm.
See Full Use Case

scenario

-

Cost impacts on open punch items are tallied by hand, and they are rarely checked against the purchase orders raised for the same project. The punch work might be covered, or nothing has been raised, and nobody can say which.

What popdock provides

--

Name a Procore project and, if you like, the text to search for in Ramp purchase order names (the default is the project name). It totals the cost impact of open punch items, ignoring closed ones, grouped by category and cost code, and reads the matching Ramp purchase orders with their amount, spend and billing status. The report gives total open punch cost impact, total purchase order amount and total spend, the five largest cost categories and the purchase orders found. It says whether any purchase order plausibly covers the punch work without asserting a link the data does not show, compares one currency at a time and changes nothing.

Business outcome

---

You see how much open punch work costs and whether any Ramp purchase orders plausibly cover it, with no link asserted that the data does not support.
See Full Use Case

scenario

-

An access review compares Procore company roles with Ramp roles and who holds each of them across two admin screens. Role drift, such as a Ramp role with active users and nothing like it in Procore, goes unnoticed for months.

What popdock provides

--

Name a Procore company and, if you like, part of a role name. It reads the company roles in Procore, then the Ramp roles and counts the active Ramp users holding each, keeping only counts and not names. Roles are matched on name ignoring case, and where there is no name match it suggests the closest Ramp role as a suggestion only. The report lists Ramp roles with active users and no Procore counterpart first, then the rest, and ends with Procore roles that have no Ramp counterpart. It says plainly that a mismatch is a question to ask, not proof of a problem, and it changes no roles or users.

Business outcome

---

An access review starts from a ranked list of Ramp roles with no Procore counterpart, using counts rather than names.
See Full Use Case

scenario

-

Admins export user lists from Procore and Ramp and compare email addresses in a spreadsheet. People who have left stay active in Ramp, and anyone with a differently spelled email shows as missing.

What popdock provides

--

It reads Procore active and inactive users, optionally limited to a company, and the users in Ramp, then matches them on lower-cased email only. The report has three tables: active in Procore and not in Ramp, inactive in Procore and still active in Ramp, and matched users whose names differ. It ends with counts and the number of users that could not be matched because they have no email. If two users share an email it lists both rather than picking one, it never treats a name match as a match, and it changes nothing.

Business outcome

---

Leavers still active in Ramp and people missing from it are found from one email match, not a spreadsheet exercise.
See Full Use Case

scenario

-

People who leave a construction firm stay active in Ramp because nobody cross-checks the Procore directory. Someone exports both user lists, matches emails and logs in to Ramp to switch users off one at a time, leaving spend access open in the meantime.

What popdock provides

--

Optionally give a date to look at only users made inactive since then. It reads the inactive Procore users and their emails, then finds them in Ramp on a lower-cased email match, leaving out anyone who is not active or already has a deactivation scheduled and saying why. You see a table with name, email, Ramp role, status and the Procore date, and you choose which rows to deactivate, since a general yes is not accepted. It deactivates each approved row once, reads each user again to report the resulting status, never acts on a name-only match and carries on if one fails.

Business outcome

---

Leavers lose Ramp access soon after they go inactive in Procore, and only the rows you approved are changed.
See Full Use Case

scenario

-

When an approved Procore requisition has no vendor bill in Ramp, someone retypes the vendor, amount and dates into a new Ramp bill. The same invoice gets keyed twice, or with the wrong amount, because nobody checked whether a bill or draft already existed.

What popdock provides

--

Give the vendor invoice number, the project and, if there is more than one Ramp business entity, which one to use. It reads the requisition from Procore and stops if it is not Approved or matches several rows. It checks Ramp bills and draft bills for the same vendor, amount and invoice number and stops on a duplicate, and it finds exactly one Ramp vendor and the entity. You see the vendor, entity, invoice number, amount and dates, and nothing is written until you say yes. It creates one draft bill with a line for the amount due, never creates vendors and never submits or approves the bill.

Business outcome

---

An approved requisition becomes one draft bill in Ramp with the right amount, with no duplicate and no approval taken on your behalf.
See Full Use Case

scenario

-

A bidder's vendor agreement can lapse while their bid is still open, and nobody tells the estimating team until the work is awarded. Finding it means listing bidders in Procore, checking agreement end dates in Ramp and writing a task for each one.

What popdock provides

--

Name a Procore estimating project, a number of days (the default is 60) and optionally who the tasks are assigned to. It finds the project's bidders and the Ramp agreements that end inside that window, and skips vendors that already have an estimating task. You see the tasks it would create, each with the vendor and the agreement end date, and nothing is written until you say yes. It creates one estimating task per vendor, reports a failed task and carries on, never edits Ramp agreements and skips agreements that have already ended unless you say otherwise.

Business outcome

---

Estimating hears about expiring vendor agreements while the bid is open, with one task per vendor and no duplicates.
See Full Use Case

scenario

-

Checking that the people who manage RFIs on a project also have active Ramp accounts means exporting two user lists and matching names in a spreadsheet. Common names produce false matches and people with no account are overlooked.

What popdock provides

--

Name a Procore project and, if you like, a Ramp role to filter by. It lists the potential RFI managers on the project with their name and login email, then looks each one up in Ramp by first and last name. When several Ramp users share a name it picks the one whose email equals the Procore login, and otherwise marks the person as ambiguous. The report gives each person's match as exact, ambiguous or none with their Ramp status and role, counts in each group and the people with no Ramp user or an inactive one. A match is exact only when the emails agree, and nothing is changed.

Business outcome

---

Project RFI managers who have no active Ramp account are identified in one list, with only email-confirmed matches counted as exact.
See Full Use Case

scenario

-

Before a bidder is awarded work, someone copies the vendor names off the bid list and searches Ramp for each one. A name spelled differently looks like a missing vendor, and the same vendor shows up twice once someone adds it.

What popdock provides

--

Name a Procore project and, if you have more than one, the company. It reads the bids on the project and stops if the project name is ambiguous or there are no bids. For each distinct bidding vendor it searches Ramp by name, and by legal name if that finds nothing. One table shows the vendor name from Procore, the Ramp vendor name, active status and a verdict of Matched, Several matches, Inactive in Ramp or Missing from Ramp, with the missing vendors listed again. It ignores case, punctuation and suffixes such as LLC or Inc, lists every candidate instead of picking one, and changes nothing.

Business outcome

---

You know before award which bidders are already set up in Ramp, which are inactive and which are genuinely missing.
See Full Use Case

scenario

-

Job-cost accountants check each direct cost booked in Procore against Ramp bills and card transactions by eye, searching Ramp vendor by vendor and amount by amount. A cost booked to a job with no real payment behind it is usually found at month-end close.

What popdock provides

--

Give a project and an optional start date, and it reads the project's Procore direct costs, then looks in Ramp for a bill and, failing that, a card transaction with the same vendor and amount. Card matches count only when the amount is the same and the date is within 7 days, otherwise they are marked Possible. If an amount fits several Ramp items it lists them and picks none. Nothing is changed in either system, and you get the total of the unmatched costs.

Business outcome

---

Direct costs with no payment behind them are found while the period is open, with no changes made to Procore or Ramp.
See Full Use Case

scenario

-

Keeping the Resource Management roster and Ramp users in step means comparing two people lists by hand, usually by name. People get scheduled on jobs with no Ramp account, and others keep an account after they leave.

What popdock provides

--

Give an optional status and a head count, and it reads the people in Procore workforce planning, sets aside anyone with no employee number, then looks each employee number up in Ramp. You get three lists: people with no Ramp user, people whose Ramp user is inactive or due to be deactivated, and people with an active user. If a number matches several Ramp users it lists them and picks none. Nothing is added or deactivated.

Business outcome

---

Planning people with no Ramp account, and leavers who still have one, are found in one read, with no accounts changed.
See Full Use Case

scenario

-

Accounts payable compare each Procore requisition with the vendor's bill in Ramp by hand, searching by vendor and amount. A missing bill or a keyed amount that differs is usually found only when the vendor calls about payment.

What popdock provides

--

Give a project and an optional billing start date, and it reads the project's Procore requisitions, then finds the Ramp bill for each by vendor and amount, comparing invoice numbers itself and widening the amount range once if nothing is found. It stops if the project name fits several projects. Vendor matches it is unsure of are marked Possible. You get a verdict per requisition, counts and the dollar gap, and nothing is changed.

Business outcome

---

Missing bills and amounts that differ are found before the vendor calls, with the dollar gap between the systems stated.
See Full Use Case

scenario

-

A new hire is added to Resource Management, but nobody remembers to give them a Ramp account, or someone creates a second one because the first was never found. Checking by hand means looking the person up in Procore, then searching Ramp by number and by name.

What popdock provides

--

Give an employee number, an email and a name, and it reads the person in Procore workforce planning and stops if they are not found or not active. It then checks Ramp by employee number and by name and stops if a user already exists. You see the email, name and proposed role, and nothing is created until you say yes. It creates the Ramp user once, then looks the user up again and reports the role and status.

Business outcome

---

New planning hires get one Ramp user each, with a confirmed role, and no duplicate accounts to clean up.
See Full Use Case

scenario

-

Adding a new starter to Ramp usually means opening Procore, copying their name and email, then retyping them in Ramp and guessing the role and department. Typos, wrong roles and a second user for someone already in Ramp follow.

What popdock provides

--

Give a Procore user name, a Ramp role and optionally a department, and it finds the one matching Procore user, refusing inactive users or ones with no email. It checks Ramp for the same email and stops if the user exists, and resolves the department if you named one. You see the name split, email, role and department, and nothing is created until you confirm. It creates the user once with the role exactly as given, then reads Ramp again to report the id and status.

Business outcome

---

New Ramp users are created once from Procore details, with the role you chose, and no duplicate or mistyped accounts to fix.
See Full Use Case

scenario

-

When a vendor is owed overdue money, the site team often finds out when work slows down. Nobody logs it against the project, because the bills sit in Ramp and the project is run in Procore.

What popdock provides

--

Give a vendor, a project and how many days overdue counts, and it checks Ramp for the vendor and its unpaid bills past that point. It stops if the vendor name fits several vendors or nothing is overdue. It then finds the vendor as an assignee on the Procore project. You see the overdue bills and the proposed observation name, and nothing is created until you confirm. It creates one observation, reads it back and reports its number. Ramp is never written to and no bank details are included.

Business outcome

---

Overdue vendor payments are logged against the project as one confirmed observation, so the site team sees them without payment data being exposed.
See Full Use Case

scenario

-

Materials purchase orders are raised in the field, and nobody confirms the supplier exists and is active in Ramp, or that a matching purchase order is being billed there. Checking means opening each order, then each vendor and each Ramp purchase order.

What popdock provides

--

Give a project and optionally a status, and it reads the project's materials purchase orders from Procore, stopping if the project name fits several projects. It checks each supplier in Ramp for existence, active state and trailing spend, then looks for a Ramp purchase order with the same name and notes billing and receipt status and amounts. Suppliers missing from Ramp are listed at the end. Anything matching several Ramp records is listed, never chosen, and nothing is changed.

Business outcome

---

Orders with a missing or inactive supplier, or no Ramp purchase order, are found before bills arrive, with nothing created or changed.
See Full Use Case

scenario

-

Someone compares the office list in Procore with the locations in Ramp by hand, matching names that are spelled differently. An office added in one system quietly never reaches the other.

What popdock provides

--

Give a company and optionally part of an office name, and it reads the company's offices from Procore and the locations from Ramp, stopping and saying which side is empty rather than reporting everything as a mismatch. It matches names ignoring case, punctuation and words like office, branch and HQ, and marks a location named after the city as a probable match. You get exact, probable and unmatched lists on each side, with counts. It recommends changes but never makes them.

Business outcome

---

Offices missing from Ramp and locations missing from Procore are listed in one read, with changes recommended and none made.
See Full Use Case

scenario

-

To judge a bidder's history, someone opens Ramp for each vendor on a Procore bid list and checks spend and unpaid bills. It is slow, so it is rarely done for every bidder.

What popdock provides

--

Give a project and optionally how many days ahead to look, and it reads the bidders on the Procore project, stopping if the project name fits several projects. For each bidder it finds the Ramp vendor and reports spend over 30 days, 365 days and all time, then its unpaid bills due in the window, sorted by due date. Bidders with no Ramp match are labelled new to Ramp, not zero spend. Several matching vendors are listed and never combined, and nothing is changed.

Business outcome

---

Every bidder's Ramp history and upcoming bills are visible before award, with unknown vendors reported as new rather than as zero spend.
See Full Use Case

scenario

-

Vendors with open field observations are not checked against the finance system. A vendor that is inactive in Ramp, or has unpaid bills, can hold open observations for months before anyone connects the two.

What popdock provides

--

Give a project and optionally a due date, and it lists the open observations from Procore and collects the vendors they are assigned to. For each vendor it checks Ramp for a record, active status, spend over the last year and unpaid bills. You get a row per vendor with open count, oldest due date and Ramp findings, and vendors that are inactive in Ramp but still have open observations are flagged. Unassigned observations are counted separately, and nothing is changed.

Business outcome

---

Vendors with open observations that are inactive or missing in Ramp are flagged, so follow-up goes to people who can actually respond.
See Full Use Case

scenario

-

Project teams cannot see how much of what they spend with roster vendors goes through Ramp without pulling reports from both systems. Matching vendor names across the two takes a while, so it is rarely done.

What popdock provides

--

Give a project and optionally a high-spend threshold, and it confirms the project in Procore, stopping if the name fits several projects, then reads the project's vendor roster. For each active vendor it finds the Ramp vendor and reports spend over 30 days, 365 days, year to date and all time. Vendors are flagged as high spend, no spend or not in Ramp, and a name matching several Ramp vendors is left blank. The report says at the top that Ramp spend is company-wide. Nothing is changed.

Business outcome

---

You see which roster vendors carry large Ramp spend, or none, with the company-wide caveat stated so the figures are not misread.
See Full Use Case

scenario

-

A project manager chasing late RFIs has no idea which of those contractors are also waiting on payment, because that lives in Ramp. Follow-ups go out without the context, and a contractor owed money gets the same email as everyone else.

What popdock provides

--

Give a project and optionally a due date, and it lists the Procore RFIs past due and not closed, stopping if the project name fits several projects. For each responsible contractor it looks for an exact match in Ramp and finds unpaid bills and spend over the last year. Partial matches are flagged as possible and not totalled, and totals are grouped by currency. The report ends with contractors both late on RFIs and owed money. Nothing is changed.

Business outcome

---

Late RFI follow-ups go out knowing which contractors are also owed money, so you chase with the right context.
See Full Use Case

scenario

-

To judge how much a vendor is owed, someone pulls Ramp spend, open bills and credits, then separately digs through Procore requisitions for the project. The two never line up on one page, and a figure copied between them loses track of which system it came from.

What popdock provides

--

Give a vendor and a project, and it finds the vendor in Ramp, stopping if the name fits several vendors, then reads year to date and yearly spend, unpaid bills and unused vendor credits. It then reads that vendor's requisitions on the Procore project, asking you to confirm if the name is spelled differently. The report labels every figure with its source system and ends with a net exposure sentence. Nothing is changed in either system.

Business outcome

---

One page shows what a vendor has claimed, what Ramp still owes and what credits remain, with every figure labelled by system.
See Full Use Case

scenario

-

Late submittals are chased without knowing whether the contractor is owed money. The submittal log is in Procore and the payables are in Ramp, so checking means two systems and a lot of name matching.

What popdock provides

--

Give a project and optionally a submittal status, and it reads the matching Procore submittals, stopping if the project name is ambiguous. For each responsible contractor it looks the vendor up in Ramp and reads year to date spend, unpaid bills and any past their due date. You get a row per contractor with the submittal count, earliest due date, overdue amount and spend, highest overdue first, plus a line on whether late submittals and overdue payables go together. Contractors not in Ramp are reported as not paid through Ramp. Nothing is changed.

Business outcome

---

You can see which contractors are late on submittals and overdue on payment before chasing, with no changes made in either system.
See Full Use Case

scenario

-

When a bid is won, someone retypes the customer from the Procore bid board into Rillet. It is forgotten, or entered twice under a slightly different name, and the first invoice then has no customer to bill.

What popdock provides

--

Give a bid status, which defaults to Won, and optionally one customer, and it reads the customer names from Procore bid board projects. It checks each against Rillet customers by name and invoicing name, ignoring case, punctuation and endings like Inc and LLC, and lists close matches apart without creating them. You see the customers that would be created, and nothing is written until you confirm the list. Each one is created with its name only, never an address or payment terms, and you get created, skipped and failed lists.

Business outcome

---

Won customers reach Rillet once, under the name Procore holds, with close matches left alone so no duplicate customer records are created.
See Full Use Case

scenario

-

A new supplier appears on a Procore materials purchase order, and someone has to key the vendor into Rillet before a bill can be booked. A near-duplicate spelling creates a second vendor record, and the bill is posted to the wrong one.

What popdock provides

--

Give a project and optionally one vendor, and it reads the vendors on the project's Procore materials purchase orders, stopping if the project name fits several projects. It compares them with Rillet vendors, ignoring case, punctuation and endings like Inc and LLC, and lists close matches as possible duplicates that are never created. You see what would be created and what was left out, and nothing is written until you confirm. It creates each vendor by name only, then re-reads Rillet to verify and tells you what to complete.

Business outcome

---

Suppliers on materials orders reach Rillet once, verified after creation, with no near-duplicate vendors and the remaining details left for you to complete.
See Full Use Case

scenario

-

A vendor turns up in the site logs, on delivery, equipment or manpower, but is missing from the ledger. Someone keys it into Rillet from memory, with typos, and sometimes a duplicate of a vendor already there.

What popdock provides

--

Give a project, a start date and optionally default payment terms, and it collects the distinct vendor names from the project's Procore manpower, equipment and delivery logs. It compares them with Rillet vendors, treating exact and partial matches as not missing and showing partial ones for you to judge. You see the vendors with no match, are told address, email and tax details will be blank, and nothing is written until you answer. Each confirmed vendor is created by name, then Rillet is read again to confirm it appears.

Business outcome

---

Vendors seen on site are set up in Rillet once, from confirmed names only, with no invented addresses or tax details.
See Full Use Case

scenario

-

Vendors added in Procore are re-keyed into Rillet by hand. Some are forgotten, and others are entered twice because the second person did not spot the first record.

What popdock provides

--

Give an optional part of a vendor name, and it reads the active Procore vendors and checks them against Rillet by tax id, by email and by name, ignoring case, punctuation and endings like LLC and Inc. It checks Rillet again for each vendor it thinks is missing. You see a table of the vendors it would create, capped at a batch size, and nothing is written until you confirm which to create. Each is created once, never retried on an error, and Rillet is then read again to verify the result.

Business outcome

---

Active Procore vendors reach Rillet once, in capped batches you approve, with a read-back so you know each one landed.
See Full Use Case

scenario

-

Estimators invite bidders without checking whether they are set up for payment. A winning vendor then turns out to be missing from the ledger, or has no payment terms or 1099 flag, and the award waits on setup.

What popdock provides

--

Give a project and optionally a look-back period, and it reads the bidders on the Procore project, stopping if the project name fits several projects. It matches each bidding vendor to a Rillet vendor, ignoring case, punctuation and endings like Inc and LLC, and reads payment terms, the 1099 flag and the count of open bills. Vendors missing from Rillet come first. If a bidder could match two Rillet vendors it lists both and chooses neither. Nothing is changed.

Business outcome

---

Bidders missing from Rillet, or set up without payment terms, are found before award, so the winning vendor can be paid on day one.
See Full Use Case

scenario

-

Teams chase vendors for delays without knowing whether the company still owes them money. The delay log is in Procore and the bills are in Rillet, so the conversation starts without the payment picture.

What popdock provides

--

Give a project and optionally a start date, and it totals delay log duration and counts the logs for each vendor named in the Procore delay logs, with the latest date. It matches each vendor to Rillet, skipping any that match several vendors, and reads their unpaid bills, earliest due date and anything past due. The exact status values seen are reported, not assumed. You get vendors with both delay and past-due bills first, and it reports what the logs record without assigning fault. Nothing is changed.

Business outcome

---

You can see which vendors are both logging delay and waiting on payment before the call, with no blame assigned beyond what the logs record.
See Full Use Case

scenario

-

Payables staff approve bills in Rillet without checking whether the vendor's insurance recorded in Procore has expired. The lapse is found at audit, or after a claim, and not at the point of payment.

What popdock provides

--

Give a due date and a warning window, and it lists the unpaid, unvoided Rillet bills due by then and attaches each vendor's name. For each vendor it reads the insurance recorded in Procore, retrying once on a partial name and marking that match as approximate. A policy ending before the bill's due date counts as expired for that bill, and a vendor is valid only if every policy is current. You get a row per bill sorted with expired first, plus counts and vendors to chase. It never pays or edits a bill.

Business outcome

---

Bills for vendors with lapsed or expiring cover are flagged before payment, so a payment run does not release money to uninsured vendors.
See Full Use Case

scenario

-

Before bills for materials orders can be booked, someone compares the vendor names on each Procore purchase order with the Rillet vendor list by eye. A spelling difference or a missing vendor only shows up when a bill is rejected.

What popdock provides

--

Give a project, and it reads the vendors on its Procore materials purchase orders, stopping if the project name fits several projects. It matches each vendor to the Rillet vendor list, ignoring case, punctuation and endings like Inc, LLC, Ltd and Co, and keeps the account code, payment terms and email of each match. It counts each vendor's open orders. You get a row per vendor with a verdict of matched, close match or not in Rillet. If two Rillet vendors fit it lists both and chooses neither. Nothing is changed.

Business outcome

---

Vendors on materials orders that Rillet cannot match are found before bills arrive, with open order counts to show which gaps matter first.
See Full Use Case

scenario

-

Rented equipment keeps running on site while its rental vendor's invoices sit unbooked, and nobody notices until the vendor chases. The equipment register and the ledger are never compared, so accruing cost goes unseen.

What popdock provides

--

Give an optional equipment category and a billing cutoff, and it lists the rented equipment on the Procore register that has a rental vendor, skipping retired or returned items and saying how many. It matches each rental vendor to Rillet, listing both candidates when two fit, then counts the vendor's bills since the cutoff and notes the latest bill date and any overdue or unpaid ones. Vendors with units on rent but no recent bills are flagged with their units. A missing bill is a lead, not proof of an error. Nothing is changed.

Business outcome

---

Rental vendors with units on site but no recent bills are found early, so unbilled rental cost is followed up before it builds.
See Full Use Case

scenario

-

Procurement keeps trades in Procore and vendors in the ledger, and nothing links them. Checking that each trade has a payable vendor, and that nothing is overdue, is manual guesswork across two lists.

What popdock provides

--

Give an optional trade name and a look-back period, and it reads the Procore trades, then proposes Rillet vendors whose names contain the trade or an obvious stem, such as Electric for Electrical. Each trade is marked Covered, Possible or No vendor, and every match is labelled a guess because trades and vendor names share no id. It counts each proposed vendor's recent bills by status and notes any overdue unpaid ones. It never states that a vendor performs a trade. Nothing is changed.

Business outcome

---

Trades with no apparent payable vendor are listed for procurement to review, with recent and overdue bills shown, and every match labelled a proposal.
See Full Use Case

scenario

-

Payments are released in the ledger without anyone confirming the subcontractor's lien waiver in Procore. The missing paperwork is found at audit or in a dispute, long after the money has gone.

What popdock provides

--

Give a payment date and optionally a project, and it lists the bills paid in Rillet since then with vendor names. For each one it looks up lien waivers in Procore by invoice number, then any active manual payment hold. Payments are grouped as no waiver found, waiver not yet signed or received, paid during an active hold, unrelated requisition status, and clean. A bill that is not a requisition is reported as no matching requisition, and a waiver is called missing only when the lookup returned nothing. Nothing is changed.

Business outcome

---

Payments released without a lien waiver or against a hold are caught and totalled while there is still time to act.
See Full Use Case

scenario

-

Checking that won bid board work was booked in the ledger means opening each Procore bid board project, noting its proposal total, then finding the matching contract in Rillet and comparing the value. Work that was won but never booked, or booked at a different value, goes unnoticed until someone reconciles by eye.

What popdock provides

--

Name a customer and, if you like, a bid board status, and it finds that customer's bid board projects in Procore and reads their proposals. It then finds the customer in Rillet and pairs each project with the contract whose name contains the project name. You get one row per project showing the proposal total against the contract value, the difference and the contract status, plus projects with no contract and contracts with no project. It stops if the customer name is ambiguous, never converts currencies, and lists every candidate when a project matches several contracts. Nothing is changed in either system.

Business outcome

---

Won work that was never booked, or booked at a different value, shows up in one table instead of a manual comparison.
See Full Use Case

scenario

-

To tell whether billing is keeping pace with progress you pull a project's percent complete from Procore, find its contract in Rillet and add up the invoices by hand. The sums are easy to get wrong, and billing that lags or runs ahead of the work goes unnoticed.

What popdock provides

--

Name a Procore workforce planning project and, if you want, a start date for invoices, and it reads the project's stage, status and percent complete. It finds the matching Rillet contract by name, falling back to the project number, and shows both names so you can confirm the match. It totals the invoices against the contract and says whether invoicing is ahead of, behind or in line with percent complete, using a 10 point band. It stops when the project name is ambiguous or no contract matches, never converts currencies and changes nothing in either system.

Business outcome

---

You see in one answer whether billing is ahead of or behind progress, with the invoices behind the figure.
See Full Use Case

scenario

-

Checking that a vendor's bills match the days it was actually on site means reading manpower and equipment logs in Procore, then reading bills and service periods in Rillet side by side. Bills for days nobody was on site, or site days nobody billed, are easy to miss.

What popdock provides

--

Name a vendor and a project, and optionally a date range, and it builds the list of days that vendor appears in the Procore manpower and equipment logs. It finds the vendor in Rillet, reads its bills and their lines with service periods, and compares the two. You see the site dates and the bills, with flags for bills whose service period has no site days, site days no bill covers, and unpaid bills. Bills without a service period are listed separately. It stops on an ambiguous vendor, shows currency as held and never changes data.

Business outcome

---

Bills that do not match the days a vendor was on site are flagged before they are approved or paid.
See Full Use Case

scenario

-

Overdue vendor bills sit in the ledger and the project team never hears about them. Chasing means finding the bills in Rillet, working out the amounts, opening the right Procore project and typing up a task by hand.

What popdock provides

--

Name a vendor and a Procore project, and it checks that exactly one vendor and one project match before going further. It finds the vendor's unpaid bills in Rillet that are past due and totals the amounts. You then see the overdue bills with the total and the exact task it would create, with a title, a description listing expense numbers, due dates and amounts, and a due date. Nothing is created until you confirm, and only one task is created. It never retries a failed call and never touches bills or payments. The write is untested, so try it in a sandbox first.

Business outcome

---

Overdue bills reach the project team as one clear task, created only after you have seen it.
See Full Use Case

scenario

-

Materials are posted as received in Procore, but nobody lines the receipts up with vendor bills in the ledger. Without that check, accruals for delivered goods are missed and vendors end up paid late.

What popdock provides

--

Name a project and, if you like, a date, and it reads the materials receipts posted since then in Procore and finds the vendor on each receipt's purchase order. It finds each vendor in Rillet and checks for a bill dated on or after the receipt. You get one row per receipt with a verdict, billed since, no bill since, vendor not in Rillet or unresolved, and the no-bill rows grouped by vendor with the oldest posting date. A missing bill is called a lead, not proof, because bills are tied by vendor and date only. Nothing is changed in either system.

Business outcome

---

Delivered materials that have no vendor bill yet are listed by vendor, ready to review for accruals.
See Full Use Case

scenario

-

The project team deactivates a vendor in Procore, but bills from that vendor keep arriving in the ledger. Without a cross-check by tax id and name, nobody notices until after the payment has gone out.

What popdock provides

--

Give a start date, or accept the last 90 days, and it reads the vendors Procore marks inactive and the bills Rillet holds since that date. It matches Rillet vendors to the inactive ones by tax id, then by name after ignoring case, punctuation and endings such as LLC. As a check it drops any vendor that Procore also holds as an active record of the same name. You get one row per bill with the match method, grouped by vendor with counts. Name only matches are labelled possible, and it never edits vendors or bills.

Business outcome

---

Bills from deactivated vendors are caught before payment, with the match method shown for each.
See Full Use Case

scenario

-

Someone compares the customer names on the Procore bid board with the Rillet customer list by eye. Spelling differences hide customers that are missing from the ledger, and the biggest pipeline can sit under a name nobody can find.

What popdock provides

--

Optionally give a bid board status, and it reads the bid board projects in Procore and the whole Rillet customer list. It compares each customer name with the Rillet name and invoicing name, ignoring case, punctuation and endings such as Inc and LLC, and classes each as an exact match, a close match or missing. You get a table of distinct customers with project counts, pipeline totals and the Rillet customer id, with missing customers first, largest pipeline first. It never merges look-alike names, and close matches are left for you to decide.

Business outcome

---

Customers missing from Rillet are found, largest pipeline first, without merging names that only look alike.
See Full Use Case

scenario

-

To see whether a vendor has billed for what was actually delivered, you open the Procore purchase order and its receipts, then hunt through the ledger for the vendor's bills. Bills that run ahead of or behind deliveries slip through.

What popdock provides

--

Name a purchase order and, optionally, a project, and it finds that one order in Procore and reads its ordered, received and outstanding quantities and its posted receipts. It finds the vendor in Rillet, picks the bills that mention the order, or falls back to the vendor's bills since the first receipt and labels that a vendor and date link. You get the order header, receipts, bills with totals and a verdict: nothing billed yet, billed less than received, in line, or bills but no receipts. It stops if more than one order matches, does not convert currencies, and does not work out a money difference because the quantities carry no prices.

Business outcome

---

You see whether a vendor has billed less than, more than or in line with what was delivered.
See Full Use Case

scenario

-

Owners are kept as programs in Procore and as customers in the ledger, and nothing links the two. Matching them by hand to see who owes what is slow, and variants of a name are missed.

What popdock provides

--

Optionally give part of a program name and a limit, and it reads Procore programs with their addresses and project counts. It matches each program to a Rillet customer by name, ignoring case, endings such as Inc and LLC and punctuation, and marks each as matched, ambiguous or not in Rillet. For matched customers it totals overdue and other open invoice amounts, with the latest annual recurring revenue where available. Matches are labelled as proposed, ambiguous ones are listed rather than chosen, and amounts are never added across currencies. Nothing is changed in either system.

Business outcome

---

You see which programs have no ledger customer and what each matched owner owes, without merging currencies.
See Full Use Case

scenario

-

Project values in Procore and contract values in Rillet are kept in separate places and drift apart over time. Comparing them means exporting both and matching by project number or name, and projects with no contract get lost.

What popdock provides

--

Optionally give a project stage, and it reads the active projects in Procore with their numbers, stages and values. It reads the contracts in Rillet and matches each project to a contract whose name contains the project number or equals the project name. You get one row per project with both values, the difference and a verdict: matched, value differs, no contract or several contracts. It then lists contracts that match no project and ends with counts. Both values are shown without converting currency, all candidates are listed when several match, and nothing is changed.

Business outcome

---

Projects with no contract and values that have drifted are listed in one table, without converting currency.
See Full Use Case

scenario

-

Vendors appear in Procore site logs well before anyone checks whether they exist in the ledger. When their first bill arrives it has nowhere to land, and the gap is found late.

What popdock provides

--

Name a project and, optionally, a date range, and it collects every vendor named in the project's manpower, equipment, delivery and dumpster logs, noting which log types each appears in and how many rows. It reads the Rillet vendor list and compares names, ignoring case, punctuation and endings such as LLC and Inc. You get a table showing each vendor as matched, possible or missing, with the Rillet vendor id and payment terms where matched, and missing vendors first. Partial name matches are shown, never treated as confirmed. It stops if the project name is ambiguous and changes nothing.

Business outcome

---

Vendors working on site without a ledger record are found before their bills arrive.
See Full Use Case

scenario

-

Estimators keep bidding for customers who are behind on invoices, because the overdue balance lives in the ledger and not on the bid board. Warning them means checking Rillet, adding up the overdue amount and writing a note on each project by hand.

What popdock provides

--

Name a customer and, optionally, a bid board status, and it finds the customer in Rillet and totals their overdue invoices. It finds the customer's bid board projects in Procore and stops if the name covers more than one customer. You see the overdue invoices, the total, the projects and the exact note, with the customer, the overdue count, the amount due and today's date. Nothing is written until you confirm. Only a bid board note is added, project status is never changed, and a project that already has the same note from today is skipped. The write is untested, so try it in a sandbox first.

Business outcome

---

Estimators see a customer's overdue balance on the bid board before they bid, added only after you approve the note.
See Full Use Case

scenario

-

Approved requisitions are retyped into the ledger as bills. Each one needs the vendor found, the account checked and the dates worked out, and duplicate or wrong-vendor entries are the usual result.

What popdock provides

--

Give a requisition number, the project and the expense account code, and it reads that one requisition in Procore and stops unless it is approved. It checks that no bill with that invoice number already exists in Rillet, finds a single clear vendor match, and confirms the account exists and is active. You see the bill it would create, with vendor, dates, currency, amount and account, and you choose between the claimed and payment due amounts. Nothing is created until you say yes. It writes one bill, checks that exactly one exists afterwards, and never changes Procore. The write is untested, so try it in a sandbox first.

Business outcome

---

Approved requisitions become one correct bill in Rillet, with no duplicates and no retyping.
See Full Use Case

scenario

-

Before pursuing a customer, you open Procore to see their bid board pipeline and then the ledger to see what they have contracted, been invoiced and owe. Pulling it into one picture takes two systems and a spreadsheet.

What popdock provides

--

Name a customer and, optionally, a bid board status, and it reads their pipeline from the Procore bid board with project status, due date and total value. It finds the customer in Rillet and reads their contracts and invoices. You get three short sections, the pipeline with a total, the contracts with value and dates, and invoicing with the invoiced total, amount due and overdue count and amount, followed by a sentence on whether the pipeline looks like contracted or new work. It reports a customer missing from Rillet instead of guessing a match, totals each currency separately and changes nothing.

Business outcome

---

You see a customer's pipeline, contracts and overdue balance in one view before you pursue them.
See Full Use Case

scenario

-

Finance checks by hand that the construction company setup in Procore, its currency and its offices match the legal entities, currencies and bank accounts in the ledger. The two sides are named differently, so mismatches stay hidden until consolidation.

What popdock provides

--

Optionally give a Procore company, and it reads the company, its currency and its offices from Procore, then the subsidiaries and bank accounts from Rillet. It matches the company name to a Rillet subsidiary, compares currencies, lists offices in countries no subsidiary appears to cover, and lists subsidiaries with no bank account in their currency. You get a table with a status of match, currency mismatch or no subsidiary, then the uncovered offices and the questions a finance lead should ask. Every name match is labelled proposed, it stops if either side is empty, and nothing is changed in either system.

Business outcome

---

Entity, currency and bank account gaps between Procore and Rillet are listed before they surface at consolidation.
See Full Use Case

scenario

-

Owner pay applications and the receipts against them are tracked in Procore and again in Rillet. Matching them line by line takes two exports, and the two drift apart without anyone seeing it.

What popdock provides

--

Name a project and, optionally, a billing date to start from, and it reads the prime contract pay applications and the payments received from Procore. It matches each to a Rillet invoice by invoice number, falling back to purchase order number, and totals the payments recorded against each invoice. You get one row per pay application with a verdict: matched, amount differs, not invoiced in Rillet, paid in Procore but not in Rillet, or paid in Rillet but not in Procore, with the total of each gap. Draft pay applications are listed separately, duplicate invoice numbers are listed instead of chosen, and nothing is changed.

Business outcome

---

Gaps between owner billings in Procore and receivables in Rillet are totalled by type instead of hunted line by line.
See Full Use Case

scenario

-

Accountants compare Procore subcontractor requisitions with Rillet bills line by line in spreadsheets. Unposted or mis-keyed invoices slip through and only show up at month end.

What popdock provides

--

Name a project and, optionally, a billing date to start from, and it reads the project's requisitions from Procore, ignoring drafts and voids and saying how many it ignored. It finds each requisition's bill in Rillet by invoice number, ignoring case, spaces and leading zeros, totals the bill lines and checks the vendor. You get one row per requisition with a verdict of matched, amount differs, vendor differs or not in Rillet, then Rillet bills with no requisition, counts per verdict and the total value of the gaps. Requisitions with no invoice number are listed rather than guessed, duplicate bills are listed, and nothing is changed.

Business outcome

---

Unposted and mis-keyed subcontractor invoices are found well before month end, with the gap valued.
See Full Use Case

scenario

-

Payments issued to subcontractors in Procore are checked against the ledger by hand. Payments that were never posted, or were posted for a different amount or date, go unnoticed.

What popdock provides

--

Name a project and, optionally, a payment date to start from, and it reads the commitment payments from Procore. It matches each to a Rillet bill payment by invoice number, comparing the funded date where there is one, and for unmatched payments checks whether the bill exists but is unpaid or does not exist at all. You get one row per payment with a verdict of matched, amount differs, date differs, bill unpaid in Rillet or no bill in Rillet, then Rillet payments with no Procore payment and the total value of the gaps. Date gaps of up to 3 days are warnings, both amounts are shown when currencies differ, and nothing is recorded.

Business outcome

---

Payments missing or different between Procore and Rillet are listed with their value, instead of found by sampling.
See Full Use Case

scenario

-

Someone compares the Procore vendor directory with the Rillet vendor list by eye. Near-identical names slip through as duplicates or gaps, and details such as email or city drift apart.

What popdock provides

--

Optionally give part of a vendor name, and it reads the active vendors in Procore and the vendors in Rillet. It matches each Procore vendor to a Rillet vendor by tax id, then email, then name after ignoring case, punctuation and endings such as LLC, and records which rule matched. You get three lists, Procore only, Rillet only, and matched with differences in email, city or state, followed by counts and the matches it considers uncertain. Name only matches are possible, not confirmed, ambiguous cases are listed instead of chosen, and nothing is created or updated.

Business outcome

---

Vendors present in only one system, or recorded differently in each, are listed with how confident each match is.
See Full Use Case

scenario

-

Payments released in Procore are keyed again against the bill in Rillet. Along the way they are sometimes missed, entered twice or applied for more than the bill is owed.

What popdock provides

--

Give an invoice number, the project and the paying account code, and it reads that one commitment payment in Procore and stops if it has not been issued or funded. It checks that the bill exists in Rillet, compares the amount and date with any payment already recorded, and confirms the account is a bank or cash account. You see the payment it would record, with bill, vendor, amount, date, currency, account and the balance still outstanding. Nothing is recorded until you say yes. It stops on an overpayment, records one payment, checks that it appears once, and never changes Procore. The write is untested, so try it in a sandbox first.

Business outcome

---

Procore payments reach the Rillet bill once, for the right amount, with no double entry or overpayment.
See Full Use Case

scenario

-

Following up on overdue observations without knowing the vendor's billing and payment position makes the conversation blind. The observations are in Procore and the bills and payments are in Rillet, so the picture is rarely assembled before the call.

What popdock provides

--

Name a project and, optionally, how many days back to look, and it finds the observations in Procore that are past due and not closed, grouped by assigned vendor with the count and the oldest due date. It finds each vendor in Rillet and reads its bills and payments for the period. You get one line per vendor with overdue observations, bills in the period, unpaid bills and total paid, sorted by overdue count, with a closing line naming vendors that have no Rillet record. A vendor with no bills is reported as zero. It sends no observation emails, pays nothing and never recommends a payment hold.

Business outcome

---

Follow-up on overdue observations starts with the vendor's billing and payment position already in front of you.
See Full Use Case

scenario

-

Vendors with open safety violations keep getting paid because nobody connects the site record to the payables list. Finding them means reading the safety logs in Procore, then checking each vendor's unpaid bills in Rillet.

What popdock provides

--

Name a project and, optionally, a note date, and it finds the vendors with open safety violation logs in Procore and checks Rillet for their unpaid bills. You see a table of vendor, violation subjects, compliance due dates, unpaid bill count and total, and the earliest due date. Nothing is written until you name the vendors to log. For each vendor you confirm it adds one payment review note to the Procore notes log, then reads the notes back to confirm each exists. Vendors with no Procore id are skipped, and Rillet bills are never changed or paid. The write is untested, so try it in a sandbox first.

Business outcome

---

Vendors with open safety violations and unpaid bills are surfaced, with a payment review note logged only for those you confirm.
See Full Use Case

scenario

-

Following one subcontract from contract value to billed, paid and booked takes several screens in two systems. Change orders, requisitions, payments, bills and ledger payments each live somewhere different, so the gap is hard to pin down.

What popdock provides

--

Give a commitment number and a project, and it finds that one purchase order or work order in Procore and reads its original and revised value, amount invoiced, payments issued and balance, with its change orders for context. It collects the invoices and payments for the commitment, then looks each invoice up as a bill and bill payment in Rillet and adds up the Rillet billed and paid amounts. You get four lines for contract value, billed, paid and balance, a table by invoice showing where each appears or is absent, and a sentence on where the gap sits. It stops on an ambiguous or missing commitment, notes unposted invoices without guessing why, and changes nothing.

Business outcome

---

You see exactly where a commitment's contract, billing and payments stop agreeing across Procore and Rillet.
See Full Use Case

scenario

-

Tying a Procore project to its invoices and bills in the ledger means copying the accounting number between systems and searching by hand. References recorded in free text, such as a memo or purchase order field, are easy to miss.

What popdock provides

--

Give a Procore project number and, optionally, a date to search bills from, and it reads the project's name, number and accounting project number. It searches Rillet invoices for that number in the memo, purchase order and invoice number fields, and Rillet bills by expense number, with a wider search if the first finds nothing. You get the project identity and two lists, invoices and bills, with the field that matched for every row. It stops if the project or its accounting number is missing, labels substring matches as proposed, reports only what is returned without inferring cost or margin, and changes nothing.

Business outcome

---

Ledger invoices and bills that reference a project are found in one search, with the match field shown for each.
See Full Use Case

scenario

-

A project manager asking what a vendor has been paid has to look in Procore for the vendor record and insurance, then in Rillet for the bills, payments and charges. The two pictures are never put side by side.

What popdock provides

--

Name a vendor and, optionally, a start date, and it finds that one vendor in Procore with its insurance policies. It finds the vendor in Rillet by tax id, then email, then name, and reads its bills, payments and charges since the start date. You get the Procore profile with status and insurance dates, bill count and total with unpaid, payment count and total with the last date, charge count and an outstanding balance, and it flags bills dated while the vendor was inactive or its insurance had expired. It stops on ambiguous matches, reports absence rather than zero, shows amounts per currency and never writes to either system.

Business outcome

---

A vendor's record, insurance and everything billed and paid in Rillet sit in one answer, with risky dates flagged.
See Full Use Case
No items found.

ready, go

Tools for Procore

Start with ready-made MCP tools for the Procore. Each one gives your AI client a single, clearly defined job: get invoices or journal entries, pull a file, or create and update records. Add a tool to your PopdockAI MCP server, choose the fields it returns and who can use it, and it's ready in Claude, ChatGPT or Microsoft Copilot. Nothing is exposed that you haven't switched on.

Tool Types

Name of tool
Description
run-action
procore-update-quantity-on-a-direct-issue-line-item-location
Update quantity on a direct issue line item location in Procore, under issuing line items (PATCH). This is a write tool: it is built Inactive and has not been run end to end through MCP, so test it in a Procore sandbox before switching it on.
run-action
procore-update-quantity-log
Update quantity log in Procore, under quantity logs (PATCH). This is a write tool: it is built Inactive and has not been run end to end through MCP, so test it in a Procore sandbox before switching it on.
run-action
procore-update-purchase-order-line-item
Update purchase order line item in Procore, under purchase order line items (PATCH). This is a write tool: it is built Inactive and has not been run end to end through MCP, so test it in a Procore sandbox before switching it on.
run-action
procore-update-purchase-order-contract-subcontractor-sov-status
Update purchase order contract subcontractor SOV status in Procore, under purchase order contracts (PATCH). Update Purchase Order Contract Subcontractor SOV status. Writes to live Procore data. It is built Inactive and has not been run end to end through MCP, so test it in a sandbox before switching it on.
run-action
procore-update-purchase-order-contract-line-item
Update purchase order contract line item in Procore, under purchase order contract line items (PATCH). Update Purchase Order Contract Line Item. Writes to live Procore data. It is built Inactive and has not been run end to end through MCP, so test it in a sandbox before switching it on.
run-action
procore-update-purchase-order-contract-detail-line-item
Update purchase order contract detail line item in Procore, under purchase order contract detail line items (PATCH). Update Purchase Order Contract detail line item. Writes to live Procore data. It is built Inactive and has not been run end to end through MCP, so test it in a sandbox before switching it on.
run-action
procore-update-purchase-order-contract
Update purchase order contract in Procore, under purchase order contracts (PATCH). Update Purchase Order Contract. Writes to live Procore data. It is built Inactive and has not been run end to end through MCP, so test it in a sandbox before switching it on.
run-action
procore-update-purchase-order-compliance-document
Update purchase order compliance document in Procore, under purchase order compliance documents (PATCH). Update a compliance document.. Writes to live Procore data. It is built Inactive and has not been run end to end through MCP, so test it in a sandbox before switching it on.

Ready to unlock your data?

‍

Start building tools that turn your business systems into AI superpowers

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation