SamhitaOffice Local Help

Start Here: What This Help Is For

SamhitaOffice help is written for officers, assistants, accounts staff, section clerks, technical teams, and administrators who work inside controlled desktop environments. The purpose is not to teach generic computer theory; the purpose is to make day-to-day official work more reliable, more reviewable, and easier to preserve as a record.

The help pages assume that the workstation may be operated without internet access and that documents may be handled under departmental rules. Use the instructions together with office orders, file movement practices, record retention instructions, security circulars, and any local standard operating procedure issued by the organisation.

SamhitaOffice is organised around the real work of an office: drafting, calculating, briefing, preserving, and handing over records without depending on cloud services.

Draft

Prepare notes, letters, minutes, circulars, statements, enclosures, and official write-ups in SamhitaPatra.

Calculate

Maintain registers, budget sheets, payment trackers, reconciliation statements, and data summaries in SamhitaHisab.

Brief

Build review decks, committee presentations, status briefings, and decision slides in SamhitaPradarshan.

Preserve

Open, review, print, and verify PDF records in SamhitaPDF after export or receipt from approved sources.

Module Map

Each SamhitaOffice module has a specific institutional role. Use the right module for the stage of work. Drafting should normally begin in the document editor, calculations should remain in spreadsheets until finalisation, presentations should be used for briefings rather than long records, and PDFs should be used for controlled sharing, viewing, and preservation after verification.

SamhitaPatra

For file notes, approval notes, administrative approvals, office memoranda, letters, annexures, minutes, agenda papers, and final textual records.

SamhitaHisab

For tables, registers, calculations, reconciliations, expenditure tracking, stock or asset records, grant utilisation sheets, and print-ready schedules.

SamhitaPradarshan

For concise briefings, review meetings, committee summaries, project status presentations, scheme dashboards, and officer-level decision decks.

SamhitaPDF

For opening final PDFs, checking exported records, preserving read-only copies, printing controlled documents, and verifying page layout before circulation.

Situation	Recommended module	Reason
Drafting a sanction note or agenda note	SamhitaPatra	The work is narrative, paragraph-based, and likely to require headings, tables, enclosures, and final PDF export.
Preparing a budget utilisation statement	SamhitaHisab	The work depends on rows, columns, formulas, totals, filters, and print area management.
Briefing a committee on progress	SamhitaPradarshan	The work needs visual structure, agenda slides, key decisions, and controlled summary points.
Checking a final signed copy	SamhitaPDF	The work is about viewing, verifying, printing, and preserving a final-format record.

Air-Gapped Working Model

In an air-gapped or restricted environment, the most important rule is predictability. A document should open from an approved location, save to an approved location, and be shared only through authorised channels. Help content is stored locally so that a user can work even when the machine has no internet connectivity.

Do not treat the absence of internet as a limitation. For government and institutional buyers, local operation can be a strength when the workflow requires sovereignty over files, predictable record handling, and reduced exposure to external services. The discipline is simple: work locally, save consciously, export deliberately, and verify the final record before release.

Operational principleKeep working files, final PDFs, scanned enclosures, and supporting spreadsheets in a predictable folder structure approved by the department. Avoid desktop clutter for important files.

Use local folders with write permission.
Avoid saving official records into temporary download folders.
Do not rely on web links for help, templates, or images.
Use approved removable media only when permitted.
Preserve the editable source file along with the final PDF wherever the office record requires it.

Daily File Discipline

A large part of office productivity is not typing speed; it is file discipline. A clear file name, a traceable draft history, and a verified final copy reduce confusion during review, audit, handover, and inspection. SamhitaOffice cannot replace departmental judgement, but it can support disciplined work when users follow consistent rules.

Practice	Recommended approach	Why it matters
File naming	Use subject, section, date, and status where practical, for example: Budget_Utilisation_HealthSection_2026-05-21_Draft.docx	Users can identify the latest record without opening multiple files.
Draft control	Use Draft, Review, Approved, or Final in names when the department allows this convention.	Reviewers know whether a file is still editable or ready for circulation.
Folder structure	Keep source files, exported PDFs, annexures, and supporting data together.	Record reconstruction becomes easier during audit or handover.
PDF verification	Open exported PDFs and check page count, margins, tables, signatures, and attachments before sharing.	Many final record errors are discovered only after export if not checked carefully.

Avoid silent overwritingWhen in doubt, use Save As and create a new copy. Silent replacement of an earlier file can remove important review history.

Common Government Workflows

The following workflows are written for practical office use. They are not rules by themselves; they are safe operating patterns that can be adapted to local instructions.

Office note: Start in SamhitaPatra, write subject, background, issue, proposal, financial implication if any, approval paragraph, and enclosure list; then export to PDF after review.

Expenditure statement: Start in SamhitaHisab, enter bill details, head of account, amount, tax, payment mode, and approval reference; verify totals; then export a print-ready statement.

Review meeting: Start in SamhitaPradarshan, create agenda, progress, issues, decisions required, and next action slides; keep the text brief and use SamhitaHisab exports for data-heavy tables.

Final record: Open the exported PDF in SamhitaPDF, check all pages, confirm readability, print if required, and preserve the source file with the final PDF.

Templates and Local Institutional Material

Your administrator may provide local templates for notes, letters, agenda papers, registers, presentations, and PDF-ready forms. Templates should be stored locally and should not depend on internet services. A good template contains structure without forcing the user to keep irrelevant sample text.

When using templates, replace all placeholders, check date formats, verify office names, and remove unused sections. Never submit a template that still contains instructional text such as “insert subject here” or “sample amount”. A template is a starting point; it is not a substitute for review.

Keep templates in a controlled folder.
Do not edit the master template casually; create a working copy.
Review margins, headers, and footers before printing.
Confirm that logos, if used, are authorised by the organisation.
Do not import unverified templates from unapproved media.

Printing, PDF Export, and Final Review

Printing and PDF export are finalisation steps. They should not be treated as mechanical actions. Before print or export, review page size, margins, page breaks, table wrapping, missing fonts, image placement, and file naming. After export, open the PDF and verify it independently.

Before finalisation	Check
Document	Headings, paragraph numbering, signature block, enclosures, page numbers, and final approval paragraph.
Spreadsheet	Formula ranges, totals, filters, hidden rows, print area, scaling, and page orientation.
Presentation	Slide order, readability, embedded images, speaker notes if any, and exported PDF view.
PDF	Page count, orientation, searchable text if expected, scanned-page clarity, and print behaviour.

Troubleshooting

Most local help problems are caused by missing files, restricted folders, moved assets, or documents opened from locations where the user does not have write permission. The first diagnostic step is to test with a simple file name in a simple local folder such as an approved Documents subfolder.

Symptom	Likely cause	Safe response
Help page opens but images do not show	The assets folder was not copied with the HTML files.	Copy the full help folder including the assets directory.
File will not save	Folder is read-only, file is open elsewhere, or user lacks permission.	Use Save As into an approved writable folder and close duplicate copies.
PDF export layout is wrong	Margins, page breaks, print area, fonts, or images need review.	Return to the source document, adjust layout, export again, and reopen the PDF.
Old help text still appears	Application may be loading help from another installed location.	Confirm the deployed help folder path and replace the correct files.

How Departments Should Use This Help Pack

This help pack is intended to be read as a working manual rather than a marketing page. An administration branch can use it during onboarding, an accounts branch can use it to train spreadsheet discipline, and an IT cell can use it to explain why the local help folder must be deployed with its assets. The pages deliberately avoid external references so that a user in a restricted network can still understand the correct workflow.

A practical rollout can begin with a short orientation: open the home page, explain the four modules, show where official documents should be saved, demonstrate export to PDF, and then ask users to verify the PDF before closing the task. This turns help from a passive page into a standard operating habit.

Office role	Most useful help section	Training focus
Dealing assistant or clerk	SamhitaPatra and SamhitaPDF	Drafting, file naming, enclosures, and final PDF checking.
Accounts staff	SamhitaHisab and SamhitaPDF	Registers, formulas, totals, print area, and PDF verification.
Section officer or reviewer	All module checklists	Review discipline, decision clarity, and safe finalisation.
IT or administration cell	Home page and troubleshooting	Deployment of help files, assets folder, and local support process.

Deployment noteCopy the complete folder. If only the HTML files are copied and the assets directory is missed, the visual identity will not load correctly.

Recommended Local Folder Discipline

The application cannot create institutional order by itself; users and administrators must agree where records are stored. A simple departmental structure may include folders for Drafts, Review, Final_PDF, Annexures, Registers, Presentations, and Archive. The exact names can change, but the principle should remain: source files and final PDFs should be easy to locate and should not be scattered across desktop, download folders, or random removable media.

For high-value records, the folder itself should tell a story. A note, its calculation sheet, its annexures, and the final PDF should sit close together. This makes audit response, handover, and future reference easier. It also reduces the common problem of sending a PDF whose source workbook or editable note is later impossible to find.

Create a subject folder. Use a clear subject and date or file reference where permitted by local practice.

Keep source files together. Store document, spreadsheet, presentation, and annexures in one controlled location.

Export final PDFs into a final folder. Do not mix scratch files with issued copies.

Review before handover. Make sure the folder contains the final PDF and the source material needed to explain it.

Offline Support Request

When troubleshooting does not resolve an issue in SamhitaOffice, create an offline help request instead of sending an unstructured message. The support form records officer details, affected module, issue facing, priority level, reproduction steps, document context, and workstation reference in a structured JSON file. The file can then be mailed or submitted to SamhitaOffice support through the organisation’s approved support channel.

What to include

Officer name, designation, department, affected module, issue summary, steps taken, expected result, actual result, priority, and safe file context.

What not to include

Do not paste confidential document contents, restricted records, personal data, passwords, activation material, or sensitive file attachments unless authorised.

Priority discipline

Use High for blocked official work, Medium for workflow issues with workaround, and Low for training questions, small layout issues, or suggestions.

Create a structured ticketOpen the offline support request form, generate the JSON help file, save it locally, and attach it to the official support email or submit it through the approved IT/support process.

Open Offline Support Request Form