Construction work can lose momentum when the site walk lives on a phone, the rough sketch is in a notebook, and the scope starts somewhere else. This sanitized RestCore™ workflow demo follows a reconstruction project from the property walk through the next office step. It keeps walkthrough details, photos, documents, and project communication in one connected record. From there, the team asks Tony for the next draft, reviews location-relevant sources when a question comes up, and keeps the estimate and the invoice with the job. The video is a quick view of the screens. This article explains the handoff: field capture becomes more useful when the office can open the same project, see the supporting context, and move the next action forward.
This is a sanitized RestCore™ demo job. Names, addresses, claim numbers, and payment details belong to a fictional demo company. It shows how one connected job can be organized; it is not a customer case study, professional advice, or a promise of any outcome.
Scenario: a reconstruction project starts at the property
The demo opens on a reconstruction job for a ground-floor unit in a multi-unit building run by a property management company. A failed condensate pump in an HVAC closet caused a water loss. The mitigation is done; now the unit has to be put back together, from the HVAC air handler reinstall to insulation, drywall, baseboard, paint, and final cleanup. The immediate need is to keep the site record, the project documents, and the next office step together without rebuilding the story from separate notes and attachments.
The project uses the Reconstruction workflow alongside the shared job workspace. It does not replace professional design, engineering, permitting, inspection, or trade judgment. It keeps the project record and its next action together for the people responsible for the work.
1. Start the project record before the details scatter
The video first opens the project job hub: walkthroughs, documents, reports, RestCore™ Sketch, mitigation, contents, the estimate, invoices, and photos, all on one job. That gives the site walk a home before a photo, note, or follow-up request travels through a separate text thread or inbox.
The job record keeps the property context beside appointments and project history. A project manager, estimator, or coordinator can see which visit produced a note and where the follow-up belongs. It is the shared starting point for the next decision.
2. Capture the site story with a walkthrough, photos, and sketch
At the property, the team records the walkthrough, photos, measurements or a sketch, and the notes needed to understand the work. In the video, the photo record shows the unit after demolition: the opened ceiling, the exposed framing, and the areas that need to be rebuilt.
Those details stay attached to the job instead of becoming an unlabelled photo folder. When the scope needs review, the team can return to the site record and its context. The demo documents observations; it does not make a design, code, or construction determination.
3. Put tasks, documents, appointments, messages, and activity on one job
A site walk is only the opening handoff. On this job the Documents screen holds a full Scope of Work and a separate Mitigation Scope of Work, a Certificate of Completion report, a moisture mapping walkthrough, and dated daily journals from each visit. Tasks, appointments, job messages, and activity stay on the same project.
When the field team leaves, a task can point to the next item, a document can stay with the site evidence, and a revision message can stay with its related photos and notes. The team still decides the work and manages the project; RestCore™ keeps the working context accessible.
4. Ask Tony to prepare the next draft from the project context
Once the site record is organized, the technician asks Tony for the next document. In the video it is a work completion report based on the details and photos on the job. Tony pulls up the photos first, writes the report from what is already there, and saves it to the Scope tab under Work Completion, where the team can edit it and export a branded PDF. The same request works for a Scope of Work or a job summary.
The report follows the job in order: the source of the loss, the emergency mitigation, the testing before demolition, the HVAC removal and reinstall, the reconstruction, and the final cleanup. The draft is a starting point for review, not a final construction direction. The project team checks it against the actual work and makes the decisions that require its experience.
5. Research sources by location, then verify what applies
A project can raise a code or standards question after the site walk. Tony can help research and cite relevant sources for the project location, keeping the research with the job rather than as an unexplained browser search.
That research does not determine compliance or approve a project. Contractors must verify the current locally adopted code, amendments, permits, inspection requirements, and applicable professional requirements before acting. Tony is research assistance, not a code official or a substitute for a licensed professional. The local authority having jurisdiction and qualified professionals determine what applies.
6. Keep the scope, estimate, customer documents, and invoice connected
The final sequence moves from the scope to the estimate and the invoices. The rebuild estimate on this job is a line-item version: the HVAC air handler reinstall labor, drywall hung, taped, and floated for the living room walls, the HVAC closet, and the hallway, R-19 insulation, custom cut baseboard, seal and prime, and two coats of paint. The mitigation estimate sits next to it, and RestCore™ Books carries one invoice for the mitigation and one for the reconstruction, with the outstanding balance on the job.
Projects do not always move in a straight line. A document may need revision, the scope may change, or the office may need more field detail. A connected record helps the team see those changes in context and identify the next action without reconstructing the history.
Tony prepares; your team confirms
Tony works inside the job context, not outside the team's control. Before Tony creates or changes a record, he shows what he is about to do and your team confirms it. A drafted document like this completion report lands as an editable draft on the job, and nothing goes to a customer, a property manager, or a carrier until your team reviews it and sends it.
Payments go to the contractor's own account. The activity record helps show what happened and what still needs follow-through.
What the office receives after the site walk
The office does not need a second telling of the property visit. In the web portal, the team opens the same job used on iPhone or iPad and reviews the walkthrough, photos, documents, tasks, messages, activity, and next action.
That shared view is the handoff value. An estimator starts from the site record rather than chasing attachments. A coordinator sees context while preparing a customer document or scheduling follow-up. An owner can see what needs attention without asking the field team to recreate the visit. Everyone sees one project record, while the responsible people still make the decisions.
Frequently asked questions
- Is this a real construction customer project?
- No. It is a sanitized demo job in a fictional company. The screens are the real RestCore™ product; the property, the people, and the invoices are not real. It is not a customer case study, testimonial, or representation of a project outcome.
- Can a site walk include a sketch and measurements?
- Yes. The job carries walkthroughs, photos, and RestCore™ Sketch alongside your notes and measurements. Your team reviews that information and decides how to use it for the project.
- Can Tony create the Scope of Work automatically?
- Tony can prepare a draft, like a Scope of Work or a completion report, from the job context. It stays an editable draft on the job, and your team reviews it before it goes anywhere.
- Can RestCore™ tell us which code or permit requirements apply?
- Tony can help research and cite relevant sources for the project location. Your team must verify the current locally adopted code, amendments, permits, inspection requirements, and applicable professional requirements before acting. Tony is not a code official or a substitute for a licensed professional.
- Can one job hold both the mitigation and the rebuild?
- Yes. The mitigation scope and estimate, the reconstruction scope and estimate, and separate invoices for each can all live on the same job.
Video transcript
A construction project gets harder to manage when the site walk, photos, scope, documents, and invoice live in different places. Start at the property. Capture the walkthrough, photos, measurements or sketch, and the notes your team needs to understand the work. Keep the supporting documents, tasks, appointments, messages, and activity on the same job, so the office and field have one project record. Ask me to prepare the next draft from the site record. I show you what I am about to create, and you review and confirm it before it is saved. For a code or standards question, I can research and cite relevant sources for the project location. Your team verifies the current local requirements. Keep the scope, estimate, signed documents, invoice, and project evidence connected from the first site walk to the next financial step. Use iPhone and iPad at the property, then open the same project in the web portal for office coordination and visibility. RestCore™ helps construction teams keep the work, paperwork, and next action connected. I'm Tony, and I ask before I act.
See the whole job, start to finish.
Watch Tony walk a complete job in RestCore™, then pick the plan that fits your team.