Keep placed-in-service dates straight by component
When a KBKG study is completed, WebRun reads the placed-in-service date for every reclassified building component, builds a clean register in Google Sheets grouped by property and recovery period, and adds the key depreciation-start milestones to Google Calendar so nothing is lost between studies.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track placed-in-service dates for each building component in a study?
When a KBKG study is completed, WebRun reads the placed-in-service date for every reclassified building component, builds a clean register in Google Sheets grouped by property and recovery period, and adds depreciation-start milestones to your internal Google Calendar, so each component's timeline stays accurate across every study.
- Every component's placed-in-service date lives in one register, not buried in a study
- Depreciation starts land on the calendar, so none are overlooked
- Short-life components are ready to track for future dispositions
Built for cost segregation firms · CPA firms · tax preparers · real estate accounting teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
kbkg.comin a real browser with your saved login - no setup, no API keys. -
1
KBKG - read per-component dates
kbkg.com How to Automate KBKG
WebRun opens KBKG to read per-component placed-in-service dates. - Open the completed study in KBKG
- Read the placed-in-service date for each reclassified component
- Note the recovery period and cost basis tied to each date
Done when Every component has its placed-in-service date read from the study.
-
2
Google Sheets - build the register
google.com How to Automate Google Sheets
WebRun opens Google Sheets to build the placed-in-service register. - Open the placed-in-service register in Google Sheets
- Add one row per component with its property, date, recovery period, and basis
- Group rows by property and recovery-period bucket so the schedule is easy to read
Done when The register lists every component with its placed-in-service date.
-
3
Google Calendar - add depreciation milestones
calendar.google.com How to Automate Google Calendar
WebRun opens Google Calendar to add depreciation milestones. - Open Google Calendar for the tax team
- Add a milestone for each depreciation start and any short-life component recovery end
- Title each event with the property and component so it is clear at a glance
Done when Depreciation-start milestones are on the calendar for each component.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change anything in the tax return?
No. WebRun only reads placed-in-service dates from KBKG and records them. It builds a register and calendar reminders, and never files, elects, or amends anything. The output is a reference for your team.
Why track placed-in-service dates by component?
Because a cost segregation study splits a building into components with different recovery periods, each with its own depreciation start. A per-component register keeps those dates straight so schedules and any later dispositions stay accurate.
Are the calendar events visible to clients?
No. The milestones go on your internal tax team calendar only. They are reminders for the firm, not client-facing events, so nothing is shared outside the team.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.