ReBOS puts the admin, the builder, the site supervisor and the homeowner on one timeline — with planned dates set against actual dates, checklists that lock until the previous stage is done, and site photos attached to every activity.
Role-based dashboards
Everyone signs in to the same project and sees only what their role needs — no chasing updates on WhatsApp, no separate spreadsheets.
The checklist engine
Every activity moves through three locked stages. That order is what makes the dates on the timeline trustworthy.
Prerequisites the site needs before work can begin: materials, clearances, readiness checks.
Actual start date is stamped on the first tick.
Execution-level tasks, tracked as they are done. Remarks and site photographs attach here.
Locked until Before is complete.
Completion checks that validate the work, plus reports and documents for the record.
Locked until During is complete.
Photos, reports and documents stay linked to the activity they belong to.
Actual end date is filled automatically the moment work is sent for review.
Delay days and the reason behind them are recorded, not argued about later.
Automatic triggers
Finishing one activity is what sets the next thing in motion — so material and money never become the reason a build stalls.
Admin links a trigger activity to a target activity and lists what that target will consume.
Payment milestones are attached to activities, so a payment only becomes due once the work behind it is done.
Common questions
ReBOS is RECONPRO’s web application for managing home construction projects. It puts the admin, the builder, the site supervisor and the homeowner on one project timeline, so every role works from the same dates, the same checklists and the same site photographs instead of chasing updates separately.
Every activity in ReBOS carries a planned start and end date alongside an actual start and end date, and ReBOS calculates the difference in days. That means each activity reads as early, on time or delayed. When work slips, the site supervisor records the number of delay days and the reason for them against that activity, so the history is on record rather than argued about later.
No. Each activity moves through three locked stages — Before, During and After. During stays locked until Before is complete, and After stays locked until During is complete. That enforced order is what makes the dates on the timeline trustworthy, because work cannot be recorded out of sequence.
An admin links a trigger activity to a target activity and lists the materials that target activity will consume. When the trigger activity is marked complete, the builder is automatically shown the material list for the target activity, and that prompt stays up until the materials are marked purchased — so material arrives before it is needed.
Payment milestones in ReBOS are attached to specific activities, so a payment only becomes due once the work behind it is actually done. When the linked activity completes, the client is shown the milestone that has fallen due, and the reminder follows them across the app until it is paid. Nothing appears out of nowhere.
Everyone signs in to the same project but sees only what their role needs. The admin creates clients, builders and projects and signs off submitted work; the builder runs execution and assigns supervisors; the supervisor records work on site through locked checklists with photo evidence; and the client watches progress, payments and procurement from their own dashboard.
