Construction site reporting, from field source to PM review

Know what happened on site without waiting for the evening update.

Rangka organises what the site team reports through Telegram into one project day, shows what is still unclear, and keeps the source available when the PM needs to check it.

See the worked example
  • Telegram reporting is available today
  • Prepared information needs PM review
Field update · Block B / Level 3Needs PM review
What the site reported

“Slab reinforcement is about 70% complete. The M&E sleeve check is still pending.”

Voice note + 2 site photos
Prepared for review
Activity
Slab reinforcement
Reported progress
About 70%
Open item
M&E sleeve check
The location, progress and open item are ready to check against the original update.

The daily problem

More messages do not create shared visibility.

When progress, photographs and the reason for a delay arrive at different times, the PM still has to reconstruct the story. The record should assemble around the work—not around the order somebody opens the chat.

Progress arrives in a voice note

Keep the audio source beside a prepared transcript when transcription is available.

Photos arrive without the explanation

Connect the images to the same reported activity and project date.

A question is still unanswered

Keep the missing detail visible instead of filling it with an assumption.

A different worked project example

One update, assembled as it arrives.

This illustrative Grid B2 record uses the same source set as the homepage Site Pulse.

  1. Telegram message

    Six of eight pipe supports installed; two await anchor bolts.

  2. Voice note

    Original audio retained with a prepared transcript.

  3. Site photographs

    Two images connected to the reported location and work.

How the workflow works

Move from chat history to a project day.

Rangka groups related submissions, prepares supported fields, and sends the interpretation to the PM—not straight into the official record.

  1. 1

    Connect the project group

    Link one Telegram group to the project and assign the people who report from site.

  2. 2

    Let the site report normally

    Text, voice notes, photographs, documents, and videos enter the chronological source record.

  3. 3

    Review what needs attention

    The PM checks the source, corrects the prepared update, and decides the next project action.

Where human judgement remains

The record is only as complete as the reporting.

Rangka cannot know about an event that was never reported. It helps the PM see submitted work and gaps sooner; it does not replace field verification or professional judgment.

Continue from here

Use the guide or working tool beside this workflow.

Questions before you start

Clear answers about this workflow.

Does the supervisor need the web app?

No. Normal field reporting continues through the linked Telegram group.

Can we find an older update?

Yes, when the source was reported and retained in the project record.

What if the interpretation is wrong?

The PM can correct, exclude, reject, or request clarification before approval.

Start with your first active project.

Create a free Rangka workspace.

Your PM stays responsible for every approved record.